Shutdown Crash

severedsolo said:

few days ago, computer refused to shutdown, ie it just sat there saying "shutting down" and stayed there, i left it overnight, thinking it was just being a little slow, and in the morning it had restarted presumably following BSOD,

Iv attached the minidump, but WhoCrashed gave me this result:

Crash dumps are enabled on your computer.


On Wed 20/01/2010 02:07:16 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000009F (0x4, 0x258, 0xFFFFFA80021E5040, 0xFFFFF80000B9C510)
Error: Unknown
Dump file: C:\Windows\Minidump\012010-13790-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.



Conclusion
1 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

I think i have isolated the problem to Vmware Workstation and since i uninstalled it the problem seems to have gone away, this seems to have been a one off, but any further help would be appreciated

Hi and welcome

The crash was probably caused by tdx.sys which is part of your network driver.

I suggest downloading a fresh copy of the driver and re-installing it

Also run a system file check
type cmd in search>right click and run as admin>sfc /scannow

Let us know the results


Ken

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\012010-13790-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\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
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02858000 PsLoadedModuleList = 0xfffff800`02a95e50
Debug session time: Tue Jan 19 21:05:46.329 2010 (GMT-5)
System Uptime: 0 days 2:10:07.451
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa80021e5040, fffff80000b9c510}

Probably caused by : tdx.sys ( tdx!TdxPnpEventNotification+a7 )

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: fffffa80021e5040, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9c510

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


DRVPOWERSTATE_SUBCODE:  4

FAULTING_THREAD:  fffffa80021e5040

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800028d1052 to fffff800028cfdda

STACK_TEXT:  
fffff880`02fc6e10 fffff800`028d1052 : fffffa80`021e5040 fffffa80`021e5040 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x7a
fffff880`02fc6f50 fffff800`028d31af : ffffffff`ffffffff 00000000`00000000 fffff800`00000000 ffffffff`ffffffff : nt!KiCommitThreadWait+0x1d2
fffff880`02fc6fe0 fffff880`03bc0977 : 00000000`00000000 00000000`00000000 fffffa80`00208700 fffff6fc`40016d00 : nt!KeWaitForSingleObject+0x19f
fffff880`02fc7080 fffff880`016e25b5 : fffffa80`03cf4010 fffff880`0176d9a0 fffff880`01767fe0 fffff800`029fd2dd : tdx!TdxPnpEventNotification+0xa7
fffff880`02fc7100 fffff880`016ca196 : fffffa80`0488c010 fffff880`02fc72e8 00000000`00000000 fffff800`028e3fa0 : tcpip!IpFlcPnpEvent+0x95
fffff880`02fc7160 fffff880`0174034e : 00000000`c00000bb 00000000`00000002 fffff880`02fc72e0 fffff880`02fc72e0 : tcpip! ?? ::FNODOBFM::`string'+0x4d8a1
fffff880`02fc71d0 fffff880`01552668 : 00000000`c00000bb fffff6fc`40016d00 00000000`c00000bb fffff8a0`027b5c00 : tcpip!Fl48PnpEvent+0xe
fffff880`02fc7200 fffff880`0155380f : fffffa80`0488c8d0 00000000`00000002 00000000`00000000 fffff880`01515101 : ndis!ndisPnPNotifyBinding+0xb8
fffff880`02fc7290 fffff880`01537792 : fffffa80`00000000 00000000`00000000 fffffa80`043ab500 00000000`00000000 : ndis!ndisPnPNotifyAllTransports+0x18f
fffff880`02fc7400 fffff880`01537760 : fffffa80`0487cc90 fffffa80`03bf51a0 fffffa80`043ab5a0 fffff880`02fc7560 : ndis!NdisFNetPnPEvent+0xd2
fffff880`02fc7440 fffff880`01537760 : fffffa80`043ab5a0 fffffa80`03bf51a0 fffffa80`0485dc90 fffff880`02fc7560 : ndis!NdisFNetPnPEvent+0xa0
fffff880`02fc7480 fffff880`01537760 : fffffa80`0485dc90 fffffa80`03bf51a0 fffffa80`04397230 fffff880`02fc7560 : ndis!NdisFNetPnPEvent+0xa0
fffff880`02fc74c0 fffff880`02db806b : fffff880`02fc7560 00000000`00000000 fffff880`02dbf110 fffffa80`043d7310 : ndis!NdisFNetPnPEvent+0xa0
fffff880`02fc7500 fffff880`01503b68 : fffffa80`04397230 fffffa80`03bf51a0 fffffa80`03bf51a0 00000000`0000000d : vwififlt!FilterNetPnPEvent+0x53
fffff880`02fc7530 fffff880`0155f227 : 00000000`00000000 fffffa80`03bf51a0 fffffa80`02df2290 00000000`00000017 : ndis!ndisDevicePnPEventNotifyFiltersAndAllTransports+0x128
fffff880`02fc7630 fffff880`00eb5df0 : 00000000`00000000 fffffa80`02df2480 fffffa80`03ea7040 00000000`00000000 : ndis! ?? ::LNCPHCLB::`string'+0x753a
fffff880`02fc76d0 fffff880`00eb5d84 : 00000000`00000000 00000000`00000400 00000000`00000000 fffffa80`03bf6b60 : Wdf01000!FxPkgFdo::_PnpPassDown+0x60
fffff880`02fc7700 fffff880`00eb7258 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`021e6148 : Wdf01000!FxPkgFdo::FireAndForgetIrp+0x20
fffff880`02fc7730 fffff880`00eb5e54 : fffffa80`02df2290 fffffa80`03bf6b60 00000000`c00000bb 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x208
fffff880`02fc77c0 fffff880`00eaddd6 : fffffa80`03d7bbd0 00000000`c00000bb 00000000`00000000 fffffa80`03bf6b60 : Wdf01000!FxPkgFdo::_PnpSurpriseRemoval+0x28
fffff880`02fc77f0 fffff880`00e7d245 : fffffa80`02df2290 fffffa80`02df2290 fffffa80`03ea7040 fffffa80`033d4060 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`02fc7860 fffff880`00e7d14b : 00000000`00000006 fffffa80`02df2290 00000000`c00000bb fffffa80`03ea7040 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`02fc7890 fffff800`02b35419 : fffffa80`03ea7040 00000000`c00000bb fffff880`02fc7988 fffffa80`02df2290 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`02fc78d0 fffff800`02cb3391 : fffffa80`033d4060 00000000`00000000 fffffa80`03d7d210 fffff880`02fc7968 : nt!IopSynchronousCall+0xc5
fffff880`02fc7940 fffff800`02cade08 : fffffa80`0499f920 fffffa80`033d4060 00000000`0000030a 00000000`00000308 : nt!IopRemoveDevice+0x101
fffff880`02fc7a00 fffff800`02cb2ed7 : fffffa80`03d7d210 00000000`00000000 00000000`00000003 00000000`0000004a : nt!PnpSurpriseRemoveLockedDeviceNode+0x128
fffff880`02fc7a40 fffff800`02cb2ff0 : 00000000`00000000 fffff8a0`09394100 fffff8a0`09212790 fffff880`02fc7b98 : nt!PnpDeleteLockedDeviceNode+0x37
fffff880`02fc7a70 fffff800`02d42f6f : 00000000`00000002 00000000`00000000 fffffa80`03d7d210 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`02fc7ae0 fffff800`02d43b2c : fffff880`02fc7cb8 fffffa80`036c7a00 fffffa80`021e5000 fffffa80`00000000 : nt!PnpProcessQueryRemoveAndEject+0x6cf
fffff880`02fc7c20 fffff800`02c2ec48 : 00000000`00000000 fffffa80`036c7a10 fffff8a0`0184a010 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`02fc7c50 fffff800`028d7161 : fffff800`02b34fc0 fffff8a0`093941d0 fffff800`02a6d5f8 fffff800`02a6d5f8 : nt! ?? ::NNGAKEGL::`string'+0x5abab
fffff880`02fc7cb0 fffff800`02b6d166 : 00000000`00000000 fffffa80`021e5040 00000000`00000080 fffffa80`021d0740 : nt!ExpWorkerThread+0x111
fffff880`02fc7d40 fffff800`028a8486 : fffff880`009e7180 fffffa80`021e5040 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fc7d80 00000000`00000000 : fffff880`02fc8000 fffff880`02fc2000 fffff880`02fc6d60 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .thread 0xfffffa80021e5040 ; kb

FOLLOWUP_IP: 
tdx!TdxPnpEventNotification+a7
fffff880`03bc0977 448b03          mov     r8d,dword ptr [rbx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tdx!TdxPnpEventNotification+a7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tdx

IMAGE_NAME:  tdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc16b

FAILURE_BUCKET_ID:  X64_0x9F_tdx!TdxPnpEventNotification+a7

BUCKET_ID:  X64_0x9F_tdx!TdxPnpEventNotification+a7

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

severedsolo said:

im getting fsv is not recognised as a valid command.... and you say tis linked to the network driver, so its likely my first thoughts were correct and that the VMware Network drivers were dodgy? as i said since unintalling the problems gone away

My apologies typo


correct is sfc /scannow

Ken