Bsod irq_not_less_or_equal

C

crea

New member
Local time
5:59 AM
Messages
2
Bsod DRIVER_IRQL_NOT_LESS_OR_EQUAL

Hello,
I am new to the forum.

I've recently built a new system using the following parts:
CPU: i7 930
RAM: Corsair [email protected], with 9-9-9-24 timings
PSU: Corsair HX850W
CPU Cooler: Cooler Master V6GT
Display Card: ATI HD5450
Sound Card: Auzentech Prelude 7.1
OS: Windows 7 Professional 64-bit
Installed about three weeks.

I have passed the Intel Burn Tests for eight hours running.
The RAMs survived memtest86+ for eight hours with no errors at all.
However, once I start using applications, it will get the BSOD randomly.
There's no definite symptom or sign before the BSOD happen.
Please help!
I have zipped up all the info as stated in the BSOD posting guide for your reference.


Thanks in advance!
 
Last edited:

My Computer

OS
Windows 7 Professional 64-bit
CPU
i7 930
Motherboard
Asus P6x58d-e
Memory
Corsair CM3X2G1600C8D
Graphics Card(s)
HD5450
Sound Card
Auzentech Prelude 7.1
Monitor(s) Displays
LG 22" TV
PSU
Corsair HX850
Case
Cooler Master
Cooling
Fan
crea said:
Hello,
I am new to the forum.

I've recently built a new system using the following parts:
CPU: i7 930
RAM: Corsair [email protected], with 9-9-9-24 timings
PSU: Corsair HX850W
CPU Cooler: Cooler Master V6GT
Display Card: ATI HD5450
Sound Card: Auzentech Prelude 7.1
OS: Windows 7 Professional 64-bit
Installed about three weeks.

I have passed the Intel Burn Tests for eight hours running.
The RAMs survived memtest86+ for eight hours with no errors at all.
However, once I start using applications, it will get the BSOD randomly.
There's no definite symptom or sign before the BSOD happen.
Please help!
I have zipped up all the info as stated in the BSOD posting guide for your reference.


Thanks in advance!
Click to expand...


Three of these were probably caused by lycosa.sys your Adder keyboard (i think) driver. I would re-install it and update the drivers listed below.

Drivers
Code: 
mcdbus.sys        fffff880`05885000    fffff880`058c1880    0x0003c880    0x49a3cd1f    2/24/2009 06:34:07                        
spldr.sys        fffff880`017de000    fffff880`017e6000    0x00008000    0x4a0858bb    5/11/2009 12:56:27                        
amdxata.sys        fffff880`011bb000    fffff880`011c6000    0x0000b000    0x4a12f2eb    5/19/2009 13:56:59                        
emupia2k.sys        fffff880`06a15000    fffff880`06a5f000    0x0004a000    0x4a3877a9    6/17/2009 00:57:13                        
ctsfm2k.sys        fffff880`05930000    fffff880`05968000    0x00038000    0x4a3877b1    6/17/2009 00:57:21                        
ctoss2k.sys        fffff880`0517d000    fffff880`051ae000    0x00031000    0x4a3877be    6/17/2009 00:57:34                        
ha20x2k.sys        fffff880`06a7c000    fffff880`06bfd000    0x00181000    0x4a387812    6/17/2009 00:58:58                        
ctaud2k.sys        fffff880`05034000    fffff880`050da580    0x000a6580    0x4a387837    6/17/2009 00:59:35                        
ctprxy2k.sys        fffff880`051ae000    fffff880`051b6000    0x00008000    0x4a38783a    6/17/2009 00:59:38                        
CTEXFIFX.DLL        fffff880`06c62000    fffff880`06dbf000    0x0015d000    0x4a387880    6/17/2009 01:00:48                        
CT20XUT.DLL        fffff880`05983000    fffff880`059b8000    0x00035000    0x4a387885    6/17/2009 01:00:53                        
CTHWIUT.DLL        fffff880`05968000    fffff880`05983000    0x0001b000    0x4a387889    6/17/2009 01:00:57
Code: 
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\091910-17768-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e09000 PsLoadedModuleList = 0xfffff800`03046e50
Debug session time: Sun Sep 19 08:46:25.672 2010 (GMT-4)
System Uptime: 0 days 0:00:41.656
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C4, {f6, 6f6f6f6f00000174, fffffa800a488b30, fffff88006c564c2}

Unable to load image \SystemRoot\system32\drivers\Lycosa.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Lycosa.sys
*** ERROR: Module load completed but symbols could not be loaded for Lycosa.sys
Probably caused by : Lycosa.sys ( Lycosa+14c2 )

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 6f6f6f6f00000174, Handle value being referenced.
Arg3: fffffa800a488b30, Address of the current process.
Arg4: fffff88006c564c2, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033033dc to fffff80002e79740

STACK_TEXT:  
fffff880`08b64318 fffff800`033033dc : 00000000`000000c4 00000000`000000f6 6f6f6f6f`00000174 fffffa80`0a488b30 : nt!KeBugCheckEx
fffff880`08b64320 fffff800`03318ae4 : fffffa80`0a488b30 6f6f6f6f`c0000022 fffffa80`00000000 fffff880`08b5c000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08b64360 fffff800`030d4b40 : 00000000`023300ac fffff880`08b64590 00000000`00000000 fffffa80`09989600 : nt!VfCheckUserHandle+0x1b4
fffff880`08b64440 fffff800`031505f5 : 00000000`00000000 fffff800`00100000 00000000`00000000 fffff880`08b5c000 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
fffff880`08b64510 fffff800`03318878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`08b64560 fffff880`06c564c2 : fffff980`237e8ee0 00000000`00000002 fffffa80`099896f0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`08b645b0 fffff980`237e8ee0 : 00000000`00000002 fffffa80`099896f0 00000000`00000000 fffff880`06c58828 : Lycosa+0x14c2
fffff880`08b645b8 00000000`00000002 : fffffa80`099896f0 00000000`00000000 fffff880`06c58828 00000000`00000000 : 0xfffff980`237e8ee0
fffff880`08b645c0 fffffa80`099896f0 : 00000000`00000000 fffff880`06c58828 00000000`00000000 00000000`00000000 : 0x2
fffff880`08b645c8 00000000`00000000 : fffff880`06c58828 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`099896f0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+14c2
fffff880`06c564c2 89442478        mov     dword ptr [rsp+78h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+14c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac2e27e

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_Lycosa+14c2

BUCKET_ID:  X64_0xc4_f6_VRF_Lycosa+14c2

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 6f6f6f6f00000174, Handle value being referenced.
Arg3: fffffa800a488b30, Address of the current process.
Arg4: fffff88006c564c2, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033033dc to fffff80002e79740

STACK_TEXT:  
fffff880`08b64318 fffff800`033033dc : 00000000`000000c4 00000000`000000f6 6f6f6f6f`00000174 fffffa80`0a488b30 : nt!KeBugCheckEx
fffff880`08b64320 fffff800`03318ae4 : fffffa80`0a488b30 6f6f6f6f`c0000022 fffffa80`00000000 fffff880`08b5c000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08b64360 fffff800`030d4b40 : 00000000`023300ac fffff880`08b64590 00000000`00000000 fffffa80`09989600 : nt!VfCheckUserHandle+0x1b4
fffff880`08b64440 fffff800`031505f5 : 00000000`00000000 fffff800`00100000 00000000`00000000 fffff880`08b5c000 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
fffff880`08b64510 fffff800`03318878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`08b64560 fffff880`06c564c2 : fffff980`237e8ee0 00000000`00000002 fffffa80`099896f0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`08b645b0 fffff980`237e8ee0 : 00000000`00000002 fffffa80`099896f0 00000000`00000000 fffff880`06c58828 : Lycosa+0x14c2
fffff880`08b645b8 00000000`00000002 : fffffa80`099896f0 00000000`00000000 fffff880`06c58828 00000000`00000000 : 0xfffff980`237e8ee0
fffff880`08b645c0 fffffa80`099896f0 : 00000000`00000000 fffff880`06c58828 00000000`00000000 00000000`00000000 : 0x2
fffff880`08b645c8 00000000`00000000 : fffff880`06c58828 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`099896f0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+14c2
fffff880`06c564c2 89442478        mov     dword ptr [rsp+78h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+14c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac2e27e

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_Lycosa+14c2

BUCKET_ID:  X64_0xc4_f6_VRF_Lycosa+14c2

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

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

DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught.  This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f6, Referencing user handle as KernelMode.
Arg2: 6f6f6f6f00000174, Handle value being referenced.
Arg3: fffffa800a488b30, Address of the current process.
Arg4: fffff88006c564c2, Address inside the driver that is performing the incorrect reference.

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


BUGCHECK_STR:  0xc4_f6

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  razerhid.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff800033033dc to fffff80002e79740

STACK_TEXT:  
fffff880`08b64318 fffff800`033033dc : 00000000`000000c4 00000000`000000f6 6f6f6f6f`00000174 fffffa80`0a488b30 : nt!KeBugCheckEx
fffff880`08b64320 fffff800`03318ae4 : fffffa80`0a488b30 6f6f6f6f`c0000022 fffffa80`00000000 fffff880`08b5c000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`08b64360 fffff800`030d4b40 : 00000000`023300ac fffff880`08b64590 00000000`00000000 fffffa80`09989600 : nt!VfCheckUserHandle+0x1b4
fffff880`08b64440 fffff800`031505f5 : 00000000`00000000 fffff800`00100000 00000000`00000000 fffff880`08b5c000 : nt! ?? ::NNGAKEGL::`string'+0x20e2e
fffff880`08b64510 fffff800`03318878 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ObReferenceObjectByHandle+0x25
fffff880`08b64560 fffff880`06c564c2 : fffff980`237e8ee0 00000000`00000002 fffffa80`099896f0 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0x48
fffff880`08b645b0 fffff980`237e8ee0 : 00000000`00000002 fffffa80`099896f0 00000000`00000000 fffff880`06c58828 : Lycosa+0x14c2
fffff880`08b645b8 00000000`00000002 : fffffa80`099896f0 00000000`00000000 fffff880`06c58828 00000000`00000000 : 0xfffff980`237e8ee0
fffff880`08b645c0 fffffa80`099896f0 : 00000000`00000000 fffff880`06c58828 00000000`00000000 00000000`00000000 : 0x2
fffff880`08b645c8 00000000`00000000 : fffff880`06c58828 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffffa80`099896f0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+14c2
fffff880`06c564c2 89442478        mov     dword ptr [rsp+78h],eax

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+14c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac2e27e

FAILURE_BUCKET_ID:  X64_0xc4_f6_VRF_Lycosa+14c2

BUCKET_ID:  X64_0xc4_f6_VRF_Lycosa+14c2

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

My Computer

Computer Manufacturer/Model Number
HP Pavillion dv-7 1005 Tx
OS
Win 8 Release candidate 8400
CPU
[email protected]
Memory
4 gigs
Graphics Card(s)
Nvidia 9600M
Sound Card
HD built-in
Monitor(s) Displays
17" Wxga
Screen Resolution
1440x900
Cooling
none
Internet Speed
45Mb down 5Mb up
Thank you for your prompt reply!
I will update the files and give it a try.

Thanks a lot!
 

My Computer

OS
Windows 7 Professional 64-bit
CPU
i7 930
Motherboard
Asus P6x58d-e
Memory
Corsair CM3X2G1600C8D
Graphics Card(s)
HD5450
Sound Card
Auzentech Prelude 7.1
Monitor(s) Displays
LG 22" TV
PSU
Corsair HX850
Case
Cooler Master
Cooling
Fan
You must log in or register to reply here.
Back
Top