Something is Busted - IRQL_NOT_LESS _OR_EQUAL

imported_inspire

Senior member
Jun 29, 2006
986
0
0
Hi Guys,

About a month and a half ago, I put together a new system. Specs:

AMD 955 BE
Scythe MUGEN-2 Cooler (w/ AS5)
Gigabyte GA-MA-790XT-UD4P
4x2 GB G.Skill DDR3 1600
64GB G.Skill Falcon SSD
1 TB WD Caviar Black HD
VisionTek Radeon HD 4770
Samsung SATA DVD-Burner
OCZ 700W Modular PSU
Thermaltake V9 Black Case
Vista 64 Home Premium

Build went fine for the first few weeks. I installed all my stuff, played around with Everest to get a baseline on the temps, didn't tweak too much as I didn't really get a chance.

After 2~3 weeks, I started noticing BSODs. They'd typically occur overnight, and I thought that maybe an update had hung. However, they started becoming more frequent. The majority of the error messages I was getting were IRQL_NOT_LESS_OR_EQUAL. Sometimes I'd get something about Memory Cache, or trying to write to read-only memory. I also noticed that, even when I didn't hit a BSOD, Vista services would randomly stop working.

Like a noob, I thought that some of this might be due to my SSD. I dl'ed the Windows 7 RC, and was going to use that until my retail version shipped. I burned the disk with Nero, and always set it to verify after burning. After going through nearly 6 DVDs, I could never get through a burn without errors. This got me thinking that maybe my SATA controller (north/South Bridge?) was being squirrelly.

Well, long story short - after several bad installs of W7 (bad burn on the disc - I got nowhere), and Vista, I'm at a complete loss. I keep getting the IRQL_NOT_LESS_OR_EQUAL BSOD - even on install to both my SSD and HD. I know it's not the drives. I also know 99.9999% that it's not a CPU heat issue, as I remember none of my everest temps ever going much higher than 40C (No, I don't remember the exact temp - I just know it wasn't hot) while priming all 4 cores.

I've no OS on the drives now. I've lost most of everything I had on there (not a big deal, but a PITA). What I want to figure out is what could it be? I'm thinking of loading my BIOS fail-safes and using just the SSD and 1 stick of memory and adding harware back in until something happens. My only concern is that if it is the mobo that's bad, I'll be wasting my time.

Ideas?

EDIT: After thinking about it some more, I think I may start with memtest before bothering to install anything else.
 

ChaiBabbaChai

Golden Member
Dec 16, 2005
1,090
0
0
yeah, I would rule out the RAM by running memtest before replacing the motherboard.

Best of luck.
 
Nov 26, 2005
15,189
401
126
NB voltage may be too high - I JUST got one of those btw - *weird coincidence*, Ram timings need to be a bit more relaxed
 
Nov 26, 2005
15,189
401
126
another possibility is if you recently took a device out from your mobo and the software is trying to access it or something is trying to access it

read here

EDIT: I took out 2 of the 2gb sticks (the new ones) and am testing the ones I know for sure are good. will report back later

signs are looking like it is a couple of bad mem sticks - they were good when i first got them a week ago.

EDIT2: nope something else keeps crashing, sorry i couldn't help
 

imported_inspire

Senior member
Jun 29, 2006
986
0
0
Originally posted by: BTRY B 529th FA BN
another possibility is if you recently took a device out from your mobo and the software is trying to access it or something is trying to access it

read here

EDIT: I took out 2 of the 2gb sticks (the new ones) and am testing the ones I know for sure are good. will report back later

signs are looking like it is a couple of bad mem sticks - they were good when i first got them a week ago.

EDIT2: nope something else keeps crashing, sorry i couldn't help

Np, man - thanks for the effort. My sticks wouldn't run at the rated speeds / timings out of the box, either - I had to manually set the speed / timings in the BIOS. One thing I have read is that this board has a known issue of overvolting memory, regardless of what the BIOS says. I've heard it usually provides 1.90~2.00v, which is a bit of overkill for my 1.65v DIMMs.

I haven't tried memtest yet - ended up having plans last night, so I'll give it a shot today after work.
 

hectorsm

Senior member
Jan 6, 2005
211
0
76
Do the memtest as suggested by ChaiBabbaChai. I ran into that same error and it ended up being one of my memory sticks. I got a new set of memory modules and the problem is now gone.

Run your memory modules in single channel and allow Memtest to do at least 2 full test. If the memory modules pass the test then I would start looking into other hardware components.

 

imported_inspire

Senior member
Jun 29, 2006
986
0
0
Originally posted by: hectorsm
Do the memtest as suggested by ChaiBabbaChai. I ran into that same error and it ended up being one of my memory sticks. I got a new set of memory modules and the problem is now gone.

Run your memory modules in single channel and allow Memtest to do at least 2 full test. If the memory modules pass the test then I would start looking into other hardware components.

That's exactly what I did last night - one of my modules came back with ~50,000 errors after 1 minute, and the rest were fine. Now I'm just waiting for G.Skill's RMA department to return my email...