Šta je novo?

Windows 10 BSOD DRIVER_POWER_STATE_FAILURE (9f)

mdp

Cenjen
Učlanjen(a)
19.02.2014
Poruke
5
Poena
151
Installirao sam windows 10 (preko upgradea) na laptop i od tad malo malo pa se pojavi BSOD (DRIVER_POWER_STATE_FAILURE (9f)). U attachmentu je nekolicina minidump fajlova kao i izvestaj WinDbg-a za jedan od njih. Izvestaj pominje fajlove ntoskrnl.exe i usbccgp.sys. Da li neko zna o cemu se radi?


Kod:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [c:\windows\minidump\080115-8031-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
OK                                             c:\windows\installer

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\installer
Windows 8 Kernel Version 10240 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10240.16393.x86fre.th1_st1.150717-1719
Machine Name:
Kernel base = 0x82269000 PsLoadedModuleList = 0x824aaa38
Debug session time: Sat Aug  1 16:07:33.975 2015 (UTC + 2:00)
System Uptime: 0 days 0:39:43.890
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 88921030, 83993b30, 8e4c6008}

Probably caused by : usbccgp.sys

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 88921030, Physical Device Object of the stack
Arg3: 83993b30, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: 8e4c6008, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: 889250a8

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  559f3caa

MODULE_NAME: usbccgp

FAULTING_MODULE: 965e0000 usbccgp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

DPC_STACK_BASE:  FFFFFFFF83998000

STACK_TEXT:
83993b08 82450d3f 0000009f 00000003 88921030 nt!KeBugCheckEx
83993b4c 82450c4e 00000000 824a83d4 00000002 nt!PopIrpWatchdogBugcheck+0xeb
83993b60 822a8c59 97fde7b0 97fde768 69a15266 nt!PopIrpWatchdog+0x28
83993c18 822a87c5 83993c68 00000000 980f6780 nt!KiExecuteAllDpcs+0x209
83993d44 823a2960 00000000 92880414 00082054 nt!KiRetireDpcList+0xe5
83993d48 00000000 92880414 00082054 88026400 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.10240.16384

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_usbccgp.sys

BUCKET_ID:  0x9F_3_IMAGE_usbccgp.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_image_usbccgp.sys

FAILURE_ID_HASH:  {2240478d-2a07-44ce-f277-d13120a9d2d6}

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 88921030, Physical Device Object of the stack
Arg3: 83993b30, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: 8e4c6008, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: 889250a8

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  559f3caa

MODULE_NAME: usbccgp

FAULTING_MODULE: 965e0000 usbccgp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

DPC_STACK_BASE:  FFFFFFFF83998000

STACK_TEXT:
83993b08 82450d3f 0000009f 00000003 88921030 nt!KeBugCheckEx
83993b4c 82450c4e 00000000 824a83d4 00000002 nt!PopIrpWatchdogBugcheck+0xeb
83993b60 822a8c59 97fde7b0 97fde768 69a15266 nt!PopIrpWatchdog+0x28
83993c18 822a87c5 83993c68 00000000 980f6780 nt!KiExecuteAllDpcs+0x209
83993d44 823a2960 00000000 92880414 00082054 nt!KiRetireDpcList+0xe5
83993d48 00000000 92880414 00082054 88026400 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.10240.16384

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_usbccgp.sys

BUCKET_ID:  0x9F_3_IMAGE_usbccgp.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_image_usbccgp.sys

FAILURE_ID_HASH:  {2240478d-2a07-44ce-f277-d13120a9d2d6}

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

0: kd> !drvobj ffffffff889250a8 f
824a9260: Unable to get value of ObpRootDirectoryObject
824a9260: Unable to get value of ObpRootDirectoryObject
Driver object (889250a8) is for:
 \Driver\usbccgp
Driver Extension List: (id , addr)

Device Object list:
889c5748: Could not read device object


DriverEntry:   965fc006 usbccgp!GsDriverEntry
DriverStartIo: 00000000
DriverUnload:  965f8915 usbccgp!USBC_DriverUnload
AddDevice:     965f4fb0 usbccgp!USBC_AddDevice

Dispatch routines:
[00] IRP_MJ_CREATE                      965e25a0 usbccgp!USBC_Dispatch
[01] IRP_MJ_CREATE_NAMED_PIPE           823179fc nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE                       965e25a0 usbccgp!USBC_Dispatch
[03] IRP_MJ_READ                        823179fc nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE                       823179fc nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION           823179fc nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION             823179fc nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA                    823179fc nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA                      823179fc nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS               823179fc nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    823179fc nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION      823179fc nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL           823179fc nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         823179fc nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL              965e25a0 usbccgp!USBC_Dispatch
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     965e25a0 usbccgp!USBC_Dispatch
[10] IRP_MJ_SHUTDOWN                    823179fc nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL                823179fc nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP                     823179fc nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT             823179fc nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY              823179fc nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY                823179fc nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER                       965e25a0 usbccgp!USBC_Dispatch
[17] IRP_MJ_SYSTEM_CONTROL              965e25a0 usbccgp!USBC_Dispatch
[18] IRP_MJ_DEVICE_CHANGE               823179fc nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA                 823179fc nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA                   823179fc nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP                         965e25a0 usbccgp!USBC_Dispatch

0: kd> usbccgp.sysusbccgp.sysusbccgp.sysusbccgp.sys
       ^ Missing whitespace after u in 'usbccgp.sysusbccgp.sysusbccgp.sysusbccgp.sys'
 

Prilozi

  • Minidump.zip
    652.6 KB · Pregleda: 18
Neki prob sa driverima. Odradi clean install za prvi korak.
 
Napiši specifikaciju laptopa, model i komponente, pa da pokušamo za početak da nađemo najnovije drajvere za Win 10.

Ako si u prilici, odradi clean install i vidi kako se ponaša...

EDIT: r!sc, bio si brži. :)
 
Nazad
Vrh Dno