BSOD Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

#1
Hi,

I am getting Windows 7 crashes (BSOD) with alarmingly increasing frequency.

A bit of googling and I reached this software called WhoCrashed.

THe output of the last few crashes is below.

Can someone suggest what could be the problem

System Information (local)[HR][/HR]
computer name: RUBAL-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i3 CPU M 380 @ 2.53GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 3077238784 total
VM: 2147352576, free: 1982308352


[HR][/HR]Crash Dump Analysis[HR][/HR]
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 12/2/2011 4:47:52 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120211-18642-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x664C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005815FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/2/2011 4:47:52 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: netw5s64.sys (NETw5s64+0x13FB5)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005815FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netw5s64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: netw5s64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: netw5s64.sys Intel Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL




On Fri 12/2/2011 3:14:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120211-15709-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x664C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005889FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/2/2011 2:26:05 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120211-23774-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x664C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005845FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/2/2011 2:13:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120211-17721-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x664C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005866FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/2/2011 1:48:49 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120211-16286-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x664C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF88005822FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/2/2011 1:18:47 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\120211-19952-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x664C0)
Bugcheck code: 0xD1 (0x0, 0x2, 0x0, 0xFFFFF880058B0FB5)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
 


gamerk2

Well-Known Member
#2
My initial thought is that its probably bad RAM, as I find it very unlikely the Windows Kernal itself is crashing. Run a memory diagnostic with either memtest86 or Windows Memory Diagnostic, and check to see if any of your RAM is faulty.
 


Trouble

Noob Whisperer
#3
Hello and welcome to the forums.
Please read the first post in this sticky thread here How to ask for help with a BSOD problem
Do your best to accumulate the data required.
Run the SF Diagnostic tool (download and right click the executable and choose run as administrator)
Download and run CPUz. Use the Windows snipping tool to gather images from all tabs including all slots populated with memory under the SPD tab.
Likewise RAMMon. Export the html report, put everything into a desktop folder that you've created for this purpose, zip it up and attach it to your next post (right click it and choose send to, compressed (zipped) folder.
Good luck
Randy
 


#4
Hi Randy,

Attached the SF tool output and minidumps zipped.

I also checked with Windows Memory Diagnostic and the RAM seems ok.

Please advise.

Thanks :)
 


Attachments

#5
Attaching CPU-Z output.
 


Attachments

Trouble

Noob Whisperer
#6
Hello and welcome to the forums.
Well at least their consistent, everyone or at least everyone that I had the patience to examine all look like this
DUMP FILE:
Code:
Unable to load image \SystemRoot\system32\DRIVERS\[U][B][COLOR=#ff0000]NETw5s64.sys[/COLOR][/B][/U], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [COLOR=#ff0000][U][B]NETw5s64.sys[/B][/U][/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for NETw5s64.sys
Probably caused by : [B][U][COLOR=#ff0000]NETw5s64.sys [/COLOR][/U][/B]( [B][U][COLOR=#ff0000]NETw5s64[/COLOR][/U][/B]+13fb5 )
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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800582cfb5, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f80e0
 0000000000000000 
CURRENT_IRQL:  2
FAULTING_IP: 
[B][U][COLOR=#ff0000]NETw5s64[/COLOR][/U][/B]+13fb5
fffff880`0582cfb5 48833b00        cmp     qword ptr [rbx],0
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
TRAP_FRAME:  fffff880027cc0d0 -- (.trap 0xfffff880027cc0d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa800579d9d0
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800582cfb5 rsp=fffff880027cc260 rbp=fffffa8008a6f990
 r8=fffffa8008fcc500  r9=0000000000000000 r10=fffff8000323b760
r11=0000000000000002 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
[B][U][COLOR=#ff0000]NETw5s64[/COLOR][/U][/B]+0x13fb5:
fffff880`0582cfb5 48833b00        cmp     qword ptr [rbx],0 ds:00000000`00000000=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER:  from fffff800030bea29 to fffff800030bf4c0
STACK_TEXT:  
fffff880`027cbf88 fffff800`030bea29 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`027cbf90 fffff800`030bd6a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`027cc0d0 fffff880`0582cfb5 : 00000000`00000004 00000000`00000000 fffffa80`00000002 00000000`00000115 : nt!KiPageFault+0x260
fffff880`027cc260 00000000`00000004 : 00000000`00000000 fffffa80`00000002 00000000`00000115 00000000`000000f9 : [U][B][COLOR=#ff0000]NETw5s64[/COLOR][/B][/U]+0x13fb5
fffff880`027cc268 00000000`00000000 : fffffa80`00000002 00000000`00000115 00000000`000000f9 fffffa80`0776ffb0 : 0x4
STACK_COMMAND:  kb
FOLLOWUP_IP: 
[B][U][COLOR=#ff0000]NETw5s64[/COLOR][/U][/B]+13fb5
fffff880`0582cfb5 48833b00        cmp     qword ptr [rbx],0
SYMBOL_STACK_INDEX:  3
SYMBOL_NAME: [B][U][COLOR=#ff0000] NETw5s64[/COLOR][/U][/B]+13fb5
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: [B][U][COLOR=#ff0000]NETw5s64[/COLOR][/U][/B]
IMAGE_NAME:  [COLOR=#ff0000][U][B]NETw5s64.sys[/B][/U][/COLOR]
DEBUG_FLR_IMAGE_TIMESTAMP:  4ba1b871
FAILURE_BUCKET_ID:  X64_0xD1_[B][U][COLOR=#ff0000]NETw5s64[/COLOR][/U][/B]+13fb5
BUCKET_ID:  X64_0xD1_[COLOR=#ff0000][U][B]NETw5s64[/B][/U][/COLOR]+13fb5
So I'm going to go out on a limb here and suggest that we start with updating the driver for your Intel WiFi Link 1000 BGN from
Version 13.2.0.30 02/18/2010
to
Version 14.2.0.10 09/01/2011 from here http://downloadcenter.intel.com/SearchResult.aspx?lang=eng&ProductFamily=Wireless+Networking&ProductLine=Intel®+Centrino®+Wi-Fi+Products&ProductProduct=Intel®+WiFi+Link+1000&ProdId=3141&LineId=1784&FamilyId=1783 select your flavor of Windows 7 (32 or 64 bit)
Good luck and keep us posted. Attach any new dump files if Blue Screens persist.
Regards
Randy
 


Last edited:
#7
The response is much appreciated

Just did as mentioned. Will report if I still see any BSOD's

Many thanks!!

:)
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.