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 playing World of Warcraft, DRIVER_IRQL_NOT_LESS_OR_EQUAL

09 Jan 2014   #1
Citizen Krang

Windows 7 Professional 64 bit
 
 
BSOD playing World of Warcraft, DRIVER_IRQL_NOT_LESS_OR_EQUAL

Received a BSOD while playing World of Warcraft just a little bit earlier today. At the top was listed DRIVER_IRQL_NOT_LESS_OR_EQUAL which I thought might be important to include. According to BlueScreenView the error code is 0x000000d1 I believe.


My System SpecsSystem Spec
.
10 Jan 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

check for an update on this driver: Driver Reference Table - e1d62x64.sys

Driver Description: Intel Gigabit Adapter NDIS 6.x driver

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Citizen Krang\SF_09-01-2014\010914-18642-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e0e000 PsLoadedModuleList = 0xfffff800`030516d0
Debug session time: Fri Jan 10 05:40:06.637 2014 (UTC + 6:00)
System Uptime: 0 days 4:10:03.449
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {3a08, 2, 0, fffff8800152f782}

*** WARNING: Unable to verify timestamp for e1d62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1d62x64.sys
Probably caused by : NETIO.SYS ( NETIO!KfdIsV4InTransportFastEmpty+32 )

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

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bb100
GetUlongFromAddress: unable to read from fffff800030bb1c0
 0000000000003a08 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
NETIO!KfdIsV4InTransportFastEmpty+32
fffff880`0152f782 83b8083a000000  cmp     dword ptr [rax+3A08h],0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88007510a10 -- (.trap 0xfffff88007510a10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffffa800664d000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800152f782 rsp=fffff88007510ba8 rbp=0000000000000002
 r8=0000000000000002  r9=fffff88007510cd0 r10=fffff88007510e40
r11=0000000080000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
NETIO!KfdIsV4InTransportFastEmpty+0x32:
fffff880`0152f782 83b8083a000000  cmp     dword ptr [rax+3A08h],0 ds:00000000`00003a08=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002e83169 to fffff80002e83bc0

STACK_TEXT:  
fffff880`075108c8 fffff800`02e83169 : 00000000`0000000a 00000000`00003a08 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`075108d0 fffff800`02e81de0 : fffffa80`07640900 00000000`00000000 fffffa80`0aba2250 fffff880`07510cd0 : nt!KiBugCheckDispatch+0x69
fffff880`07510a10 fffff880`0152f782 : fffff880`0168f9c3 00000000`00000000 fffffa80`07614fa0 00000000`00000000 : nt!KiPageFault+0x260
fffff880`07510ba8 fffff880`0168f9c3 : 00000000`00000000 fffffa80`07614fa0 00000000`00000000 fffff880`07510d10 : NETIO!KfdIsV4InTransportFastEmpty+0x32
fffff880`07510bb0 fffff880`0165fafb : ffff0000`00000000 fffff880`01662325 fffffa80`75c16827 00000000`07510d10 : tcpip!IsInboundFastPath+0x43
fffff880`07510be0 fffff880`01662458 : fffffa80`0b065310 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!InetInspectReceiveDatagram+0x5b
fffff880`07510c80 fffff880`0166197a : fffffa80`0b065310 fffff800`02e8e900 fffffa80`0760a500 fffff800`02ffee80 : tcpip!TcpTcbReceive+0x11c
fffff880`07510d90 fffff880`01662aeb : fffffa80`09377eac fffffa80`07771008 00000000`00000000 fffffa80`09fa8100 : tcpip!TcpMatchReceive+0x1fa
fffff880`07510ee0 fffff880`0164565c : fffffa80`07640900 00000000`00000001 fffff880`000021eb 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`07510fb0 fffff880`016566f2 : fffffa80`08e4fc60 fffffa80`09411010 fffffa80`08fa0006 00000000`00000006 : tcpip!IpFlcReceivePreValidatedPackets+0x5bc
fffff880`07511110 fffff800`02e8f878 : 00000000`00000000 00000000`00004800 fffffa80`0aa06580 00000000`00000000 : tcpip!FlReceiveNetBufferListChainCalloutRoutine+0xa2
fffff880`07511160 fffff880`01656e22 : fffff880`01656650 00000000`00000000 fffffa80`090ac402 fffff880`07511400 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`07511240 fffff880`014f70eb : fffffa80`094117c0 00000000`00000000 fffffa80`08f831a0 00000000`00000000 : tcpip!FlReceiveNetBufferListChain+0xb2
fffff880`075112b0 fffff880`014c0ad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ndis!ndisMIndicateNetBufferListsToOpen+0xdb
fffff880`07511320 fffff880`0143aac1 : fffffa80`08f831a0 00000000`00000002 00000000`00000001 00000000`00000000 : ndis!ndisMDispatchReceiveNetBufferLists+0x1d6
fffff880`075117a0 fffff880`06cff4d3 : fffffa80`090ed000 00000000`00000001 fffffa80`093cf800 fffffa80`090eddc0 : ndis!NdisMIndicateReceiveNetBufferLists+0xc1
fffff880`075117f0 fffffa80`090ed000 : 00000000`00000001 fffffa80`093cf800 fffffa80`090eddc0 00000000`00000801 : e1d62x64+0x254d3
fffff880`075117f8 00000000`00000001 : fffffa80`093cf800 fffffa80`090eddc0 00000000`00000801 00000000`00000001 : 0xfffffa80`090ed000
fffff880`07511800 fffffa80`093cf800 : fffffa80`090eddc0 00000000`00000801 00000000`00000001 00000000`00000001 : 0x1
fffff880`07511808 fffffa80`090eddc0 : 00000000`00000801 00000000`00000001 00000000`00000001 fffff880`06cff6a1 : 0xfffffa80`093cf800
fffff880`07511810 00000000`00000801 : 00000000`00000001 00000000`00000001 fffff880`06cff6a1 00000000`00000001 : 0xfffffa80`090eddc0
fffff880`07511818 00000000`00000001 : 00000000`00000001 fffff880`06cff6a1 00000000`00000001 fffffa80`093cf800 : 0x801
fffff880`07511820 00000000`00000001 : fffff880`06cff6a1 00000000`00000001 fffffa80`093cf800 fffffa80`093cf800 : 0x1
fffff880`07511828 fffff880`06cff6a1 : 00000000`00000001 fffffa80`093cf800 fffffa80`093cf800 fffffa80`090ed000 : 0x1
fffff880`07511830 00000000`00000001 : fffffa80`093cf800 fffffa80`093cf800 fffffa80`090ed000 fffffa80`00000000 : e1d62x64+0x256a1
fffff880`07511838 fffffa80`093cf800 : fffffa80`093cf800 fffffa80`090ed000 fffffa80`00000000 fffffa80`090ed08c : 0x1
fffff880`07511840 fffffa80`093cf800 : fffffa80`090ed000 fffffa80`00000000 fffffa80`090ed08c 0000000a`00000001 : 0xfffffa80`093cf800
fffff880`07511848 fffffa80`090ed000 : fffffa80`00000000 fffffa80`090ed08c 0000000a`00000001 00000000`00000000 : 0xfffffa80`093cf800
fffff880`07511850 fffffa80`00000000 : fffffa80`090ed08c 0000000a`00000001 00000000`00000000 00000000`00000000 : 0xfffffa80`090ed000
fffff880`07511858 fffffa80`090ed08c : 0000000a`00000001 00000000`00000000 00000000`00000000 fffff880`07511ad8 : 0xfffffa80`00000000
fffff880`07511860 0000000a`00000001 : 00000000`00000000 00000000`00000000 fffff880`07511ad8 fffffa80`08a8f100 : 0xfffffa80`090ed08c
fffff880`07511868 00000000`00000000 : 00000000`00000000 fffff880`07511ad8 fffffa80`08a8f100 00000000`00000000 : 0x0000000a`00000001


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!KfdIsV4InTransportFastEmpty+32
fffff880`0152f782 83b8083a000000  cmp     dword ptr [rax+3A08h],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  NETIO!KfdIsV4InTransportFastEmpty+32

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5034f6a0

FAILURE_BUCKET_ID:  X64_0xD1_NETIO!KfdIsV4InTransportFastEmpty+32

BUCKET_ID:  X64_0xD1_NETIO!KfdIsV4InTransportFastEmpty+32

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

0: kd> lmvm e1d62x64
start             end                 module name
fffff880`06cda000 fffff880`06d55000   e1d62x64 T (no symbols)           
    Loaded symbol image file: e1d62x64.sys
    Image path: \SystemRoot\system32\DRIVERS\e1d62x64.sys
    Image name: e1d62x64.sys
    Timestamp:        Wed Jan 23 22:37:18 2013 (510011BE)
    CheckSum:         0007EAF6
    ImageSize:        0007B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
Please run these tests and report back the results.

1. SFC /scannow to check windows for corruption - SFC /SCANNOW - System File Checker
2. Disk check for errors on the hard drive - Run Disk Check in Windows 7
3. Troubleshoot apps by a clean boot - Performing a Clean Startup
4. Memtest86+ paying attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure
My System SpecsSystem Spec
Reply

 BSOD playing World of Warcraft, DRIVER_IRQL_NOT_LESS_OR_EQUAL




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while playing World of Warcraft
The game crashed and then from what I saw it also managed to cause BSOD.
BSOD Help and Support
BSOD playing world of warcraft
The BSOD only occurs when I play WoW.....I have tried updating all my drivers and even reformatting my computer in an attempt to get rid of the multiple BSODs when playing WoW.....Unfortunately it doesn't help. Hopefully you guys can see what's wrong Thanks for the help
BSOD Help and Support
BSOD while playing World of Warcraft (WoW)
Hey, I have had this problem for a couple of weeks. My laptop get BSOD everytime I'm playing WoW especially when I'm doing battlegrounds, PvP, etc. ... I have tried to reinstall Windows 7, updated all my drivers and tried registry cleaner and pc clean-up. But won't work anyway it keeps...
BSOD Help and Support
BSOD after playing World of Warcraft
Hello, I've been getting bsod for a few months now so I'm pretty frustrated with it, i've tried everything I can think of/found. (I updated ALL of my drivers) My CPU gets bsod after playing only certain games, for example: when I play "World of Warcraft", after I shut down "WoW", about 2-5 mins...
BSOD Help and Support
BSOD playing World Of Warcraft, DRIVER_IRQL_NOT_LESS_OR_EQUAL
I've been getting a BSOD while playing WOW, seems to only happen while playing. Win7 32bit Full Retail Intel Core i7-2600K Sandy Bridge 3.4GHz ASRock Z68 EXTREME4 GEN3 G.SKILL Ripjaws Series 8GB (2 x 4GB) GeForce GTX 460 x2 SLI
BSOD Help and Support
BSOD When Only Playing World Of Warcraft
My computer keeps crashing when playing WoW. It will flicker for about 1-2 minutes before it finally BSoD's. I have tried reinstalling OS and still same problem. My Drivers are also up to date according to Windows 7 Driver Update. The system is about 2 years old. The problem began when I upgraded...
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 08:56.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App