[R3TR3C]

So I just put an Athlon 64 3400+ into an old computer I had butchered and I'm having a really weird problem with it. When I go to install the OS it gets to the windows screen and is ok for like 10 seconds and then either goes to a BSOD with the message "IRQL_NOT_LESS_OR_EQUAL" or the screen gets like 50 little black lines that shoot across and the system restarts. I was wondering if maybe I put too much thermal paste on the CPU and its keeping it from getting cooled and causing the system to shut down. In BIOS I checked my temps and they are at 28-29 C. Is that too high still for just being in BIOS? My dual core system im on right now has those temps right now while I'm typing so I'm thinking that may be the problem.

Any thoughts?

Thanks,
R3TR3C

 

[PR1M3R]

The temps sounds fine, the bios actually puts a moderate load on the cpu. The black lines makes me think video card, but honestly I have no idea exept that the temps are fine.

 

[R3TR3C]

I also forgot to mention that it used to have 1 gig PC3200 RAM but I gave it to my dad and took 1 gig of PC2700 RAM from another old comp while putting this one together. Thats the only other part ive changed.

 

[R3TR3C]

The computer doesn't have a video card, it has integrated. So should I go steal that RAM back from my dad and pop it in there? It's really my only other option.

 

[txtmstrjoe]

Quote:

Originally Posted by R3TR3C I also forgot to mention that it used to have 1 gig PC3200 RAM but I gave it to my dad and took 1 gig of PC2700 RAM from another old comp while putting this one together. Thats the only other part ive changed.

Well, most BSODs are caused by faulty memory. I'd swap RAM DIMMs and test to see which one is faulty. (I suggest using MemTest86+ to test the RAM.)

Hope this helps!

 

[rsfkevski]

I must agree with the RAM swapping suggestion. Probably got some bad RAM stuck in there. Swap out with your Dad's temporarily and see if that works. Good Luck and let us know how things turn out!

 

[R3TR3C]

Well I would do that except for now the computer doesnt post anymore...I think I mightve hurt the cpu by pulling it out too much when I thought that the temps were bad...As soon as I get it posting again ill try what you guys suggested. Thanks for all the help anyway though.

 

[nigel]

i have only ever seen the IRQL_NOT_LESS_OR_EQUAL once,
and that was when i went to far with my overclock. but thats it.

 

[R3TR3C]

well i got it posting again and I'm about to run memtest to see if the RAM is the problem. Wish me luck =)

 

[Rocky]

Good Luck!

 

[nigel]

luck.lol

 

[txtmstrjoe]

Quote:

Originally Posted by R3TR3C well i got it posting again and I'm about to run memtest to see if the RAM is the problem. Wish me luck =)

I was just about to suggest that it's very unlikely you damaged your CPU, even from lots of taking it in and out of the socket. These things are quite tough, to be perfectly frank.

Unless you do something truly dumb, like take off the IHS and damage the resistors (or whatever those very tiny components are surrounding the die itself), or drop something heavy on the die and destroy it that way, or mutilate the pins, CPUs can absorb a lot of punishment and live to tell the tale.

My money is still on RAM being wonky.

 

[thlnk3r]

Funny, I just experienced the same issue on a machine I was working on at work. Got the "IRQL_NOT_LESS_OR_EQUAL", tested the memory and it failed.

 

[R3TR3C]

My memory went through 3 memtest runs without finding any errors =/. I guess I can still swap back to the original memory I had just to be sure memtest isnt messing up and not finding errors. (Which I think is highly unlikely). Now I'm even more confused as to what the problem could possibly be =/.

 

[v1ruz]

If the keyboard is working enough to get to the Bios, then It's probably RAM. I had the same problem with alot of systems I was working with in StRUT, and if it wasn't the keyboard, usually switching the RAM out worked.

 

[txtmstrjoe]

Some quick Googling found this and this.

Evidently a hardware fault causes this. Since we've apparently eliminated the RAM, and the CPU doesn't seem to be overheating, do any of the chipsets have any active cooling on them?

Also, please describe precisely when the BSOD happens. Is it during OS installation? Or after the installation is complete and you're booting into the OS? This might make a difference because, according to Microsoft, this error message can also be caused by a corrupt driver, which can only happen if there is an OS installed.

Lots of things to check off the list, perhaps, but such is the nature of the beast.

Good luck! And hope this helps.

 

[thlnk3r]

Are you able to do a full drive read scan on your main HD just to rule that out?

 

[R3TR3C]

It happens right before I attempt to install the OS. I don't think my RAM has been completely ruled out. I read on a site I just googled that a guy did the same thing as me with his RAM and even though the new RAM worked ok in memtest the settings were specialized for his old ram so he popped the old ram in and fixed it. I'm still gonna pop the RAM I gave to my dad back into mine just to completely rule out RAM if it isn't the problem.

 

[txtmstrjoe]

Quote:

Originally Posted by R3TR3C It happens right before I attempt to install the OS. I don't think my RAM has been completely ruled out. I read on a site I just googled that a guy did the same thing as me with his RAM and even though the new RAM worked ok in memtest the settings were specialized for his old ram so he popped the old ram in and fixed it. I'm still gonna pop the RAM I gave to my dad back into mine just to completely rule out RAM if it isn't the problem.

Good idea.

It might also help to reset everything to default settings (in case this hasn't been done).

Keep at it!

 

[R3TR3C]

Yea I haven't reset CMOS just yet because on another PC I had some trouble with I reset CMOS and one of the default options was to fail POST if no floppy was installed (or something like that). And since I dont own a floppy drive I can't make it post =/. I didn't want that to happen to the current PC I'm working on as well. (Although it didn't even come with a floppy drive so I'm oblivious to any BIOS options that have that kind of effect). I guess if the RAM switch doesn't work then thats the last thing to try.