I have had no problems with my system since buying it 6 months ago. Today I am getting BSOD when booting, and am only able to run it in Safe Mode. I cannot run in Safe mode with Networking.
I have tried a System Restore (no help), run a memory diagnostic (no problems found) and uninstalled the only software I added recently (for syncing an HTC Android phone). But I am still getting the BSOD.
Problem event name: BlueScreen
Error message: driver-irql-not-less-or-equal - it also mentions the ndis.sys file
Most recent "unexpected shutdown message":
BCCode: d1
BCP1: 0000000000000010
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF88001675A26
OS Version: 6_1_7601
Service pack: 1_0
Product: 768_1
System is Windows 7 Home Premium 64bit, OEM pre-installed. System is about 6 months old, and the OS is from the original OEM install.
I've attached the BSOD Dump and System File Collection as a zip file. The System Health Report wouldn't run - "The system cannot find the path specified".
I have no idea what to do, so thanks for any help with this.
Your athrx.sys driver is crashing NDIS. re-install with newest version. Also update the below old drivers.
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\052211-18314-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 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03202000 PsLoadedModuleList = 0xfffff800`03447650
Debug session time: Sun May 22 11:29:54.117 2011 (GMT-4)
System Uptime: 0 days 0:00:22.100
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {10, 2, 0, fffff880016bda26}
Unable to load image athrx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+2e297 )
Followup: MachineOwner
---------
2: 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: 0000000000000010, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880016bda26, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b1100
0000000000000010
CURRENT_IRQL: 2
FAULTING_IP:
ndis!NdisFreeTimerObject+16
fffff880`016bda26 488b5310 mov rdx,qword ptr [rbx+10h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
TRAP_FRAME: fffff880035548b0 -- (.trap 0xfffff880035548b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880016f4ac8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880016bda26 rsp=fffff88003554a40 rbp=fffff8000341f260
r8=0000000000011120 r9=0000000000000000 r10=fffff80003202000
r11=fffffa80100f8030 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ndis!NdisFreeTimerObject+0x16:
fffff880`016bda26 488b5310 mov rdx,qword ptr [rbx+10h] ds:e040:00000000`00000010=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032812a9 to fffff80003281d00
STACK_TEXT:
fffff880`03554768 fffff800`032812a9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03554770 fffff800`0327ff20 : fffffa80`00001f00 00000000`00000801 fffffa80`100febb0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`035548b0 fffff880`016bda26 : fffffa80`06d8eb60 fffffa80`0ad31558 fffffa80`100f9440 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03554a40 fffff880`07e6d297 : fffffa80`100f9440 fffff880`07e8332f fffff880`07f82100 fffff880`07f820f0 : ndis!NdisFreeTimerObject+0x16
fffff880`03554a70 fffffa80`100f9440 : fffff880`07e8332f fffff880`07f82100 fffff880`07f820f0 00000000`00011120 : athrx+0x2e297
fffff880`03554a78 fffff880`07e8332f : fffff880`07f82100 fffff880`07f820f0 00000000`00011120 fffff880`07e6d4f3 : 0xfffffa80`100f9440
fffff880`03554a80 fffff880`07f82100 : fffff880`07f820f0 00000000`00011120 fffff880`07e6d4f3 fffffa80`100f82c0 : athrx+0x4432f
fffff880`03554a88 fffff880`07f820f0 : 00000000`00011120 fffff880`07e6d4f3 fffffa80`100f82c0 fffffa80`07f20000 : athrx+0x143100
fffff880`03554a90 00000000`00011120 : fffff880`07e6d4f3 fffffa80`100f82c0 fffffa80`07f20000 fffffa80`0ac03050 : athrx+0x1430f0
fffff880`03554a98 fffff880`07e6d4f3 : fffffa80`100f82c0 fffffa80`07f20000 fffffa80`0ac03050 fffff880`07e70878 : 0x11120
fffff880`03554aa0 fffffa80`100f82c0 : fffffa80`07f20000 fffffa80`0ac03050 fffff880`07e70878 fffffa80`07f2e030 : athrx+0x2e4f3
fffff880`03554aa8 fffffa80`07f20000 : fffffa80`0ac03050 fffff880`07e70878 fffffa80`07f2e030 fffff880`07e700c9 : 0xfffffa80`100f82c0
fffff880`03554ab0 fffffa80`0ac03050 : fffff880`07e70878 fffffa80`07f2e030 fffff880`07e700c9 fffffa80`100f8030 : 0xfffffa80`07f20000
fffff880`03554ab8 fffff880`07e70878 : fffffa80`07f2e030 fffff880`07e700c9 fffffa80`100f8030 00000000`00000000 : 0xfffffa80`0ac03050
fffff880`03554ac0 fffffa80`07f2e030 : fffff880`07e700c9 fffffa80`100f8030 00000000`00000000 00000000`00000000 : athrx+0x31878
fffff880`03554ac8 fffff880`07e700c9 : fffffa80`100f8030 00000000`00000000 00000000`00000000 fffffa80`100f8000 : 0xfffffa80`07f2e030
fffff880`03554ad0 fffffa80`100f8030 : 00000000`00000000 00000000`00000000 fffffa80`100f8000 fffffa80`0ad19050 : athrx+0x310c9
fffff880`03554ad8 00000000`00000000 : 00000000`00000000 fffffa80`100f8000 fffffa80`0ad19050 fffff880`07e70069 : 0xfffffa80`100f8030
STACK_COMMAND: kb
FOLLOWUP_IP:
athrx+2e297
fffff880`07e6d297 ?? ???
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: athrx+2e297
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athrx
IMAGE_NAME: athrx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a2997be
FAILURE_BUCKET_ID: X64_0xD1_athrx+2e297
BUCKET_ID: X64_0xD1_athrx+2e297
Followup: MachineOwner
---------
Old drivers
Code:
OA002Afx.sys 6/8/2007 4:00:36 AM fffff880`02ccb000 fffff880`02cfef80 0x00033f80 0x46690ca4
OA002Ufd.sys 6/3/2008 5:30:37 AM fffff880`0604b000 fffff880`060743a0 0x000293a0 0x48450f3d
OA002Vid.sys 8/1/2008 5:34:52 AM fffff880`06000000 fffff880`0604ad80 0x0004ad80 0x4892d8bc
athrx.sys 6/5/2009 6:10:06 PM fffff880`03e40000 fffff880`03fae000 0x0016e000 0x4a2997be
CtClsFlt.sys 6/15/2009 1:06:41 AM fffff880`06075000 fffff880`0609f2a0 0x0002a2a0 0x4a35d6e1
PxHlpa64.sys 6/23/2009 7:16:35 PM fffff880`012f5000 fffff880`01300e00 0x0000be00 0x4a416253
How To Find Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.
- - The most common drivers are listed on this page: Driver Reference Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads