SOLVED NDIS.SYS BSOD

[xDjCeex]

Hey all, I have a HP DV6-3055dx.. I used it last night, it worked great, used it this morning, it worked great, came home this afternoon turned it on BSOD =( .. The message doesn't stay up for long but I do know it says DRIVER_IRQL_NOT_LESS_OR_EQUAL at the top .. and NDIS.SYS at the bottom. I came up with the conclusion it dealt with a network driver.. I came up with that because it boots in regular safe mode but not safe mode with networking. I attached the dump files.. Can someone please help me?

 

[bassfisher6522]

On your hunch, have you updated the LAN driver from HP's website or from what vendor that HP might have used.

 

[TrainableMan]

There are 10 different drivers listed on the HP site for your computer and 64-bit W7. Install the latest ones for your computer. Get the right ones as you likely need only two of them (one for the wired connection and one for wireless/wi-fi/bluetooth adapter).
As Bass suggested, updating those drivers is a good place to start.

 

[Ace]

*******************************************************************************
*                                                                             *
*                        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: fffff880014a0a26, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032fd100
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisFreeTimerObject+16
fffff880`014a0a26 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:  fffff8800317e8b0 -- (.trap 0xfffff8800317e8b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880014d7ac8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014a0a26 rsp=fffff8800317ea40 rbp=fffff8000326b260
 r8=0000000000011120  r9=0000000000000000 r10=fffff8000304e000
r11=fffffa8006e36040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ndis!NdisFreeTimerObject+0x16:
fffff880`014a0a26 488b5310        mov     rdx,qword ptr [rbx+10h] ds:6040:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030ca1e9 to fffff800030cac40

STACK_TEXT:  
fffff880`0317e768 fffff800`030ca1e9 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0317e770 fffff800`030c8e60 : 00000000`00000110 fffffa80`03272550 fffffa80`074d6bb0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0317e8b0 fffff880`014a0a26 : fffffa80`04c2eb60 00000000`000007ff fffffa80`06e36388 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0317ea40 fffff880`02cd4677 : fffffa80`06e36388 fffff880`02ccd34f fffff880`02dbb588 fffff880`02dbb578 : ndis!NdisFreeTimerObject+0x16
fffff880`0317ea70 fffffa80`06e36388 : fffff880`02ccd34f fffff880`02dbb588 fffff880`02dbb578 00000000`00011120 : athrx+0x47677
fffff880`0317ea78 fffff880`02ccd34f : fffff880`02dbb588 fffff880`02dbb578 00000000`00011120 fffff880`02cb9b83 : 0xfffffa80`06e36388
fffff880`0317ea80 fffff880`02dbb588 : fffff880`02dbb578 00000000`00011120 fffff880`02cb9b83 fffffa80`06e362b8 : athrx+0x4034f
fffff880`0317ea88 fffff880`02dbb578 : 00000000`00011120 fffff880`02cb9b83 fffffa80`06e362b8 fffffa80`065c0000 : athrx+0x12e588
fffff880`0317ea90 00000000`00011120 : fffff880`02cb9b83 fffffa80`06e362b8 fffffa80`065c0000 fffffa80`0646d050 : athrx+0x12e578
fffff880`0317ea98 fffff880`02cb9b83 : fffffa80`06e362b8 fffffa80`065c0000 fffffa80`0646d050 fffff880`02cbcd88 : 0x11120
fffff880`0317eaa0 fffffa80`06e362b8 : fffffa80`065c0000 fffffa80`0646d050 fffff880`02cbcd88 fffffa80`065cb030 : athrx+0x2cb83
fffff880`0317eaa8 fffffa80`065c0000 : fffffa80`0646d050 fffff880`02cbcd88 fffffa80`065cb030 fffff880`02cbc5e9 : 0xfffffa80`06e362b8
fffff880`0317eab0 fffffa80`0646d050 : fffff880`02cbcd88 fffffa80`065cb030 fffff880`02cbc5e9 fffffa80`06e36040 : 0xfffffa80`065c0000
fffff880`0317eab8 fffff880`02cbcd88 : fffffa80`065cb030 fffff880`02cbc5e9 fffffa80`06e36040 00000000`00000000 : 0xfffffa80`0646d050
fffff880`0317eac0 fffffa80`065cb030 : fffff880`02cbc5e9 fffffa80`06e36040 00000000`00000000 00000000`00000000 : athrx+0x2fd88
fffff880`0317eac8 fffff880`02cbc5e9 : fffffa80`06e36040 00000000`00000000 00000000`00000000 fffffa80`06e36010 : 0xfffffa80`065cb030
fffff880`0317ead0 fffffa80`06e36040 : 00000000`00000000 00000000`00000000 fffffa80`06e36010 fffffa80`065c9100 : athrx+0x2f5e9
fffff880`0317ead8 00000000`00000000 : 00000000`00000000 fffffa80`06e36010 fffffa80`065c9100 fffff880`02cbc589 : 0xfffffa80`06e36040


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+47677
fffff880`02cd4677 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  athrx+47677

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a2ea4b9

FAILURE_BUCKET_ID:  X64_0xD1_athrx+47677

BUCKET_ID:  X64_0xD1_athrx+47677

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)

(Why is it a NDIS.sys BSOD? All of your bugchecks point towards athrx.sys)

This bugcheck indicates to me that there was a read exception, and a driver tried to access a pageable or inaccessable/invalid address while the IRQL was too high.

Things to do first: *Try checking for updates to your driver before doing the following

1) Download and run Memtest86 on boot: http://www.memtest86.com
Make sure to let it run and do it's thing for about the first 6 tests. If it passes those, then everything should be good, otherwise any failure to pass those tests indicates a corruption in your memory.

If you get an error on one of the tests, then you should try by booting up your computer with each RAM inserted separately one at a time. When you find one that doesn't return any errors then test it in every single RAM slot to test for a bad socket.

2) Driver Verifier: Note make sure you backup your data first

If you have access to another computer you can contact us through your other working system in case any problems prevent you from getting into Windows. Make a System Restore point as well.

A startup repair disk may assist you in a system restore during boot if you can't get into Windows as well. In Windows 7 you can make a Startup Repair disk by going to Start > All Programs > Maintenance > "Create a System Repair Disc". With Windows Vista you'll have to use your installation CD/DVD or the "Repair your computer" option in the F8/Safe mode boot menu

Follow these steps:
- Go to Start and type in "verifier.exe" and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Note: If Norton Antivirus is installed, do not enable Driver Verifier's Deadlock Detection

Reboot the system and wait for it to crash to the BSOD. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 48 hours (recommended) of continuous operation to make sure.

Reboot into Windows after the crash once again and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, or by opening a command prompt and typing in: "verifier /reset" (without quotes). If for some reason you can't get into Windows after the crash and reboot, try booting up in Safe Mode, then try these options to disable Driver Verifier from there.

If you can't get into Windows because it crashes too soon, try it in Safe Mode (recommended) or boot from Last Known Good Configuration.
If you can't get into Safe Mode, try using System Restore from your installation DVD or startup repair menu to set the system back to the previous restore point that you created.

Make sure your minidumps are enabled so the creation of one with Driver Verifier is available, and post it so I can review it.

The point of driver verifier is to have a more accurate say on which driver may be held responsible.

If you want, after Memtest86 you can try running in a Clean Boot state to see if the issue still is causing you problems when running your machine, othewise uninstalling the drivers completely using "Driver Sweeper" then reinstall to start clean. If the problem still persists, then i'll see what your driver verifier log entails.

I would suggest posting the new logs from Driver Verifier first though before doing a reinstall. If and when you decide to reinstall though, make sure that after uninstalling the driver, you reboot before installing it again.

 

[xDjCeex]

Thank you all very kindly for your help and quick responses, I've figured it out. It was the Atheros driver that was faulty, and I needed to update it. I updated it straight from the HP website and was in business. Thanks all !

 

[bassfisher6522]

Glad to here.