DRIVER_IRQL_NOT_LESS_OR_EQUAL

Joined
Jan 23, 2012
Messages
2
Reaction score
0
Hi guys, I know that there are a ton of threads about this issue on the forum, but I also know that the fix is different for everyone, hence my making this thread.

I need urgent help guys as my PC is crashing almost every night.

http://i.imgur.com/G1duq.jpg

Here is a picture of the BSOD.


Attached are two minidumps, from the 22nd and the 23rd, 012312-24523-01 is from the 23rd and is the latest one. These two dumps are the only two files located in C:\Windows\Minidump.

My PC Specs:

PSU: Corsair VX-450
GPU: NVidia GTX 560
CPU: Intel e6500
MOBO: Gigabyte GA-G31M-ES2L
RAM: 4gb DDR2 G-Skill [Brand New]

Connected USB Devices:
Saitek x52 pro flight control system
Cyber Snipa Sonar 5.1 Headset
USB keyboard
USB wireless mouse


Thanks for the help guys, I will be very grateful should anyone be able to find the solution to my problem.


Anteara.
 

Attachments

Ace

Microsoft MVP
Joined
Jul 7, 2011
Messages
314
Reaction score
61
Summary
Code:
*******************************************************************************
*                                                                             *
*                        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: 0000000000000323, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880014c5c42, address which referenced memory
 
Debugging Details:
------------------
 
 
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002b06100
 0000000000000323 
 
CURRENT_IRQL:  2
 
FAULTING_IP: 
ndis!NdisQueryNetBufferPhysicalCount+32
fffff880`014c5c42 8b4a28          mov     ecx,dword ptr [rdx+28h]
 
CUSTOMER_CRASH_COUNT:  1
 
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
 
BUGCHECK_STR:  0xD1
 
PROCESS_NAME:  uTorrent.exe
 
TRAP_FRAME:  fffff8800c099d20 -- (.trap 0xfffff8800c099d20)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=00000000000002fb rsi=0000000000000000 rdi=0000000000000000
rip=fffff880014c5c42 rsp=fffff8800c099eb8 rbp=fffffa80042e9e00
 r8=0000000000000000  r9=000000000000000c r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
ndis!NdisQueryNetBufferPhysicalCount+0x32:
fffff880`014c5c42 8b4a28          mov     ecx,dword ptr [rdx+28h] ds:fca0:00000000`00000323=????????
Resetting default scope
 
LAST_CONTROL_TRANSFER:  from fffff800028d31e9 to fffff800028d3c40
 
STACK_TEXT:  
fffff880`0c099bd8 fffff800`028d31e9 : 00000000`0000000a 00000000`00000323 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0c099be0 fffff800`028d1e60 : fffff880`05e6f758 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0c099d20 fffff880`014c5c42 : fffff880`05e6f52d 00000000`00000000 00000000`00000000 fffffa80`06c33030 : nt!KiPageFault+0x260
fffff880`0c099eb8 fffff880`05e6f52d : 00000000`00000000 00000000`00000000 fffffa80`06c33030 fffffa80`06c40660 : ndis!NdisQueryNetBufferPhysicalCount+0x32
fffff880`0c099ec0 00000000`00000000 : 00000000`00000000 fffffa80`06c33030 fffffa80`06c40660 fffffa80`05394040 : L1C62x64+0x552d
 
 
STACK_COMMAND:  kb
 
FOLLOWUP_IP: 
L1C62x64+552d
fffff880`05e6f52d ??              ???
 
SYMBOL_STACK_INDEX:  4
 
SYMBOL_NAME:  L1C62x64+552d
 
FOLLOWUP_NAME:  MachineOwner
 
MODULE_NAME: L1C62x64
 
IMAGE_NAME:  L1C62x64.sys
 
DEBUG_FLR_IMAGE_TIMESTAMP:  4a6d5184
 
FAILURE_BUCKET_ID:  X64_0xD1_L1C62x64+552d
 
BUCKET_ID:  X64_0xD1_L1C62x64+552d
 
Followup: MachineOwner
---------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)
Similar to 0xA this error is caused when the attempt was made to access a pageable address while IRQL was too high or the memory itself is corrupt. Usually common to assume this one is a driver issue.

This particular error was initiated from a read operation, and directly points to L1C62x64.sys. Most recent in trap indicates a query for the net buffer physical count by uTorrent.exe.

BOTH crash dumps with the same error point towards L1C62x64.sys driver, which is your Atheros L1c PCI-E Gigabit Ethernet Controller. I would suggest reinstalling that network driver to test, as it seems to be the problem here by uTorrent calling it.



Reinstalling Drivers:
  • 1. Make sure after uninstalling, that a reboot is made
    2. After rebooting your system install the necessary drivers, and do one more final reboot for all possible changes to take effect
Download and install Driver Sweeper to remove and reinstall the following drivers: L1C62x64.sys
*Please note the above steps for proper driver reinstallation

Upon noticing other errors however, I would also suggest this...



1) Download and run Memtest86 on boot: http://www.memtest86.com
  • Make sure to let it run and do it's thing for about the first 6 tests. If it passes those, then everything should be good, otherwise any failure to pass those tests indicates a corruption in your memory.
  • If you get an error on one of the tests, then you should try by booting up your computer with each RAM inserted separately one at a time. When you find one that doesn't return any errors then test it in every single RAM slot to test for a bad socket.
 
Last edited:

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top