IRQL_Not_Less_Or_Equal on newly formatted PC

[prizna]

I formatted and reinstalled Windows 7 Home Premium on my custom build yesterday and have just received an 'IRQL_Not_Less_Or_Equal' BSOD, I installed all of the Windows updates yesterday (about 2 or 3 lots of updates) and when I booted up my PC this morning there was another 15 or so updates to be installed, I started the updates and decided to go do something else during the update and when I came back I had a BSOD, so I'm not exactly sure when it occurred but I'm pretty sure it was during the update.

I'm not sure if it is relevant but after restarting from the BSOD, my wireless was not working and I had to disconnect and reconnect it (I have a Netgear USB wireless adapter) to get it working again.

I followed the instructions and have attached the zip folder from the diagnostic tool.

thanks,

 

[koolkat77]

Caused by a driver: Netgear Neutral Wireless Solution

Check for an update on its driver: Driver Reference Table

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_05-08-2013\SF_05-08-2013\080513-9016-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Machine Name:
Kernel base = 0xfffff800`02c06000 PsLoadedModuleList = 0xfffff800`02e49670
Debug session time: Mon Aug  5 06:50:10.638 2013 (UTC + 6:00)
System Uptime: 0 days 1:29:55.467
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, fffff80002c8292c}

*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
Probably caused by : scmndisp.sys ( scmndisp+16d1 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002c8292c, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb3100
GetUlongFromAddress: unable to read from fffff80002eb31c0
 0000000000000000 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`02c8292c f00fba2e07      lock bts dword ptr [rsi],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009ebd70 -- (.trap 0xfffff880009ebd70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000054705 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002c8292c rsp=fffff880009ebf00 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff880009ee180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x13c:
fffff800`02c8292c f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7b1a9 to fffff80002c7bc00

STACK_TEXT:  
fffff880`009ebc28 fffff800`02c7b1a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009ebc30 fffff800`02c79e20 : 00000000`00000000 a079654b`02e81798 fffffa80`06a57ad8 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009ebd70 fffff800`02c8292c : fffffa80`0a4881a0 fffffa80`0b7d5a90 fffffa80`0b33aca0 fffffa80`0b7d5c80 : nt!KiPageFault+0x260
fffff880`009ebf00 fffff880`020c25b2 : 00000000`00000000 00000000`00000000 fffffa80`0a488100 fffffa80`0b488600 : nt!KeWaitForSingleObject+0x13c
fffff880`009ebfa0 fffff880`021f26d1 : 00000000`00000000 fffffa80`0b488e00 fffff880`009ec050 00000000`000001f1 : ndis!NdisWaitEvent+0x32
fffff880`009ebfe0 00000000`00000000 : fffffa80`0b488e00 fffff880`009ec050 00000000`000001f1 00000000`00000110 : scmndisp+0x16d1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
scmndisp+16d1
fffff880`021f26d1 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  scmndisp+16d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: scmndisp

IMAGE_NAME:  scmndisp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ddf7d3e

FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1

BUCKET_ID:  X64_0xA_scmndisp+16d1

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

1: kd> lmvm scmndisp
start             end                 module name
fffff880`021f1000 fffff880`021fb000   scmndisp T (no symbols)           
    Loaded symbol image file: scmndisp.sys
    Image path: \SystemRoot\system32\DRIVERS\scmndisp.sys
    Image name: scmndisp.sys
    Timestamp:        [U]Fri May 27 16:30:22 2011[/U] (4DDF7D3E)
    CheckSum:         00009C0C
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[prizna]

Thanks for the reply, I was unable to find a new driver that made a difference, I have read in other forum posts that there is meant to be a driver version that can be obtained through Windows Update that does not include the problematic scmndisp.sys but I am unable to find it.

 

[prizna]

I have just received this BSOD again after 3 months of no problems, I have removed the problematic driver and have purchased a new wireless adapter since the last time I received this BSOD and hadn't had any BSOD until now, I have attached the folder from the diagnostics tool.

thanks in advance,

 

[koolkat77]

• Uninstall kaspersky and use Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
  • Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
  • Help protect your PC with Microsoft Security Essentials
  • Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

• Also take a look at: Good & Free System Security Combination

• System File Checker
  • The SFC /SCANNOW Command - System File Checker scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible. If you have modified your system files as in theming explorer/system files, running sfc /scannow will revert the system files to it's default state.
    • Link to full tutorial: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
• Run Disk Check in Windows 7
  • Run this on your Hard Drive(s). This will show you how to run Check Disk or chkdsk in Windows 7 to check a selected hard disk for file system errors and bad sectors on it. With both boxes checked for all HDDs and with Automatically fix file system errors. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
    • Link to full tutorial: http://www.sevenforums.com/tutorials/433-disk-check.html

 

[prizna]

Was the crash definately caused by Kaspersky or is Kaspersky just a likely cause?

thanks,

 

[koolkat77]

It contributes but you can put it back later.