BSOD while playing games/downloading, Driver IRQL Not Less Or Equal

[zech]

Hello,



I'm having an issue when I browse on the internet watching videos and litsening to music or connecting to a game I will have a sudden BSOD




Thank you

 

[Arc]

Hi zech.

Update the driver to Killer e2200 PCI-E Gigabit Ethernet Controller from Driver Downloads | Qualcomm Atheros, Inc.

And 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.
5. Apply > OK
6. Accept then restart.

Let us know the results.
__________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff880166a2000, 2, 0, fffff88002d56fa0}

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f11100
GetUlongFromAddress: unable to read from fffff80002f111c0
 fffff880166a2000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
e22w7x64+19fa0
fffff880`02d56fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  LolClient.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800947e670 -- (.trap 0xfffff8800947e670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000002be rbx=0000000000000000 rcx=fffffa8006d26aa8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88002d56fa0 rsp=fffff8800947e800 rbp=fffffa8006d269f0
 r8=0000000000000300  r9=0000000000000000 r10=fffffa80083f0280
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
e22w7x64+0x19fa0:
fffff880`02d56fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14 ds:00000000`00000248=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cd9169 to fffff80002cd9bc0

STACK_TEXT:  
fffff880`0947e528 fffff800`02cd9169 : 00000000`0000000a fffff880`166a2000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0947e530 fffff800`02cd7de0 : fffff8a0`048d7124 fffff8a0`00023150 fffff880`0947e810 fffffa80`083dcb40 : nt!KiBugCheckDispatch+0x69
fffff880`0947e670 fffff880`02d56fa0 : fffffa80`083dcb40 00000000`00002d3c fffffa80`083dcb58 fffffa80`083dcb40 : nt!KiPageFault+0x260
fffff880`0947e800 fffffa80`083dcb40 : 00000000`00002d3c fffffa80`083dcb58 fffffa80`083dcb40 fffffa80`083daa38 : e22w7x64+0x19fa0
fffff880`0947e808 00000000`00002d3c : fffffa80`083dcb58 fffffa80`083dcb40 fffffa80`083daa38 fffff880`02d55eb2 : 0xfffffa80`083dcb40
fffff880`0947e810 fffffa80`083dcb58 : fffffa80`083dcb40 fffffa80`083daa38 fffff880`02d55eb2 00000000`00000002 : 0x2d3c
fffff880`0947e818 fffffa80`083dcb40 : fffffa80`083daa38 fffff880`02d55eb2 00000000`00000002 00000000`00000000 : 0xfffffa80`083dcb58
fffff880`0947e820 fffffa80`083daa38 : fffff880`02d55eb2 00000000`00000002 00000000`00000000 fffffa80`0a466410 : 0xfffffa80`083dcb40
fffff880`0947e828 fffff880`02d55eb2 : 00000000`00000002 00000000`00000000 fffffa80`0a466410 00000000`0000024c : 0xfffffa80`083daa38
fffff880`0947e830 00000000`00000002 : 00000000`00000000 fffffa80`0a466410 00000000`0000024c fffffa80`085b6760 : e22w7x64+0x18eb2
fffff880`0947e838 00000000`00000000 : fffffa80`0a466410 00000000`0000024c fffffa80`085b6760 fffff880`02d60432 : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e22w7x64+19fa0
fffff880`02d56fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  e22w7x64+19fa0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: e22w7x64

IMAGE_NAME:  e22w7x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50bf79c4

FAILURE_BUCKET_ID:  X64_0xD1_e22w7x64+19fa0

BUCKET_ID:  X64_0xD1_e22w7x64+19fa0

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0xd1_e22w7x64+19fa0

FAILURE_ID_HASH:  {13809988-6ac7-9638-6d45-c609868649bd}

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

2: kd> lmvm e22w7x64
start             end                 module name
fffff880`02d3d000 fffff880`02d67000   e22w7x64 T (no symbols)           
    Loaded symbol image file: e22w7x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e22w7x64.sys
    Image name: e22w7x64.sys
    Timestamp:        Wed Dec 05 22:13:48 2012 (50BF79C4)
    CheckSum:         00035FA2
    ImageSize:        0002A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[zech]

Thank you I will try that, would you be able to tell me what the driver is called?

 

[Arc]

Thank you I will try that, would you be able to tell me what the driver is called?

I have already told in my earlier post. Read it again?

Update the driver to Killer e2200 PCI-E Gigabit Ethernet Controller from Driver Downloads | Qualcomm Atheros, Inc.

Then click the link supplied in the earlier post?

:ar: Driver Downloads | Qualcomm Atheros, Inc.

Is not is clearly stated in the resulted link?

View attachment 314928

 

[zech]

Sorry I'm so stupid lol I thought that was for a wireless version because mine isn't wireless thanks again for your help

 

[Arc]

How can it be wireless whereas it is marked as ethernet?

 

[zech]

I didn't see the comma between e2200 and Wireless-N so I thought it was for something else sorry

 

[Arc]

OK, let us know the situation after applying the driver.