New
#1
BSOD while typing a term paper
Good thing OOo saves automatically.
Can anyone shed some light on this mini dump for me?
Thanks,
6027
Good thing OOo saves automatically.
Can anyone shed some light on this mini dump for me?
Thanks,
6027
That dmp tells me that a driver caused the issue. However, I can't tell which one.
If that is the only BSOD you have gotten, I wouldn't worry about it. If it happens again, upload the new dmp and we'll take a look.
Code:Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Jonathan\AppData\Local\Temp\Temp2_dmp 42410.zip\042410-127484-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 7600.16539.amd64fre.win7_gdr.100226-1909 Machine Name: Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e43e50 Debug session time: Sat Apr 24 07:30:24.058 2010 (GMT-4) System Uptime: 1 days 3:49:05.806 Loading Kernel Symbols ............................................................... ................................................................ .......................... Loading User Symbols Loading unloaded module list .......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000009F, {4, 258, fffffa8003cf3680, fffff80000b9c510} Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8003cf3680, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c510 Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: fffffa8003cf3680 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002c7d752 to fffff80002c7c4da STACK_TEXT: fffff880`031fc590 fffff800`02c7d752 : fffffa80`03cf3680 fffffa80`03cf3680 00000000`00000000 00000000`0000000d : nt!KiSwapContext+0x7a fffff880`031fc6d0 fffff800`02c79c4b : fffff8a0`0b7f0b00 00000000`00000200 fffffa80`00000000 00000000`00000066 : nt!KiCommitThreadWait+0x1d2 fffff880`031fc760 fffff800`02ee44bc : fffffa80`00000003 fffff880`031fca68 00000000`00000001 fffff8a0`00000000 : nt!KeWaitForMultipleObjects+0x271 fffff880`031fca10 fffff800`03017f99 : 00000000`00000000 fffffa80`0de1d010 fffff8a0`078e7710 00000000`00000000 : nt!PnpNotifyUserMode+0x158 fffff880`031fca90 fffff800`030f0f61 : 00000000`00000000 00000000`00000000 fffff8a0`078e7710 00000000`00000000 : nt!PnpNotifyUserModeDeviceRemoval+0x49 fffff880`031fcae0 fffff800`030f169c : fffff880`031fccb8 00000000`00000000 fffff8a0`0752f300 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xb51 fffff880`031fcc20 fffff800`02fdc73c : 00000000`00000000 fffffa80`044f5cf0 fffff8a0`078e7710 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`031fcc50 fffff800`02c83861 : fffff800`02ee2e80 fffff8a0`078e7710 fffff800`02e1b5f8 fffffa80`03cf3680 : nt! ?? ::NNGAKEGL::`string'+0x592eb fffff880`031fccb0 fffff800`02f1ba86 : 20f007cc`008070cf fffffa80`03cf3680 00000000`00000080 fffffa80`03c719e0 : nt!ExpWorkerThread+0x111 fffff880`031fcd40 fffff800`02c54b06 : fffff880`009f1180 fffffa80`03cf3680 fffff880`009fbf40 78e08740`2020c4c1 : nt!PspSystemThreadStartup+0x5a fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .thread 0xfffffa8003cf3680 ; kb FOLLOWUP_IP: nt!KiSwapContext+7a fffff800`02c7c4da 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: 4b88cfeb FAILURE_BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8003cf3680, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c510 Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: fffffa8003cf3680 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002c7d752 to fffff80002c7c4da STACK_TEXT: fffff880`031fc590 fffff800`02c7d752 : fffffa80`03cf3680 fffffa80`03cf3680 00000000`00000000 00000000`0000000d : nt!KiSwapContext+0x7a fffff880`031fc6d0 fffff800`02c79c4b : fffff8a0`0b7f0b00 00000000`00000200 fffffa80`00000000 00000000`00000066 : nt!KiCommitThreadWait+0x1d2 fffff880`031fc760 fffff800`02ee44bc : fffffa80`00000003 fffff880`031fca68 00000000`00000001 fffff8a0`00000000 : nt!KeWaitForMultipleObjects+0x271 fffff880`031fca10 fffff800`03017f99 : 00000000`00000000 fffffa80`0de1d010 fffff8a0`078e7710 00000000`00000000 : nt!PnpNotifyUserMode+0x158 fffff880`031fca90 fffff800`030f0f61 : 00000000`00000000 00000000`00000000 fffff8a0`078e7710 00000000`00000000 : nt!PnpNotifyUserModeDeviceRemoval+0x49 fffff880`031fcae0 fffff800`030f169c : fffff880`031fccb8 00000000`00000000 fffff8a0`0752f300 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xb51 fffff880`031fcc20 fffff800`02fdc73c : 00000000`00000000 fffffa80`044f5cf0 fffff8a0`078e7710 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`031fcc50 fffff800`02c83861 : fffff800`02ee2e80 fffff8a0`078e7710 fffff800`02e1b5f8 fffffa80`03cf3680 : nt! ?? ::NNGAKEGL::`string'+0x592eb fffff880`031fccb0 fffff800`02f1ba86 : 20f007cc`008070cf fffffa80`03cf3680 00000000`00000080 fffffa80`03c719e0 : nt!ExpWorkerThread+0x111 fffff880`031fcd40 fffff800`02c54b06 : fffff880`009f1180 fffffa80`03cf3680 fffff880`009fbf40 78e08740`2020c4c1 : nt!PspSystemThreadStartup+0x5a fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .thread 0xfffffa8003cf3680 ; kb FOLLOWUP_IP: nt!KiSwapContext+7a fffff800`02c7c4da 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: 4b88cfeb FAILURE_BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_POWER_STATE_FAILURE (9f) A driver is causing an inconsistent power state. Arguments: Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp subsystem. Arg2: 0000000000000258, Timeout in seconds. Arg3: fffffa8003cf3680, The thread currently holding on to the Pnp lock. Arg4: fffff80000b9c510 Debugging Details: ------------------ DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: fffffa8003cf3680 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x9F PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff80002c7d752 to fffff80002c7c4da STACK_TEXT: fffff880`031fc590 fffff800`02c7d752 : fffffa80`03cf3680 fffffa80`03cf3680 00000000`00000000 00000000`0000000d : nt!KiSwapContext+0x7a fffff880`031fc6d0 fffff800`02c79c4b : fffff8a0`0b7f0b00 00000000`00000200 fffffa80`00000000 00000000`00000066 : nt!KiCommitThreadWait+0x1d2 fffff880`031fc760 fffff800`02ee44bc : fffffa80`00000003 fffff880`031fca68 00000000`00000001 fffff8a0`00000000 : nt!KeWaitForMultipleObjects+0x271 fffff880`031fca10 fffff800`03017f99 : 00000000`00000000 fffffa80`0de1d010 fffff8a0`078e7710 00000000`00000000 : nt!PnpNotifyUserMode+0x158 fffff880`031fca90 fffff800`030f0f61 : 00000000`00000000 00000000`00000000 fffff8a0`078e7710 00000000`00000000 : nt!PnpNotifyUserModeDeviceRemoval+0x49 fffff880`031fcae0 fffff800`030f169c : fffff880`031fccb8 00000000`00000000 fffff8a0`0752f300 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0xb51 fffff880`031fcc20 fffff800`02fdc73c : 00000000`00000000 fffffa80`044f5cf0 fffff8a0`078e7710 00000000`00000001 : nt!PnpProcessTargetDeviceEvent+0x4c fffff880`031fcc50 fffff800`02c83861 : fffff800`02ee2e80 fffff8a0`078e7710 fffff800`02e1b5f8 fffffa80`03cf3680 : nt! ?? ::NNGAKEGL::`string'+0x592eb fffff880`031fccb0 fffff800`02f1ba86 : 20f007cc`008070cf fffffa80`03cf3680 00000000`00000080 fffffa80`03c719e0 : nt!ExpWorkerThread+0x111 fffff880`031fcd40 fffff800`02c54b06 : fffff880`009f1180 fffffa80`03cf3680 fffff880`009fbf40 78e08740`2020c4c1 : nt!PspSystemThreadStartup+0x5a fffff880`031fcd80 00000000`00000000 : fffff880`031fd000 fffff880`031f7000 fffff880`031fc9f0 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: .thread 0xfffffa8003cf3680 ; kb FOLLOWUP_IP: nt!KiSwapContext+7a fffff800`02c7c4da 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: 4b88cfeb FAILURE_BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a BUCKET_ID: X64_0x9F_nt!KiSwapContext+7a Followup: MachineOwner ---------
Thanks
After it happened last night I updated my wireless driver because I was connected to wireless (usually I'm plugged in). It hasn't crashed yet so I'll hope for the best.