BSOD - Randomly over the last few days. Driver_irql_not_less_or_equal

Hello, recently I have received 2 BSOD. Yesterday when i was playing Dota 2(with Itunes in background), and today when i was just browsing the internet and listening to Youtube. I can't seem to find the issue, so hopefully someone can help.

I am reasonably sure that this is coming from a driver issue(not video drivers, i have tested several of those and the problem persist) since i have tested my computer several times with Prime 95, memtest86 with no errors/issues.

I also reformatted my computer less then a month ago because of this very same problem, i couldn't figure out which driver was causing my computer to crash, and was problem free for nearly 2 1/2 weeks, up in till a few days ago.

In the days before the BSOD i installed 3 things. Daemon Tools Lite and Fraps and windows updates. I have since uninstalled both programs.

Last thing as well is i have a separate hard drive where i keep several installed files on and store various videos/music/etc, i don't know if this is relevant or not.

Thanks! Any help is appreciated


System Information:
i7-930 @ 3.6
GTX 470
P6x58D-E
6GB Ram

Two drivers need to be removed.

Please remove any CD visualization programs such as Daemon Tools and Alcohol 120%.

They use a driver, found in your dmp, called sptd.sys, that is notorious for causing BSODs.

Use this SPTD uninstaller DuplexSecure - Downloads DuplexSecure - FAQ

when you're done you can use this Freeware:

MagicISO Virtual CD/DVD-ROM (MagicDisc) in its place

Using MagicISO to create ISO image files


The other Related to RTCore64.sys MSI Afterburner from Micro-Star Int'l Co. Ltd. has known problems with win 7. Yours from 2005

Brando424 said:

Thanks for the response. I removed Daemon Tools after the first BSOD and i still received another 2 BSOD(one a few hours ago while using Driver Verifier, I attached that to this post under "updated BIOS information").

I used the link to STPD uninstaller DuplexSecure and the "uninstaller" was blacked out, the only thing available was install. So i installed it, and then "uninstalled it". I checked my computer and couldn't find a trace of the SPTD.sys driver, unless i missed it somewhere.


I also uninstalled MSI Afterburner and installed EVGA precision instead, which also the RTcore64.sys, but i think its a different version of the driver.

I guess its a waiting game now, to see if it happens again.

Nope RTcore64.sys is still installed and still the same date.

I uninstalled MSI and installed EVGA after the latest BSOD so it wouldn't be in the latest .dmp i have provided. But so far it looks good and my computer hasn't crashed yet since i uninstalled MSI.

Arghh.. Received another BSOD today. Bluescreenviewer seems to say it was caused by yk62x64.sys which is odd because the last 3 bsod were by " ntoskrnl.exe". Yk62x64.sys is a Marvell Yukon Driver, which I updated after the BSOD, but id appreciate some more feedback, these BSOD's are driving my insane. It's very frustrating that it only happens once every 1-2 weeks, making it very difficult to tell whether i have fixed it or not.

Possible outdated drivers

Code:

yk62x64	fffff880`0fe00000	fffff880`0fe64000	Wed May 20 02:14:06 2009 (4a13bbce)	00063e08		yk62x64.sys

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\Brando424\Updated Dump file 3-2-12\030212-22932-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03258000 PsLoadedModuleList = 0xfffff800`03495e70
Debug session time: Fri Mar  2 23:47:20.848 2012 (UTC - 7:00)
System Uptime: 0 days 11:06:30.879
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+3362383332623565
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

EXCEPTION_RECORD:  fffff80000b9c3a8 -- (.exr 0xfffff80000b9c3a8)
ExceptionAddress: fffff800032d3bed (nt!KiProcessExpiredTimerList+0x000000000000003d)
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

TRAP_FRAME:  fffff80000b9c450 -- (.trap 0xfffff80000b9c450)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80097d98d0 rbx=0000000000000000 rcx=0000000000000000
rdx=fffffa80097d9930 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032d3bed rsp=fffff80000b9c5e0 rbp=0000000000271dad
 r8=0000000003445002  r9=0000000000000003 r10=00000000000000ad
r11=fffffa80097d98f0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt!KiProcessExpiredTimerList+0x3d:
fffff800`032d3bed db              ???
Resetting default scope

MISALIGNED_IP: 
nt!KiProcessExpiredTimerList+3d
fffff800`032d3bed db              ???

LAST_CONTROL_TRANSFER:  from fffff800032c02ee to fffff800032c8590

STACK_TEXT:  
fffff800`00b9b498 fffff800`032c02ee : fffffa80`07cc9c80 fffff880`00000610 fffff800`00b9bc10 fffff800`032f5524 : nt!KeBugCheck
fffff800`00b9b4a0 fffff800`032ee2dd : fffff800`034d6b7c fffff800`03410e68 fffff800`03258000 fffff800`00b9c3a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`00b9b4d0 fffff800`032f5950 : fffff800`03417b0c fffff800`00b9b548 fffff800`00b9c3a8 fffff800`03258000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`00b9b500 fffff800`033028cf : fffff800`00b9c3a8 fffff800`00b9bc10 fffff800`00000000 fffff800`00b9c620 : nt!RtlDispatchException+0x410
fffff800`00b9bbe0 fffff800`032c7c02 : fffff800`00b9c3a8 fffffa80`097d9930 fffff800`00b9c450 00000000`00000002 : nt!KiDispatchException+0x16f
fffff800`00b9c270 fffff800`032c5d5f : fffff800`00b9c450 00000000`00000002 fffffa80`06c28000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff800`00b9c450 fffff800`032d3bed : fffffa80`097d9930 fffffa80`05b2ec68 00000000`00000000 00000000`00000000 : nt!KiInvalidOpcodeFault+0x11f
fffff800`00b9c5e0 fffff800`032d434e : 0000005d`1c6beb65 fffff800`00b9cc58 00000000`00271dad fffff800`03446828 : nt!KiProcessExpiredTimerList+0x3d
fffff800`00b9cc30 fffff800`032d3b57 : 00000021`27845fc2 00000021`00271dad 00000021`27845fb0 00000000`000000ad : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`032d0d8a : fffff800`03442e80 fffff800`03450c40 00000000`00000000 fffff880`04202db0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiKernelCalloutExceptionHandler+e
fffff800`032c02ee 90              nop

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiKernelCalloutExceptionHandler+e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

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

The above debugging analysis does point to a hardware issue, and this type of crash usually does mean an underlying driver problem. See if updating the Marvell Yukon driver helps since it was probably outdated.

Post back if you get any more crashes; best wishes it is now stable, though!