Random BSOD Crash

[Eblim]

I need help with this. I notice that it happens a few minutes after I wake the computer up from sleep mode. This has been happening since a recent Windows 7 update from Windows Update.

The attachment contains two .dmp files from today, and yesterday.

If there is anymore information you require or something that I need to do for assistance, please let me know.

 

[writhziden]

[list=1][*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\Eblim\032012-20014-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0301a000 PsLoadedModuleList = 0xfffff800`0325e650
Debug session time: Tue Mar 20 17:19:44.479 2012 (UTC - 6:00)
System Uptime: 0 days 19:34:57.931
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa80068c71a0, 808627cc, fffffa8005e375a8}

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+6c )

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

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

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
	using a physical memory address that was not allocated by
	the USBport driver.
Arg2: fffffa80068c71a0, Device extension pointer of the host controller
Arg3: 00000000808627cc, PCI Vendor,Product id for the controller
Arg4: fffffa8005e375a8, Pointer to Endpoint data structure

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: usbport!_DEVICE_EXTENSION                     ***
***                                                                   ***
*************************************************************************

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88002e4ff7e to fffff80003096d40

STACK_TEXT:  
fffff880`0318ca18 fffff880`02e4ff7e : 00000000`000000fe 00000000`00000005 fffffa80`068c71a0 00000000`808627cc : nt!KeBugCheckEx
fffff880`0318ca20 fffff880`02e7dfac : 00000000`60eb5100 fffffa80`068c86a0 00000000`00000000 fffffa80`05e37720 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`0318ca60 fffff880`02e7db73 : fffffa80`05e375a8 fffff800`0301a000 fffffa80`05e37720 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
fffff880`0318caf0 fffff880`02e82d91 : fffffa80`05e375a8 00000000`00000000 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff880`0318cb30 fffff880`02e23e8b : 00000000`00000002 fffffa80`068c71a0 00000000`00000000 00000000`00000040 : usbehci!EHCI_PollEndpoint+0x41
fffff880`0318cb70 fffff880`02e289d1 : 00000000`00000040 00000000`00000004 fffffa80`05e37360 fffffa80`068c7050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`0318cba0 fffff880`02e34077 : fffffa80`068c71a0 00000000`00000040 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`0318cc00 fffff880`02e24f89 : fffffa80`068c7050 00000000`00000000 fffffa80`068c7a02 fffffa80`068c7a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`0318cc60 fffff800`030a151c : fffff880`03164180 fffffa80`068c7a18 fffffa80`068c7a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`0318cc90 fffff800`0308ea6a : fffff880`03164180 fffff880`0316efc0 00000000`00000000 fffff880`02e24db0 : nt!KiRetireDpcList+0x1bc
fffff880`0318cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci!EHCI_sMode_PollEndpointSlot+6c
fffff880`02e7dfac 4533c9          xor     r9d,r9d

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d8c0c00

FAILURE_BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c

BUCKET_ID:  X64_0xFE_INVALID_PHYSICAL_ADDR_usbehci!EHCI_sMode_PollEndpointSlot+6c

Followup: MachineOwner
---------
[/list]

1. 
   The crash was caused by a USB device. Microsoft does not seem to provide the symbols for the device causing the conflict. What USB devices do you have plugged in?

• If you are overclocking any hardware, please stop.
  
  
  
• Start with http://www.sevenforums.com/tutorials/165554-usb-driver-general-fix-problems.html to resolve the USB issues. Also, USB ports can sometimes enter a safe power state to protect the system from power surges due to USB devices. To reset the USB ports to a nominal power state, use a hard reset to resolve hardware and software issues which works for all computers, not just HP Pavilions (minus the HP driver update step).

 

[Eblim]

Thank you. I know exactly what the cause of the problem is then. It's a Wireless device for my internet. Would a driver update fix this? Or is there something else I should do?

EDIT: I'm now working at the General USB fix at this time. I have already done the "hard reset" and it hasn't changed anything. I also searched for a driver update, and I found that it's already up-to-date.

 

[alishathomaz]

If a problem occurs on your computer after you install or update a driver. Do
Device Driver Rollback to replace the driver with the previously installed version.

1 Click the Start button and click Control Panel.
2 Under Pick a Category, click Performance and Maintenance.
3 Click System.
4 In the System Properties window, click the Hardware tab.
5 Click Device Manager.
6 Right-click the device for which the new driver was installed and click Properties.
7 Click the Drivers tab.
8 Click Roll Back Driver.
If Device Driver Rollback does not resolve the problem, then use System Restore to return your computer to the operating state that existed before.

 

[writhziden]

If you can roll back the driver, and it does not resolve the problem, try installing the updated version a second time. Sometimes drivers can get corrupted and cause conflicts. To re-install the driver, follow these steps:

1. Click Start Menu
2. Right Click My Computer/Computer
3. Click Manage
4. Click Device Manager from the list on the left
5. Find the device you are trying to uninstall by expanding the appropriate set of devices
6. Right click the device
7. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
8. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
9. Do not restart your computer
10. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. Click Start Menu
3. Click Control Panel
4. Click Hardware and Sound
5. Click Device Manager (the last link under Devices and Printers)
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Do not restart your computer
11. Install the latest driver for the device.

Normally, it is a good idea to restart your computer after a driver uninstall, but for network drivers, Windows will often install the driver again on restart and reject any driver updates. Windows has trouble with network drivers from time to time and tends to give messages that the driver is already up to date during updates. The above steps prevent this from happening.