shantd Posted June 7, 2011 Share Posted June 7, 2011 Hey there. I've got a strange issue that I can't seem to identify. My system seems to have a roughly 3-day lifespan before the BSOD hits. After about 3 days of use, if I leave the computer alone for several hours (ie when I go to bed and leave the system on), I'll return to a BSOD or simply a frozen screen. I realize it sounds like the screensaver or hibernation is the culprit, but it isn't because I've turned those off. I never experience the crash while I'm using the computer. Apparently something is kicking in after several hours of inactivity, but I can't seem to track down what that is. And again, for the first couple days after a restart, it won't happen. By roughly day 3 or 4 is when my system will become primed and ready for it. The event viewer shows nothing. Any ideas? Thanks, Shant Link to comment Share on other sites More sharing options...
jaclaz Posted June 7, 2011 Share Posted June 7, 2011 Knowing which EXACT BSOD (STOP ERROR number) you get would greatly help....jaclaz Link to comment Share on other sites More sharing options...
shantd Posted June 7, 2011 Author Share Posted June 7, 2011 I suppose I won't be able to provide that until it happens again. Keep in mind though, that sometimes the screen just freezes...no blue screen. I've been trying to 'cheat' by putting the system into standby mode before going to sleep. This method seems to buy me an extra day or two. At that point (4 days or more without a crash), however, my system will be ultra primed for a crash where leaving it alone for just an hour will be enough to come back to a frozen/BSOD. So it seems like there's some sort of internal clock where the longer my system goes without a crash, the more sensitive it will be for a crash. What sort of programs do you know of (besides screensaver or hibernation) that kick in after several hours of inactivity? Link to comment Share on other sites More sharing options...
dencorso Posted June 7, 2011 Share Posted June 7, 2011 Nobody's in a hurry. Take a good pic of the blue screen and post it.And, after that, do set the system to create a system dump or minidump on crash, and disable the auto-reboot feature, although it doesn't seem to be kicking in, in your case, so that we can get a crash dump on the crash following the next one. Link to comment Share on other sites More sharing options...
Tripredacus Posted June 7, 2011 Share Posted June 7, 2011 I suppose I won't be able to provide that until it happens again. Any time you get a BSOD, there will be an event regarding it in Event Viewer. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted June 7, 2011 Share Posted June 7, 2011 upload at least the dmp files from the folder C:\Windows\Minidump or better the large dump (memory.dmp) from C:\Windows Link to comment Share on other sites More sharing options...
shantd Posted June 8, 2011 Author Share Posted June 8, 2011 do set the system to create a system dump or minidump on crash, and disable the auto-reboot feature, although it doesn't seem to be kicking in, in your case, so that we can get a crash dump on the crash following the next one.Very well...how exactly do I do this? Link to comment Share on other sites More sharing options...
shantd Posted June 8, 2011 Author Share Posted June 8, 2011 I suppose I won't be able to provide that until it happens again. Any time you get a BSOD, there will be an event regarding it in Event Viewer.What is it called in the event viewer? Is it under system or application? And is it yellow (warning), red (error), or white? Link to comment Share on other sites More sharing options...
shantd Posted June 8, 2011 Author Share Posted June 8, 2011 upload at least the dmp files from the folder C:\Windows\Minidump or better the large dump (memory.dmp) from C:\WindowsI don't have memory.dmp, but I have found the mini dump. Not sure if you meant I should attach it to a post, but if you did, I am not allowed to do so. Link to comment Share on other sites More sharing options...
dencorso Posted June 8, 2011 Share Posted June 8, 2011 do set the system to create a system dump or minidump on crash, and disable the auto-reboot feature, although it doesn't seem to be kicking in, in your case, so that we can get a crash dump on the crash following the next one.Very well...how exactly do I do this?Right-click on "My Computer", select "Properties" -> "Advanced", go to "Startup and Recovery" and click on "Settings", go to "System Failure", select the "Write an event to the system log" and deselect both "Send an administrative alert" and "Automatically restart", then go to the box below "Write debugging information" and select "Small memory dump (64KB)" for a minidump or "Kernel memory dump" for a full dump. Click "OK", then "OK". Let's start with minidumps. Now, even minidumps are too large to attach. So upload them somewhere like uploadade.to or megaupload and post the link to it here. Link to comment Share on other sites More sharing options...
Tripredacus Posted June 8, 2011 Share Posted June 8, 2011 What is it called in the event viewer? Is it under system or application? And is it yellow (warning), red (error), or white?Its probably under system. It will be either Yellow or Red. Just look through them, if you see something suspicious, post what it says even if it isn't what we are looking for. Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted June 9, 2011 Share Posted June 9, 2011 http://www.nirsoft.net/utils/blue_screen_view.html ??? Maybe? Link to comment Share on other sites More sharing options...
shantd Posted June 9, 2011 Author Share Posted June 9, 2011 OK here's a copy of the last BSOD:A problem has been detected and Windows has been shut down to prevent damageto your computer.The problem seems to be caused by the following file: ntoskrnl.exeCRITICAL_OBJECT_TERMINATIONIf this is the first time you've seen this stop error screen,restart your computer. If this screen appears again, followthese steps:Check to make sure any new hardware or software is properly installed.If this is a new installation, ask your hardware or software manufacturerfor any Windows updates you might need.If problems continue, disable or remove any newly installed hardwareor software. Disable BIOS memory options such as caching or shadowing.If you need to use safe mode to remove or disable components, restartyour computer, press F8 to select Advanced Startup Options, and thenselect Safe Mode.Technical Information:*** STOP: 0x000000f4 (0x00000003, 0x8ad8a690, 0x8ad8a804, 0x805d2970)*** ntoskrnl.exe - Address 0x804f9f33 base at 0x804d7000 DateStamp 0x4802516aI hope that helps you out...it seems ntoskrnl.exe is the culprit. Any ideas? Thanks for all your help gentlemen, it's truly appreciated.Shant Link to comment Share on other sites More sharing options...
dencorso Posted June 9, 2011 Share Posted June 9, 2011 KB977178 might perhaps apply? Link to comment Share on other sites More sharing options...
shantd Posted June 10, 2011 Author Share Posted June 10, 2011 That's for Windows 7, I don't believe it applies to XP.. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now