BSoD - DRIVER_IRQL_NOT_LESS_OR_EQUAL

[Third Policeman]

I've started getting these DRIVER_IRQL_NOT_LESS_OR_EQUAL crashes with increasing regularity and now they've happened 3 times in the same week and I'm getting worried. (BSoDs are such a grim reminder of your computer's - and your own - mortality)

I wasn't able to do a System Health Report, I kept getting a "The parameter is incorrect" error message. I have attached a Windows_NT6_BSOD_jcgriff2 folder, though. I can't remember what my system specs are, but my computer is an Asus G73JW. If the specs are terribly important I guess I can find them.

 

[Wallonn7]

Hi Third Policeman and welcome to SF!
Use CPU-Z (.zip, no installation) to fill out your system specs.
Run Driver Verifier.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Upload Windows_NT6_BSOD_jcgriff2.zip again as soon as BSOD happens.

 

[Third Policeman]

When I restarted my computer after running the verifier, I got a bluescreen immediately. Now when I try to start my computer, it offers me the options to either start Windows normally (which bluescreens) or do some startup repair thing. What should I do?

 

[Wallonn7]

When I restarted my computer after running the verifier, I got a bluescreen immediately. Now when I try to start my computer, it offers me the options to either start Windows normally (which bluescreens) or do some startup repair thing. What should I do?

Reboot in safe mode. Disable Driver Verifier. Upload Windows_NT6_BSOD_jcgriff2.zip again.

 

[Third Policeman]

Here.

 

[Wallonn7]

Hi Third Policeman.
Please uninstall tbbMeter - its "pssdklbf.sys" is the culprit - and replace it with this one - NetSpeedMonitor -, if you are interested.
I use it and I have no problems with it.
Then use "chkdsk /f" to correct some errors. And then SFC /SCANNOW Command.
Let us know if the BSODs cease.

Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`03207000 PsLoadedModuleList = 0xfffff800`03444e50
Debug session time: Fri Jun 17 06:27:09.708 2011 (UTC - 3:00)
System Uptime: 0 days 8:19:10.269
Loading Kernel Symbols
...............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8014579000, 2, 0, fffff88009053af0}

Unable to load image \??\C:\Windows\system32\Drivers\pssdklbf.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for pssdklbf.sys
*** ERROR: Module load completed but symbols could not be loaded for pssdklbf.sys
Probably caused by : [B][COLOR=Red]pssdklbf.sys[/COLOR][/B] ( pssdklbf+caf0 )

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

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034af0e0
 fffffa8014579000 

CURRENT_IRQL:  2

FAULTING_IP: 
pssdklbf+caf0
fffff880`09053af0 488b040a        mov     rax,qword ptr [rdx+rcx]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff88003189ea0 -- (.trap 0xfffff88003189ea0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=417ada8bd1bf5ac3 rbx=0000000000000000 rcx=fffff8800be717b8
rdx=0000020008707846 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88009053af0 rsp=fffff8800318a038 rbp=0000000000000b41
 r8=00000000000005d1  r9=000000000000000e r10=0000000000001615
r11=fffff8800be713b4 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
pssdklbf+0xcaf0:
fffff880`09053af0 488b040a        mov     rax,qword ptr [rdx+rcx] ds:05d5:fffffa80`14578ffe=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003276c69 to fffff80003277700

STACK_TEXT:  
fffff880`03189d58 fffff800`03276c69 : 00000000`0000000a fffffa80`14579000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03189d60 fffff800`032758e0 : fffffa80`04108002 fffffa80`14578bfa fffff880`0318a440 fffff880`0318a028 : nt!KiBugCheckDispatch+0x69
fffff880`03189ea0 fffff880`09053af0 : fffff880`0904b62f fffffa80`0459fdd0 fffff880`03163180 fffffa80`0459fe08 : nt!KiPageFault+0x260
fffff880`0318a038 fffff880`0904b62f : fffffa80`0459fdd0 fffff880`03163180 fffffa80`0459fe08 fffffa80`0408cec0 : pssdklbf+0xcaf0
fffff880`0318a040 fffffa80`0459fdd0 : fffff880`03163180 fffffa80`0459fe08 fffffa80`0408cec0 00000000`00000000 : pssdklbf+0x462f
fffff880`0318a048 fffff880`03163180 : fffffa80`0459fe08 fffffa80`0408cec0 00000000`00000000 fffffa80`139dde60 : 0xfffffa80`0459fdd0
fffff880`0318a050 fffffa80`0459fe08 : fffffa80`0408cec0 00000000`00000000 fffffa80`139dde60 fffffa80`0459fe08 : 0xfffff880`03163180
fffff880`0318a058 fffffa80`0408cec0 : 00000000`00000000 fffffa80`139dde60 fffffa80`0459fe08 fffff880`07116a91 : 0xfffffa80`0459fe08
fffff880`0318a060 00000000`00000000 : fffffa80`139dde60 fffffa80`0459fe08 fffff880`07116a91 fffffa80`03cd8b28 : 0xfffffa80`0408cec0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
pssdklbf+caf0
fffff880`09053af0 488b040a        mov     rax,qword ptr [rdx+rcx]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  pssdklbf+caf0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: pssdklbf

IMAGE_NAME:  pssdklbf.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a408af2

FAILURE_BUCKET_ID:  X64_0xD1_pssdklbf+caf0

BUCKET_ID:  X64_0xD1_pssdklbf+caf0

Followup: MachineOwner

 

[Third Policeman]

I never liked that bandwidth monitor anyhow. I'll more likely let you know if the BSoDs don't cease. Thanks for the help.

 

[Wallonn7]

You're welcome.
Keep reporting.