BSOD randomly gaming/idle 0xd1 ndis.sys

Varobun · 20 Feb 2015

Hi, Ive been having almost daily or every couple days blue screen errors.

Every crash with me actively on the computer has been 0xd1 irql ndis.sys error.
There has also been crashing i think when the computer is returning from sleep or during sleep (powerstatefailure?)

I am mainly interested in solving the first type of crash, why its happening and what to do to prevent it.
It has happened twice now i believe while playing the game 'RuneScape', and other times in other situations i do not recall.

Crashes have either came up recently or have definitely been more frequent the past week or two.
I might have deleted dump files older than this month or last month.

This might be due to not having recent windows updates installed, i havent had the chance in awhile but i could upate now if the reports are pointing towards the lack of updates.

Arc · 25 Feb 2015

Please update your network driver to Version: 1.0.0.22 from https://www.atheros.cz/atheros-wirel...et=47&system=6

Let us know for any further BSOD.
_________________________________________

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {28, 2, 0, fffff8800147a650}

*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+76b8 )

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: 0000000000000028, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800147a650, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ec0100
GetUlongFromAddress: unable to read from fffff80002ec01c0
 0000000000000028 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
ndis! ?? ::FNODOBFM::`string'+15dd
fffff880`0147a650 8b4728          mov     eax,dword ptr [rdi+28h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  JagexLauncher.

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff8800d15d900 -- (.trap 0xfffff8800d15d900)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000008 rbx=0000000000000000 rcx=0000000000000024
rdx=fffffa80069648e0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800147a650 rsp=fffff8800d15da90 rbp=fffffa800695ca10
 r8=fffffa8005fe22c0  r9=0000000000000001 r10=0000000000000000
r11=fffffa80059981a0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ndis! ?? ::FNODOBFM::`string'+0x15dd:
fffff880`0147a650 8b4728          mov     eax,dword ptr [rdi+28h] ds:00000000`00000028=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c88169 to fffff80002c88bc0

STACK_TEXT:  
fffff880`0d15d7b8 fffff800`02c88169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0d15d7c0 fffff800`02c86de0 : 00000000`00000000 fffff880`06eb2c10 fffffa80`05fe2260 fffffa80`069648e0 : nt!KiBugCheckDispatch+0x69
fffff880`0d15d900 fffff880`0147a650 : fffffa80`049b2030 fffffa80`0695ca10 00000001`000000a0 00000000`00000004 : nt!KiPageFault+0x260
fffff880`0d15da90 fffff880`06eb26b8 : fffffa80`059981a0 00000000`00000000 fffffa80`05fe22c0 fffffa80`0695ca10 : ndis! ?? ::FNODOBFM::`string'+0x15dd
fffff880`0d15db30 fffffa80`059981a0 : 00000000`00000000 fffffa80`05fe22c0 fffffa80`0695ca10 fffffa80`05ff7780 : L1E62x64+0x76b8
fffff880`0d15db38 00000000`00000000 : fffffa80`05fe22c0 fffffa80`0695ca10 fffffa80`05ff7780 fffffa80`000001c0 : 0xfffffa80`059981a0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
L1E62x64+76b8
fffff880`06eb26b8 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  L1E62x64+76b8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: L1E62x64

IMAGE_NAME:  L1E62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a90ceb9

FAILURE_BUCKET_ID:  X64_0xD1_L1E62x64+76b8

BUCKET_ID:  X64_0xD1_L1E62x64+76b8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_l1e62x64+76b8

FAILURE_ID_HASH:  {b323fb0f-ecbc-bb6e-a188-6324d78c8445}

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

2: kd> lmvm L1E62x64
start             end                 module name
fffff880`06eab000 fffff880`06ebd000   L1E62x64 T (no symbols)           
    Loaded symbol image file: L1E62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\L1E62x64.sys
    Image name: L1E62x64.sys
    Timestamp:        Sun Aug 23 10:38:09 2009 (4A90CEB9)
    CheckSum:         0001697B
    ImageSize:        00012000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Varobun · 25 Feb 2015

Installed driver succesfully, will wait a couple days or week at most for any BSODs

Arc · 26 Feb 2015

OK, observe the situation, inform us if needed.

Varobun · 26 Feb 2015

Marking as solved as it has not came up for 6 days

Arc · 26 Feb 2015

No problem, but if you experience any more BSOD then let us know.

Varobun · 16 Mar 2015

The problem has resurfaced lately. Ive had 3 crashes in the past 2-3 days and i believe 2 more further back, but they did not create dump files.

Same errors 0xd1 and 0x9f.

The crashes are still pretty random however the only time i see them is while multitasking the game Runescape with something else such as teamspeak, listening to music or browsing.

Ive never seen the crash happen in much much more intensive games, like DayZ for example.

Uploading newer dump files if needed

Arc · 17 Mar 2015

The same thing .... the Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller is failing, with two different bugcheck codes, at two different situations.

Code:

BugCheck D1, {28, 2, 0, fffff88001441650}

*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
Probably caused by : L1E62x64.sys ( L1E62x64+79e9 )

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

Code:

BugCheck 9F, {3, fffffa800470da10, fffff80000b9c4d8, fffffa80070c3be0}

Probably caused by : pci.sys

Followup: MachineOwner
--------------------------------------
*** WARNING: Unable to verify timestamp for L1E62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for L1E62x64.sys
 \Driver\L1E    nt!PopSystemIrpCompletion
            Args: 00015400 00000000 00000005 00000003

And teh driver is the latest possible one for it.

Code:

    Image name: L1E62x64.sys
    Timestamp:        Mon Mar 29 07:38:44 2010 (4BB00BAC)

In this situation I can suggest you only one thing, dont use the onboard ethernet. Better you get a PCIe ethernet card.

Varobun · 17 Mar 2015

So would disabling the ethernet and using wireless internet potentially fix the problem? Or am i understanding that wrong?

Arc · 18 Mar 2015

Varobun said:

So would disabling the ethernet and using wireless internet potentially fix the problem?

Yes, it will fix this issue particularly.