Blackmagic Forum

Hello, I'm having trouble with Resolve consistently crashing in Windows 10, and I'm hoping that someone here might have an answer for me. Every time I go into a coloring session, I can last about 30 minutes before Resolve will freeze with the loading wheel, and then it will exit itself out. I'll open the project back up, get about another 5 or 10 minutes in, and then Resolve will quite itself again.

The project that I first noticed it with is only working with 1080p C-Log2 footage from the C300 so I wouldn't have imagined the footage to be intensive on my system (system specs are in my signature). If anyone has any tips / tricks / suggestions, that would be much appreciated, thanks!

Have you resolved this yet? (that wasn't intended as a pun..)

I've been running into the same thing, but just lately, when I first installed 14 it seemed to be ok - but now as soon as I navigate to media folders or try and open an existing project I get a windows out of memory error and it closes Resolve. I occasionally got the same windows errors before too but I'd choose ignore and be able to continue working.

I'm wondering if this is as much a windows issue as it is a Resolve issue - I just had an instance where it also shut down Chrome when the memory error popped up.

I have 16GB RAM and there's always around 7GB showing free when this error pops up. I am wondering if recent updates to windows 10 have had an effect.

ps. I just installed 14.1 and the same thing keeps happening.

Similar results here running windows 10 with 16GB and NVIDIA GTX1070. I tried 14 and 14.0.1 and the latter seemed to be worse for me. Haven't tried 14.1 yet as I was waiting to see what others report. Sometimes I'll get the windows memory dialog before the crash, sometimes not. I've been generally shutting down all other apps while running resolve. Also, windows is generally showing around 50% memory free when this occurs. I sent some of the crash logs that occurred during render to BMD support as it was happening very frequently while trying to render. I did find that rendering with a DNXHR codec seemed to crash less frequently than using an H.264 codec but I'm still getting lots of crashes at various times.

I was trying to find an article I read recently about the memory errors in W10 having something to do with heap dumps or something like that, and on a whim thought I'd go check the virtual memory (paging file) settings. It was set to be system managed, and showing a size of about 1.6GB.

I changed it to custom size, with a low end of 3GB and high of 6GB, started up Resolve again and so far so good as far as crashes go. I still get the stuttering in preview/editing mode, even when I generate optimized media - so I don't know what's going on there..

But I edited and rendered a video no problems or crashes, and Resolve has been left running while I've done a bunch of other stuff - still no memory errors.

Not sure if this is same as your situation or not, but you may want to just try changing paging file size.

Guys, please review
viewtopic.php?f=21&t=54509

Thanks Peter - will do

@Glen, really appreciate the suggestion on page file settings. Since I'm using an SSD, I had disabled paging for wear leveling reasons. As your system has the same amount of memory as mine, I just used the settings you suggested. After 2 days of editing and 1 render (with an H.264 codec), I haven't experienced a single crash. Since I always had close to 50% free memory when I checked while running Resolve, I thought the issue was elsewhere. It may still be a bit early to declare victory but ordinarily I would have seen several crashes by now so I think that was the culprit. 3 - 6 GB of page swap isn't much but it made a major difference for me.

Thanks!
Jeff H.

Glad it worked for you Jeff. Did you put your pagefile on your SSD or on a spinning disk? I put mine on my SSD but I thought I had specified it to use my HDD. I may move it to my HDD and see how much difference it makes. Right now I'm running a 500GB SSD, 1TB Toshiba 7200 rpm HDD and an older 2TB WD Black 7200 rpm HDD. I am contemplating getting a 1TB SSD for a scratch drive and upgrading the older WD Black to a 6TB WD Black because I'm running short on space.

Now if I can just figure out why I have playback preview lag.. sometimes it's fine, even with no optimized media, and other times even when I optimize the clips I still get stuttery preview. Tempted to go back to Vegas but I want to make sure I've tried everything first..

I know you probably will not want to publish this but the crashing issue I and possibly others are having, I'm sure is related to the timeline titler.
Loading projects from Version 14.01 into V14.1 causes the program to crash, if titles are included in the timeline, and the project attempts to load the timeline directly into either the edit or the media pages.
These project timelines, will however load directly into color, fairlight, or deliver (with titles) and act as normal. However the system will crash if you then attempt to open this timeline in edit, or go back to the media.
This may help you to resolve some of these issues.
Peter Fleming

Glen Stromquist wrote:I was trying to find an article I read recently about the memory errors in W10 having something to do with heap dumps or something like that, and on a whim thought I'd go check the virtual memory (paging file) settings. It was set to be system managed, and showing a size of about 1.6GB.

I changed it to custom size, with a low end of 3GB and high of 6GB, started up Resolve again and so far so good as far as crashes go. I still get the stuttering in preview/editing mode, even when I generate optimized media - so I don't know what's going on there..

But I edited and rendered a video no problems or crashes, and Resolve has been left running while I've done a bunch of other stuff - still no memory errors.

Not sure if this is same as your situation or not, but you may want to just try changing paging file size.

@Glen apologies for not being able to check-in on this until now! I think you're right and it might be more of a Windows issue than DaVinci issue. I'd like to test your idea of changing the virtual memory, but still being fairly new to Windows myself, I'm not sure how. Is there an article that you might be able to send to a Windows novice like me?

Since the only onboard disk I have is the SSD, I put it there. Regarding playback, a few questions:
1.What GPU are you using?
2. Also, I assume you're using the free version of Resolve(??)
3. What codec for your editing media?
I was running into precisely the same issues last year editing H.264 encoded files so I upgraded my system just for running Resolve and then purchased the studio version. On my old system, which was underpowered based on BMD recommendations, it was usable for editing as long as I used optimized media with a suitable DNX codec but sometimes it would get quite laggy and other times ran perfectly smooth, much like what you describe. I never could nail down the reason for the variance. With a significantly better GPU and the enhancements for H.264 in the studio version, playback has been very smooth. I came from Vegas as well and was tempted to go back but decided to stick with it and try to get the issues worked out.

1 - I'm using a AMD Radeon RX 480 & 8GB, i7 6800 3.4 core CPU
2 - yes
3 - I was not aware the codec chosen affected editing, I thought it was just chosen for rendering. So usually whatever the default is I guess.

When I render stock video I'm using mov with photo jpeg at best quality, for other work usually MP4 with H264.

Just now I started a new project with 4 clips I took with my Phantom - all played back flawlessly with no lag, no optimized video etc., and I have Chrome open with several tabs (usually I close Chrome when using Resolve)

Very strange..

JeffSpott wrote:

Glen Stromquist wrote:I was trying to find an article I read recently about the memory errors in W10 having something to do with heap dumps or something like that, and on a whim thought I'd go check the virtual memory (paging file) settings. It was set to be system managed, and showing a size of about 1.6GB.

I changed it to custom size, with a low end of 3GB and high of 6GB, started up Resolve again and so far so good as far as crashes go. I still get the stuttering in preview/editing mode, even when I generate optimized media - so I don't know what's going on there..

But I edited and rendered a video no problems or crashes, and Resolve has been left running while I've done a bunch of other stuff - still no memory errors.

Not sure if this is same as your situation or not, but you may want to just try changing paging file size.

@Glen apologies for not being able to check-in on this until now! I think you're right and it might be more of a Windows issue than DaVinci issue. I'd like to test your idea of changing the virtual memory, but still being fairly new to Windows myself, I'm not sure how. Is there an article that you might be able to send to a Windows novice like me?

@Jeff - you just go to control panel - system - advanced system settings - advanced - performance (or something like that) then choose virtual memory settings.

Thanks @Glen!

Apologies for taking a while to reply back on the thread. I've been editing heavily for 9 straight days now without a single crash. Also, the occasional database errors along with a few other error dialogs no longer occur. So, the issue I was having with constant crashes on Windows 10 has been resolved. The issue was having no virtual memory allocated. For those who might be troubleshooting a similar issue and find this thread, it might be a bit misleading as every time I checked available memory when editing in Resolve, I always had around 50% of my 16GB free. However, operations at some point obviously wanted more. In retrospect, the other errors that seemed to be popping up from everywhere in resolve now make a bit more sense. So, if you're seeing these types of issues, even if you feel like you have enough memory, make sure to have some swap space allocated to buffer for those times when Resolve needs more.
@Glen - as a side note, on the performance issues you mentioned, my guess would be that if you were running the studio version, you would be seeing smooth playback during edit. Although upgrading my system helped my performance problems immensely, the H.264 decoding enhancements in the studio version really made things completely smooth. For me, that feature alone was worth the price of admission (although I'm quite happy to support good products with my money).

Hoping this thread might be helpful to others,
Jeff H.

Hi,

I installed the latest version DaVinci Resolve but it keeps crashing every time I try opening the application.
It's a 15 inch Macbook Pro Late 2013 running High Sierra Version 10.13.2
Processor 2.3 GB intel Core i7
Memory 16 GB 1600 MHz DDR3
Graphics NVIDIA GeForce GT 750M 2 GB intel iris Pro 1536 MB

Can someone point me in the right direction to get this fixed?

Thanks Ruddy

Please review
viewtopic.php?f=21&t=54509