Hello and welcome to Sevenforums.
Updating System Specs will give us a better sight of
how your system is put together. It's simply done.§ Download
Speccy
§
|User CP (top of the page)| |Edit System Spec|
§
COPY & PASTE section to section
§ Include
Laptop, Desktop information
§ End with |
Save Changes|
BSOD Analyse
As Skylais nicely spotted, we're dealing with a blocked irp. IRP is basically a relation to the whole plug-in and plug-out management in the I/O section. In short, it's what sorts out your whole plugged in devices, and it'll deal with devices that wants to get plugged out. As far as I'm concerned, blocked IRP may also have relations and roots to drivers, but it's primarily devices.
Now let's take a look, your 'Probably Caused By'-line was pointing to a USB legacy driver -- as we covered:
Code:
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : usbccgp.sys
That's not too interesting. What's interesting is the blocked irp, which showed up in our bugcheck:
Code:
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: fffffa800627ea00, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8005889940, The blocked IRP
Debugging Details:
Let's get all the dirt:
Code:
0: kd> !irp fffffa8005889940 1
Irp is active with 21 stacks 18 is current (= 0xfffffa8005889ed8)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace.
Flags = 00000000
ThreadListEntry.Flink = fffffa8005889960
ThreadListEntry.Blink = fffffa8005889960
IoStatus.Status = c00000bb
IoStatus.Information = 00000000
RequestorMode = 00000000
Cancel = 00
CancelIrql = 0
ApcEnvironment = 00
UserIosb = 00000000
UserEvent = 00000000
Overlay.AsynchronousParameters.UserApcRoutine = 00000000
Overlay.AsynchronousParameters.UserApcContext = 00000000
Overlay.AllocationSize = 00000000 - 00000000
CancelRoutine = 00000000
UserBuffer = 00000000
&Tail.Overlay.DeviceQueueEntry = fffffa80058899b8
Tail.Overlay.Thread = 00000000
Tail.Overlay.AuxiliaryBuffer = 00000000
Tail.Overlay.ListEntry.Flink = fffff80002e3cb00
Tail.Overlay.ListEntry.Blink = fffff80002e3cb00
Tail.Overlay.CurrentStackLocation = fffffa8005889ed8
Tail.Overlay.OriginalFileObject = 00000000
Tail.Apc = 00000000
Tail.CompletionKey = 00000000
cmd flg cl Device File Completion-Context
Args: 00000000 00000000 00000000 00000000
>[ 16, 2] 0 e0 fffffa800627ea00 00000000 fffff8800183ffd4-fffffa8002426660 Success Error Cancel
\Driver\usbccgp ks!CKsDevice::CompleteDevicePowerIrp
Args: 00000000 00000001 00000001 00000000
[ 16, 2] 0 1 fffffa800242d630 00000000 00000000-00000000 pending
\Driver\usbvideo
Args: 00000000 00000001 00000001 00000000
[ 16, 2] 0 e1 fffffa80062818d0 00000000 00000000-00000000 pending
\Driver\ksthunk
Args: 00000000 00000001 00000001 00000000
[ 0, 0] 0 0 00000000 00000000 00000000-fffffa80063f9520
Args: 00000000 00000000 00000000 00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
0: kd> !error c00000bb
Error code: (NTSTATUS) 0xc00000bb (3221225659) - The request is not supported.
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Couple of things going on here, two USB related ones shows up. usbccgp and usbvideo. Let's see if we can get to see their driver/device.
Code:
0: kd> !devobj fffffa800627ea00
Device object (fffffa800627ea00) is for:
Cannot read info offset from nt!ObpInfoMaskToOffset
\Driver\usbccgp DriverObject fffffa8005a934b0
Current Irp 00000000 RefCount 2 Type 00000022 Flags 00003040
DevExt fffffa800627eb50 DevObjExt fffffa800627ef90 DevNode fffffa8006276c30
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000180) FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) fffffa800242d630 \Driver\usbvideo
Device queue is not busy.
Nothing special there. The ksthunk is quite interesting though.
Code:
0: kd> !devobj fffffa80062818d0
Device object (fffffa80062818d0) is for:
InfoMask field not found for _OBJECT_HEADER at fffffa80062818a0
\Driver\ksthunk DriverObject fffffa8005f92b80
Current Irp 00000000 RefCount 0 Type 0000002f Flags 00002040
DevExt fffffa8006281a20 DevObjExt fffffa8006281a28
ExtensionFlags (0x00000800) DOE_DEFAULT_SD_PRESENT
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) fffffa80023e9210*** WARNING: Unable to verify timestamp for edevmon.sys
*** ERROR: Module load completed but symbols could not be loaded for edevmon.sys
\Driver\edevmon
AttachedTo (Lower) fffffa80023e9520Unable to load image \SystemRoot\system32\DRIVERS\CtClsFlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for CtClsFlt.sys
*** ERROR: Module load completed but symbols could not be loaded for CtClsFlt.sys
\Driver\CtClsFlt
Device queue is not busy.
Interesting, more drivers popped up, attached to this device.* edevmon.sys - ESET
* CtClsFlt.sys - Creative Camera Class Upper Filter Driver
If you want to keep ESET, call their customer service and tell them the situation, however -- if you'd like to use a simple solution, go for Microsoft Security Essentials. It's free and bugless.
Create Camera -- update/uninstall/reinstall this driver.
Best Regards,
Frederik.