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 - driver irql not less or equal

07 Apr 2012   #1
estephens

Windows 7 Ultimate
 
 
BSOD - driver irql not less or equal

Hi,

Recently my home pc has been re-starting with a BSOD sayying IRQL_NOT_LESS_OR_EQUAL. This forum has been a great help to me in the past and I hope you can help me again.

I have completed the details of my system spec on my profile and completed the analysis as detailed in the how to post guide.

The other details as suggested in the guide are?:
Is Windows 7 . . .
- x86 (32-bit) or x64 ? Windows 7 Ultimate 64 bit
- the original installed OS on the system? as above
- an OEM or full retail version? Full retail version

- What is the age of system (hardware)? 1.5 years
- What is the age of OS installation (have you re-installed the OS?) 1.5 years and has not been re-installed.

Thanks in advance for any assistance you can offer.

Ed


My System SpecsSystem Spec
.
08 Apr 2012   #2
writhziden

Windows 7 Home Premium 64 Bit
 
 

Problem Devices:
Code:
Shrew Soft Lightweight Filter	ROOT\LEGACY_VFLT\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Unibrain 1394 PC	UB1394\UNIBRAIN&1394_PC\004DE58B0000241D	The drivers for this device are not installed.
Shrew Soft Inc : Support
Unibrain Software Download Section


Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):
Code:
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	12036	8	200	1380	7/04/2012 5:29 PM	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	14476	8	200	1380	7/04/2012 5:29 PM	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	13824	8	200	1380	7/04/2012 5:30 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 2:35 PM

Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\estephens\Windows_NT6_BSOD_jcgriff2\040712-55427-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03202000 PsLoadedModuleList = 0xfffff800`03446650
Debug session time: Sat Apr  7 01:26:14.940 2012 (UTC - 6:00)
System Uptime: 0 days 9:21:35.017
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {30, 2, 1, fffff8000328812f}

Probably caused by : afd.sys ( afd!AfdAbortConnection+20 )

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

0: 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: 0000000000000030, 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: fffff8000328812f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b0100
 0000000000000030 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`0328812f 488717          xchg    rdx,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  UNS.exe

TRAP_FRAME:  fffff8800dd8c520 -- (.trap 0xfffff8800dd8c520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800dd8c720 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328812f rsp=fffff8800dd8c6b0 rbp=fffff8800dd8c768
 r8=fffff8800dd8c720  r9=0000000003f6df08 r10=0000000000000001
r11=fffffa80093930c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`0328812f 488717          xchg    rdx,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000327e2e9 to fffff8000327ed40

STACK_TEXT:  
fffff880`0dd8c3d8 fffff800`0327e2e9 : 00000000`0000000a 00000000`00000030 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0dd8c3e0 fffff800`0327cf60 : fffffa80`08589460 00000000`0000000a 00000000`00000001 fffffa80`b23de500 : nt!KiBugCheckDispatch+0x69
fffff880`0dd8c520 fffff800`0328812f : 00000000`0000001c fffff800`0325ee75 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0dd8c6b0 fffff880`05162100 : fffff880`0dd8c768 fffffa80`b23de520 00000000`00000000 fffff880`050ffc76 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff880`0dd8c700 fffff880`05167e57 : fffffa80`072be580 fffffa80`4a4da530 fffffa80`066b4880 fffffa80`b23de520 : afd!AfdAbortConnection+0x20
fffff880`0dd8c750 fffff880`01b8761a : fffffa80`0752e580 fffffa80`0752e580 fffffa80`4a4da501 fffff880`00000010 : afd!AfdTLInspectEventHandler+0x4d7
fffff880`0dd8c7d0 fffff880`01b16176 : 00000000`4f0c2e77 fffff880`0dd8ca68 00000000`4f0c2e77 fffffa80`0772d438 : tcpip!TcpInspectConnectionOnListener+0x13a
fffff880`0dd8c880 fffff880`01aae8c2 : 00000000`4f0c2e77 fffffa80`09755010 fffffa80`066b4880 fffffa80`066def00 : tcpip! ?? ::FNODOBFM::`string'+0x47e54
fffff880`0dd8c910 fffff880`01ab02ab : fffffa80`0772d438 fffffa80`09286300 00000000`00000000 fffff880`01806500 : tcpip!TcpMatchReceive+0x442
fffff880`0dd8ca60 fffff880`01a8affa : fffffa80`066def00 fffff880`000055f6 fffff880`00006042 fffff880`0dd86042 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`0dd8cb30 fffff800`0328aa88 : fffff880`01bc69a0 fffffa80`03deeb06 fffffa80`03deeb60 ffffd319`20076902 : tcpip!IppLoopbackTransmit+0x11a
fffff880`0dd8cbe0 fffff880`01a8b90f : fffff880`01ad7c70 fffff880`018b953a fffff880`0dd8ce02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0dd8ccc0 fffff880`01aae277 : fffffa80`0772d1a0 00000000`00000004 fffff880`0dd8d101 00000000`00000000 : tcpip!IppLoopbackEnqueue+0x22f
fffff880`0dd8cd70 fffff880`01ab4de5 : fffffa80`066dec50 00000000`00000001 00000000`00000001 00000000`00000080 : tcpip!IpNlpFastSendDatagram+0xb77
fffff880`0dd8d120 fffff880`01ac109f : 00000000`03f44143 fffffa80`085a40a8 00000000`00000008 fffffa80`c234d38c : tcpip!TcpTcbSend+0x495
fffff880`0dd8d3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpCreateAndConnectTcbRateLimitComplete+0x39f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdAbortConnection+20
fffff880`05162100 0fba6b0414      bts     dword ptr [rbx+4],14h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  afd!AfdAbortConnection+20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4efa9418

FAILURE_BUCKET_ID:  X64_0xA_afd!AfdAbortConnection+20

BUCKET_ID:  X64_0xA_afd!AfdAbortConnection+20

Followup: MachineOwner
---------
This crash was network related. It also appears your Intel controller drivers are corrupted. Re-install your Ethernet drivers and your SATA controller drivers.
Make sure to uninstall and re-install the drivers using the following general method.
  1. First, download the latest driver. Then do the next steps.
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices (Network adapter/IDE ATA/ATAPI controllers)
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer only if Windows asks you to.
  11. Install the latest driver for the device.

Alternatively:
  1. Login as an adminstrative user.
  2. First, download the latest driver. Then do the next steps.
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Find the device you are trying to uninstall by expanding the appropriate set of devices (Network adapter/IDE ATA/ATAPI controllers)
  8. Right click the device
  9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  11. Restart your computer only if Windows asks you to.
  12. Install the latest driver for the device.
My System SpecsSystem Spec
10 Apr 2012   #3
estephens

Windows 7 Ultimate
 
 

Once again a fantastic response, how can I thank you enough! I have changed those drivers and the machine is back to running like a dream!
My System SpecsSystem Spec
.

10 Apr 2012   #4
writhziden

Windows 7 Home Premium 64 Bit
 
 

Good to see. You are very welcome.
My System SpecsSystem Spec
25 Aug 2013   #5
Hypermusic4

Windows 7 Proffessional 64bit
 
 
Same Problem

Quote   Quote: Originally Posted by writhziden View Post
Problem Devices:
Code:
Shrew Soft Lightweight Filter	ROOT\LEGACY_VFLT\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Unibrain 1394 PC	UB1394\UNIBRAIN&1394_PC\004DE58B0000241D	The drivers for this device are not installed.
Shrew Soft Inc : Support
Unibrain Software Download Section


Security Software (this is just to check that it is installed and working properly; nothing needs to be done with this information at this time):
Code:
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	12036	8	200	1380	7/04/2012 5:29 PM	3.0.8402.0	12.48 KB (12,784 bytes)	27/04/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	14476	8	200	1380	7/04/2012 5:29 PM	3.0.8402.0	281.52 KB (288,272 bytes)	27/04/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	13824	8	200	1380	7/04/2012 5:30 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	15/06/2011 2:35 PM

Code:
Loading Dump File [D:\Kingston\BSODDmpFiles\estephens\Windows_NT6_BSOD_jcgriff2\040712-55427-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.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`03202000 PsLoadedModuleList = 0xfffff800`03446650
Debug session time: Sat Apr  7 01:26:14.940 2012 (UTC - 6:00)
System Uptime: 0 days 9:21:35.017
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {30, 2, 1, fffff8000328812f}

Probably caused by : afd.sys ( afd!AfdAbortConnection+20 )

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

0: 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: 0000000000000030, 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: fffff8000328812f, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b0100
 0000000000000030 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeAcquireInStackQueuedSpinLock+5f
fffff800`0328812f 488717          xchg    rdx,qword ptr [rdi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  UNS.exe

TRAP_FRAME:  fffff8800dd8c520 -- (.trap 0xfffff8800dd8c520)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff8800dd8c720 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000328812f rsp=fffff8800dd8c6b0 rbp=fffff8800dd8c768
 r8=fffff8800dd8c720  r9=0000000003f6df08 r10=0000000000000001
r11=fffffa80093930c0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KeAcquireInStackQueuedSpinLock+0x5f:
fffff800`0328812f 488717          xchg    rdx,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000327e2e9 to fffff8000327ed40

STACK_TEXT:  
fffff880`0dd8c3d8 fffff800`0327e2e9 : 00000000`0000000a 00000000`00000030 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0dd8c3e0 fffff800`0327cf60 : fffffa80`08589460 00000000`0000000a 00000000`00000001 fffffa80`b23de500 : nt!KiBugCheckDispatch+0x69
fffff880`0dd8c520 fffff800`0328812f : 00000000`0000001c fffff800`0325ee75 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0dd8c6b0 fffff880`05162100 : fffff880`0dd8c768 fffffa80`b23de520 00000000`00000000 fffff880`050ffc76 : nt!KeAcquireInStackQueuedSpinLock+0x5f
fffff880`0dd8c700 fffff880`05167e57 : fffffa80`072be580 fffffa80`4a4da530 fffffa80`066b4880 fffffa80`b23de520 : afd!AfdAbortConnection+0x20
fffff880`0dd8c750 fffff880`01b8761a : fffffa80`0752e580 fffffa80`0752e580 fffffa80`4a4da501 fffff880`00000010 : afd!AfdTLInspectEventHandler+0x4d7
fffff880`0dd8c7d0 fffff880`01b16176 : 00000000`4f0c2e77 fffff880`0dd8ca68 00000000`4f0c2e77 fffffa80`0772d438 : tcpip!TcpInspectConnectionOnListener+0x13a
fffff880`0dd8c880 fffff880`01aae8c2 : 00000000`4f0c2e77 fffffa80`09755010 fffffa80`066b4880 fffffa80`066def00 : tcpip! ?? ::FNODOBFM::`string'+0x47e54
fffff880`0dd8c910 fffff880`01ab02ab : fffffa80`0772d438 fffffa80`09286300 00000000`00000000 fffff880`01806500 : tcpip!TcpMatchReceive+0x442
fffff880`0dd8ca60 fffff880`01a8affa : fffffa80`066def00 fffff880`000055f6 fffff880`00006042 fffff880`0dd86042 : tcpip!TcpPreValidatedReceive+0x36b
fffff880`0dd8cb30 fffff800`0328aa88 : fffff880`01bc69a0 fffffa80`03deeb06 fffffa80`03deeb60 ffffd319`20076902 : tcpip!IppLoopbackTransmit+0x11a
fffff880`0dd8cbe0 fffff880`01a8b90f : fffff880`01ad7c70 fffff880`018b953a fffff880`0dd8ce02 00000000`00000000 : nt!KeExpandKernelStackAndCalloutEx+0xd8
fffff880`0dd8ccc0 fffff880`01aae277 : fffffa80`0772d1a0 00000000`00000004 fffff880`0dd8d101 00000000`00000000 : tcpip!IppLoopbackEnqueue+0x22f
fffff880`0dd8cd70 fffff880`01ab4de5 : fffffa80`066dec50 00000000`00000001 00000000`00000001 00000000`00000080 : tcpip!IpNlpFastSendDatagram+0xb77
fffff880`0dd8d120 fffff880`01ac109f : 00000000`03f44143 fffffa80`085a40a8 00000000`00000008 fffffa80`c234d38c : tcpip!TcpTcbSend+0x495
fffff880`0dd8d3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!TcpCreateAndConnectTcbRateLimitComplete+0x39f


STACK_COMMAND:  kb

FOLLOWUP_IP: 
afd!AfdAbortConnection+20
fffff880`05162100 0fba6b0414      bts     dword ptr [rbx+4],14h

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  afd!AfdAbortConnection+20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: afd

IMAGE_NAME:  afd.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4efa9418

FAILURE_BUCKET_ID:  X64_0xA_afd!AfdAbortConnection+20

BUCKET_ID:  X64_0xA_afd!AfdAbortConnection+20

Followup: MachineOwner
---------
This crash was network related. It also appears your Intel controller drivers are corrupted. Re-install your Ethernet drivers and your SATA controller drivers.
Make sure to uninstall and re-install the drivers using the following general method.
  1. First, download the latest driver. Then do the next steps.
  2. Click Start Menu
  3. Right Click My Computer/Computer
  4. Click Manage
  5. Click Device Manager from the list on the left
  6. Find the device you are trying to uninstall by expanding the appropriate set of devices (Network adapter/IDE ATA/ATAPI controllers)
  7. Right click the device
  8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  10. Restart your computer only if Windows asks you to.
  11. Install the latest driver for the device.

Alternatively:
  1. Login as an adminstrative user.
  2. First, download the latest driver. Then do the next steps.
  3. Click Start Menu
  4. Click Control Panel
  5. Click Hardware and Sound
  6. Click Device Manager (the last link under Devices and Printers)
  7. Find the device you are trying to uninstall by expanding the appropriate set of devices (Network adapter/IDE ATA/ATAPI controllers)
  8. Right click the device
  9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
  10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  11. Restart your computer only if Windows asks you to.
  12. Install the latest driver for the device.
Hi I had this blue Screen problem, so if i download the driver updates you suggested will this fix my problem as well?

Sorry I am very new to this stuff
My System SpecsSystem Spec
25 Aug 2013   #6
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

Quote   Quote: Originally Posted by Hypermusic4 View Post
Hi I had this blue Screen problem, so if i download the driver updates you suggested will this fix my problem as well?

Sorry I am very new to this stuff
Hypermusic welcome to seven forums.

You need to create a thread for yourself, and fully follow -
My System SpecsSystem Spec
Reply

 BSOD - driver irql not less or equal




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Driver IRQL Not Less or Equal BSOD
Hi All, I first experienced this BSOD error around 5 months ago. My computer got infected, I believe, around the same time but I am not sure whether the BSOD is related to this. I have since completed a clean install of Windows 7 HP x64 but the BSOD problem persists. The 'Driver IRQL Not Less or...
BSOD Help and Support
BSOD - Driver IRQL Not Less Or Equal
Hi, Desperate to have some help. My computer's been giving me BSOD these few days. I have updated my profile with as much information as possible -Windows Ultimate 64bit -OEM version computer age - under one year
BSOD Help and Support
BSOD Driver IRQL Not Less or Equal
Was watching a YouTube video and browsing a video game client menu while this happened. Having this error for the 3rd time and not sure of the origins. Currently trying to update all drivers. ZIP of the BSOD support instructions is attached.
BSOD Help and Support
BSOD: driver irql less or equal
Hi Guys, I'm getting BSOD at a different scenario while playing games. Can you help me determine the cause? I have attached the minidump i got. Appreciate your response. TIA! regards, Paul
BSOD Help and Support
BSOD IRQL driver not less or equal
Ok I have had a custom computer built some time ago (1-2 years ago I think). I built it mainly for gaming and surfing the web. I have Windows 7 Professial 32-bit. The problem I have is the BSOD only happens when i surf the net. Different internet sites may or may not cause the BSOD. Sites like...
BSOD Help and Support
BSOD Driver Irql Not Less Or Equal
I am getting BSOD error Driver Irql Not Less Or Equal After running a crack file which is downloaded,i forgot the filename because when it is run the system was power down. now for every restart after logon it shows the Error " Driver Irql Not Less Or Equal" i am sure it is a virus...
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 19:28.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App