my comp is dead!

ok. lests start from the beginning of this.

first, i have been getting BSODs (with this same error, IRQL not less than or equal) for nearly 2 months. changing VC drivers was a fix but then i had no glide. i ignored. about a week ago i started having problems with double-clicking and XP not loading right. (no login sound till 5 min after boot?!) then, yesterday, it started crashing ans BSODing, ALOT. i changed drivers and removed the clock settings on my voodoo. this didnt help. windows started 'pausing' alot, i traced this down to my LAN card, and updated the drivers. Mistake #1. from there, i had about 2 minutes of XP run time before a BSOD or lock. i used system restore, went back to a week ago. NO CHANGE. getting annoye4d, i swap out my lan card for a NETGear one. no change. i remove the netgear. no change. i replace the Voodoo with a PCI 4 meg Trident card. still BSODing and locking (no change) i then thought it might have been a CMOS setting. i restore back to Fail-Safe settings. Mistake #2. now it wont even post. i get a nice pretty black screen. not even some beeps. removing the IDE devices, changing memory, changing VCs, all have had no effect. the only 3 components left on are the PSU, Mobo, and CPU.

did somthing just blow?!

im gonna swap out my athlon for a Duron in my basement, see if i can get her to boot.

on a final note, i did try to flush the bios and reboot. i have done this before and it worked fine, this time it did not.

any feedback/ideas would be nice

no, it BSODs in safe mode (aswell as while booting (before any bootloaders even!) and once in the CMOS.

as for LEDs, i have 1. power. green. if your mobo is on and you dont have the green light. be afraid.

Tried: Remove everything but Video, CPU and RAM and see if it posts....
Tried: If not... Remove Ram and see if you get a Beep-code..
Tried: If Not... Put the Ram back in and remove the Vid...See if you get beep-code
Tried: If not....Walk a single Ram stick down your slots.....
Hope Not: Still nothing.....Mobo dead

Originally posted by DexterII
I had the same problem and it turned out my keyboard and mouse were in the wrong PS/2 slots, my mobo wouldn't do anything.

Try switching the two or the one if there is no mouse.

Click to expand...

the mouse and keyboard ARE in the correct slots, and have not been moved since their installation.

read the whole post

all IDE devieces are spinning up, but i removed the cables to be sure it wasnt a problem with any of them. mobo power light comes on, fans spin up, (including the ones mobo powered)

well, i figured it out.

about 2 months ago i had a stick of slower 20ns ram in mny system. this is back when i last had to use failsafe. i had since removed that ram. now, when we revert to failsafe, memory settings get thrown to PC100. with 2 sticks of 15ns PC133 which WILL NOT RUN AT PC100, this presented a problem.

once again, saved by a 32 meg dimm

now i just have to get it running STABLE.

i was able to put the ram back in after i set the ram clock speeds right.

just re-installed windows (fresh) waiting for some crashing.

re-installed XP, seems stable now.

i also moved Linux on to its own HDD (i have to install again, i botched up the install and am logging into a nice seksi command prompt )

Originally posted by Clayeth|BuF

umm... there's no reason for PC133 ram not to run at 100mhz. The only difference between PC100 and PC133 is the speed that they have tested to be stable at. Lowering the speed shouldn't cause problems. I would say one of those pieces you removed is bad. My computer has PC133 running at 100mhz at this very moment.

Click to expand...

same memory i had in before. also, i could isolate each one and still the same problems. NTM it didnt work with both at the time wither, and works FINE with both now. odd, yes. impossible, no.