Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD

03 Apr 2010   #1

Windows 7
 
 
BSOD

Umm I'm not quite sure what happened. I didn't catch the BSOD error message in time. This is what the event viewer says:

Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Date: 4/3/2010 11:19:38 AM
Event ID: 1001
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: BATCAVE-PC
Description:
The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0xfffff88001e8ee80, 0x0000000000000002, 0x0000000000000008, 0xfffff88001e8ee80). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 040310-22573-01.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-04-03T18:19:38.000000000Z" />
<EventRecordID>2567</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>BATCAVE-PC</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">0x000000d1 (0xfffff88001e8ee80, 0x0000000000000002, 0x0000000000000008, 0xfffff88001e8ee80)</Data>
<Data Name="param2">C:\Windows\MEMORY.DMP</Data>
<Data Name="param3">040310-22573-01</Data>
</EventData>
</Event>

I'm also attaching the minidump. Any help with this is greatly appreciated!!


My System SpecsSystem Spec
.

03 Apr 2010   #2

Windows 7 Professional x64
 
 

Looks like your Atheros network adapter is the culprit here, from the dmp. I suggest updating anything Atheros related.

Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Jonathan\Desktop\040310-22573-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a05000 PsLoadedModuleList = 0xfffff800`02c42e50
Debug session time: Sat Apr  3 14:18:42.685 2010 (GMT-4)
System Uptime: 0 days 0:04:33.059
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff88001e8ee80, 2, 8, fffff88001e8ee80}

Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
Probably caused by : athrxusb.sys ( athrxusb+54e80 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff88001e8ee80, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff88001e8ee80, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cad0e0
 fffff88001e8ee80 

CURRENT_IRQL:  2

FAULTING_IP: 
athrxusb+54e80
fffff880`01e8ee80 ??              ???

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88002ffb800 -- (.trap 0xfffff88002ffb800)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000005 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa8001da5e10 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001e8ee80 rsp=fffff88002ffb998 rbp=0000000000000000
 r8=fffffa80051a92a0  r9=0000000000000050 r10=fffff88002fd3b80
r11=fffff88002ffba78 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
<Unloaded_athrxusb.sys>+0x54e80:
fffff880`01e8ee80 ??              ???
Resetting default scope

IP_MODULE_UNLOADED: 
athrxusb+54e80
fffff880`01e8ee80 ??              ???

LAST_CONTROL_TRANSFER:  from fffff80002a76469 to fffff80002a76f00

FAILED_INSTRUCTION_ADDRESS: 
athrxusb+54e80
fffff880`01e8ee80 ??              ???

STACK_TEXT:  
fffff880`02ffb6b8 fffff800`02a76469 : 00000000`0000000a fffff880`01e8ee80 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff880`02ffb6c0 fffff800`02a750e0 : 00000000`00000000 fffffa80`01da5fbb fffffa80`026ae1a0 00000000`00000201 : nt!KiBugCheckDispatch+0x69
fffff880`02ffb800 fffff880`01e8ee80 : fffff800`02a79516 fffffa80`04416c50 fffffa80`01f26f98 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02ffb998 fffff800`02a79516 : fffffa80`04416c50 fffffa80`01f26f98 00000000`00000000 fffff880`042e6300 : <Unloaded_athrxusb.sys>+0x54e80
fffff880`02ffb9a0 fffff880`0429d5d9 : fffffa80`03565050 fffffa80`05482300 ffffffff`c0000011 00000000`00000000 : nt!IopfCompleteRequest+0x3a6
fffff880`02ffba80 fffff880`0429dab7 : fffffa80`01f26c02 fffffa80`01da5e10 00000000`ffffffff fffffa80`03565ea8 : USBPORT!USBPORT_Core_iCompleteDoneTransfer+0xa15
fffff880`02ffbb60 fffff880`0429b64f : fffffa80`03565ea8 fffffa80`035651a0 fffffa80`03566040 00000000`00000000 : USBPORT!USBPORT_Core_iIrpCsqCompleteDoneTransfer+0x3a7
fffff880`02ffbbc0 fffff880`0428cf89 : fffffa80`03565050 00000000`00000000 fffffa80`03336702 fffffa80`03565ea8 : USBPORT!USBPORT_Core_UsbIocDpc_Worker+0xf3
fffff880`02ffbc00 fffff880`00ed64ce : fffffa80`03336000 fffffa80`03565ea8 fffffa80`03336750 fffffa80`03565ec0 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`02ffbc30 fffffa80`03336000 : fffffa80`03565ea8 fffffa80`03336750 fffffa80`03565ec0 fffff880`02fd3180 : sptd+0x424ce
fffff880`02ffbc38 fffffa80`03565ea8 : fffffa80`03336750 fffffa80`03565ec0 fffff880`02fd3180 00000000`00000000 : 0xfffffa80`03336000
fffff880`02ffbc40 fffffa80`03336750 : fffffa80`03565ec0 fffff880`02fd3180 00000000`00000000 fffff880`02fd7f40 : 0xfffffa80`03565ea8
fffff880`02ffbc48 fffffa80`03565ec0 : fffff880`02fd3180 00000000`00000000 fffff880`02fd7f40 00000000`00000022 : 0xfffffa80`03336750
fffff880`02ffbc50 fffff880`02fd3180 : 00000000`00000000 fffff880`02fd7f40 00000000`00000022 00000000`00000000 : 0xfffffa80`03565ec0
fffff880`02ffbc58 00000000`00000000 : fffff880`02fd7f40 00000000`00000022 00000000`00000000 00000000`00000000 : 0xfffff880`02fd3180


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrxusb+54e80
fffff880`01e8ee80 ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  athrxusb+54e80

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrxusb

IMAGE_NAME:  athrxusb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_athrxusb+54e80

BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_athrxusb+54e80

Followup: MachineOwner
---------
My System SpecsSystem Spec
03 Apr 2010   #3

Windows 7
 
 
Thank you

for looking =) How do I find that Atheros thing? I'm not sure which of my product is related to that..
My System SpecsSystem Spec
.


03 Apr 2010   #4

Windows 7 Professional x64
 
 

That's your network adapter. Find your network card in Device Manager, right-click on it, and select Update Driver Software.
My System SpecsSystem Spec
03 Apr 2010   #5

Windows 7
 
 
oh

THANKS! I have it updated. So far so good.. but only time will tell. Thanks again!
My System SpecsSystem Spec
03 Apr 2010   #6

Windows 7 Professional x64
 
 

No problem, good luck!
My System SpecsSystem Spec
Reply

 BSOD




Thread Tools



Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 04:07 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33