New system - Daily BSOD

[issinoho]

Hi guys,

This is a brand new homebrew box running Windows 7 Ultimate x64 (RTM) and other than a nightly BSOD it is going beautifully. Mainly used as a Media Center with a 360 extender.

BugCheck in eventvwr is as follows,

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000000a (0xfffff88008d88ff8, 0x0000000000000002, 0x0000000000000001, 0xfffff8000300502e). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 090909-18454-01.

This is consistent and happens mainly in the early hours of the morning when the computer is basically doing nothing. Doesn't happen under load, even gaming.

I have analysed the Minidump and appended to the end of this post.

My main concern is that somewhere I have a faulty component, in which case I would raise a support call; or is this simply a Windows 7 issue which will be picked up by MS in due course.

All help welcome. My system specs are in my profile.

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8800b792ff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only
on chips which support this level of status)
Arg4: fffff8000300002e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cae0e0
fffff8800b792ff8

CURRENT_IRQL: 2

FAULTING_IP:
hal!memcpy+25e
fffff800`0300002e 48894118 mov qword ptr [rcx+18h],rax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff88002f22a10 -- (.trap 0xfffff88002f22a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=41fa60828beeede3 rbx=0000000000000000 rcx=fffff8800b792fe0
rdx=fffffffff8e00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000300002e rsp=fffff88002f22ba8 rbp=0000000000000002
r8=0000000000001000 r9=0000000000000080 r10=c545f571155f71fb
r11=fffff8800b792000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!memcpy+0x25e:
fffff800`0300002e 48894118 mov qword ptr [rcx+18h],rax ds:fffff880`0b
792ff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a77469 to fffff80002a77f00

STACK_TEXT:
fffff880`02f228c8 fffff800`02a77469 : 00000000`0000000a fffff880`0b792ff8 000000
00`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f228d0 fffff800`02a760e0 : fffffa80`04180f98 fffff880`0b792000 000000
00`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f22a10 fffff800`0300002e : fffff800`02fe5e15 fffff880`0b78eeb0 000000
00`00000002 fffffa80`045e8e70 : nt!KiPageFault+0x260
fffff880`02f22ba8 fffff800`02fe5e15 : fffff880`0b78eeb0 00000000`00000002 fffffa
80`045e8e70 fffffa80`039dfc68 : hal!memcpy+0x25e
fffff880`02f22bb0 fffff800`02fe569a : fffffa80`04ee5ca0 00000000`00001000 fffffa
80`050a5240 00000000`0000ce40 : hal!HalpDmaSyncMapBuffers+0x1bd
fffff880`02f22c60 fffff800`02fe883f : fffffa80`04ee5ca0 fffff880`0b78eeb0 fffffa
80`050a5240 00000000`0000ff90 : hal!HalpDmaFlushScatterTransfer+0xae
fffff880`02f22cb0 fffff800`02fe77d5 : fffffa80`07351a30 fffff880`0b78eeb0 000000
00`0000ff90 fffffa80`045e8e70 : hal!IoFlushAdapterBuffers+0xaf
fffff880`02f22cf0 fffff880`03a3b023 : fffffa80`050491a0 fffffa80`04920970 fffffa
80`05049050 fffffa80`050491a0 : hal!HalPutScatterGatherList+0x85
fffff880`02f22d50 fffff880`03a3bab7 : fffffa80`0504a040 fffffa80`047db4a0 fffff8
80`02f22e98 fffffa80`050491a0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f

fffff880`02f22e30 fffff880`03a3964f : fffffa80`05049ea8 fffffa80`050491a0 fffffa
80`0504a040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer
+0x3a7
fffff880`02f22e90 fffff880`03a2af89 : fffffa80`05049050 00000000`00000000 fffffa
80`05049e02 fffffa80`05049ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f22ed0 fffff800`02a835dc : fffff880`009e5180 fffffa80`05049ea8 fffffa
80`05049ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f22f00 fffff800`02a7e065 : 3441582e`3b532b37 fffffa80`04d68510 000000
00`00000000 fffff880`03a2adb0 : nt!KiRetireDpcList+0x1bc
fffff880`02f22fb0 fffff800`02a7de7c : 00000000`00000000 00000000`00000000 000000
00`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06830950 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
00`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`03a3b023 4533c0 xor r8d,r8d

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07

FAILURE_BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

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

 

[issinoho]

Uploaded Minidump file for analysis by others.

 

[Tews]

Hi issinoho and Welcome to the forums!

Thanks for doing such a super job providing all the information that you did... We have several Microsoft MVP members that can help you out with your problem .. hopefully it wont take long... Has this BSOD problem been present since you installed the OS, or did it begin recently??

Once again, Welcome!

 

[issinoho]

Hi Tews, thanks for the warm welcome.

Yes, it's happened roughly once per day (night) since I installed the OS, which was last Saturday (5th).

Looking forward to working with you guys.

 

[chev65]

Looks like either a driver problem or something is plugged into one of your USB ports that Win7 doesn't like.

 

[ZeshanA]

Happens to me as well! Works fine, no problems! But when I shut it down.... it flashes me a BSOD and restarts! Any help?

ZeshanA

 

[Tews]

ZeshanA .. Please start a new thread specific to your problem... it eases confusion when answering a question..

 

[zigzag3143]

Uploaded Minidump file for analysis by others.

Issinoho

This bsod was proibably caused by the usbport.sys file. After a quick look it appears that you may want to update the usbdriver. When someone with a true debugger comes along they can give you more comprehensive info

dl driver page http://www.dynamiclink.nl/htmfiles/rframes/info_sys/info_u/27.htm
Ken

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


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

Symbol search path is: SRV*d:\symbols*Symbol information
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`02a06000 PsLoadedModuleList = 0xfffff800`02c43e50
Debug session time: Sat Sep 5 07:09:51.961 2009 (GMT-4)
System Uptime: 0 days 0:20:09.881
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff8800b792ff8, 2, 1, fffff8000300002e}

Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff8800b792ff8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000300002e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cae0e0
fffff8800b792ff8

CURRENT_IRQL: 2

FAULTING_IP:
hal!memcpy+25e
fffff800`0300002e 48894118 mov qword ptr [rcx+18h],rax

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: System

TRAP_FRAME: fffff88002f22a10 -- (.trap 0xfffff88002f22a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=41fa60828beeede3 rbx=0000000000000000 rcx=fffff8800b792fe0
rdx=fffffffff8e00000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000300002e rsp=fffff88002f22ba8 rbp=0000000000000002
r8=0000000000001000 r9=0000000000000080 r10=c545f571155f71fb
r11=fffff8800b792000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
hal!memcpy+0x25e:
fffff800`0300002e 48894118 mov qword ptr [rcx+18h],rax ds:fffff880`0b792ff8=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002a77469 to fffff80002a77f00

STACK_TEXT:
fffff880`02f228c8 fffff800`02a77469 : 00000000`0000000a fffff880`0b792ff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02f228d0 fffff800`02a760e0 : fffffa80`04180f98 fffff880`0b792000 00000000`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`02f22a10 fffff800`0300002e : fffff800`02fe5e15 fffff880`0b78eeb0 00000000`00000002 fffffa80`045e8e70 : nt!KiPageFault+0x260
fffff880`02f22ba8 fffff800`02fe5e15 : fffff880`0b78eeb0 00000000`00000002 fffffa80`045e8e70 fffffa80`039dfc68 : hal!memcpy+0x25e
fffff880`02f22bb0 fffff800`02fe569a : fffffa80`04ee5ca0 00000000`00001000 fffffa80`050a5240 00000000`0000ce40 : hal!HalpDmaSyncMapBuffers+0x1bd
fffff880`02f22c60 fffff800`02fe883f : fffffa80`04ee5ca0 fffff880`0b78eeb0 fffffa80`050a5240 00000000`0000ff90 : hal!HalpDmaFlushScatterTransfer+0xae
fffff880`02f22cb0 fffff800`02fe77d5 : fffffa80`07351a30 fffff880`0b78eeb0 00000000`0000ff90 fffffa80`045e8e70 : hal!IoFlushAdapterBuffers+0xaf
fffff880`02f22cf0 fffff880`03a3b023 : fffffa80`050491a0 fffffa80`04920970 fffffa80`05049050 fffffa80`050491a0 : hal!HalPutScatterGatherList+0x85
fffff880`02f22d50 fffff880`03a3bab7 : fffffa80`0504a040 fffffa80`047db4a0 fffff880`02f22e98 fffffa80`050491a0 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0x45f
fffff880`02f22e30 fffff880`03a3964f : fffffa80`05049ea8 fffffa80`050491a0 fffffa80`0504a040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02f22e90 fffff880`03a2af89 : fffffa80`05049050 00000000`00000000 fffffa80`05049e02 fffffa80`05049ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02f22ed0 fffff800`02a835dc : fffff880`009e5180 fffffa80`05049ea8 fffffa80`05049ec0 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02f22f00 fffff800`02a7e065 : 3441582e`3b532b37 fffffa80`04d68510 00000000`00000000 fffff880`03a2adb0 : nt!KiRetireDpcList+0x1bc
fffff880`02f22fb0 fffff800`02a7de7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06830950 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f
fffff880`03a3b023 4533c0 xor r8d,r8d

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: USBPORT

IMAGE_NAME: USBPORT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc07

FAILURE_BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

BUCKET_ID: X64_0xA_USBPORT!USBPORT_Core_iCompleteDoneTransfer+45f

Followup: MachineOwner

 

[zigzag3143]

Happens to me as well! Works fine, no problems! But when I shut it down.... it flashes me a BSOD and restarts! Any help?

ZeshanA

When you start the new thread cold you goto c:\wondows\minibump, zip the dump file (*.dmp) and upload it for us to examine

Ken

 

[issinoho]

2 things,

1. My version of usbport.sys (6.1.7600.16385) is newer than anything in that link.
2. The link points to a paid for download!

I think not.

 

[Snufffed]

IRQL_NOT_LESS_OR_EQUAL

99% of all errors of this nature are DRIVERS.

You might simply locate your driver ( might be corrupt) delete it, then reboot Win 7 will install a new (same driver). I had this problem with a new External USB device.

 

[usasma]

The stack goes from the usbport.sys driver to the hal.dll, then into a page fault, then the crash. Hal.dll is responsible as a translation layer between the hardware and Windows.

As such, an error that involves hal.dll is likely to be caused by Windows not being able to use the hardware in the way that it's supposed to be used (there's differing degrees of this).

So, if we presume that Windows is OK, then it's gotta be something about the translation from hardware to Windows. This is most commonly an incompatible piece of hardware - or an incompatible driver.

I would first suggest running this free tool to see if it identifies the problem: http://www.microsoft.com/downloads/...90-7659-4BD9-9E51-2497C146AF15&displaylang=en

Once that's done, please let us know what the report says.
Then, go into Device Manager and inventory the USB devices on your system. Disconnect all that you can remove - and disable those that you can't remove.
Test to see if that alleviates the BSOD problem.
Please let us know the results.

 

[issinoho]

I have 2 external hard drives (on USB) through a powerless USB hub. One of these disks is the main recording drive for Media Center.

As an experiment, I pulled out the hub and plugged only the Media Center drive back directly into the PC. I thought this may workaround any anomalies to do with power supply to the drives. Well the system *hated* this move. My Xbox extender refused to connect properly and even when it did, starting up Live TV crashed the system.

I reassembled as before and after a couple of reboots all went back to normal.

Bizarrely, last night went by without a BSOD. First time.

Assuming it happens again, I'm going to resume mucking about with the USB devices and potentially may even re-install to see if the problem persists.