Computer is failing to install WindowsXP

obobski

2[H]4U
Joined
Aug 10, 2005
Messages
2,386
alright, so, I think my new PC just ate it, and I'm out of ideas for fixing it

background:
was playing L4D for a few hours last night, hosting a local server (me and one other person), it CTD'd once on us, so I restarted L4D, it went for another ~20-30 minutes, and then CTD'd again, it wasn't due to us playing with console or overloading the software

so I figure, ok, computer's been on for 5-6 days, lets reboot it, and see if things improve (normally they do), so I restart it, and the KB doesn't work (as in, it doesn't matter what you do, what you sacrifice to god, how many times you restart, how many times you clear CMOS, KB will not work, yes I tried other KBs, no none of them worked either (and PS/2 is NOT AN OPTION before someone suggests that (as the mainboard can't))

SO after screwing around with a windows (Windows XP for reference) recovery console/repair install, I finally decide to just nuke everything, so I get both disks to "unpartioned", create a "raw" partition, format it to NTFS, everything goes good

and then

BSOD ! :mad::mad:

with
"IRQL_NOT_LESS_OR_EQUAL"

some googling finds that this happens with overheating, I promptly clean the inside of my PC and make sure temps are good

IRQL_NOT_LESS_OR_EQUAL

clear CMOS and reset BIOS settings

IRQL_NOT_LESS_OR_EQUAL

its always at the exact same point, during the "Installing Windows" phase when it runs the progress bar for "Devices Installing" or whatever, always at the same point, just keeps BSOD'ing repeatedly

I have not changed hardware on this system since building it
It has never BSOD'd in the some 11 months of nearly consistent 24/7 operation
it will sit stable in BIOS, or any bootable environment (DOS, Win Receovery Console, System Works' bootable environment, Win installer, etc) with no issues
it doesn't reboot loop (and never has)


SO
before it gets to have a nice'n'personal with an axe :)mad:) does anyone have any advice?

specs:
Intel DX48BT2
Intel Core 2 Quad Q9550 (is currently, and always has been, 100% full stock, with EIST enabled)
G.Skill Pi Series DDR3 1333Mhz
Sapphire Radeon HD 4870X2 2GB
PC Power & Cooling TurboCool 860W (non-ESA version)
2x WD CaviarGP 500GB (the older version with 16MB cache)
Auzen X-Fi Prelude

haven't changed any hardware since this came out of boxes from newegg, haven't overclocked any hardware, haven't modified any hardware, temps are alright (40-45*C on CPU, 60-70* C on GPU), to my knowledge no surges/etc (there is a surge protector between the PC and the wall, and nothing else on the protector is displaying any issues, so I don't think a power surge damaged anything), I didn't see any burn marks or burst capacitors on the mobo/HDs/graphics card, theres no artifacts/distortion on screen, etc

I'm really beating my head against the wall here, because for all intents and purposes this shouldn't even have failed in the first place, let alone be FUBARd like this :confused::confused:


sorry for the ridiculously long post, figured I'd provide everything I can (if theres something I missed, just ask)
 
Back to basics time;

- Will the system pass a 24 hour run of Memtest86+ (bootable version) with no errors?
- Will the hard drives pass the extended manufacturer's diagnostic tests?
....start there.

A good way to get both those tests and a bunch of other good stuff is to burn a copy of the Ultimate Boot CD. Got a couple on the bench around here.....it's good stuff.

Also, check the voltages on your power supply while the system is up and running with a volt meter. If you don't have one, maybe a buddy does....??
 
download knopix are ubuntu and try the live os without installation since the entire o.s. can boot from the cd. there is nothing virus wise etc... that can be the probelm it isolates it to a full hardware problem try it without the harddrive installed .
 
download knopix are ubuntu and try the live os without installation since the entire o.s. can boot from the cd. there is nothing virus wise etc... that can be the probelm it isolates it to a full hardware problem try it without the harddrive installed .

I don't understand how there could be a virus issue if both HDs are blank?

@ blinded:

both HDs worked on another system for a number of hours transfering data (backups, so I could blank them), so I think we can assume they're ok? (SMART also didn't report any issues, on either system)

so I guess it gets to sit up all night crunching away at memtest then
 
In my experience, SMART doesn't always work. Like I had this 160GB Seagate that is fine according to SMART, but when I go to do anything on the drive it locks up.
 
In my experience, SMART doesn't always work. Like I had this 160GB Seagate that is fine according to SMART, but when I go to do anything on the drive it locks up.

oh, that makes me feel better :p:eek:

I've had it report a drive failure in advance, but beyond that not much, figured it was "foolproof" though (at least, "foolproof enough")

so I'm still gonna go ahead with memtest overnight/through tomorrow, unless you think I should run the WD Disk utility first? (since that won't take 24+ hours)

::EDIT
ok WD DLG came back 0000 no errors on both disks, 0'ing them out right now (I've had this fix issues in the past, and all data is backed up)
then its off to play with other features on this very nice bootdisk that blinded suggested, many thanks for such a good utility man
 
Last edited:
Sorry was in a hurry . Knoppix doesn't require the hardrive to boot up so you can use this if there is nothing are a virus on your harddrive to see if its a hardware problem(harddriver are other hardware). Really nice o.s. for testing
 
Sorry was in a hurry . Knoppix doesn't require the hardrive to boot up so you can use this if there is nothing are a virus on your harddrive to see if its a hardware problem(harddriver are other hardware). Really nice o.s. for testing

oh, yeah, so far its handled the WD Diagnostic tool for ~6 hours continuously, so I'm thinking the stability is still there

after I finish with the HDs, what would be the next fun step? any other suggestions from the bootCD?
 
I also got the irql less or equal error and the only solution was to swap the ram. My ram even passed memtest but it would still BSOD with this stupid error. I tried a friends ram and it didnt BSOD, so I bought some RAM and still no BSODs. I'm on DDR2.
 
Try with a single stick of ram. If it does the same problem swap it for another. If it BSODs at the same spot for all 3 sticks, it shouldn't be the ram at fault (maybe the controller, but that wold be very odd since you are able to run knoppix, which unpacks everything into ram)

If you get a BSOD @ devices installing, it 'could' be a bad driver. Is this the exact same XP install disc you used last time? Try to slipstream SP3 + your drivers into your XP install disc (www.nliteos.com). I think that should fix your issue.
 
Try with a single stick of ram. If it does the same problem swap it for another. If it BSODs at the same spot for all 3 sticks, it shouldn't be the ram at fault (maybe the controller, but that wold be very odd since you are able to run knoppix, which unpacks everything into ram)

If you get a BSOD @ devices installing, it 'could' be a bad driver. Is this the exact same XP install disc you used last time? Try to slipstream SP3 + your drivers into your XP install disc (www.nliteos.com). I think that should fix your issue.

yes same xp disc, RAM hasn't changed, so why would it be failing now, and not the last few times its loaded an OS or application? unless the memory has gone bad, which ~8 hours of HD diagnostics and 24 hours of memtest have more or less debunked imho

I'll try installing again, now that its 0'd out, maybe with better luck

really not loving the idea of replacing this DDR3 set after less than a full year, for no reason other than "windows is having a bitch fit"
 
yes same xp disc, RAM hasn't changed, so why would it be failing now, and not the last few times its loaded an OS or application? unless the memory has gone bad, which ~8 hours of HD diagnostics and 24 hours of memtest have more or less debunked imho

I'll try installing again, now that its 0'd out, maybe with better luck

really not loving the idea of replacing this DDR3 set after less than a full year, for no reason other than "windows is having a bitch fit"


if things dont work.. try switching the ram in different slots.. so put stick 2 in slot 1 and stick 1 in slot 2.. sometimes it works.. ive had to do it a few times with my ballistix tracer ram..
 
if things dont work.. try switching the ram in different slots.. so put stick 2 in slot 1 and stick 1 in slot 2.. sometimes it works.. ive had to do it a few times with my ballistix tracer ram..

tried, stability stays the same, crashes stay the same :eek:
 
I must've missed it, but did you run memtest overnight? I assume you did, but it wasn't explicit from what I've read above. Anyhow, you could also try different SATA cables.
 
yes same xp disc, RAM hasn't changed, so why would it be failing now, and not the last few times its loaded an OS or application? unless the memory has gone bad, which ~8 hours of HD diagnostics and 24 hours of memtest have more or less debunked imho

I'll try installing again, now that its 0'd out, maybe with better luck

really not loving the idea of replacing this DDR3 set after less than a full year, for no reason other than "windows is having a bitch fit"

What I meant was to test with only 1 stick of ram in the machine, then try to install. If it fails, try using another. You do this to narrow down the problem. If it works with 1 stick and not the other, you can pretty much say 1 of the sticks is bad.

Also try to slipstream SP3 + your drivers into an XP install disc and try from there (www.nliteos.com). See if it still crashes at the "installing devices" screen.
 
I must've missed it, but did you run memtest overnight? I assume you did, but it wasn't explicit from what I've read above. Anyhow, you could also try different SATA cables.

yeah 23 hours and change with no issues (and did get new SATA cables, because the old ones didn't fit with the case very well (below was true before I changed cables))

actually FIXED the issue:

got a newer XP CD from a neighbor, put it in, and it wouldn't even finish loading (like the pre-install load), and the DVDRW was making a clunking noise, pulled it out, XP loaded and installed in under 45 minutes and I've had no issues for ~day by now


best guess is the drive itself was at fault, and was causing me the IRQL_NOT_LESS_OR_EQUAL troubles (i.e: driver issues of some sort as a result of drive failure), thanks for all of the suggestions, do appreciate the troubleshooting tips, even if there wasn't a 100% answer, at least got me thinking towards things :)
 
Back
Top