Overclock.net banner

Windows crash during idle

4K views 29 replies 9 participants last post by  Kazumi 
#1 ·
Hey everyone.

Not sure what is happening. Recently my windows has been blue screening when idle. I can game on BF3 for countless hours. But soon as I leave my system alone and idle for more then half an hour I come back to it rebooted because of a crash. Cannot figure out what is causing it. Scanned my system with Advance system optimizer, Windows security essentials, and virpre. Nothing is reporting any errors. I defrag twice a week, and repair registry and any other issues twice a week as well. I consider my system well optimized and running smoothly. But I cannot grasp why I'd be crashing recently.

Any help would be welcomed, Tera online is coming out soon, and I've been trying to DL the beta with no luck due to the crashing at night.
 
#2 ·
Sounds like a driver problem. I've had this happen before as well. Make sure all your drivers are up to date. Did you update or download anything prior to your current problem? Maybe try a system restore before you noticed the problem started. Also, are you overclocked at all?
 
#3 ·
How long have you had that CPU, and what overclock is it at?
 
#4 ·
Ok, after doing some research I stumbled on to something I think might help you figure your issue out.

Go to Control Panel -> System -> Advanced System Settings -> Startup and Recovery [Settings] Make sure that "Write Debugging Information" is set to Small Memory Dump (256kb) if it is not already.

Next, make sure that the folder C:\Windows\Minidump exists. If not, create it (allow permission if asked). Make sure any dumps you want to analyze are in this folder.

Download and install WhoCrashed. When the installer is done installing, just uncheck the box to launch, because it will give you an error that Admin privileged is required. Run from Desktop or Start Menu, and click "Analyze".

Now you should be able to view your dump files and get a good idea of what's causing your BSOD..
 
#5 ·
Quote:
Originally Posted by pioneerisloud View Post

How long have you had that CPU, and what overclock is it at?
I've had it a few months. And only a mild 4.6ghz. If it was unstable it'd crash during high load. But I can fold, and stress test fine without issues. So I doubt it's a bad OC since I consider myself fairly experienced now at it.
 
#6 ·
This is the error. I've recently updated my CPU driver (today, after the last crash) So I'll see what happens. But everything is updated. As I said, I make sure to clean, update, and manage my files twice a week. So I doubt anything is outdated..haha

On Sun 4/1/2012 6:23:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-8704-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CD40)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003BE7949, 0xFFFFF88005520EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
 
#7 ·
Quote:
Originally Posted by Kazumi View Post

Quote:
Originally Posted by pioneerisloud View Post

How long have you had that CPU, and what overclock is it at?
I've had it a few months. And only a mild 4.6ghz. If it was unstable it'd crash during high load. But I can fold, and stress test fine without issues. So I doubt it's a bad OC since I consider myself fairly experienced now at it.
Increase your vcore a few notches (just a few). I'll bet the problem disappears.
wink.gif


You've reached what I like to call, the "Burn In" period of these chips. After a few weeks to a few months (depending on the overclock), the chip degrades ever so slightly, to the point it needs a bump in vcore at this point. Not much, like 0.025v or so. Everybody that I have personally talked to, has had this happen sooner or later.

Do that, and make sure your C3 / C6 states are set correctly (enabled if constant voltage, disabled if using offset). I'll bet the problem disappears.
 
#10 ·
Quote:
Originally Posted by |2A|N View Post

You need to upgrade your firmware for your SSD. Go HERE and pick your SSD then it will tell you how to update your firmware. See if this solves your issue.
He said he's only had this machine for a few months at most. The latest firmware should already be on his SSD, and he should be nowhere NEAR the 5200 hour mark yet. So that is NOT causing his issue. But it is worth looking into, and making sure he's on the latest...to avoid that 5200 hour BSOD later on.
Quote:
Originally Posted by Kazumi View Post

Huh, enable if using constant...I guess I'll have to check. I bumbed it up to
If you're using constant vcore, then c3 / c6 need to be enabled or auto.

If you're using offset vcore, they need to both be disabled.
 
#12 ·
Ok, so I did the firmware update. I believe I was already at 0309. But I updated again to be safe. Also checked the C3/C6 and they are both enabled. I use constant volts because I don't like off sets. Let us hope this all resolves the issue..

oh, a few days ago, I bumped up Vcore from 1.30 to 1.325 so I already increased the volts to account for any degrading of the chip from the break in period.
 
#13 ·
Quote:
Originally Posted by Kazumi View Post

Ok, so I did the firmware update. I believe I was already at 0309. But I updated again to be safe. Also checked the C3/C6 and they are both enabled. I use constant volts because I don't like off sets. Let us hope this all resolves the issue..

oh, a few days ago, I bumped up Vcore from 1.30 to 1.325 so I already increased the volts to account for any degrading of the chip from the break in period.
Good.
smile.gif
This SHOULD solve any of your issues. If you end up getting an x124 BSOD, then try a little bit more vcore. 4.60GHz with only 1.325v...that's really REALLY good. Mine wants 1.37v just for 4.5GHz. So you're still well within reason on voltages.
 
#14 ·
Yea, I really worked hard on timings, and the settings to get the CPU to clear Prime95 and IBT at the 1.3v but I assumed when I BSOD that it was from to low volts. But even with the increase it was still crashing at idle. But, let us hope it's all resolved..haha
 
#15 ·
Quote:
Originally Posted by Kazumi View Post

Yea, I really worked hard on timings, and the settings to get the CPU to clear Prime95 and IBT at the 1.3v but I assumed when I BSOD that it was from to low volts. But even with the increase it was still crashing at idle. But, let us hope it's all resolved..haha
Like I said, it might need just a tad more. Mine wanted 0.05v increase.
eek.gif
Mine was a bad chip to begin with though, so whatever.

If it does it again, make note of the BSOD code. If its x000124, I'll bet it just needs a little more vcore.
 
#20 ·
Quote:
Originally Posted by Kazumi View Post

Bumped up Vcore again. From 1.325 to 1.355. So hopefully this will work. But I cannot understand WHY it would crash on nearly idle load, and not on high usage.
It could be the power states causing it. I would trying turning them off and see if you still crash. I just know that some people had issues with overclocking and leaving c3/c6/c1/EIST on. Turn them all off and see if you still crash while idle.

Those were actually the first things I turned off when I got my 2500k....
 
#22 ·
Hello!
smile.gif


Can you please navigate to C:/Windows/Minidump and zip / rar up your latest dump files? Once you've done that, please attach the zip / rar to your post by clicking the paperclip icon in the reply / post box.

If there are no files there, you may have it set to writing Kernel Memory Dumps rather than Small. If so, the DMP will be located in C:/Windows itself and named MEMORY.DMP.
 
#23 ·
If this latest bump in vcore doesn't do the trick...then its possible it has something to do with how your C states are setup, and how your voltage is going. This is exactly why I don't use the constant voltage feature, and use offset with turbo.
tongue.gif
 
#25 ·
Is it occurring only when you're downloading something ? Downloads were crashing me after a windows update a while back, i ended up having to roll back those updates.
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top