Blue Screen Issue When Video Encoding

liberty610

Distinguished
Oct 31, 2012
466
5
18,815
Hey guys,

I am currently having an issue with my current custom built Windows 10 machine that I have not had before in previous setups. I do a lot of video and audio work, and right now I am having a crash/reboot issue when rendering/encoding video.

My last PC I built was running Windows 7 ultimate with an AMD 6 core processor (I can not remember the exact model off the top of my head.) I had no issues with that processor on my previous motherboard when it came to using Handbrake or Sony Vegas to encode/render video. I could use it for hours on end, with the processor getting pushed to the max for hours at a time without issues.

Last September I upgraded my machine. I have a cooler master haf X case with 3 major 120mm intake fans, and one outtake on the back. I am running Windows 10 pro with an AMD FX-8350 8 core processor on a GIGABYTE GA-990FXA-UD5 R5 (rev. 1.0) board. The processor has the Cooler Master Hyper 212 EVO heat sink with Arctic 5 paste on it. Ram is G.SKILL Ripjaws Z Series 16GB (2 x 8GB) 240-Pin DDR3 SDRAM DDR3 1866 (PC3 14900).

Up until now, I have not been doing any super heavy processor tasks on this machine for long periods of time. When I put it together, I used Prime95 for a solid hour or so with CPUID Hardware monitor watching my temps. I did not experience any issues. I am NOT overclocking at all, and I use the old Windows gadgets setup with ALL CPU Meter gadget to monitor the processor load.

Recently, I have been getting random restarts and blue screens when rendering video. I was able to render for several hours with Sony Vegas the other day. The processor was not being used at full load; maybe half load. Each render was about an hour and half, and I was able to render maybe 4or 5 tasks without issue. Then, all of a sudden, it started rebooting by itself when I would try to render more down. It even froze up at one point, forcing me to do a manual reset. I do not let a screen saver come on, nor do I let it go into lock mode for my user name during rendering. So there are really no other tasks going on when i am doing this stuff.

When using the software Handbrake to encode video, I have no issues with short files that only run for a couple of minuets, but as soon as I have a clip that takes 5 to 20 minuets, I get a reboot or blue screen about 1/4 of the way through it.

One of the days where I was rendering for several hours, I kept CPUID open to monitor my cpu temps. When idle or doing general tasks, it runs anywhere between 15 degrees Celsius to 25 Celsius. Under full load using Handbreak, the hottest it reads is 41 Celsius with an average of 36 to 38.

I can encode short clips that only take a minuet or two just fine, but if it's estimating to be a longer encode of 5 to 20 minuets, it only gets 1/3 of the way finished and then blue screens or reboots.

And like I said, when rendering with Sony Vegas the one day, I was able to do several hours, then all of a sudden it started to freeze or reboot. I shut down for the night, came back the next day and rendered a couple files just fine, then 3 or 4 files in, it rebooted by itself.

Is there something I may have missed in my setup? Is there anything else I should be looking at to see why this is happening? Thanks in advance for any help/replies.

John
 
Make sure that you have activated so the memory dump file will be saved:
1. Open the computer's System Properties dialog Start > Run > (or just type in the start menu) >Type: sysdm.cpl > Press return.
2. Select the 'Advanced' tab.
3. Under the section 'Startup and Recovery' select the 'Settings...' button.
4. Under the section 'System failure' > 'Write debugging information' from the drop down menu select 'Dump memory" (or similar).
5. Click 'OK' to confirm the change.
6. You must restart the computer for the change to take effect.
The computer will now write the entire contents of the computer's RAM to a dump file if a system crash occurs.

Then download and install free BlueScreenView http://www.nirsoft.net/utils/blue_screen_view.html
run the s/w to see if there are any memory dump file with errors, that suggest a Windows system crash.
The important info is: Error message and the stop error code.

Best regards from Sweden

 

liberty610

Distinguished
Oct 31, 2012
466
5
18,815
Thanks for the reply Flyfisherman. Under the memory dump section, I have several options to choose from that are all similar. They are:

1. Small memory dump
2. Kernel Memory dump
3. Complete memory dump
4. Automatic memory dump
5. Active memory dump.

Which one should I select? The complete memory dump?
 
It is not so important, nr. 2 will suffice, perhaps it is activated already?
Remember to restart the computer.

The thing is that a memory dump file must be created so that the BlueScreenView program can open and read it.
If no memory dump file is created, then it is not a blue screen (BSOD) issue.

In the program there will also be an option under the file menu to save the info to a text file which you could attached in your next post, so perhaps someone can take a look at it or You could also by yourself google a solution (a direct google search for the error codes is provided directly under the file menu).
 

liberty610

Distinguished
Oct 31, 2012
466
5
18,815
Thanks for the reply! I'll see about pushing the processor again today with some renders and see if I can get anything out of it. Like I said, it doesn't always blue screen. The other issue is, it will randomly restart. It'll act as if someone hit the reset button on the case, but it just restarts by itself automatically. That's been the issue a couple times during Sony Vegas renders.
 

liberty610

Distinguished
Oct 31, 2012
466
5
18,815
UPDATED - BSOD text attatched:

ok guys, last night I ran Handbrake on 2 different occasions for long periods of time for several files without any single issue, and then shut down my PC when i was done. Today, I booted up, started another file on hrandbrake, and got a hard reset. After the hard reset, I loaded handbrake again, and successfully converted a couple files, and then BAM - BSOD.

I used the suggested program above, and looked at the error/googled it. This is what it outputed to a text file:

==================================================
Dump File : 070116-18953-01.dmp
Crash Time : 7/1/2016 7:58:40 AM
Bug Check String :
Bug Check Code : 0x00000124
Parameter 1 : 00000000`00000000
Parameter 2 : ffffe000`210c4028
Parameter 3 : 00000000`f0800000
Parameter 4 : 00000000`00040151
Caused By Driver : hal.dll
Caused By Address : hal.dll+35f1f
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1427a0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\070116-18953-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 10586
Dump File Size : 256,356
Dump File Time : 7/1/2016 7:59:31 AM
==================================================

I also googled it, and there was a youtube video suggesting it could be driver related? And to disable driver signature enforcement? So I gave that a try, and after the reboot of setting that up, I ran handbrake and it froze the entire pc again within a matter of a few seconds. As I started in my original post, the Hottest my system runs when handbrake pushes a full load is 41 Celsius, and that's on a warmer day. The hottest it got the last couple times was 39 Celsius. When idle, it runs between 14 and 18.
 
Perhaps a missing or a corrupted hal.dll in the Windows system?

Run System File Checker (SFC /scannow) to see if there are any corrupted system files that can be repaired.
Se instructions here:
Windows 10 Forums - SFC Command - Run in Windows 10

Another thing; have You overclocked Your CPU? In any case, also make sure to load BIOS Optimized Defaults or Load BIOS Default in the BIOS Settings menu, check the boot priority for your drives afterwards and then Save & Exit.
Best Regards from Sweden


 

liberty610

Distinguished
Oct 31, 2012
466
5
18,815



I made a few moves yesterday in regards to this issue. One of them was loading optimized defaults in the BIOS. I am not doing any over clocking at all.

I attempted to use handbrake on a normal boot, and within seconds it froze up the entire pc. Had to do a reset. I booted up in safe mode, and attempted to convert the same video and it converted the video all the way through without a single issue, and it took about 25 minuets solid of a full processor load.

I made a call to a local pc store, and to MSI (my graphics card manufacturer). The other suggestions I got from them and tried where un-installing the video driver, and re-installing it. So I un-installed, used CCleaner to clean up all files, and then rebooted, and then re-reinstalled the driver. I then used Sony Vegas and rendered down 3 videos (the render time took over an hour each) without an issue. I then used handbrake on a few other files without issues. I then attempted another video on handbrake, and a few seconds into the conversion, the pc froze up.

The only other thing I have not tried yet is re-seeding the graphics card. So I plan on pulling the card out tomorrow and cleaning the motherboard slots out and the card itself out real good and doing what I can to push it with handbrake again. If none of these work, as well as checking for the corrupted windows files, I will probably RMA the card. I have another video card (a real weak baby one from my last system) that I can also try out. I'm assuming if that card has no issues rendering anything down (even though it will take a little longer) then it has something to do with the current card I have.

I may also try a fresh windows install?
 

liberty610

Distinguished
Oct 31, 2012
466
5
18,815
UPDATE: After swapping out to my older video card that never gave me any issues in the past, I still received a BSOD and several freezes. So I started pulling out Ram chips and testing slots, and every combination of those tests resulted in freezing/crashing.

In a desperate attempt to NOT send back any hardware (motherboard included), and to try and save as much time as I could so I could get back to work on my projects, I just re-installed Windows 10. So far (knock on wood) with many handbreak runs on several different files, there have been Zero issues.

Is it possible something like Windows Updates or even AVG could have been causing issues? I decided since I was doing a fresh install to give Avast anti virus a whirl. So far it seems less demanding then AVG, and less annoying with pop ups about buying add ons or higher pair protection.
 
That is amazing, but not unbelievable.
And while youre at it, skip AVG, not because its a poor antivirus engine, but because it take up so very much performance of the CPU.
If you want to go with the best Free antivirus s/w: Avast https://www.avast.com
Begin with adjust the settings as your preferred profile, update, restart the computer and you are ready to go.

Ooh, I just forgot: You really need to uninstall any Antivirus package before You install the new one - Restart the computer > install the new one..
Very Important. See here and perhaps You will need the AVG Remover tool.
https://support.avg.com/SupportArticleView?l=en_US&urlName=How-to-uninstall-AVG
Restart

Btw. As for firewall speaking: Microsoft Windows 7, 8 and 10 have among the best firewall inbuilt.
Best regards from Sweden
 

liberty610

Distinguished
Oct 31, 2012
466
5
18,815


Thanks for the tip, but, I actually did just that with Avast already. I notice AVG was using a lot of resources, and I heard a lot of great things about Avast. So after I installed windows 10 and got all the updates for it, Avast was the next thing I installed. So no worries about needing to un-install AVG, as I never re-installed it after I reinstalled 10.