Plenty of BSODs, driver irql not less or equal.

Ximor · 02 Apr 2010

In the past week I've had 11 BSODs with the message DRIVER_IRQL_NOT_LESS_OR_EQUAL. After some google-fu I updated all my drivers to the latest from their respective manufacturer but still had problems.
I formatted my OS harddrive and didn't install any drivers but still got several bluescreens so I updated them all again but still the problem persists.
I'm going to run my RAM through a few hours of Memtest to check if its not that causing the problem but in the meantime I've uploaded my windows\minidump to see if anyone could diagnose the problem in the meantime.

Ximor · 02 Apr 2010

Just got another one, though this referred to executable memory trying to access non-executable memory which leads to be believe there might be RAM involved too. Didn't add an entry to \minidump though but this was the Event Viewer details:

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power

[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 2

Level 1

Task 63

Opcode 0

Keywords 0x8000000000000002

- TimeCreated

[ SystemTime] 2010-04-02T10:01:24.668021300Z

EventRecordID 5537

Correlation

- Execution

[ ProcessID] 4

[ ThreadID] 8

Channel System

Computer shaGuarbeazt

- Security

[ UserID] S-1-5-18

- EventData

BugcheckCode 252

BugcheckParameter1 0x24535

BugcheckParameter2 0x81e0000000a0b847

BugcheckParameter3 0xfffff88002f8c9d0

BugcheckParameter4 0x0

SleepInProgress false

PowerButtonTimestamp 0

smarteyeball · 02 Apr 2010

Considering the randomness to the dumps, it looks like your OC is not 100% stable.

memtest is a good start, but not a guarantee that all is well.

I've had overclocks that have passed 20+ IBT runs, 24hr prime, 24hr memtest runs and still had these random sorts of errors.

It could point to to insufficient vtt (QPI) volts, vcore just a notch or two low, the IMC controller on the chip just a little dodgy, RAM timings slightly to aggressive etc - in other words it could be anything.

As much of a PITA it is, try going back to stock settings for a couple of days and see if it still has all these random crashes.

Ximor · 03 Apr 2010

I dropped the clocks and voltages back to stock and 13 hours uptime so far, which is a new record (I think). Assuming I do want to OC again, is there anything I can do to avoid this or is it just trial and error?