Windows 7 Forums
Join Forum | Login | Today's Posts | Tutorials | Vista Forum | Windows 8 Forum


Windows 7: Problem Event Name: BlueScreen

01 Aug 2010  
gurphy

Windows 7
3 posts
 
 
Problem Event Name: BlueScreen
Hey guys,



so I restarted my computer for some software update. When it boots up again I get NDTLR not found (or something to that effect). So I unplug my external hard drive and ctrl alt delete. When it boots up again it gets to the sign in screen and then red and green lines appear and the system crashes and reboots. So i reboot in safe mode and I get:

Problem event name: BlueScreen
OS version: 6.1.7600.2.0.0.768.3
Locale ID: 6153

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000010
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880010DD5D6
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Attached is all my .dmp files from my mini dump.

Any help would be much appreciated, thanks.
Gurphy.
My System SpecsSystem Spec

01 Aug 2010  
Dzomlija

Windows 7 Ultimate x64
1,322 posts
 
 
Quote   Quote: Originally Posted by gurphy View Post
Hey guys,

so I restarted my computer for some software update. When it boots up again I get NDTLR not found (or something to that effect). So I unplug my external hard drive and ctrl alt delete. When it boots up again it gets to the sign in screen and then red and green lines appear and the system crashes and reboots. So i reboot in safe mode and I get:

Problem event name: BlueScreen
OS version: 6.1.7600.2.0.0.768.3
Locale ID: 6153

Additional information about the problem:
BCCode: d1
BCP1: 0000000000000010
BCP2: 0000000000000002
BCP3: 0000000000000000
BCP4: FFFFF880010DD5D6
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Attached is all my .dmp files from my mini dump.

Any help would be much appreciated, thanks.
Gurphy.
You appear to be getting a STOP 0xD1 error, which is defined by Microsoft as follows:

Quote:
A driver tried to access an address that is pageable (or that is completely invalid) while the IRQL was too high.

This bug check is usually caused by drivers that have used improper addresses.
You can get more information on how to fix this from Microsoft: Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Are you able to boot into Safe Mode? If yes, then boot to safe mode and uninstall and new drivers and/or software that you have recently installed prior to this problem.

You might also want to try using System Restore to revert back to an earlier state before this problem started.
My System SpecsSystem Spec
01 Aug 2010  
gurphy

Windows 7
3 posts
 
 
Hey, thanks for the help Dzomlija.

Quick question regarding the drivers. I can boot up in safe mode but I cannot boot up in safe mode with networking. Does this mean that the driver in question is more than likely one for networking uses?

Cheers,
gurphy
My System SpecsSystem Spec
.


01 Aug 2010  
zigzag3143

Win 8 Release candidate 8400
2,141 posts
 
 
Quote   Quote: Originally Posted by gurphy View Post
Hey, thanks for the help Dzomlija.

Quick question regarding the drivers. I can boot up in safe mode but I cannot boot up in safe mode with networking. Does this mean that the driver in question is more than likely one for networking uses?

Cheers,
gurphy
There is a pretty good reason for both the crashes and your inability to safe boot with networking. The cause in all the DMP files is your athrx.sys file which is your ahteros networking driver.

Yoou need to re-install it and both problems should be fixed


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\072910-24476-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
Debug session time: Thu Jul 29 10:28:13.506 2010 (GMT-4)
System Uptime: 3 days 11:09:29.519
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 D1, {10, 2, 0, fffff8800167b5d6}

Unable to load image \SystemRoot\system32\DRIVERS\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
---------

5: 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: fffff8800167b5d6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb10e0
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisFreeTimerObject+16
fffff880`0167b5d6 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:  fffff880031468b0 -- (.trap 0xfffff880031468b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880016b2908
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800167b5d6 rsp=fffff88003146a40 rbp=fffff80002e1e5a0
 r8=0000000000011120  r9=0000000000000000 r10=fffff80002c09000
r11=fffffa8007e3b030 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ndis!NdisFreeTimerObject+0x16:
fffff880`0167b5d6 488b5310        mov     rdx,qword ptr [rbx+10h] ds:d040:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c78b69 to fffff80002c79600

STACK_TEXT:  
fffff880`03146768 fffff800`02c78b69 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03146770 fffff800`02c777e0 : 00000000`00000000 00000000`00000000 00000000`000007ff fffff980`16786ae0 : nt!KiBugCheckDispatch+0x69
fffff880`031468b0 fffff880`0167b5d6 : fffffa80`06d1e040 fffff880`056fd5e0 fffffa80`07e3c440 00000000`00000000 : nt!KiPageFault+0x260
fffff880`03146a40 fffff880`0566d297 : fffffa80`07e3c440 fffff880`0568332f fffff880`05782100 fffff880`057820f0 : ndis!NdisFreeTimerObject+0x16
fffff880`03146a70 fffffa80`07e3c440 : fffff880`0568332f fffff880`05782100 fffff880`057820f0 00000000`00011120 : athrx+0x2e297
fffff880`03146a78 fffff880`0568332f : fffff880`05782100 fffff880`057820f0 00000000`00011120 fffff880`0566d4f3 : 0xfffffa80`07e3c440
fffff880`03146a80 fffff880`05782100 : fffff880`057820f0 00000000`00011120 fffff880`0566d4f3 fffffa80`07e3b2c0 : athrx+0x4432f
fffff880`03146a88 fffff880`057820f0 : 00000000`00011120 fffff880`0566d4f3 fffffa80`07e3b2c0 fffffa80`0a730000 : athrx+0x143100
fffff880`03146a90 00000000`00011120 : fffff880`0566d4f3 fffffa80`07e3b2c0 fffffa80`0a730000 fffffa80`0a6c8050 : athrx+0x1430f0
fffff880`03146a98 fffff880`0566d4f3 : fffffa80`07e3b2c0 fffffa80`0a730000 fffffa80`0a6c8050 fffff880`05670878 : 0x11120
fffff880`03146aa0 fffffa80`07e3b2c0 : fffffa80`0a730000 fffffa80`0a6c8050 fffff880`05670878 fffffa80`0a738030 : athrx+0x2e4f3
fffff880`03146aa8 fffffa80`0a730000 : fffffa80`0a6c8050 fffff880`05670878 fffffa80`0a738030 fffff880`056700c9 : 0xfffffa80`07e3b2c0
fffff880`03146ab0 fffffa80`0a6c8050 : fffff880`05670878 fffffa80`0a738030 fffff880`056700c9 fffffa80`07e3b030 : 0xfffffa80`0a730000
fffff880`03146ab8 fffff880`05670878 : fffffa80`0a738030 fffff880`056700c9 fffffa80`07e3b030 00000000`00000000 : 0xfffffa80`0a6c8050
fffff880`03146ac0 fffffa80`0a738030 : fffff880`056700c9 fffffa80`07e3b030 00000000`00000000 00000000`00000000 : athrx+0x31878
fffff880`03146ac8 fffff880`056700c9 : fffffa80`07e3b030 00000000`00000000 00000000`00000000 fffffa80`07e3b000 : 0xfffffa80`0a738030
fffff880`03146ad0 fffffa80`07e3b030 : 00000000`00000000 00000000`00000000 fffffa80`07e3b000 fffffa80`0a897230 : athrx+0x310c9
fffff880`03146ad8 00000000`00000000 : 00000000`00000000 fffffa80`07e3b000 fffffa80`0a897230 fffff880`05670069 : 0xfffffa80`07e3b030


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+2e297
fffff880`0566d297 ??              ???

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
---------
My System SpecsSystem Spec
01 Aug 2010  
gurphy

Windows 7
3 posts
 
 
Cheers guys. After much fiddling around I finally got it all sorted and the drivers properly updates.

Thanks again,
gurphy
My System SpecsSystem Spec
01 Aug 2010  
Dzomlija

Windows 7 Ultimate x64
1,322 posts
 
 
Glad it worked out for you, Gurphy.

And because this problem was driver related, remember this bit of advice: Always, ALWAYS download drivers from only the original manufacturer for your devices....
My System SpecsSystem Spec
Reply

 Problem Event Name: BlueScreen problems?



« "Windows Explorer stopped working" | PLEASE HELP ME stop this disk check!!!!!!! »
Thread Tools



Similar help and support threads for: Problem Event Name: BlueScreen
Thread Forum
Solved Problem Event Name: BlueScreen BSOD Help and Support
Problem Event Name:BlueScreen BSOD Help and Support
Problem event name: BlueScreen BSOD Help and Support
Help Please:Problem Event Name BlueScreen BSOD Help and Support
Problem Event Name: BlueScreen BSOD Help and Support


All times are GMT -5. The time now is 03:29 PM.

Contact Us - Windows 8 Support - Windows Vista Support - Legal - Privacy and cookies - Top


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