Need help with BSOD

gladiusgg

Supremacy Member
Joined
May 2, 2011
Messages
7,114
Reaction score
35

tungsten2

Master Member
Joined
May 30, 2000
Messages
4,147
Reaction score
1
Basically your BSOD is caused by some driver. But I am not able to tell which driver.
Checked your dump file and here is the result :

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: fffffa8018b3cb50, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9a3d0, nt!TRIAGE_9F_PNP on Win7 and higher

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

Implicit thread is now fffffa80`18b3cb50

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: fffffa8018b3cb50

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

LOCK_ADDRESS: fffff800032cbda0 -- (!locks fffff800032cbda0)

Resource @ nt!PiEngineLock (0xfffff800032cbda0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff800032cbda0
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff800030c6802 to fffff800030c52aa

STACK_TEXT:
fffff880`033bd520 fffff800`030c6802 : fffffa80`18b3cb50 fffffa80`18b3cb50 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`033bd660 fffff800`030ca51f : ffffa13e`a647f910 fffffa80`1c371250 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x1d2
fffff880`033bd6f0 fffff800`03186d25 : fffff880`033bd700 fffffa80`00000000 fffffa80`18e54100 fffff800`03484e00 : nt!KeWaitForSingleObject+0x19f
fffff880`033bd790 fffff800`0346a20e : fffff800`032cbb60 fffff880`033bd864 00000000`00000000 00000000`00000001 : nt!PnpDeviceCompletionQueueGetCompletedRequest+0x35
fffff880`033bd7e0 fffff800`034aace8 : fffffa80`18e54130 fffffa80`18e54130 00000000`00000001 00000000`00000000 : nt!PnpDeviceCompletionProcessCompletedRequests+0x5e
fffff880`033bd810 fffff800`034ab198 : fffff800`032c9720 00000000`00000000 00000000`00000001 fffff800`0332c2f4 : nt!PipProcessDevNodeTree+0x378
fffff880`033bda80 fffff800`031c3de7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`033bdad0 fffff800`030cc6a5 : fffff800`031c3ac0 fffff800`033b8701 fffffa80`18b3cb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`033bdb70 fffff800`0335caba : 00000000`00000000 fffffa80`18b3cb50 00000000`00000080 fffffa80`18ac29e0 : nt!ExpWorkerThread+0x111
fffff880`033bdc00 fffff800`030b4426 : fffff880`03174180 fffffa80`18b3cb50 fffff880`0317f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`033bdc40 00000000`00000000 : fffff880`033be000 fffff880`033b8000 fffff880`033bd190 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .thread 0xfffffa8018b3cb50 ; kb

FOLLOWUP_IP:
nt!KiSwapContext+7a
fffff800`030c52aa 488d8c2400010000 lea rcx,[rsp+100h]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiSwapContext+7a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5507a73c

IMAGE_VERSION: 6.1.7601.18798

FAILURE_BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a

BUCKET_ID: X64_0x9F_4_nt!KiSwapContext+7a

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:x64_0x9f_4_nt!kiswapcontext+7a

FAILURE_ID_HASH: {988e0922-fc98-5cf6-5921-ee45c15cab37}

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


Need you to run the windbg from your machine. (and run the cmd highlighted in red)
As I am getting this msg:
kd> !locks fffff800032cbda0

Resource @ nt!PiEngineLock (0xfffff800032cbda0) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
 
Last edited:

gladiusgg

Supremacy Member
Joined
May 2, 2011
Messages
7,114
Reaction score
35
Thanks for ur help! I have updated all my drivers. Hopefully it solves the problem. Probably Bluetooth driver problem.
 

tungsten2

Master Member
Joined
May 30, 2000
Messages
4,147
Reaction score
1
If you believe it to be Bluetooth, definitely go ahead and disable that. See if the crashes continue

For your last 2nd dmp file, with this error :
rjik4n.png

There is a fix from microsoft : https://support.microsoft.com/en-us/kb/2675806
 
Last edited:
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top