Yet Another Blue Screen

.................

I think you can send it to repair now. I don't see any potential cause by software here

Code:

BugCheck 3B, {c0000005, fffff80003080805, fffff8800492a690, 0}

That exception code indicate memory

If it is still under warranty, I would choose to have them look at that.

There is one stop code FE, which is related to USB device driver, what USB driver that you currently attach to your computer

STOP 0x000000FE: BUGCODE_USB_DRIVER

Usual causes: USB device driver

With the parameter 0x5 This is not caused by driver bug, but "A hardware failure has occurred due to a bad physical address found in a hardware data structure"

BUGCHECK SUMMARY:

Code:

BugCheck FE, {5, fffffa800749a1a0, 80863b34, fffffa80082b7250}
Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )

Followup: MachineOwner
---------
BugCheck 3B, {c0000005, fffff80003080805, fffff8800492a690, 0}

Probably caused by : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySListFault16+0 )

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

Good Luck,

Tuan

Thanks for the quick reply ttran.

I'll probably send it in for repair now.

Have you ever tried to use computer without it. You might want to check this article
Stop 0xFE Resuming from Sleep or Hibernate with USB Streaming Device

TheUnreadEmail said:

Hi,

Well ever since purchase (about 3 months now) I have always kept on recieving BSOD's. Now I have 3 years left of warranty on the unit. However, before I send it in for repairs I would like to see if the problem can be fixed via a software method other than being stuffed around for weeks by HP ;D.


I've attached the BSOD mini dumps as well as a screen shot of the internal hard drive (as for some reason their is an error - maybe that could be it?)

TheUnreadEmail

Hi and welcome


These crashes are caused by the usbehci.sys driver.
How many external un-powered USB devices do you have?
More than 2-3 could be the cause.

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Let us know the results from the report at the end.

If you need further help let us know.

Jan

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\New folder\080210-27799-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03011000 PsLoadedModuleList = 0xfffff800`0324ee50
Debug session time: Sun Aug  1 18:52:39.780 2010 (GMT-4)
System Uptime: 0 days 0:00:21.982
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

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

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa800749a1a0, 80863b34, fffffa80082b7250}

Probably caused by : usbehci.sys ( usbehci!EHCI_sMode_PollEndpointSlot+67 )

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

7: 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: fffffa800749a1a0, Device extension pointer of the host controller
Arg3: 0000000080863b34, PCI Vendor,Product id for the controller
Arg4: fffffa80082b7250, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff88002fb2e4e to fffff80003081600

STACK_TEXT: 
fffff880`0338fa18 fffff880`02fb2e4e : 00000000`000000fe 00000000`00000005 fffffa80`0749a1a0 00000000`80863b34 : nt!KeBugCheckEx
fffff880`0338fa20 fffff880`02f79fdf : 00000000`226d5100 fffffa80`0749b6a0 fffffa80`082b73c0 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`0338fa60 fffff880`02f79ba4 : fffff880`05fc6080 ffffffff`ffffff00 fffffa80`082b73c0 ffffffff`ffffff00 : usbehci!EHCI_sMode_PollEndpointSlot+0x67
fffff880`0338faf0 fffff880`02f7ea71 : fffffa80`082b7250 fffffa80`0749a1a0 fffffa80`03cd39e0 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x84
fffff880`0338fb70 fffff880`02f86e8b : 00000000`00000002 fffffa80`0749a1a0 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollEndpoint+0x41
fffff880`0338fbb0 fffff880`02f8b9b1 : 00000000`00000000 00000000`00000004 fffffa80`082b7010 fffffa80`0749a050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`0338fbe0 fffff880`02f97043 : fffffa80`0749a1a0 00000000`00000000 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`0338fc40 fffff880`02f87f89 : fffffa80`0749a050 00000000`00000000 fffffa80`0749aa02 fffffa80`0749aa10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff880`0338fca0 fffff800`0308ccdc : fffff880`03367180 fffffa80`0749aa10 fffffa80`0749aa28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`0338fcd0 fffff800`03089dfa : fffff880`03367180 fffff880`033720c0 00000000`00000000 fffff880`02f87db0 : nt!KiRetireDpcList+0x1bc
fffff880`0338fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP:
usbehci!EHCI_sMode_PollEndpointSlot+67
fffff880`02f79fdf 4533c9          xor     r9d,r9d

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci!EHCI_sMode_PollEndpointSlot+67

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc06

FAILURE_BUCKET_ID:  X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+67

BUCKET_ID:  X64_0xFE_usbehci!EHCI_sMode_PollEndpointSlot+67

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

frankly I don't know how to read the log, can you please just tell me the final result of the system file check?

Would you be willing to do a Repair Install