View Full Version : (Driver) IRQL NOT LESS THAN OR EQUAL

06-12-2010, 07:53 PM
iv'e been getting these BSODs(driver specific and the other one) regularly over the past few weeks, the PC is running fine for a few hours then as soon as i trigger some event (open MPC or run an update) it goes down in flames.
PC specs -- EP45T-UD3 mobo ; 4 GB Transend DDR3 ram 1333 ; intel Core2 Quad 2.6GHz ; Leadtek PX9800GT GPU ; 2 Seagate HDDs , running Win7 Ultimate
i learned that the problem might be RAM so i ran memtest and one of the chips was in fact buggy so i got a new one but the problem persists , i think it might even be happening more frequently
some guy even said it might be that the RAM frequency is faster than the bus speed causing conflicts but i'm a pink pineapple if i know how to fix that

06-12-2010, 08:10 PM
Got a stop error code, like x000000007E or something? And/or a file name.

06-12-2010, 08:21 PM
Usually a driver error.

06-12-2010, 08:23 PM
Every time a PC gets a BSOD a dumpfile is created. You can find it in C:\windows\minidump - named by the date it happened.

That file can be analysed using WinDBG (http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi). It won't tell you what the problem is exactly but point you in the right direction so you can google etc from there.

Once downloaded and installed put this:

into the symbol path. Save the workspace and open the dump file. The dump file takes a while to get analysed (5min or so) during which time the program appears to be doing nothing, so just be patient :)

Good luck, BSODs suck :D

ps. That download link I gave you is for 32bit platforms, if you're running x64 use WinDBG x64 (http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.11.1.404.msi), the rest of the process is the same.

18-01-2011, 02:41 AM
Hey guys
Sorry for the wait, was in wild africa...
Anyway, would it be beneficial if I loaded the dump files onto the forum and you guys could take a look? The problem's gotten much more complicated in my absence and the BSODs are now of varying origin. I could just format but I absolutely know that that's not going to be a permanent fix as I've done it before (4 times in 2 months, did all the driver and OS updates every time)

18-01-2011, 02:43 AM
Also , I did get an error code for (the only time it happened) a BSOD = 00x000000D1 (or close to) saying something about USBPort.sys

18-01-2011, 06:36 AM
USB - you got the latest chipset drivers?