[Brennan C.]

Hello,

My system has bluescreened three times in about the last week or so; each time showed the same error: DRIVER_POWER_STATE_FAILURE. My system almost never bluescreened before this issue started happening. I wasn't doing anything particularly resource-intensive when my system crashed; just browsing the internet as I normally would before the crashes started. There's no new hardware or software to be causing it; it just seems to be random. I've got these two screencaps from BlueScreenView from the last two crashes:


The second screencap is the third one of these bluescreens to occur. In the first two, the crash address and caused-by driver were both at ntoskrnl.exe, but this third one was caused by Dnetr28ux.sys; it occurred at the same address as before, though.

My system specs are:
Operating System: MS Windows 7 64-bit SP1
CPU: AMD Phenom II X3 720 Heka 45nm Technology
RAM: 4.00 GB Dual-Channel DDR2 @ 401MHz (5-5-5-15)
Motherboard: Gigabyte Technology Co., Ltd. GA-MA790X-UD4P (Socket M2)
Graphics: SM2333T (1920x1080@60Hz) ATI Radeon HD 4800 Series (MSI)
Hard Drives: 625GB Western Digital WDC WD6401AALS-00L3B2 ATA Device (SATA) (2x)
Optical Drives: TSSTcorp CDDVDW SH-S223Q ATA Device
Audio: Realtek High Definition Audio
Browser: Google Chrome Version 24.0.1312.57 m

Thanks in advance for your help!

[Advertisements]

Brennan C

I will post the analysis shortly

Please do not post your problem, on another topic in future, for the reasons stated - on the topic where you did so.,

http://www.geekstogo...__fromsearch__1


Thanks for your co-operation.

Edited by Macboatmaster, 11 February 2013 - 07:18 PM.

[Macboatmaster]

Brennan C

I will post the analysis shortly

Please do not post your problem, on another topic in future, for the reasons stated - on the topic where you did so.,

http://www.geekstogo...__fromsearch__1


Thanks for your co-operation.

Edited by Macboatmaster, 11 February 2013 - 07:18 PM.

[Macboatmaster]

Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03459000 PsLoadedModuleList = 0xfffff800`0369d670
Debug session time: Mon Feb 11 15:37:53.319 2013 (UTC - 5:00)
System Uptime: 3 days 1:41:11.326
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80060b4a00, Physical Device Object of the stack
Arg3: fffff80000ba2748, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa80052e9b50, The blocked IRP

Debugging Details:
------------------

TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff88005784000 usbccgp

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME:FahCore_a4.exe

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00ba26f8 fffff800`035426d2 : 00000000`0000009f 00000000`00000003 fffffa80`060b4a00 fffff800`00ba2748 : nt!KeBugCheckEx
fffff800`00ba2700 fffff800`034e2c3c : fffff800`00ba2830 fffff800`00ba2830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33ac0
fffff800`00ba27a0 fffff800`034e2ad6 : fffff800`0367ff20 00000000`010377af 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00ba2810 fffff800`034e29be : 00000269`a2081a59 fffff800`00ba2e88 00000000`010377af fffff800`0364e868 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00ba2e60 fffff800`034e27a7 : fffff800`0364aec1 fffffa80`010377af fffffa80`04e77a30 00000000`000000af : nt!KiTimerExpiration+0x1be
fffff800`00ba2f00 fffff800`034db105 : 00000000`00000000 fffffa80`05e5bb50 00000000`00000000 fffff880`043a8db0 : nt!KiRetireDpcList+0x277
fffff800`00ba2fb0 fffff800`034daf1c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`097dabe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_lvuvc64_IMAGE_usbccgp.sys

BUCKET_ID: X64_0x9F_3_lvuvc64_IMAGE_usbccgp.sys

Followup: MachineOwner



I have highlighted in red the important points. It is related to a usb common class generic parent driver.

What do you have connected USB - printers are favourite to look at first - update the drivers.

Check device manager see if there are any warnings please on devices

The process name in red and large print - it can cover many things - HOWEVER have you overclocked please

Edited by Macboatmaster, 11 February 2013 - 06:09 PM.

[Brennan C.]

What do you have connected USB - printers are favourite to look at first - update the drivers.

Currently connected USB devices:

• Logitech webcam
• Logitech wireless mouse
• Microsoft wireless keyboard
• D-Link Wi-Fi adapter
• M-Audio FastTrack Pro audio card
• Standard miniUSB phone charger cable

I don't have a printer.

My system BSOD'd again while updating drivers for the receiver for my mouse; I imagine it's because the mouse is part of a wireless desktop (keyboard/mouse) combo. I've attached the dump for this latest BSOD to this post. After my system restarted, I tried installing the updates via Windows Update (instead of searching for updates via the control panel) and it returned Windows update error 80070103, which I Googled to find that I basically already have the correct or later drivers installed; I hid that update and everything is now up to date.

Check device manager see if there are any warnings please on devices

No warnings under any Device Manager headings.

The process name in red and large print - it can cover many things - HOWEVER have you overclocked please.

No, I have not overclocked.

Attached Files

•  021113-17004-01.zip   26.46KB   215 downloads

[Macboatmaster]

analysing these files is not a two minute job

I was just about to press the big switch

that FahCore_a4.exe

see if it running as a process please in task manager and then ascertain from there where it is and for what

the analysis of the latest dump will have to wait until I return at 1800 hrs UK

sorry about that

For now check for drivers for all possible on usb devices please, then try with all you can disconnected

Also try clean boot state and see if that solves the problem

Good luck back online as stated

Edited by Macboatmaster, 11 February 2013 - 08:36 PM.

[Macboatmaster]

Cannot stay really - should have gone just had another look at the crash analysis

Disconnect the webcam

Test system - think it may be the webcam

FAILURE_BUCKET_ID: X64_0x9F_3_lvuvc64_IMAGE_usbccgp.sys

[Brennan C.]

analysing these files is not a two minute job

I was just about to press the big switch

that FahCore_a4.exe

see if it running as a process please in task manager and then ascertain from there where it is and for what

FahCore_a4.exe is the executable portion of the Folding@Home client. I've been running F@H on this system for over a year with no previous issues.

Disconnect the webcam

Test system - think it may be the webcam

FAILURE_BUCKET_ID: X64_0x9F_3_lvuvc64_IMAGE_usbccgp.sys

As nothing I've knowingly done has made my system BSOD, I have no way to test. I'll unplug the webcam and let you know if anything happens.

[Macboatmaster]

FahCore_a4.exe is the executable portion of the Folding@Home client. I've been running F@H on this system for over a year with no previous issues.

As nothing I've knowingly done has made my system BSOD, I have no way to test. I'll unplug the webcam and let you know if anything happens.

When you say you have no way to test, disconnecting the webcam is a test. As is updating or changing drivers for it.

The crash unless it is a ram issue which we will test later or another hardware issue, which I view as unlikely, as you will have seen from the analysis is related to the usb and - the webcam or the Folding@Home Client.

It is not necessarily caused by anything YOU have done per se. A driver update, that windows 7 does not like can be the cause, as can a driver update that was corrupted.

Folding@Home Client - the fact you have been running it for a year does not mean that it is NOT now the cause of the crash., again not in itself by some other circumstances that Windows 7 does not like.

Edited by Macboatmaster, 13 February 2013 - 07:48 PM.

[Macboatmaster]

Brennan C



Re the other crash dump it is the same USB Fatal Time out loading driver

Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0344d000 PsLoadedModuleList = 0xfffff800`03691670
Debug session time: Mon Feb 11 20:40:19.317 2013 (UTC - 5:00)
System Uptime: 0 days 5:01:42.955
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000a, TimeoutCode
Arg4: fffffa80050427a0

*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: System

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff880056e7a60 to fffff800034cbfc0

STACK_TEXT:
fffff880`03169c18 fffff880`056e7a60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`0000000a : nt!KeBugCheckEx
fffff880`03169c20 fffff800`037be583 : fffffa80`04fb6050 00000000`00000001 ffffffff`dc3a58a0 fffff800`036692d8 : usbhub!UsbhHubProcessChangeWorker+0xec
fffff880`03169c80 fffff800`034d5641 : fffff800`03669200 fffff800`037be501 fffffa80`03a8f000 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`03169cb0 fffff800`03762e5a : 00000000`00000000 fffffa80`03a8f040 00000000`00000080 fffffa80`03a099e0 : nt!ExpWorkerThread+0x111
fffff880`03169d40 fffff800`034bcd26 : fffff880`02f64180 fffffa80`03a8f040 fffff880`02f6ef80 351b1d31`171b2d14 : nt!PspSystemThreadStartup+0x5a
fffff880`03169d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_IP:
usbhub!UsbhHubProcessChangeWorker+ec
fffff880`056e7a60 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbhub!UsbhHubProcessChangeWorker+ec

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: usbhub

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15

FAILURE_BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

BUCKET_ID: X64_0xFE_usbhub!UsbhHubProcessChangeWorker+ec

Followup: MachineOwner
---------



HOWEVER on this one do you have a USB hub connected.
I am wondering if the problem is the usb drivers rather than the camera.

Disconnect all USB devices

Device manager

USB root hubs check power management - set do not allow computer to turn off power to hub

also check for any driver updates and/or right click uninstall

Reboot computer will automatically reconfigure

Edited by Macboatmaster, 13 February 2013 - 08:04 PM.

[Brennan C.]

Instructions followed; I will advise if problems continue. Haven't had a another BSOD since the last incident.

[Macboatmaster]

Thanks for replying

Instructions followed; I will advise if problems continue.

It is always nice when it appears that we have managed to solve the problem, of course it is far too early to say yet

[Brennan C.]

We've got another one:

Dump attached.

Attached Files

•  021513-17862-01.zip   26.19KB   206 downloads

[Brennan C.]

And another one this morning; at least it says it was this morning, it just seemed to power on normally. I figure it probably happened last night, after I told it to "sleep", because it took much longer than usual to get to sleep. Dump attached. :-(

Attached Files

•  021713-18002-01.zip   134.43KB   206 downloads

[Brennan C.]

Just as I was thinking that it's been a little while since the last BSoD, I had another one this morning:


Are you still there, buddy?

Attached Files

•  022513-20841-01.zip   117.89KB   206 downloads

[narenxp]

Hi Brennan

kd> !irp fffffa8006b32c10
Irp is active with 9 stacks 7 is current (= 0xfffffa8006b32e90)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
Args: 00000000 00000000 00000000 00000002
>[ 16, 2] 0 1 fffffa8005d0ce10 00000000 00000000-00000000 pending
Unable to load image \SystemRoot\system32\DRIVERS\lvuvc64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for lvuvc64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvuvc64.sys
\Driver\LVUVC64
Args: 00041100 00000001 00000001 00000002
[ 16, 2] 0 e1 fffffa8005d11e30 00000000 fffff80003468750-fffffa80041a2110 Success Error Cancel pending
\Driver\ksthunk nt!IopUnloadSafeCompletion
Args: 00041100 00000001 00000001 00000002
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa80085394b0

SystemRoot\system32\DRIVERS\lvuvc64.sys is cause of the BSOD.You could try reinstalling your logitech webcam driver.I guess that you are receiving BSOD only when webcam is connected to the PC.