Blue Screen - OC Crash?

[Giganizer300PRO]

So I was working on a video in Vegas Pro 12 and suddenly I got this Windows message, that said I was running out of memory and that Vegas needed to close. I ignored that, but very shortly after that, Vegas crashed, so I restarted it. When Vegas started up, I got a BLUE SCREEN!

I think this is because I am overclocking my CPU, (specs in signature), a thread of which you can find here: http://linustechtips.com/main/topic/327500-a-good-first-time-overclock/#entry4452140, since Vegas is a pretty hungry beast.

Basically I'm running my i-5 @ 4.0 GHz with a voltage (set to 1.100) of 1.112.

I ran OCCT stress test for 2 hours and everything seemed normal with an average core temperature of 49-50 degrees C.

Am I right and if so, how do I fix this?

[Giganizer300PRO]

r you kidding me?!

what is this topic invisbru or what?!

[Bittenfleax]

r you kidding me?!

what is this topic invisbru or what?!

1. Have you tested without the OC?

2. Have you run Memtest86 or something just in-case it is your memory? 

[Queek]

So I was working on a video in Vegas Pro 12 and suddenly I got this Windows message, that said I was running out of memory and that Vegas needed to close. I ignored that, but very shortly after that, Vegas crashed, so I restarted it. When Vegas started up, I got a BLUE SCREEN!

I think this is because I am overclocking my CPU, (specs in signature), a thread of which you can find here: http://linustechtips.com/main/topic/327500-a-good-first-time-overclock/#entry4452140, since Vegas is a pretty hungry beast.

Basically I'm running my i-5 @ 4.0 GHz with a voltage (set to 1.100) of 1.112.

To address the elephant in the room: is this your copy of vegas?  Less-than-legit copies of things can sometimes come with their own instability and suboptimal performance.  

 

How many times has this happened?  Does it happen every time?  Can you give us the output of the blue screen?

 

You asked for help, but provided no relevant information to troubleshoot with.

[Giganizer300PRO]

To address the elephant in the room: is this your copy of vegas?  Less-than-legit copies of things can sometimes come with their own instability and suboptimal performance.  

 

How many times has this happened?  Does it happen every time?  Can you give us the output of the blue screen?

 

You asked for help, but provided no relevant information to troubleshoot with.

This is a trial version of Vegas Pro 12, downloaded from the official website.

This has only happened once, only on this new PC, never before I was OC and this is the first time I used Vegas while OC.

Sadly I cannot give you the output of the blue screen, it was only on for 2 or 3 seconds before the machine restarted, but I read at the top something like DRIVER_ and then some "random" letters and numbers with _ every 4 symbols or something like that.

Thank you for your response

[Giganizer300PRO]

1. Have you tested without the OC?

2. Have you run Memtest86 or something just in-case it is your memory? 

No I haven't yet tested without the overclock, but this never happened before the OC.

I have not run an memory check, can you please recommend some good software for it?

Thank you for your response

[Bittenfleax]

No I haven't yet tested without the overclock, but this never happened before the OC.

I have not run an memory check, can you please recommend some good software for it?

Thank you for your response

Memtest86 here is the site: http://www.memtest86.com/

[Giganizer300PRO]

Memtest86 here is the site: http://www.memtest86.com/

I just checked out their site...

DO I NEED TO BOOT IN TO THE SOFTWARE?!

[runit3]

I just checked out their site...

DO I NEED TO BOOT IN TO THE SOFTWARE?!

Yes.

Knowing the BSOD code would shed some light on what actually happened. 124 or 101 would be voltage (sometimes 09C). 01A would be RAM.

My first guess is voltage. Bump it up to at least 1.175v on core and see how it goes.

[Queek]

I just checked out their site...

DO I NEED TO BOOT IN TO THE SOFTWARE?!

Grab a small flash drive and use the "image for creating bootable USB drive" link.  Boot to that USB and let it run for a while (at least 1 pass).  This could take a very long time depending on how much memory you have.  

[Giganizer300PRO]

Yes.

Knowing the BSOD code would shed some light on what actually happened. 124 or 101 would be voltage (sometimes 09C). 01A would be RAM.

My first guess is voltage. Bump it up to at least 1.175v on core and see how it goes.

I'm sorry for being such a noob, but you're talking about the error code on the blue screen?

[runit3]

I'm sorry for being such a noob, but you're talking about the error code on the blue screen?

Yes. Should look something like address: 000x00000XXX. The X's will be the error code.

[Giganizer300PRO]

Yes. Should look something like address: 000x00000XXX. The X's will be the error code.

Well, all I saw was the thing at the top. It was DRIVER_ something (random letters and numbers) so if that's what you're talking about, I can maybe recognize one from a list but I only saw it for 1 second, so I don't think any luck there.

Also you said to crank the voltage up to 1.175, so I am going to do that and then try to edit a video again.

Thank you do much for your help!

[runit3]

Well, all I saw was the thing at the top. It was DRIVER_ something (random letters and numbers) so if that's what you're talking about, I can maybe recognize one from a list but I only saw it for 1 second, so I don't think any luck there.

Also you said to crank the voltage up to 1.175, so I am going to do that and then try to edit a video again.

Thank you do much for your help!

NP. You can also find the code by looking through your event viewer log.

 

Windows key

Type "event" in the search bar

First result should say event viewer, launch it

Expand Custom Views, highlight Administrative Events

In the right panel click Level to organize by level, make Critical top priority

Find the approximate time of the BSOD and highlight it in the listings

Go do the details tab of the bottom window once it's selected and find the BugcheckParameter listings, the red circled one should end in 124, 101, etc.

[Giganizer300PRO]

NP. You can also find the code by looking through your event viewer log.

 

Windows key

Type "event" in the search bar

First result should say event viewer, launch it

Expand Custom Views, highlight Administrative Events

In the right panel click Level to organize by level, make Critical top priority

Find the approximate time of the BSOD and highlight it in the listings

Go do the details tab of the bottom window once it's selected and find the BugcheckParameter listings, the red circled one should end in 124, 101, etc.

I found only 1 critical event on the day I got the crash and I think it's the right one.

Here's the "code": 0xfffff88006c128ba

[runit3]

I found only 1 critical event on the day I got the crash and I think it's the right one.

Here's the "code": 0xfffff88006c128ba

That is an odd one. Are your Nvidia drivers up to date? I'm not familiar with Vegas as I use Premiere, but if it has GPU acceleration or something tied to graphics/display drivers that may have tripped it up. If you remember seeing DRIVER_ somewhere in the BSOD readout that may be the most likely culprit. Most driver related BSOD's look like DRIVER_IRQL_NOT_LESS_OR_EQUAL, this article may help: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-7-blue-screen-driverirqlnotlessorequal/018fd6e7-c503-4241-9a7f-e67177bc3e50

 

First thing I would try is performing a clean install of Nvidia's latest non-beta drivers. Just make sure to check the box for clean install.

 

[Giganizer300PRO]

That is an odd one. Are your Nvidia drivers up to date? I'm not familiar with Vegas as I use Premiere, but if it has GPU acceleration or something tied to graphics/display drivers that may have tripped it up. If you remember seeing DRIVER_ somewhere in the BSOD readout that may be the most likely culprit. Most driver related BSOD's look like DRIVER_IRQL_NOT_LESS_OR_EQUAL, this article may help: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-7-blue-screen-driverirqlnotlessorequal/018fd6e7-c503-4241-9a7f-e67177bc3e50

 

First thing I would try is performing a clean install of Nvidia's latest non-beta drivers. Just make sure to check the box for clean install.

I bumped the core voltage up to 1.150 which gave me a core voltage of 1.60. After that I edited and even rendered the video without any problems.

I guess that was the issue?

[runit3]

I bumped the core voltage up to 1.150 which gave me a core voltage of 1.60. After that I edited and even rendered the video without any problems.

I guess that was the issue?

How could bumping core to 1.15 give you 1.6!?! Are you running an offset? 1.6v is WAY too high for vcore. You should be operating around 1.3 for a 24/7 OC.

[Giganizer300PRO]

How could bumping core to 1.15 give you 1.6!?! Are you running an offset? 1.6v is WAY too high for vcore. You should be operating around 1.3 for a 24/7 OC.

No...

Looks like I miss spelled it. It's 1.160. Sorry.

[runit3]

No...

Looks like I miss spelled it. It's 1.160. Sorry.

Lol you scared me! Glad everything is working.

[Giganizer300PRO]

Lol you scared me! Glad everything is working.

I am glad too. Thank you so much for your help!

Also there was a new NVIDIA driver update that came out a few days ago and when I was updating, I checked "Clean Install" just-in-case.