Help with DRIVER_POWER_STATE_FAILURE, caused by ntoskrnl.exe+7cc40

Craigg64 · 19 Feb 2012

HI

I have been experiencing DRIVER_POWER_STATE_FAILURE crashes lately caused by ntoskrnl.exe.

I originally thought I would reinstall W7 but that has not fixed the issue

I am using OEM W7 Professional x64

The CPU is a i7 2600
The PC is only no more than 2 yrs old.
I d have an old Canon scanner LiDE 100 that I expect is causing the problem. The PC was working fine for over a year until NOv 2011 and then started crashing. I reinstallled W7 all seamed to be fine util I loaded the software for the scanner. I have loaded the latest software from the canon site.

I hope some one can some one help me?
If it is the driver for the scanner, why now?
Cheers
Craig

usasma · 19 Feb 2012

I'm running a Dec, a Jan, and a Feb 2012 memory dump.

Atheros AR3011 Bluetooth (no firmware) device isn't installed. Please download and install the drivers from the PC Manufacturer's website.

The BSOD's blame the disks connected to your Marvell controller. This means that it's either the disk or the controller. To test the controller, switch the disks to another controller (most Asus boards have 2) and see if that helps. Don't forget to update the controller drivers. If any of the drives fail, backup your data IMMEDIATELY! There's no telling when the drive will fail.

To test the disk, start with these free diagnostics: HD Diagnostic
Test ALL hard drives!

Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs:
3RD PARTY DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please either update the older drivers from the device manufacturer's website - or uninstall 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.

Code:


nvhda64v.sys    Thu Nov 11 18:10:36 2010 (4CDC77EC)
iaStor.sys      Sat Nov 06 03:44:52 2010 (4CD50774)
nusb3hub.sys    Thu Sep 30 00:00:03 2010 (4CA40B43)
mv91xx.sys      Fri Aug 27 05:49:22 2010 (4C778A22)
mvxxmm.sys      Fri Aug 27 05:49:03 2010 (4C778A0F)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
aswTdi.SYS      Mon Nov 28 12:52:18 2011 (4ED3CA52)
aswSnx.SYS      Mon Nov 28 12:54:05 2011 (4ED3CABD)
dump_mvxxmm.sys Fri Aug 27 05:49:03 2010 (4C778A0F)
aswRdr.SYS      Mon Nov 28 12:52:20 2011 (4ED3CA54)
ElbyCDIO.sys    Thu Dec 16 17:58:13 2010 (4D0A9985)
aswSP.SYS       Mon Nov 28 12:53:57 2011 (4ED3CAB5)
GEARAspiWDM.sys Mon May 18 08:17:04 2009 (4A1151C0)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
aswMonFlt.sys   Mon Nov 28 12:52:10 2011 (4ED3CA4A)
aswFsBlk.SYS    Mon Nov 28 12:51:52 2011 (4ED3CA38)
RTKVHD64.sys    Tue Nov 02 07:25:59 2010 (4CCFF547)
dump_mv91xx.sys Fri Aug 27 05:49:22 2010 (4C778A22)
Rt64win7.sys    Mon Oct 25 05:33:07 2010 (4CC54ED3)
nvlddmkm.sys    Sat May 21 00:07:04 2011 (4DD73A68)
nvBridge.kmd    Fri May 20 23:58:23 2011 (4DD7385F)
nusb3xhc.sys    Thu Sep 30 00:00:03 2010 (4CA40B43)
AnyDVD.sys      Sun Dec 04 16:23:55 2011 (4EDBE4EB)
nvlddmkm.sys    Wed Feb 23 22:01:34 2011 (4D65CA0E)
nvBridge.kmd    Wed Feb 23 21:57:02 2011 (4D65C8FE)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021912-22136-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Feb 19 05:11:04.121 2012 (UTC - 5:00)
System Uptime: 0 days 1:12:55.964
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_mv91xx.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07546050 fffff800`00b9c3d8 fffffa80`07232620
BiosVersion = 1502
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\010212-21637-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Jan  1 19:32:35.019 2012 (UTC - 5:00)
System Uptime: 0 days 0:47:23.863
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_mv91xx.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07249050 fffff800`0467f3d8 fffffa80`0acd3010
BiosVersion = 1502
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\122611-21824-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Dec 26 01:35:44.140 2011 (UTC - 5:00)
System Uptime: 0 days 1:17:25.983
*** WARNING: Unable to verify timestamp for mv91xx.sys
*** ERROR: Module load completed but symbols could not be loaded for mv91xx.sys
Probably caused by : mv91xx.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_disk_IMAGE_mv91xx.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`092b2050 fffff800`00b9c3d8 fffffa80`071279d0
BiosVersion = 1502
BiosReleaseDate = 03/02/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3411
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Craigg64 · 20 Feb 2012

Thanks for the reply.
I am in the process of doing a low level scan with seatools. It is taking some time:) So far one HD has passed.
A bit of a dumb question, are you suggesting I update the windows drivers you have links for in your post?
Cheers
Craig

usasma · 20 Feb 2012

Nope, the list of drivers is just FYI. I only suggest updating the older drivers (from 2008 and earlier)

The list comes in handy when reviewing future memory dumps - as it's a concise summary of what we found in the memory dump analysis.