BSOD Random IRQL_NOT_LESS_OR_EQUAL (STOP: 0x0000000A)

No, it's still enabled and another BSOD just happend... again when I was copying my data on disks...

I've updated ASACPI.sys to it's latest version ( I've found 1043.6.0.0 dated 10/10/2009 hidden on ASUS FTP ) and tryied but not...

Already leaved memtest86+ for hours some days ago, 7 pass and no errors found... I leave it again this night just to be extra sure but I really think the problem it's not the ram ( I've tried it a lot )

Anyway, here's my dumps

humah said:

No, it's still enabled and another BSOD just happend... again when I was copying my data on disks...

I've updated ASACPI.sys to it's latest version ( I've found 1043.6.0.0 dated 10/10/2009 hidden on ASUS FTP ) and tryied but not...

Already leaved memtest86+ for hours some days ago, 7 pass and no errors found... I leave it again this night just to be extra sure but I really think the problem it's not the ram ( I've tried it a lot )

Anyway, here's my dumps

All your drivers are updated, now either its a hardware issue or some kind of Malware activity, run a scan of Malwarebytes
Reset your BIOS RAM settings especially your RAM voltages and timings to their Default/Auto values

Malwerebytes found nothing, and I leaved memtest86+ all night with 12 pass and 0 errors... BIOS is on default setting since the first installation for almost all ( just disabled floppy that I haven't it ), I'm really speechless..

Another crash... Should I put the pc on trash and get a new one? :)

Please re-enable driver verifier, current dumps do not indicate any causes
Update your Logitech Setpoint software
Support + Downloads

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa80239ba448, 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: fffff80002ccf72c, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002efa100
 fffffa80239ba448 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+17c
fffff800`02ccf72c 4c8938          mov     qword ptr [rax],r15

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  plugin-contain

TRAP_FRAME:  fffff88007015980 -- (.trap 0xfffff88007015980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa80239ba448 rbx=0000000000000000 rcx=fffffa80039ba448
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ccf72c rsp=fffff88007015b10 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000001
r11=fffff880009ea180 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x17c:
fffff800`02ccf72c 4c8938          mov     qword ptr [rax],r15 ds:0001:fffffa80`239ba448=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cc71e9 to fffff80002cc7c40

STACK_TEXT:  
fffff880`07015838 fffff800`02cc71e9 : 00000000`0000000a fffffa80`239ba448 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`07015840 fffff800`02cc5e60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`07015980 fffff800`02ccf72c : 00000000`00000500 ffffe119`56db9f00 00000000`00000824 fffff800`02c8270a : nt!KiPageFault+0x260
fffff880`07015b10 fffff800`02fbe44e : 00000000`00000000 fffff800`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x17c
fffff880`07015bb0 fffff800`02cc6ed3 : fffffa80`03ba0800 00000000`00000500 00000000`00000000 fffffa80`039ba440 : nt!NtWaitForSingleObject+0xde
fffff880`07015c20 00000000`73902e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0691eb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x73902e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KeWaitForSingleObject+17c
fffff800`02ccf72c 4c8938          mov     qword ptr [rax],r15

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!KeWaitForSingleObject+17c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3

FAILURE_BUCKET_ID:  X64_0xA_VRF_nt!KeWaitForSingleObject+17c

BUCKET_ID:  X64_0xA_VRF_nt!KeWaitForSingleObject+17c

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

Updated all Logitech drivers and enabled Driver Verifier... I try to copy some other things again : seems to help the BSOD!

Crash... here's the files

Crashed again.. this time I was doing nothing... I'm out of ideas... Last thing it could be it's the CPU, the only one thing that I haven't changed yet on this machine...

humah said:

Crashed again.. this time I was doing nothing... I'm out of ideas... Last thing it could be it's the CPU, the only one thing that I haven't changed yet on this machine...

You can test your CPU with Prime95, but dumps are still blaming Memory
https://www.sevenforums.com/tutorials...t-prime95.html