
Quote: Originally Posted by
tassmuc
Am having two or more BSOD a day when resuming from standby or closing a VMWare virtual machine on my laptop.
Complete dump attached, any help appreciated !!!
You have massive USBPORT
driver issues. YOu need to remove them all and re-install only what is needed.
Ken J
[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\Windows_NT6_BSOD_jcgriff2\101110-15132-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/;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.x86fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0x82e38000 PsLoadedModuleList = 0x82f80810
Debug session time: Mon Oct 11 05:11:36.737 2010 (GMT-4)
System Uptime: 0 days 0:00:19.624
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate
drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 8657b800, Address of the IRP
Arg2: 00000eae
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
IRP_ADDRESS: 8657b800
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 8ed6c868 to 82ea0ebd
STACK_TEXT:
8078aea0 8ed6c868 82e78354 85d78100 00000000 nt!IopfCompleteRequest+0x4b0
8078aed0 8ed6d178 8657a3b8 8657b800 8c91d4d4 USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x6e0
8078aefc 8ed709af 85e0e028 85e0e0f0 85e0ea98 USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x33b
8078af24 8ed6ad18 85e0e028 85e0ea98 85e0e002 USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xbc
8078af48 82ea03b5 85e0eaa4 85e0e002 00000000 USBPORT!USBPORT_Xdpc_Worker+0x173
8078afa4 82ea0218 82f61d20 87663c10 00000000 nt!KiExecuteAllDpcs+0xf9
8078aff4 82e9f9dc 8acafce4 00000000 00000000 nt!KiRetireDpcList+0xd5
8078aff8 8acafce4 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2c
WARNING: Frame IP not in any known module. Following frames may be wrong.
82e9f9dc 00000000 0000001a 00d6850f bb830000 0x8acafce4
STACK_COMMAND: kb
FOLLOWUP_IP:
USBPORT!USBPORT_Core_iCompleteDoneTransfer+6e0
8ed6c868 8a4d17 mov cl,byte ptr [ebp+17h]
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: USBPORT!USBPORT_Core_iCompleteDoneTransfer+6e0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: USBPORT
IMAGE_NAME: USBPORT.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc871
FAILURE_BUCKET_ID: 0x44_USBPORT!USBPORT_Core_iCompleteDoneTransfer+6e0
BUCKET_ID: 0x44_USBPORT!USBPORT_Core_iCompleteDoneTransfer+6e0
Followup: MachineOwner
---------