Sleep / Hibernate BSOD

[dangad]

Hey there,

I've seen a lot of threads like this one, but since it seems everyone has a different cause, I'm posting my info here

My laptop is about 3 weeks old
Windows 7 Home Premium 64 bits pre-installed

I'm sure it started happening after some update I did, or something I installed, since it wasn't happening on the first couple of weeks.

This error is sneeky... I'm not able to reproduce it every time I want.... It seems to only happen when It will make me most annoyed.

Attachment 1 is the error I get after it crashes, Attachment 2 is the most recent minidump thing, from earlier today.


Thanks for any help,

Dan

 

[dangad]

if you require any additional information, please let me know.

 

[usasma]

If it's 3 weeks old, see about returning it for a new one.
If not, then let's try gathering this info:
http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

The dump file that you uploaded is from a different crash than the screenshot.
The screenshot shows a STOP 0xA0 {0x9, 0xc000009c, 0x1, 0x0}
Info on this error is here: BSOD Index
And the parameters translate to an error while hibernating, due to a

STATUS_DEVICE_DATA_ERROR ((NTSTATUS)0xC000009C while it was mirroring the data.

​

So, I'd first suggest trying these free diagnostic tests:

I suggest starting all troubleshooting with the following diagnostic tests. They'll save you a lot of time and heartache if there is a hardware failure, and you'll have the disks on hand in case you need them in the future:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised: Free Online AntiMalware Scanners (read the details at the link)

Then comes the uploaded memory dump (a STOP 0x7F)
First, please do this:

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Please update these drivers from the device manufacturer's website - or uninstall/remove them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

[font=lucida console]
iaStor.sys      Sat Nov 06 03:44:52 2010 (4CD50774)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
Impcd.sys       Mon Oct 26 16:39:41 2009 (4AE6090D)
ehdrv.sys       Thu Dec 09 00:29:58 2010 (4D006956)
dump_iaStor.sys Sat Nov 06 03:44:52 2010 (4CD50774)
L1C62x64.sys    Fri Nov 27 02:47:56 2009 (4B0F842C)
SynTP.sys       Tue Jul 14 17:36:36 2009 (4A5CFA64)
rtl8192se.sys   Thu Apr 01 04:51:46 2010 (4BB45EA2)
nvhda64v.sys    Thu Nov 11 18:10:36 2010 (4CDC77EC)
RTKVHD64.sys    Mon Nov 16 05:52:27 2009 (4B012EEB)
btwampfl.sys    Wed Jan 20 15:55:10 2010 (4B576DAE)
TurboB.sys      Tue Sep 29 20:25:28 2009 (4AC2A578)
eamonm.sys      Thu Dec 09 00:29:20 2010 (4D006930)
epfwwfpr.sys    Thu Dec 09 00:26:09 2010 (4D006871)
[/font]

http://www.carrona.org/dvrref.html#iaStor.sys
http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#Impcd.sys
http://www.carrona.org/dvrref.html#ehdrv.sys
http://www.carrona.org/dvrref.html#dump_iaStor.sys
http://www.carrona.org/dvrref.html#L1C62x64.sys
http://www.carrona.org/dvrref.html#SynTP.sys
http://www.carrona.org/dvrref.html#rtl8192se.sys
http://www.carrona.org/dvrref.html#nvhda64v.sys
http://www.carrona.org/dvrref.html#RTKVHD64.sys
http://www.carrona.org/dvrref.html#btwampfl.sys
http://www.carrona.org/dvrref.html#TurboB.sys
http://www.carrona.org/dvrref.html#eamonm.sys
http://www.carrona.org/dvrref.html#epfwwfpr.sys

Then, if all this doesn't fix up the BSOD's - please run Driver Verifier according to these directions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

BSOD BUGCHECK SUMMARY

[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon Apr  4 08:41:36.226 2011 (UTC - 4:00)
System Uptime: 0 days 2:39:31.693
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
BUGCHECK_STR:  0x7f_8
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2
Bugcheck code 0000007F
Arguments 00000000`00000008 00000000`80050033 00000000`000006f8 fffff800`034d9e6f
BiosVersion = QL2L3I51
BiosReleaseDate = 01/06/2010
CPUID:        "Intel(R) Core(TM) i5 CPU       M 480  @ 2.67GHz"
MaxSpeed:     2670
CurrentSpeed: 2660
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[dangad]

now I wish I had done those tests earlier... logged in on my windows yesterday and everything was gone... softwares installed, files, everything everything but google chrome...(weirdly)...

since there wasn't really many things important to save there... I formated the whole thing and got windows reinstalled... It seems to be working as it should now, but the question is... Can I trust it? Is there any tests you think I should still run before going trough the trouble of getting a new one via warranty?

thanks for your help.

Dan.

 

[usasma]

The tests in the first QUOTE box are the most common hardware tests used for warranty work.

If you wiped and reinstalled, then wait to see if it gives further problems.
Don't install anything right now - just wait to see what happens.
After about a week, then carefully install a few essential things - and wait another week to see if it gives problems.
If not, then you should be OK.

Good luck!

 

[dangad]

did the Memory Diagnostics... It all ran ok... No errors there.

couldnt do HD ones tho... Toshiba HD... couldn't get the test to boot from the USB like I did with the memory test.

I heard from a friend that Everest has a HD test? True? Is it worth doing?

thanks,

Dan.

 

[usasma]

Try the Seagate Seatools and see if that'll work for you. I'm not familiar with the Everest HD test, but on the link above there's a description of HDTune - a freeware program that runs in Windows. But, if this is a hard drive problem, the bootable tests are the definitive diagnostic.

 

[dangad]

Seagate test worked... ran the quick one and the long boring one... both said that everything was OK with the HD... so I'm guessing this issue wasn't hardware related...

It really started happening after I did all the updates I could find for my drivers and from microsoft... I guess I'll start updating things slower now? .. well lets see what happens..

thanks for your help so far, I'll keep you posted.

 

[usasma]

Update all drivers from the system manufacturer's website. Even if they seem to be current, update them anyway.
Then update any programs that you may have installed (particularly antivirus/antispyware/fireswall programs), such as your NOD32.

The most common problem with Service Packs are:
- malware infections
- older (incompatible) 3rd party drivers

When a Service Pack first comes out, I don't suggest using the PC Manufacturer's website to update drivers. But after the Service Pack has been out for a couple of months the PC Manufacturer's usually have posted any new drivers that are needed - so it's OK to use then.

 

[dangad]

ok... new one happened today... scarred the crap out of me, cause It made the HD vanish for a good time... (HD wasn't recognized after boot... it simply said that there was no HD)

*photo of error on attachment*

sadly... no minidump file... no idea why.

weird thing is, I turned on the laptop an hour later... and it logged on windows, perfectly... no errors or anything...

I'm keeping this updated here, but I'm pretty sure I'll just take it to the tech support in a couple of days... maybe fighting against it isn't worth it hah!

again, thanks for your help so far.

 

[usasma]

The symptoms that you describe are either a hardware problem - or a virus.
Since you've reformatted, the most likely cause is a hardware problem - but a virus is possible also.

I'd suggest taking it in for warranty work and describe what you've already done.