IRQL BSOD on Windows 7 x64

[soke]

Hi all! Since I bought my computer (about 2 months ago), I had BSODs in sometimes.

I have reinstalled all the system, but the BSODs still occurs. I think it could be caused by Wireless PCI Card, but I'm not so sure of that. Can you help me?

I attach the latest two minidumps, cause I reinstalled one week before.

Thank you in advance!

P.D: I don't have installed perfmon program. Sorry for the inconvenience .

Asus P7P55D
Intel Core i5 760
4 GB Mushkin <- Tested with memtest OK
Ati HD5770
Conceptronic Wifi PCI Card (C300Ri)

 

[Capt.Jack Sparrow]

Hello and Welcome !

The Dumps are pointing to Core Windows Files which may not be the problem. Follow these steps. One of the crashed happen with I-tunes i.e. mDNSResponder and the next Dump is Ralink Wireless Utility

Run a Hardware Diagnostic just in case Hardware Diagnostic !! « Captain Debugger

Remove the Duplex Driver
sptd.sys Mon Oct 12 02:25:14 2009 follow this article DuplexSecure - FAQ

Remove Asus Utilities :
ASACPI.sys Mon Mar 28 08:00:36 2005 then go to C:\Windows\Drivers and find ASACPI.sys and rename to ASACPI.old

Download Malwarebytes and run a complete scan

Update the Drivers:

ov530vx.sys  Thu Jul 12 18:30:05 2007
camfilt2.sys Wed Aug 29 18:26:49 2007

Check this site: http://www.carrona.org/drvrdown.html

Bugcheck:

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: fffff80002ae22a8, address which referenced memory

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


WRITE_ADDRESS:  0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeReleaseSemaphore+38
fffff800`02ae22a8 f00fba2907      lock bts dword ptr [rcx],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  RaUI.exe

TRAP_FRAME:  fffff88009565470 -- (.trap 0xfffff88009565470)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000002 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ae22a8 rsp=fffff88009565600 rbp=fffffa8003deb600
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeReleaseSemaphore+0x38:
fffff800`02ae22a8 f00fba2907      lock bts dword ptr [rcx],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002acaca9 to fffff80002acb740

STACK_TEXT:  
fffff880`09565328 fffff800`02acaca9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`09565330 fffff800`02ac9920 : fffff880`00dbca00 00000000`00000000 01cb8819`aeca06fe 01cb8819`aeca06fe : nt!KiBugCheckDispatch+0x69
fffff880`09565470 fffff800`02ae22a8 : 00000000`00000000 fffffa80`074cd390 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`09565600 fffff800`02b101cf : fffff8a0`033bac70 fffffa80`00000000 00000000`00000000 fffffa80`03deb600 : nt!KeReleaseSemaphore+0x38
fffff880`09565680 fffff880`01233029 : fffff8a0`033bac70 fffff880`00000000 fffffa80`074a4e40 fffff880`01286088 : nt!ExConvertExclusiveToSharedLite+0x6f
fffff880`095656b0 fffff880`01237303 : 00000000`00000000 fffff8a0`033bac70 fffff880`095658e0 fffff880`095657d8 : Ntfs!NtfsCachedRead+0x1e9
fffff880`09565710 fffff880`01239f78 : fffffa80`074a4e40 fffffa80`03deb600 fffff880`09565801 fffffa80`0408c600 : Ntfs!NtfsCommonRead+0x583
fffff880`095658b0 fffff880`00dac23f : fffffa80`03deb9a0 fffffa80`03deb600 fffffa80`0408c620 00000000`00000001 : Ntfs!NtfsFsdRead+0x1b8
fffff880`09565960 fffff880`00daa6df : fffffa80`04db98e0 00000000`00000001 fffffa80`04db9800 fffffa80`03deb600 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`095659f0 fffff800`02de1ca9 : 00000000`00000000 fffffa80`074cd390 00000000`00000001 fffffa80`03deb600 : fltmgr!FltpDispatch+0xcf
fffff880`09565a50 fffff800`02de94a3 : fffffa80`074cd390 fffffa80`074cd390 fffffa80`074cd390 fffffa80`074cd301 : nt!IopSynchronousServiceTail+0xf9
fffff880`09565ac0 fffff800`02aca993 : ffffffff`ffffffff 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x631
fffff880`09565bb0 00000000`74a32dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008ebf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74a32dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeReleaseSemaphore+38
fffff800`02ae22a8 f00fba2907      lock bts dword ptr [rcx],7

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeReleaseSemaphore+38

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0xA_nt!KeReleaseSemaphore+38

BUCKET_ID:  X64_0xA_nt!KeReleaseSemaphore+38

Followup: MachineOwner

Hope this helps,
Captain

 

[soke]

Excuse me, this is the first time I'm trying to repair a BSOD fail. I don't understand which is the main failure, and what I have to do with it.

I understand that the first BSOD is provoked by ITunes, and the next one by Ralink Wireless Utility. Why do I have to remove the other two files? Will it be fixed if I uninstall those applications?

Thanks for all.

 

[Capt.Jack Sparrow]

Excuse me, this is the first time I'm trying to repair a BSOD fail. I don't understand which is the main failure, and what I have to do with it.

I understand that the first BSOD is provoked by ITunes, and the next one by Ralink Wireless Utility. Why do I have to remove the other two files? Will it be fixed if I uninstall those applications?

Thanks for all.

Well as if now the cause is unknown. Windows didn't catch the exact cause. Other two files are notorious for BSOD so it's recommend to remove it.

 

[CarlTR6]

Hi soke; and welcome to the forum. Often dumps do not pinpoint a specific reason for a crash and there can be more than one cause. Troubleshooting a BSOD is many times a process of elimination. In your case, both bug checks are general and do not give a specific cause. The advice Captain Jack gave you is based on clues from your dump coupled with his vast experience.

Daemon tools is a documented cause of BSOD's on some Win 7 systems due to its sptd.sys driver. Uninstall Daemon Tools and then run this program to delete all traces of sptd.sys. Select uninstall; do not select reinstall. DuplexSecure - Downloads

Here is a free alternative CD virtualization program that does not use the sptd.sys driver.
Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Outdated drivers can and do cause conflicts, memory corruption and BSOD's. Will updating these drivers and unstalling sptd.sys fix your problem? We don't know; it is part of the process of elimination.