Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD - Driver IRQL Not Less Or Equal

06 Jan 2014   #1
xenonz98

Windows 7 Ultimate x64
 
 
BSOD - Driver IRQL Not Less Or Equal

Hi,

Desperate to have some help. My computer's been giving me BSOD these few days.
I have updated my profile with as much information as possible


-Windows Ultimate 64bit
-OEM version

computer age - under one year
os age - under one year

Hope to hear news soon...


My System SpecsSystem Spec
.
06 Jan 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Hi xenonz98.

Update Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20) driver from www.killergaming.com/solutions/Embedded_Ethernet

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.
_________________________________________________________________________________________________
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800b531000, 2, 0, fffff88007772fa0}

Unable to load image \SystemRoot\system32\DRIVERS\e22w7x64.sys, Win32 error 0n2
*** 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
---------

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

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


OVERLAPPED_MODULE: Address regions for 'EX64' and 'ENG64.SYS' overlap

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c1100
 fffff8800b531000 

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  LolClient.exe

TRAP_FRAME:  fffff8800c7e7670 -- (.trap 0xfffff8800c7e7670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffffa800a9b06e8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007772fa0 rsp=fffff8800c7e7800 rbp=fffffa800a9b0630
 r8=0000000000000300  r9=0000000000000000 r10=fffffa80089b4280
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
e22w7x64+0x19fa0:
fffff880`07772fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14 ds:0db4:00000000`00000248=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e89169 to fffff80002e89bc0

STACK_TEXT:  
fffff880`0c7e7528 fffff800`02e89169 : 00000000`0000000a fffff880`0b531000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c7e7530 fffff800`02e87de0 : fffff8a0`06540124 fffff8a0`00022290 fffff880`0c7e7810 fffffa80`089a0b40 : nt!KiBugCheckDispatch+0x69
fffff880`0c7e7670 fffff880`07772fa0 : fffffa80`089a0b40 00000000`00001864 fffffa80`089a0b58 fffffa80`089a0b40 : nt!KiPageFault+0x260
fffff880`0c7e7800 fffffa80`089a0b40 : 00000000`00001864 fffffa80`089a0b58 fffffa80`089a0b40 fffffa80`0899ea38 : e22w7x64+0x19fa0
fffff880`0c7e7808 00000000`00001864 : fffffa80`089a0b58 fffffa80`089a0b40 fffffa80`0899ea38 fffff880`07771eb2 : 0xfffffa80`089a0b40
fffff880`0c7e7810 fffffa80`089a0b58 : fffffa80`089a0b40 fffffa80`0899ea38 fffff880`07771eb2 00000000`00000002 : 0x1864
fffff880`0c7e7818 fffffa80`089a0b40 : fffffa80`0899ea38 fffff880`07771eb2 00000000`00000002 00000000`00000000 : 0xfffffa80`089a0b58
fffff880`0c7e7820 fffffa80`0899ea38 : fffff880`07771eb2 00000000`00000002 00000000`00000000 fffffa80`0a26aee0 : 0xfffffa80`089a0b40
fffff880`0c7e7828 fffff880`07771eb2 : 00000000`00000002 00000000`00000000 fffffa80`0a26aee0 00000000`0000024c : 0xfffffa80`0899ea38
fffff880`0c7e7830 00000000`00000002 : 00000000`00000000 fffffa80`0a26aee0 00000000`0000024c fffffa80`08bdf7c8 : e22w7x64+0x18eb2
fffff880`0c7e7838 00000000`00000000 : fffffa80`0a26aee0 00000000`0000024c fffffa80`08bdf7c8 fffff880`0777c432 : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e22w7x64+19fa0
fffff880`07772fa0 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

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

3: kd> lmvm e22w7x64
start             end                 module name
fffff880`07759000 fffff880`07783000   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
My System SpecsSystem Spec
09 Jan 2014   #3
xenonz98

Windows 7 Ultimate x64
 
 

Hi I have updated the drivers and i'm still seeing the BSOD..
My System SpecsSystem Spec
.

10 Jan 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

It appears that the driver is not updated.
Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff8800796a000, 2, 0, fffff88007781fa0}

Unable to load image \SystemRoot\system32\DRIVERS\e22w7x64.sys, Win32 error 0n2
*** 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
---------

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003106100
 fffff8800796a000 

CURRENT_IRQL:  2

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

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  java.exe

TRAP_FRAME:  fffff8800b5ef670 -- (.trap 0xfffff8800b5ef670)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000003f rbx=0000000000000000 rcx=fffffa8009368aa8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88007781fa0 rsp=fffff8800b5ef800 rbp=fffffa80093689f0
 r8=0000000000000300  r9=0000000000000000 r10=fffffa8008b24280
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
e22w7x64+0x19fa0:
fffff880`07781fa0 4c39b748020000  cmp     qword ptr [rdi+248h],r14 ds:9db4:00000000`00000248=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002ece169 to fffff80002ecebc0

STACK_TEXT:  
fffff880`0b5ef528 fffff800`02ece169 : 00000000`0000000a fffff880`0796a000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0b5ef530 fffff800`02eccde0 : fffff8a0`06546124 fffff8a0`00024010 fffff880`0b5ef810 fffffa80`08b10b40 : nt!KiBugCheckDispatch+0x69
fffff880`0b5ef670 fffff880`07781fa0 : fffffa80`08b10b40 00000000`0000115c fffffa80`08b10b58 fffffa80`08b10b40 : nt!KiPageFault+0x260
fffff880`0b5ef800 fffffa80`08b10b40 : 00000000`0000115c fffffa80`08b10b58 fffffa80`08b10b40 fffffa80`08b0ea38 : e22w7x64+0x19fa0
fffff880`0b5ef808 00000000`0000115c : fffffa80`08b10b58 fffffa80`08b10b40 fffffa80`08b0ea38 fffff880`07780eb2 : 0xfffffa80`08b10b40
fffff880`0b5ef810 fffffa80`08b10b58 : fffffa80`08b10b40 fffffa80`08b0ea38 fffff880`07780eb2 00000000`00000002 : 0x115c
fffff880`0b5ef818 fffffa80`08b10b40 : fffffa80`08b0ea38 fffff880`07780eb2 00000000`00000002 00000000`00000000 : 0xfffffa80`08b10b58
fffff880`0b5ef820 fffffa80`08b0ea38 : fffff880`07780eb2 00000000`00000002 00000000`00000000 fffffa80`0732c3d0 : 0xfffffa80`08b10b40
fffff880`0b5ef828 fffff880`07780eb2 : 00000000`00000002 00000000`00000000 fffffa80`0732c3d0 00000000`0000024c : 0xfffffa80`08b0ea38
fffff880`0b5ef830 00000000`00000002 : 00000000`00000000 fffffa80`0732c3d0 00000000`0000024c fffffa80`08d58528 : e22w7x64+0x18eb2
fffff880`0b5ef838 00000000`00000000 : fffffa80`0732c3d0 00000000`0000024c fffffa80`08d58528 fffff880`0778b432 : 0x2


STACK_COMMAND:  kb

FOLLOWUP_IP: 
e22w7x64+19fa0
fffff880`07781fa0 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

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

1: kd> lmvm e22w7x64
start             end                 module name
fffff880`07768000 fffff880`07792000   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
My System SpecsSystem Spec
10 Jan 2014   #5
xenonz98

Windows 7 Ultimate x64
 
 

I could not load the website at all to download the Update Killer e2200 PCI-E Gigabit Ethernet Controller (NDIS 6.20) driver, both chrome and internet explorer keeps showing "The webpage cannot be loaded/This page can't be displayed"

I had previously tried to update the driver using MSI Live Update 5 to download the ethernet driver instead, and it said it's been installed.

In that case, is it possible to help me download the driver application from the site??
My System SpecsSystem Spec
10 Jan 2014   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Yeah neither of the links to Killer is working ATM. Very Strange. May be the website is down

But the notification in device manager ... that is not the true.

Try the updating after a few days?
My System SpecsSystem Spec
20 Mar 2014   #7
Starzrus

Windows 7 Ultimate x64
 
 

Driver Downloads | Qualcomm Atheros, Inc.
This is the website for their driver. I am currently having the same trouble. Have you solved it yet?
My System SpecsSystem Spec
Reply

 BSOD - Driver IRQL Not Less Or Equal




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Driver IRQL Not Less or Equal BSOD
Hi All, I first experienced this BSOD error around 5 months ago. My computer got infected, I believe, around the same time but I am not sure whether the BSOD is related to this. I have since completed a clean install of Windows 7 HP x64 but the BSOD problem persists. The 'Driver IRQL Not Less or...
BSOD Help and Support
BSOD Driver IRQL Not Less or Equal
Was watching a YouTube video and browsing a video game client menu while this happened. Having this error for the 3rd time and not sure of the origins. Currently trying to update all drivers. ZIP of the BSOD support instructions is attached.
BSOD Help and Support
BSOD: driver irql less or equal
Hi Guys, I'm getting BSOD at a different scenario while playing games. Can you help me determine the cause? I have attached the minidump i got. Appreciate your response. TIA! regards, Paul
BSOD Help and Support
BSOD - driver irql not less or equal
Hi, Recently my home pc has been re-starting with a BSOD sayying IRQL_NOT_LESS_OR_EQUAL. This forum has been a great help to me in the past and I hope you can help me again. I have completed the details of my system spec on my profile and completed the analysis as detailed in the how to post...
BSOD Help and Support
BSOD IRQL driver not less or equal
Ok I have had a custom computer built some time ago (1-2 years ago I think). I built it mainly for gaming and surfing the web. I have Windows 7 Professial 32-bit. The problem I have is the BSOD only happens when i surf the net. Different internet sites may or may not cause the BSOD. Sites like...
BSOD Help and Support
BSOD Driver Irql Not Less Or Equal
I am getting BSOD error Driver Irql Not Less Or Equal After running a crack file which is downloaded,i forgot the filename because when it is run the system was power down. now for every restart after logon it shows the Error " Driver Irql Not Less Or Equal" i am sure it is a virus...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

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

All times are GMT -5. The time now is 20:12.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App