View Single Post
04 Apr 2011  
Microsoft MVP


If it's 3 weeks old, see about returning it for a new one.
If not, then let's try gathering this info:

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:

- 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:

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)
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

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 )
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
My System SpecsSystem Spec