Solved Recurring BSOD, error Locale ID 2057

[Amzadi]

Hi,

After approximately 15 mins of running my Laptop reboots without warning, when it comes back up it has the above BSOD error.
I have ran memtest86+ for 7 clean passes, I have also ran diskcheck, checked for Virus and Malware issues but found nothing.

I have also ran the computer in all three Safemodes without incident.

Unfortunatly I am now out of ideas and hoped you guys could help, the Laptop specs are:

Dell Inspiron N7010
Intel Core i3 M370 @ 2.4GHz
3GB RAM
320Gb HD
Windows 7 Home Premium 64-bit

The Additional Info provided by the unexpected shutdown window is as follows:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800633EA00
BCP3: FFFFF800042A3518
BCP4: FFFFFA8007149940
OS Version: 6_1_7601
Service pack: 1_0
Product: 768_1

I have also attached the requested files.

Regards,

 

[Skylais]

Hi all of the dumps point toward this : usbccgp.sys
This is a windows property, therefore it did not cause the actual problem most likely. Something else probably created this "usbccgp.sys" to occur.
As you said 15 minutes and then reboots, Well the dump also states this " A driver has failed to complete a power IRP within a specific time (usually 10 minutes)."
1.Try unplugging Your USB devices, and rebooting see if it will run for more than the usual time without a BSOD.
2. If BSOD still occur, then try removing all power. EX: laptop = remove the battery and ac adapter hold down the power button for about 15 seconds and drain the electricity charge out of the capacitors.
3. Use this link to find the latest drivers for your Dell : Drivers and Downloads | Dell [United States]
*There are 46 drivers on that page* I recommend, you start with the BIOS, Chipset, Removable storage, Video, Serial ATA, CPU.*
OR you can use the program on your computer called "Dell system software" to automatically check for you. If you cannot find dell system software download it here : Drivers and Downloads | Dell [United States]

 

[Amzadi]

Hi all of the dumps point toward this : usbccgp.sys
This is a windows property, therefore it did not cause the actual problem most likely. Something else probably created this "usbccgp.sys" to occur.
As you said 15 minutes and then reboots, Well the dump also states this " A driver has failed to complete a power IRP within a specific time (usually 10 minutes)."
1.Try unplugging Your USB devices, and rebooting see if it will run for more than the usual time without a BSOD.
2. If BSOD still occur, then try removing all power. EX: laptop = remove the battery and ac adapter hold down the power button for about 15 seconds and drain the electricity charge out of the capacitors.
3. Use this link to find the latest drivers for your Dell : Drivers and Downloads | Dell [United States]
*There are 46 drivers on that page* I recommend, you start with the BIOS, Chipset, Removable storage, Video, Serial ATA, CPU.*
OR you can use the program on your computer called "Dell system software" to automatically check for you. If you cannot find dell system software download it here : Drivers and Downloads | Dell [United States]

There were no USB devices connected, I drained the charge from the capacitors and have updated the driver's from the dell website but it still reboots.

Is there anything else I could try?

Regards,

 

[FredeGail]

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:

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

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
[COLOR=#00B050]Arg4: fffffa8005889940, The blocked IRP[/COLOR]

Debugging Details:

Let's get all the dirt:

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
[COLOR=#00B050]IoStatus.Status = c00000bb[/COLOR]
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 [COLOR=#00B050]fffffa800627ea00[/COLOR] 00000000 fffff8800183ffd4-fffffa8002426660 Success Error Cancel 
           [COLOR=#00B050]\Driver\usbccgp    ks!CKsDevice::CompleteDevicePowerIrp[/COLOR]
            Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0  1 fffffa800242d630 00000000 00000000-00000000    pending
           [COLOR=#00B050]\Driver\usbvideo[/COLOR]
            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.

0: kd> !devobj fffffa800627ea00
Device object (fffffa800627ea00) is for:
 [COLOR=Red]Cannot read info offset from nt!ObpInfoMaskToOffset[/COLOR]
 \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.

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 [COLOR=Red]edevmon.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR=Red]edevmon.sys
 \Driver\edevmon[/COLOR]
AttachedTo (Lower) fffffa80023e9520Unable to load image [COLOR=Red]\SystemRoot\system32\DRIVERS\CtClsFlt.sys, Win32 error 0n2[/COLOR]
*** WARNING: Unable to verify timestamp for [COLOR=Red]CtClsFlt.sys[/COLOR]
*** 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.

 

[Amzadi]

Thank you for the help, I disabled the creative driver first (turns out the creative driver was crashing my Laptop before Eset could at 21mins of running).

I tried uninstalling and reinstalling Eset and it has been stable so far. I have not done anything further with the creative driver hower.

 

[FredeGail]

Great job, let's see how it turns out.

Best Regards,
Frederik.