VP to Handbrake render causes BSOD on Win 8.1

Cliff Etzel wrote on 2/4/2015, 9:38 AM
I have a Xeon x5670 that was slightly OC'd from stock 2.93ghz to 3.51ghz using the dummy OC feature in the BIOS of my EVGA X58-SLI3 Mobo. Running 24GB All GSkill matched RAM with a Crucial Memory M500 240GB SSD drive for OS/Apps. Supposedly this feature in the MoBo is suppose to be pretty safe and it makes all the adjustments accordingly.

Watching task manager CPU performance pegs all cores at 100% when running the handbrake script and leaves it there until all of a sudden I get the Windows 8.1 equivalent of a BSOD and have to do a hard shutdown.

I have had no issues with running my CPU in the configuration with Premiere Pro CS6 but I have noticed that CPU performance isn't pegged like it is when rendering from Vegas to Handbrake via the script.

Given I have no experience with even mildly overclocking a CPU and my research so far has yielded what constitutes to mind numbing information, anyone have recommendations on what I should try considering the overclock is only about 500mhz more than stock clock speed or should I just leave it at stock speed?

**Edit: I'm still running the nVidia GTX-660ti with GPU acceleration turned on - could this be the issue?**

Comments

wwaag wrote on 2/4/2015, 10:16 AM
I'd suggest you check your CPU temp when rendering. It may be overheating and the system simply shuts down. My 3.5 GHZ core I7 was OC'd to 4.4 GHZ without problems until last summer when I had a similar problem. Moved it back to 4.2 and all is fine. I use Speedfan for monitoring.

wwaag

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

BruceUSA wrote on 2/4/2015, 10:27 AM
Cliff,

If you are Overclocking your CPU. You should really run Prime95 for 30 minutes test for stability. Prime95 will loads the CPU hard, if the CPU can pass 30 minutes mark. Chance are you will never get BOSD while rendering video. The best I can guess your situation is this. Reset your CPU to default and try to render again? Or you can increase your Vcore a little. Be careful, over do it can kill your CPU. For a Xeon Chip, try to keep under 1.35v max vcore.


Here an example, My 4930K @4.5Ghz OCed can run Prime95 for hrs+ but I shot it down because I felt that is good enough for stability reason. In rendering video. I never ever have gotten a BOSD. Just wanna share.

CPU:  i9 Core Ultra 285K OCed @5.6Ghz  
MBO: MSI Z890 MEG ACE Gaming Wifi 7 10G Super Lan, thunderbolt 4
RAM: 48GB RGB DDR5 8200mhz
GPU: NVidia RTX 5080 16GB Triple fan OCed 3100mhz, Bandwidth 1152 GB/s     
NVMe: 2TB T705 Gen5 OS, 4TB Gen4 storage
MSI PSU 1250W. OS: Windows 11 Pro. Custom built hard tube watercooling

 

                                   

                 

               

 

Cliff Etzel wrote on 2/5/2015, 7:08 AM
After some poking around in the BIOS, came across a setting related to using alternative cooling (Extreme Cooling) - settings included disable, 0C and -50C. appears I had mistakenly set it to -50C and as such my CPU apparently was getting way too hot and causing the BSOD. Disabled it and re-ran frameserving to Handbrake with the Dummy OC settings and renders competed without issue. So I'm OC's comfortably at 3.51Ghz which is more than I thought I would get.

Go figure...

Now just patiently waiting for the Radeon 6970 to be delivered so I can test and see if there's a genuine performance difference for me with Vegas Pro.