Forum Home
Press F1
 
Thread ID: 114522 2010-12-06 06:53:00 (Driver) IRQL NOT LESS THAN OR EQUAL loonar (16118) Press F1
Post ID Timestamp Content User
1159362 2010-12-06 06:53:00 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
loonar (16118)
1159363 2010-12-06 07:10:00 Got a stop error code, like x000000007E or something? And/or a file name. Snorkbox (15764)
1159364 2010-12-06 07:21:00 Usually a driver error. mikebartnz (21)
1159365 2010-12-06 07:23:00 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 (msdl.microsoft.com). 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:
SRV*c:\websymbols*msdl.microsoft.com

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 (msdl.microsoft.com), the rest of the process is the same.
WarNox (8772)
1159366 2011-01-17 13:41:00 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)
loonar (16118)
1159367 2011-01-17 13:43:00 Also , I did get an error code for (the only time it happened) a BSOD = 00x000000D1 (or close to) saying something about USBPort.sys loonar (16118)
1159368 2011-01-17 17:36:00 Drivers.
USB - you got the latest chipset drivers?
pctek (84)
1