New
#1
irql_not_less_equal bsod during games
Good day everyone. I've been browsing these forums looking for a solution for a BSOD problem I have been having.
I see tons of usefull advice here, it seems a great tech support forum, but none of the cases are identical to mine and no solution has worked so far, so I'll post mine. I'll try to be thorough in describing, so apologies if this appears like a wall of text.
Attached is a rar file with the last 5 minidumps.
Some basic system specs are:
Mainboard: Asus m4a78lt-m
cpu: Amd phenom II x6 1055T
graphics card: Saphire AMD Radeon HD 6850
RAM: 2 x Kingston 2gb ddr3 (identical, kit of 2)
OS: Windows 7 64 bit (OEM system builder pack, no previous OS present)
The system and all parts are completely new, aside from an IDE harddisk with files I put in later from my old pc, and its DVD reader.
The bluescreens started shortly after I assembled this current system, I'm not exactly certain when. At first it was only occasionally after hours of playing fairly new (and computing power demanding) games and I could tolerate it, but those same games right now don't last even five minutes.
But the bsod happens pretty much all the time, whenever I do anything more than having windows on, and browsing on the web. Any game, media player, and it's a matter of time before it bluescreens on me.
The message is IRQL_NOT_LESS_OR_EQUAL with the bugcheck code being 0xA (0x00000a something on the screen, if I remember correct, logs are attached)
Sometimes after that, the system can't reboot, and needs startup restore. Sometimes startup restore hangs too, with varying errors, and it's even gotten so bad at some point that I needed to reinstall windows, and even that the system hung before displaying even the asus express gate, which shows even before the BIOS screen.
Another thing I noticed is that BIOS sometimes loses the unlocking of the 6 cores during these reboots.
I have tried having a crash log analysed by a program called WhoCrashed, because I read elsewhere it picked the faulty driver flawlessly. For me however it says that 2 third-party drivers are to blame:
-unknown_module_00000`000001.sys
-g? (yes, just the letter g and a question mark)
That didn't make me much wiser about where to find the cause of the problem. I've seen it in one other place, but the circumstances and solution there were very different.
I've seen older errors in the bluescreens blame various .sys files such as atikmdag.sys, dxgmm.sys, dm1gg.sys, and the nto-something kernel sys files, but that seemed to be pretty random.
Things I have done myself that haven't helped:
-Remove graphics card and replace it with an older gefore 7600 GS
-Updated all drivers
-Fixed an issue where a virtual device ATK0110 wasn't getting drivers and was listed as an unknown device
-BIOS is the latest version
-Set BIOS to plug&play OS on (also tested with it turned off)
-Run memtest86, made only 1 pass, no errors. I also left it on all night, but woke up to a black screen with no results. Will try again soon.
-All cables are connected like they should
-No visible damage on motherboard condensators or any connectors
-Temperatures on hardware are all well within safe limites
-Deinstalled anti-virus, and did a clean install without having antivirus at all
-Tried to play with a total clean install of windows, 1 older game (2005), and only graphic drivers for the geforce 7600 gs
-Installed windows to a different harddisk and ran all critical processes from there
-650 watt power supply should provide plenty of power for this setup
Strangely, one thing that did help somewhat, was to fool around with IRQ using devices in the device manager. I started disabling random devices to see what would accidently solve the problem, and when I took out a "Standard OpenHCB USB Host-controller", the crashes occured less frequently, even though they persisted. This controller shares IRQ 16 with the onboard audio and another exactly the same entry, which apparently controls my mouse (since disabling that one stopped my mouse). Disabling the onboard audio device had no effect at all.
I hope you guys have an idea on what to do about this, because untill Asus answers my e-mail with a solution, or I decide to set fire to this computer in frustration, it seems nothing is going to be fixed about the errors it seems.
More information available if needed.
Quote