BSOD error message DRIVER_POWER_STATE_FAILURE

edpring · 25 Mar 2012

This is not from my current system, but another system. If the submission must be made from the system that created the minidump, please let me know.

This dump is from a Win 7 Pro (OEM and only O/S), HP Desktop, 64 bit system. It randomly occurs and probably on average of every 3 days.

I have attached the last minidump file..

Any help would be greatly appreciated.

Ed Pring

usasma · 25 Mar 2012

MSINFO32 shows issues with a PS2 mouse. If you're using a USB mouse it's safe to ignore this error.

MSINFO32 shows issues with CPU-Z 133. Please uninstall it from your system.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on Win7 systems (mostly due to the sptd.sys driver).
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

The BSOD blames Texas Instruments USB 3.0 Host Drivers - please:
- download a fresh copy of the drivers from the PC Manufacturer's website
- uninstall the current drivers from the system
- install the fresh copy
- monitor for further BSOD's

Acronis dates from 2007. Older versions (such as this) are known to cause BSOD's on Win7 systems. Please uninstall it immediately.

Your Diagnostic Interface x64 Driver for a USB modem dates from 2007. If this is a wireless USB device, Win7 doesn't like them - especially with older drivers and it will BSOD in a hearbeat! Here's my rant on these devices:

I do not recommend using wireless USB devices. Especially in Win7 systems.
These wireless USB devices have many issues with Win7 - and using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Regardless of what the device is, the driver dates from 2007 and MUST BE UPDATED
If not updated, then it must be uninstalled and the device physically removed from the system.

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

Code:


atikmpag.sys    Mon Oct 24 00:40:06 2011 (4EA4EC26)
PxHlpa64.sys    Tue Jun 23 19:16:35 2009 (4A416253)
ACFVA64.sys     Wed Sep 02 16:26:15 2009 (4A9ED4E7)
iaStor.sys      Sat Nov 06 03:44:52 2010 (4CD50774)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
snapman.sys     Thu Nov 22 03:19:33 2007 (47453B95)
tdrpman.sys     Mon Nov 12 08:36:33 2007 (473856E1)
timntr.sys      Wed Aug 29 08:38:23 2007 (46D568BF)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
btwampfl.sys    Thu Jan 05 18:14:07 2012 (4F062EBF)
tifsfilt.sys    Wed Aug 29 08:37:29 2007 (46D56889)
btwavdt.sys     Wed Dec 14 16:30:32 2011 (4EE91578)
btwaudio.sys    Thu Jan 05 19:43:37 2012 (4F0643B9)
btwl2cap.sys    Sat Aug 27 18:58:52 2011 (4E5976AC)
btwrchid.sys    Wed Dec 14 16:31:21 2011 (4EE915A9)
HCW85BDA.sys    Thu Sep 29 11:20:41 2011 (4E848CC9)
ACFDCP64.sys    Wed Apr 29 14:21:42 2009 (49F89AB6)
usbser.sys      Sat Nov 20 05:43:57 2010 (4CE7A66D)
netr28x.sys     Tue Feb 15 08:37:50 2011 (4D5A81AE)
tihub3.sys      Fri Jan 14 15:35:41 2011 (4D30B39D)
Rt64win7.sys    Wed Dec 29 06:44:36 2010 (4D1B1F24)
tixhci.sys      Fri Jan 14 15:35:26 2011 (4D30B38E)
hcw85cir3.sys   Thu Sep 29 11:20:14 2011 (4E848CAE)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
stwrt64.sys     Fri Jun 10 03:41:46 2011 (4DF1CABA)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
atikmdag.sys    Mon Oct 24 01:12:50 2011 (4EA4F3D2)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
MpNWMon.sys     Wed Apr 06 16:07:23 2011 (4D9CC7FB)
ACFSDK64.sys    Thu Mar 15 19:08:46 2007 (45F9D1FE)
npf.sys         Fri Jun 25 12:50:58 2010 (4C24DE72)
ACFXAU64.sys    Wed Apr 29 14:21:34 2009 (49F89AAE)
mbam.sys        Wed Nov 02 09:07:48 2011 (4EB140A4)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-42401-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 24 00:25:00.945 2012 (UTC - 4:00)
System Uptime: 2 days 3:29:06.788
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b776cd0 fffff800`00b9c3d8 fffffa80`0d7cb010
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

edpring · 25 Mar 2012

usasma,

Thanks much for the quick response. Will get to work on his system and report back.

Regards

edpring

edpring · 26 Mar 2012

usasma,

On the original post, I mentioned that this minidump was not from my system. However, when I created the zip file Windows_NT6_BSOD_jcgriff2, I created it on my system using the minidump from another system. I am not sure what data and from where the zip file Windows_NT6_BSOD_jcgriff2 gathers its information.

IF...this is an isssue, I can now send everything to you from the "offending system". His network was down at the time, but I now have it back up. If what I did was in error, I appologize...just let me know.

edpring

usasma · 27 Mar 2012

If the jcgriff2 came from another system, then the first 3 paragraphs pertain to that system (up to and including the stuff about Daemon Tools) - everything else pertains to the memory dump

Just FYI, I first start the memory dumps running, then I look at:
- perfmon /report
- systeminfo.txt
- MSINFO32 - Disks, Problem Devices, Error Reporting, Startup Items, and Program Groups (sometimes look at network adapters and drivers depending on what shows up).

edpring · 29 Mar 2012

John,
I worked with some of the things you recommended in your response. However, many of the files listed I could not find in windows/system32 folder. What I have decided to do is - what I should have done in the first place - I am sending the minidumps from the machine that created the BSODs. Please take a look at these and let me know what to do with his system.

Your help is very much appreciated.

edpring

usasma · 30 Mar 2012

Where do the rest of the reports come from? If they're from the problem machine, then they may have significant info about the problem.

Here's my evaluation of the memory dumps. I did not include any of the other reports as I'm not sure where they're from.

Most of the BSOD's blame tihub3.sys - a driver component of your Texas Instruments USB 3.0 Host Drivers.
Please visit the HP website for these drivers. I can't seem to easily locate them at the TI website.
- download a fresh copy of the drivers
- uninstall the current drivers
- install the fresh copy
- monitor for further BSODs

The earlier BSOD's blame Rt64win7.sys - a driver component of your Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC. Please visit the Realtek website for these drivers: Realtek
- uninstall the current drivers
- install the fresh copy
- monitor for further BSODs

I'm running late, so I may redo some stuff here....

Make sure to uninstall the Acronis True Image stuff. It's older and it can cause BSOD's

Conexant Modem drivers date from 2007, they need to be updated also.

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

Code:


PxHlpa64.sys    Tue Jun 23 19:16:35 2009 (4A416253)
iaStor.sys      Sat Nov 06 03:44:52 2010 (4CD50774)
amdxata.sys     Fri Mar 19 12:18:18 2010 (4BA3A3CA)
hcw85cir3.sys   Thu Sep 29 11:20:14 2011 (4E848CAE)
AtihdW76.sys    Wed Nov 17 07:02:04 2010 (4CE3C43C)
tixhci.sys      Fri Jan 14 15:35:26 2011 (4D30B38E)
atikmpag.sys    Mon Oct 24 00:40:06 2011 (4EA4EC26)
timntr.sys      Wed Aug 29 08:38:23 2007 (46D568BF)
tdrpman.sys     Mon Nov 12 08:36:33 2007 (473856E1)
snapman.sys     Thu Nov 22 03:19:33 2007 (47453B95)
MpFilter.sys    Wed Apr 06 16:07:29 2011 (4D9CC801)
HCW85BDA.sys    Thu Sep 29 11:20:41 2011 (4E848CC9)
btwampfl.sys    Thu Jan 05 18:14:07 2012 (4F062EBF)
Rt64win7.sys    Wed Dec 29 06:44:36 2010 (4D1B1F24)
netr28x.sys     Tue Feb 15 08:37:50 2011 (4D5A81AE)
HECIx64.sys     Tue Oct 19 19:33:43 2010 (4CBE2AD7)
atikmdag.sys    Mon Oct 24 01:12:50 2011 (4EA4F3D2)
btwaudio.sys    Thu Jan 05 19:43:37 2012 (4F0643B9)
btwl2cap.sys    Sat Aug 27 18:58:52 2011 (4E5976AC)
btwrchid.sys    Wed Dec 14 16:31:21 2011 (4EE915A9)
tifsfilt.sys    Wed Aug 29 08:37:29 2007 (46D56889)
btwavdt.sys     Wed Dec 14 16:30:32 2011 (4EE91578)
tihub3.sys      Fri Jan 14 15:35:41 2011 (4D30B39D)
ACFDCP64.sys    Wed Apr 29 14:21:42 2009 (49F89AB6)
usbser.sys      Sat Nov 20 05:43:57 2010 (4CE7A66D)
ACFVA64.sys     Wed Sep 02 16:26:15 2009 (4A9ED4E7)
stwrt64.sys     Fri Jun 10 03:41:46 2011 (4DF1CABA)
ACFXAU64.sys    Wed Apr 29 14:21:34 2009 (49F89AAE)
cpuz135_x64.sys Wed Sep 21 04:23:41 2011 (4E799F0D)
MpNWMon.sys     Wed Apr 06 16:07:23 2011 (4D9CC7FB)
ACFSDK64.sys    Thu Mar 15 19:08:46 2007 (45F9D1FE)
npf.sys         Fri Jun 25 12:50:58 2010 (4C24DE72)
mbam.sys        Wed Nov 02 09:07:48 2011 (4EB140A4)
atikmpag.sys    Thu Jan 13 22:31:00 2011 (4D2FC374)
atikmdag.sys    Thu Jan 13 23:06:38 2011 (4D2FCBCE)
stwrt64.sys     Thu Jan 27 02:58:55 2011 (4D4125BF)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032612-16286-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Mon Mar 26 09:11:06.616 2012 (UTC - 4:00)
System Uptime: 2 days 8:44:37.459
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0bacccd0 fffff800`00b9c3d8 fffffa80`09ed1b40
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032412-42401-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 24 00:25:00.945 2012 (UTC - 4:00)
System Uptime: 2 days 3:29:06.788
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b776cd0 fffff800`00b9c3d8 fffffa80`0d7cb010
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\032012-30919-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Tue Mar 20 09:51:38.101 2012 (UTC - 4:00)
System Uptime: 2 days 0:19:51.944
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0c6c0ab0 fffff800`044fe3d8 fffffa80`10e79260
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031812-15834-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Sat Mar 17 20:30:55.396 2012 (UTC - 4:00)
System Uptime: 3 days 12:56:23.239
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b554cd0 fffff800`00b9c3d8 fffffa80`0faabab0
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031412-22885-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Wed Mar 14 01:53:23.121 2012 (UTC - 4:00)
System Uptime: 0 days 4:07:06.964
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b338870 fffff800`00b9c3d8 fffffa80`117d86e0
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\031112-26020-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Mar 11 19:57:39.801 2012 (UTC - 4:00)
System Uptime: 2 days 21:35:23.644
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0c1278d0 fffff800`00b9c3d8 fffffa80`0fc1fa80
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\030812-23493-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Thu Mar  8 21:11:24.543 2012 (UTC - 4:00)
System Uptime: 2 days 19:43:28.387
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b40b740 fffff800`00b9c3d8 fffffa80`119ff010
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\030512-23072-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Mon Mar  5 15:52:44.724 2012 (UTC - 4:00)
System Uptime: 1 days 21:32:07.567
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b9d9cd0 fffff800`040ff3d8 fffffa80`1179b6c0
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\030212-40825-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Mar  2 08:49:53.490 2012 (UTC - 4:00)
System Uptime: 2 days 23:04:52.333
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b96d550 fffff800`00b9c3d8 fffffa80`0e9c2b60
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022812-18096-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Feb 28 09:42:44.381 2012 (UTC - 4:00)
System Uptime: 0 days 8:37:07.224
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b7648c0 fffff800`00b9c3d8 fffffa80`0a258010
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\022512-54319-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Feb 25 10:53:18.438 2012 (UTC - 4:00)
System Uptime: 3 days 13:13:23.170
*** WARNING: Unable to verify timestamp for btwampfl.sys
*** ERROR: Module load completed but symbols could not be loaded for btwampfl.sys
*** WARNING: Unable to verify timestamp for tihub3.sys
*** ERROR: Module load completed but symbols could not be loaded for tihub3.sys
Probably caused by : tihub3.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_IMAGE_tihub3.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`0b5a5cd0 fffff800`00b9c3d8 fffffa80`07395010
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021012-19656-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb 10 19:26:39.579 2012 (UTC - 4:00)
System Uptime: 0 days 10:35:52.422
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07763060 fffff800`040f0748 fffffa80`0e264840
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\021012-16582-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Fri Feb 10 08:13:59.054 2012 (UTC - 4:00)
System Uptime: 0 days 6:50:21.897
Probably caused by : pci.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x9F
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x9F_3_Rt64win7_IMAGE_pci.sys
Bugcheck code 0000009F
Arguments 00000000`00000003 fffffa80`07823060 fffff800`00ba2748 fffffa80`0d33f5a0
BiosVersion = 7.09
BiosReleaseDate = 07/22/2011
CPUID:        "Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3392
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

edpring · 30 Mar 2012

John,

All of the dump files were from the same system. That is why I wanted to send you the files from his system. I did delete and refresh the TI USB Hub drivers. They were the same as installed, but it is a new refreshed set now. I plan to check TI directly to see if anything has been updated.

Thanks for your help and time...

edpring

usasma · 31 Mar 2012

I think that the confusion here is that you uploaded more than just memory dump files.
In particular, I use the perfmon /report (if present), the systeminfo.txt report, and the MSINFO32.nfo report.

Here's what I got from them:

Dual Stream 802.11n Wireless LAN Card is disabled. Please:
- enable the card
- update the drivers
- disable the card, if so desired

I prefer that you uninstall the software/drivers for that card, and then physically remove the card from the system (if not using it). There's no need to leave it in the system (IMO), and leaving it in could leave in hardware and/or software problems - so removing it is better for troubleshooting.

CPU-Z has configuration issues. Please unininstall it. Then generate another perfmon /report to see if the errors are gone.

The WER section of MSINFO32 shows 17 memory dumps - and all blame Rt64win7.sys. This is a driver component of the software for your network card. Please visit the Realtek website and download/install the latest available version: Realtek
If you've already updated this, there's no need to do it again.

edpring · 08 Apr 2012

usasma,

Fixing the two major problems you pointed out, along with your other suggestions have now given me an error free and trouble free system. John, you are “da man”. Thank you very much for your quick and accurate responses. Your help is very much appreciated.
edpring

BSOD error message DRIVER_POWER_STATE_FAILURE

BSOD error message DRIVER_POWER_STATE_FAILURE

Possible misleading info...

Follow-up dump file

Other minidumps included...

Well Done!