As of last week I've noticed that my computer will crash to the blue screen about 10-15 seconds upon waking from sleep mode. I'm not sure what happened in the last week, but since the first few experiences with the blue screen I now just leave the computer running.
The unit doesn't fail any other time, just upon waking from sleep mode.
The zip you uploaded does not contain any crash dump.
Follow it: Dump Files - Configure Windows to Create on BSOD
Go to Option Two, Point 2. Download the .reg file and merge it in registry by double clicking it.
Now wait for another BSOD. When it occurred, search the .dmp files manually in the default path: C:\Windows\Minidump or %SystemRoot%\Minidump. See if the crash dump is recorded or not (hopefully it will be recorded).Post it following the Blue Screen of Death (BSOD) Posting Instructions.
In between, disable sleep. It is not needed at all for a desktop PC.
Uninstall Marvell 91xx SATA 6G Controller from Control Panel > Programs and Features. Then follow Drivers - Clean Left over Files after Uninstalling to free up the leftover.
Check that the following drivers are up to date or not.
JMicron JMB36X Controller : ftp://driver.jmicron.com.tw/SATA_Controller/Windows/
NEC Electronics USB 3.0 Host Controller: RENESAS/NEC Drivers & Firmwares
Let us know the results.
I uninstalled/cleaned and reloaded the drivers you outlined just to see if any of those would make a difference. It appears that my computer is performing better as I've always wondered why I've had USB/Driver issues, BUT..... When I tried out sleep mode again I did get another blue screen. You're right, it isn't necessary to use Sleep Mode and shutting the system down doesn't effect anything either, however I want my computer to work regardless instead of having to do some work-around.
Hopefully this log report will have the crash on it: Attachment Attachment 272896
A sleep related BSOD is a stop 0x9f, which is software/driver specific, and for that reason it is not possible to debug perfectly without a crash dump. Unfortunately your latest zip does not contain any crash dump, too.
In that situation, I would suggest you follow post #4 again, to configure crash dump recording during a BSOD. And dont use any disc cleaner program until you upload another zip.
Sleep/hibernate is not necessary for a desktop PC at all. Sleep/hibernate is useful for mobile computers (notebook/netbook/laptop) which run on battery. So you can disable sleep/hibernate without any hesitation.
Hibernate - Enable or Disable
If this is of any particular use to you when the system does crash often times, if not always, the computer cannot find the Main HD. It will see the External Drives connected by USB, but not the Internal Main HD. I have to go into BIOS and either disable Primary, reboot several times or power down the computer for several minutes, reboot, then the BIOS will see the Drive when POSTing.
I'm not sure if that somehow clears the Dump Files? You're right, I don't "have" to use sleep mode, but its one of those sticklers where I simply want my computer to work correctly regardless of what I do, it should work and has worked fine out of sleep mode in the two years I've had it. I do appreciate all your help, if this log doesn't have any useful information then we'll just considered this resolved as I don't want to use up any more of your time. Attachment 272983
I know. And that's why I suggested to uninstall Marvell, and update JMicron. But it seems that it did not help. It's clear that the Internal HDD, 1 TB Seagate, is having a controller error during sleep.
But which controller is actually in use (mv91xx.sys, jraid.sys, intelide.sys and pciide.sys, all are installed and active; so without the crash dump it is difficult to determine).Event[763]:
Log Name: System
Source: atapi
Date: 2013-04-26T12:55:38.878
Event ID: 11
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: RW-PC
Description:
The driver detected a controller error on \Device\Ide\IdePort0.
Now, do two more things. The internal HDD, which is connected to a SATA port on the motherboard, remove the cable from the motherboard's end and apply to another port. Also you may use a new SATA cable.
Coming to the other thing a bit later.
Coz, in your case it is the storage controllers are being late to response when you resume the computer from sleep. And here is the result.
This log also does not have any crash dump. But you are here to get some assistance, and we will not mind to try to help you to get a clue.Event[765]:
Log Name: System
Source: Disk
Date: 2013-04-26T12:59:51.661
Event ID: 15
Task: N/A
Level: Error
Opcode: N/A
Keyword: Classic
User: N/A
User Name: N/A
Computer: RW-PC
Description:
The device, \Device\Harddisk0\DR0, is not ready for access yet.
Two years is some time. Hardware depreciates. Controller drivers get old. So it is obvious that it will not serve as a new machine does. But it should be fixed.
If you disable sleep, you will not loss anything. It's the right practice to not put the desktop to sleep. Sleep is for portable computers only, but the OS mechanism is present in all the computers. Still, take care of the HDD particularly.
Follow Power Plan Settings - Change . When you are at step 5, Expand "Hard Disc" > "Turn off hard disc after" > Setting (minutes) > put it to never (0). Apply > OK.
Attachment 273014
Also Seatool for dos: SeaTools | Seagate download. Burn it in a blank cd. boot from the CD, click on "Accept", wait for it to finish detecting the drives, then in the upper left corner select "Basic Tests", then select "Long Test" and let it run. The long test will take a timee, and if there are any corruption, it will attempt to recover it.
Let us know the results.
Arc, the HD "Passed" all testing, "However", prior to the conclusion SeaTools couldn't find the HD. I benched the unit, reseated the cables (in the same ports), hooked the unit back up and No Power. Benched it again, reseated everything, hooked it back up, No Power.
Out of frustration I ran it over to Best Buy. They popped the case open and the tech said "we don't have a power supply that big". I said, well, take out the GPU as it uses the most power and see what happens (which is what I should have done as part of Minimal Trouble shooting). He took the GPU out and the unit fired right up, we repeated this twice and the Video Card was bad.
So, I bought a new GPU (EVGA 660ti), as that was the best card they had in stock (at the time). Brought the unit home, installed the GPU, hooked everything up and the computer "could not" find the HD! Benched it again, moved the SATA and HD Power Cable into a different port(s), reconnected everything and the computer found the HD right away.
Thus far whether rebooting or shutting down and or connecting the USB Externals the computer see's the HD every time. I'm not even going to mess with Sleep Mode. I'm half thinking manually powering down the unit messed the Video Card up. Now that it has the new card and the HD is plugged into new ports, the computer seems a lot more responsive and snappy-er.
Its possible that the bad GPU was disrupting power flow and affecting all the components?
Quote