BSOD while boot - DRIVER_IRQL_NOT_LESS_EQUAL - ndis.sys

Upload your MSINFO32.nfo file.

1. Click on the start button
2. Type "msinfo32" (without quotes) in the search bar of the start menu, click the resulting link. It will open the System Information window.
3. File>Save. In the "File Name" filed, put "MSINFO32" (without Quote), give the save location to desktop, and click the "save" button.
4. Give the time for processing, it will save a .nfo file on your desktop.
5. Zip it, and upload it following the instruction.

It is needed to see to suggest the appropriate driver.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {10, 2, 0, fffff88001511566}

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+4c0c7 )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000350f100
 0000000000000010 

CURRENT_IRQL:  2

FAULTING_IP: 
ndis!NdisFreeTimerObject+16
fffff880`01511566 488b5310        mov     rdx,qword ptr [rbx+10h]

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff8800319a8a0 -- (.trap 0xfffff8800319a8a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff88001547ac8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88001511566 rsp=fffff8800319aa30 rbp=fffff8000347d280
 r8=0000000000011120  r9=0000000000000000 r10=fffff80003262000
r11=fffffa8005c34030 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
ndis!NdisFreeTimerObject+0x16:
fffff880`01511566 488b5310        mov     rdx,qword ptr [rbx+10h] ds:5040:00000000`00000010=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800032d7169 to fffff800032d7bc0

STACK_TEXT:  
fffff880`0319a758 fffff800`032d7169 : 00000000`0000000a 00000000`00000010 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0319a760 fffff800`032d5de0 : fffff880`00000000 00000000`00000801 fffffa80`05c45bb0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0319a8a0 fffff880`01511566 : fffffa80`033e0b50 fffff880`04518c56 fffffa80`05c35448 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0319aa30 fffff880`044a50c7 : fffffa80`05c35448 fffff880`0449d81f fffff880`0459d140 fffff880`0459d130 : ndis!NdisFreeTimerObject+0x16
fffff880`0319aa60 fffffa80`05c35448 : fffff880`0449d81f fffff880`0459d140 fffff880`0459d130 00000000`00011120 : athrx+0x4c0c7
fffff880`0319aa68 fffff880`0449d81f : fffff880`0459d140 fffff880`0459d130 00000000`00011120 fffff880`04487933 : 0xfffffa80`05c35448
fffff880`0319aa70 fffff880`0459d140 : fffff880`0459d130 00000000`00011120 fffff880`04487933 fffffa80`05c342c8 : athrx+0x4481f
fffff880`0319aa78 fffff880`0459d130 : 00000000`00011120 fffff880`04487933 fffffa80`05c342c8 fffffa80`05130000 : athrx+0x144140
fffff880`0319aa80 00000000`00011120 : fffff880`04487933 fffffa80`05c342c8 fffffa80`05130000 fffffa80`04cf8050 : athrx+0x144130
fffff880`0319aa88 fffff880`04487933 : fffffa80`05c342c8 fffffa80`05130000 fffffa80`04cf8050 fffff880`0448acf8 : 0x11120
fffff880`0319aa90 fffffa80`05c342c8 : fffffa80`05130000 fffffa80`04cf8050 fffff880`0448acf8 fffffa80`05130030 : athrx+0x2e933
fffff880`0319aa98 fffffa80`05130000 : fffffa80`04cf8050 fffff880`0448acf8 fffffa80`05130030 fffff880`0448a549 : 0xfffffa80`05c342c8
fffff880`0319aaa0 fffffa80`04cf8050 : fffff880`0448acf8 fffffa80`05130030 fffff880`0448a549 fffffa80`05c34030 : 0xfffffa80`05130000
fffff880`0319aaa8 fffff880`0448acf8 : fffffa80`05130030 fffff880`0448a549 fffffa80`05c34030 00000000`00000000 : 0xfffffa80`04cf8050
fffff880`0319aab0 fffffa80`05130030 : fffff880`0448a549 fffffa80`05c34030 00000000`00000000 00000000`00000000 : athrx+0x31cf8
fffff880`0319aab8 fffff880`0448a549 : fffffa80`05c34030 00000000`00000000 00000000`00000000 fffffa80`05c34000 : 0xfffffa80`05130030
fffff880`0319aac0 fffffa80`05c34030 : 00000000`00000000 00000000`00000000 fffffa80`05c34000 00000000`00000000 : athrx+0x31549
fffff880`0319aac8 00000000`00000000 : 00000000`00000000 fffffa80`05c34000 00000000`00000000 fffff880`0448a4e9 : 0xfffffa80`05c34030


STACK_COMMAND:  kb

FOLLOWUP_IP: 
athrx+4c0c7
fffff880`044a50c7 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  athrx+4c0c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: athrx

IMAGE_NAME:  athrx.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a553e89

FAILURE_BUCKET_ID:  X64_0xD1_athrx+4c0c7

BUCKET_ID:  X64_0xD1_athrx+4c0c7

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

2: kd> lmvm athrx
start             end                 module name
fffff880`04459000 fffff880`045c8000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Thu Jul 09 06:19:13 2009 (4A553E89)
    CheckSum:         0016D79F
    ImageSize:        0016F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

The device is D-Link AirPlus DWL-G520 Wireless PCI Adapter(rev.B)

No feasible update is there with D-Link: D-Link Technical Support

Attachment 299461

But You may get it from Atheros: Drivers for Atheros AR9285 and Windows 7

Attachment 299464

So it seems to be the appropriate one.

• Version: 10.0.0.255
• Release: 2013-07-02

Install it by following Driver Install - Device Manager

Let us know the results.

longfellow01 said:

Boot did take pretty long (its not really a fast computer to begin with)

That's not fair.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus, Microsoft Security Client; MSC.
5. Apply > OK
6. Accept then restart.

Now take a restart as a test. Does it improve the booting process anyhow?