Crashing every time I try to render

Whatthefnu wrote on 3/27/2016, 3:48 PM
Consistently around the 65%-75% mark, my computer is cutting to black as if my display driver crashed (doesn't even give me a blue screen), and if I had any audio playing, it would start the tell-tale buzz of a crash a few seconds later. For reference, my computer is an HP p7-1154, and my processor is an AMD A6-3600 APU with Radeon. It's running Windows 10 (much to my chagrin), but this issue started cropping up a little before Misrosoft forced my hand on that one. Is there an update I'm missing or something? Also, my videos are usually around 30 minutes or so in length, and I'm rendering them at 1980x1080 30-p.

Knowing all that, anyone have an idea what's going on?


Markk655 wrote on 3/27/2016, 4:00 PM
By any chance are you also measuring the cpu temp? Perhaps the insides need a dusting?

Have you tried rendering the clips in the range that would be 60-80% just to make sure there isn't an issue with those clips?
Whatthefnu wrote on 3/27/2016, 5:16 PM
I dusted it about a month ago, but it is an older computer, so maybe it's on its last legs...

Also, I'm trying your suggestion now. I'll let you know if it works. If you're right, this might be a problem with my capture card. Which would still suck, but it would be better than having to buy a whole new computer.
musicvid10 wrote on 3/27/2016, 5:57 PM
I agree with Mark that it is probably a hardware heating issue.
Another unrelated thing you can try is turning off Vegas' GPU entirely.
Why do you mention a capture card when your problem occurs during rendering?
UKharrie wrote on 3/28/2016, 7:33 AM
You don't say, but was this PC Rendering similar Video prior to the change to Win10? . . . . and what OS was that?
Can you bring back an earlier Project? Use a quick-Render that worked OK prior - and try it with the new OS?
Are any other programs affected? - you could try to "Rotate" a large still-picture in Painshop/Similar as this creates a lot of work for the PC.

( Not sure I like the CPU overheating ans . . . but the above Duty-Test may assist - however, if you are in a warm / hot room, then that's different. ). Of course you've shut-down everything else....

If the PC is running only something like a WP or a YT film - does that cause a crash?

You mentioned a "noise" - did I understand that is something mechanical? Always worth doing a HDD check - defrag is now automatic I think, but there are Tests for segment woes - BTW how much space does yr HDD have free - could it be you are pushing the limit ?

Why did you upgrade to Win10? - surely there was no force from Microsoft - I understand my Win7 PC will remain operational - "If it ain't broke, don't fix it" sprngs to mind - but I accept you are now in a somewhat different position.

Good luck.
Whatthefnu wrote on 4/4/2016, 2:14 PM
Right. So here's an update for everybody. Over the past couple days, I've tried a multitude of ways to keep my PC cool. I dusted it out with some canned air, and I vacuumed around where the PC was. It worked for a while, then started crashing again. I then moved it to a more open space so it had more room to breathe. It worked for a while, then started crashing again. Then, I opened the case, took a desk fan, and set it up so that it was blowing cool air directly onto the hardware. Again, it worked for a while, but then started crashing again. Whatever problem I have, I can now 100% confirm that it's not related to overheating.

I've confirmed that the position in the render doesn't matter, so it's not an issue with the footage, or the program I'm using to record it. And yes, UKharrie. Windows forced my hand on that one. I could not restart or shut down the computer without it performing the update operation. I'l try rendering an older project file and let you know how that goes.
Eagle Six wrote on 4/4/2016, 2:31 PM

What is the temperature of your CPU and GPU running? If you don't know, perhaps download a free copy of Speccy or CPUZ, either will display various running temperatures of your computer components. A quick search for your cpu and gpu should reveal the normal operating temperature range. Then you know for sure about the temperature question. You of course will not know if previous high temperatures may have caused some damage.

You stated in your OP that this condition started before the Win 10 installation. Did the condition go away after the Win 10 install and then come back? If not, it appears Win 10 may not have anything to do with it. However, I have read many have had issues with the Win 10 upgrade and went to a clean install of Windows 10 to resolve those issues. I have no idea, I'm still running Windows 7, but just thought I would mention it. If haven't performed a clean install of Windows 10, maybe a clean un-install and a clean install of Vegas with a program reset may be helpful.

Best Regards.......George

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2