BSOD While Shutting Down

[Inferdramon]

Hello, for the past couple months, I've been, at random, experiencing a BSOD that only occurs when I am trying to shut down the computer. It has not occured any other time. And strange thing is, it doesn't always happen. Usually the computer shuts down just fine, but on occasion it crashes and reboots. I am only made aware of this the next day when I notice the computer is still on and I get a message telling me Windows recovered from an unexpected error.


Here's the information from my DUMP file of the incident.





Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\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`0741e000 PsLoadedModuleList = 0xfffff800`0765be50
Debug session time: Sun Jul 18 01:25:54.218 2010 (UTC - 4:00)
System Uptime: 0 days 15:17:12.121
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols

Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800522ebb0, fffff80000b9c4d8, fffffa80055a0e10}

*** ERROR: Module load completed but symbols could not be loaded for VMNetSrv.sys
Probably caused by : ntkrnlmp

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa800522ebb0, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa80055a0e10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88004901000 VMNetSrv

IRP_ADDRESS: fffffa80055a0e10

DEVICE_OBJECT: fffffa8006c67050

DRIVER_OBJECT: fffffa80068a4380

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

STACK_TEXT:
fffff800`00b9c488 fffff800`074fd1b3 : 00000000`0000009f 00000000`00000003 fffffa80`0522ebb0 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`0749a6a6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000004 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c530 fffff800`07499a26 : fffffa80`08a2f400 fffffa80`08a2f400 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`0749a57e : 00000080`21b34a27 fffff800`00b9cc18 00000000`0035d3fd fffff800`0760d228 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`07499d97 : 00000024`9ce74cc5 00000024`0035d3fd 00000024`9ce74c74 00000000`000000fd : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`07496dfa : fffff800`07608e80 fffff800`07616c40 00000000`00000000 fffff880`03d10588 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp

BUCKET_ID: X64_0x9F_3_IMAGE_ntkrnlmp

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

 

[Jonathan_King]

Welcome to SF!

Looks like VMware is causing the issue. Try removing it and see what happens.

If that doesn't work, please follow these instructions: http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[Inferdramon]

I don't have VMWare installed on this machine, however I do have VirtualBox and Microsoft Virtual PC installed. I did find VMNetSrv.sys located in Microsoft Virtual PC, so could that be the culprit?

 

[Jonathan_King]

That sounds right. I must confess I didn't research what driver in particular VMNetSrv.sys was. It looked virtual so I assumed VMware.

A Google search reveals that it belongs to VirtualPC.