BSOD irql not less or equal

speedlever said:

I have yet to replace the AData 2x2GB ram with the known good sticks of 2x1Gb ram from the standby computer.

Another bsod today, while the computer was sitting unused.

Looking at event viewer, I can't really interpret anything from what I see. The critical events seem to parallel bsods... best I can tell.

Seems to be memory related, the dumps point to win32k.sys as the cause, system files will never cause any BSODs unless being triggered by a hardware factor

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002ad8bb6, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff88007923140, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!KeSetEvent+16
fffff800`02ad8bb6 f6037f          test    byte ptr [rbx],7Fh

CONTEXT:  fffff88007923140 -- (.cxr 0xfffff88007923140)
rax=fffff900c2c61ce0 rbx=00f7ff0fff080000 rcx=0000000000000001
rdx=0000000000000001 rsi=00000000fffdb000 rdi=fffff900c2c6ffe0
rip=fffff80002ad8bb6 rsp=fffff88007923b20 rbp=fffff88007923ca0
 r8=0000000000000000  r9=0000000000000006 r10=fffff96000164470
r11=00000000fffdb000 r12=000000007505addc r13=000000000013fd20
r14=000000000013e850 r15=0000000075032450
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!KeSetEvent+0x16:
fffff800`02ad8bb6 f6037f          test    byte ptr [rbx],7Fh ds:002b:00f7ff0f`ff080000=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff9600016478f to fffff80002ad8bb6

STACK_TEXT:  
fffff880`07923b20 fffff960`0016478f : 00000000`75032450 00000000`00000001 00000000`7505ad00 00000000`0000002a : nt!KeSetEvent+0x16
fffff880`07923b90 fffff960`0016486e : fffff900`c20fd010 fffffa80`08e9b060 fffff880`07923ca0 fffff960`001148b9 : win32k!zzzWakeInputIdle+0xc7
fffff880`07923bc0 fffff960`001644be : 00000000`000404ff 00000000`00000000 00000000`0000000a 00000000`fffdb000 : win32k!xxxGetInputEvent+0xa6
fffff880`07923bf0 fffff800`02ad3ed3 : fffffa80`08e9b060 fffff880`07923ca0 00000000`fffdb000 00000000`00000020 : win32k!NtUserCallOneParam+0x4e
fffff880`07923c20 00000000`7507fdfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0013dee8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7507fdfa


FOLLOWUP_IP: 
win32k!zzzWakeInputIdle+c7
fffff960`0016478f 488b4f10        mov     rcx,qword ptr [rdi+10h]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  win32k!zzzWakeInputIdle+c7

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4df2dbd1

STACK_COMMAND:  .cxr 0xfffff88007923140 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_win32k!zzzWakeInputIdle+c7

BUCKET_ID:  X64_0x3B_win32k!zzzWakeInputIdle+c7

Ok. I will replace the AData ram and see if I can run 4x1Gb sticks for a while. I've had 3 bsods in the last 6 hours, two unattended and just now recovered from one (system service exception). If that seems to be stable, I'll just spring for 4x2Gb of new DDR2 ram (much as I hate to invest in old ram.)

Update: after suffering 4 BSODs within 8 hours yesterday, I swapped out the AData 2x2Gb ram for some value Kingston 2x1Gb DDR2-667 ram from the standby computer. Results: no BSODs in the last 24 hours. I'm running a mix of 2x1GB DDR2-800 Corsair ram and 2x1Gb DDR2-667 Kingston ram.

The good news is that this points the finger at the AData ram as being the culprit. The bad news is that investing in new DDR2 ram seems futile except for the short term. So I'm considering replacing the mobo, cpu, and ram.

That will set me back at least $400. Perhaps in the short term I can get AData to replace the defective ram under warranty.