So I finally have all the parts for my mod that I've been planning for months. Everything is together and looking great... except with installing windows.
So far, I've been hitting loads of problems trying to get windows installed. A few times, I've managed to get as far as the 'finalization' steps (entering the date, time, location etc) and then BSOD. Twice I got to the "initializing network' stage and then BSOD. More recently I got a BSOD while it was creating a 'list of files to download'.
I've gotten a few different errors too. A 'PFN_LIST_CORRUPT' error was the most recent.
I suspected the RAM and ran a full test with memtest86, which came back with no errors. The other suspect I have is the HDD. Its a cannibalized drive from a dead rig that I inherited, so I don't have proof that it ever even worked.
Where do you think the problem might be? Does a clean memtest suggest that the RAM is OK? What should my next steps be?
What make HD? Try downloading DFT from IBM/Hitachi and make boot diskette/CD to test the drive. What CPU, video adapter, PSU? Dodgy PSU can cause install problems.
The drive is a Western Digital. I checked the WD website but it seemed like their bootable CDs didn't have drive tests, they only mentioned things like "how to install" "pin placement" etc.
//////The drive is a Western Digital. I checked the WD website but it seemed like their bootable CDs didn't have drive tests, they only mentioned things like "how to install" "pin placement" etc.
@Shez We need more information to find the proper HDD Diagnostic disk from Western Digital for your HDD like the exact model # and its connection type IDE or SATA, and more than likely you'll need a Floppy Drive to run the diagnostic program.
------------------------------Badges? We don't need no stinkin' badges!
Reply to 4ryan6
Just got done talking to my IT guy and he suspects the mobo and not the HD or RAM. When I get home, I'll test with a working HD, reseat everything and try for the millionth time.
Shez, that was the correct site, Data Lifeguard is the diagnostic program, can be run under windows OR DOS - Floppy or CD. Different HD is also valid test. If you have blown (bulging/leaking0 caps on the motherboard, then that may well be your problem.
The mobo is brand new and doesn't have the tell tale signs of burnt components. It's in the open air, so I've had plenty of face time with it
So tonight - I'm using the new and working HD. On the first run through the system hung while part way through the install. No BSOD but a complete hang.
I'm currently working my way through the 3rd install for today. The install made it all the way to the point of "saving" and then I got a BSOD stating "IRQL_NOT_LESS_OR_EQUAL".
I read up on the error and it apparently is commonly the CPU overheating (i'll try again with a house fan pointed at it) or bad RAM. Which makes me wonder again, does a clean memtest suggest that the RAM is OK?
If HS feels very hot, fan is slow or HS clogged with fluff. If HS very cool, is not making good contact with CPU, needs reseating and new thermal compound. You could go into BIOS and check CPU temp, keep watching until it stabilises, or gets to 70C, which would indicate a problem. Can you plug a known good PSU into this for testing. Memory should be OK.
@Mike. Yeah, I had thought that might be a problem as well. The CPU is soldered down onto the mobo, so reseating isn't a possibility. And as for the heating, I placed a house fan, on high in front of the board and blasted it with cool air. Checking through the BIOS, the temps never rose more than 42C.
I'll see if I can't find another PSU. And I also ran memtest a few more times last night and again, no errors.
You bring up a good point though mike, maybe I should take off the HS and try reapplying thermal compound.
So I finally have all the parts for my mod that I've been planning for months. Everything is together and looking great... except with installing windows.
So far, I've been hitting loads of problems trying to get windows installed. A few times, I've managed to get as far as the 'finalization' steps (entering the date, time, location etc) and then BSOD. Twice I got to the "initializing network' stage and then BSOD. More recently I got a BSOD while it was creating a 'list of files to download'.
I've gotten a few different errors too. A 'PFN_LIST_CORRUPT' error was the most recent.
I suspected the RAM and ran a full test with memtest86, which came back with no errors. The other suspect I have is the HDD. Its a cannibalized drive from a dead rig that I inherited, so I don't have proof that it ever even worked.
Where do you think the problem might be? Does a clean memtest suggest that the RAM is OK? What should my next steps be?
The mobo is brand new and doesn't have the tell tale signs of burnt components. It's in the open air, so I've had plenty of face time with it
So tonight - I'm using the new and working HD. On the first run through the system hung while part way through the install. No BSOD but a complete hang.
I'm currently working my way through the 3rd install for today. The install made it all the way to the point of "saving" and then I got a BSOD stating "IRQL_NOT_LESS_OR_EQUAL".
I read up on the error and it apparently is commonly the CPU overheating (i'll try again with a house fan pointed at it) or bad RAM. Which makes me wonder again, does a clean memtest suggest that the RAM is OK?
@Mike. Yeah, I had thought that might be a problem as well. The CPU is soldered down onto the mobo, so reseating isn't a possibility. And as for the heating, I placed a house fan, on high in front of the board and blasted it with cool air. Checking through the BIOS, the temps never rose more than 42C.
I'll see if I can't find another PSU. And I also ran memtest a few more times last night and again, no errors.
You bring up a good point though mike, maybe I should take off the HS and try reapplying thermal compound.
To repay me, you can figure out what's wrong with my damn computer
I was fully intending to help you anyway, but I wanted to research your exact setup first.
First off use the MSFT memory diagnostic program to diagnose the memory, [download page link below], its a lot more in depth at stressing areas of the memory that are Windows OP/SYS dependent and also run the extended test by pressing T I believe it is, anyhow the test and extended test instructions are at the top of the program.
Because Memtest doesn't fully cover memory failures that are related to the Windows OP/SYS so MSFT released their own memory testing program, and because the errors you've received can cover more than 1 thing but they both can cover memory errors.
As far as overheating of the CPU, 42c is gravy zone for a Celeron processor, thats not a problem!
The original HDD would just need to be wiped clean of all previous OP/SYS and boot records, and the diagnostic disk should allow that.
But you mentioned another HDD new?
What is that exactly?
FYI you're not limited to a SATA1 150 HDD, the SATA2 300 HDDs have a transfer jumper you can set to the 150 Transfer mode, because you may find a SATA2 today cheaper than an older SATA1.
What type optical drive are you using to load the OP/SYS and how is it connected,[IE? CDROM,CDRW,DVDROM,DVDRW???]?
FYI WinXP don't like CDROM drives, it will default to PIO transfer mode if it encounters 1 error, so you need at least a CDRW to run in DMA mode.
Are you using a PS2 connected mouse and Keyboard?
FYI Its best to stay away from USB Mouse and Keyboard when first installing XP.
Have you double checked all the cables to make sure they're all the way plugged in, and do you possibly have additional cables to swap out to check for a bad cable possibility?
------------------------------Badges? We don't need no stinkin' badges!
Reply to 4ryan6
Unfortunately, I just sent off the motherboard for replacement. I tried further tests... but definitely didn't hit all the fixes you just suggested.
In response...
I checked the heat on the CPU again and again, and the thing never seemed to raise above 45. I even scraped off the crappy thermal pad it came with and applied Artic Silver in a last ditch effort before boxing it up.
As per the HD, I ran a WD diagnostic test on the SATA drive I had been using and it came back clean as a whistle. I also tried using another ATA drive just in case, that was known to work. But again, all the same problems arose.
I definitely didn't know that you could step down a SATA2 - that's awesome to know! Now you taught me something
For the optical drive, I was using a DVD drive from my home computer via the ATA cable. I made sure that everything was jumpered correctly and hooked up to the right parts of the cord (HD on the end).
I unfortunately was only able to use the USB keyboard/mouse that I had because I didn't have a PS2 at my disposal. If I had, I definitely would have though
Cables and components were reseated a couple times throughout my trials but I never went as far as checking for bad cabling. I guess I assumed that if the cable looked good and didn't cause initial problems that they'd be good to go.
Other things I did before sending it off...
I ran memtest several more times, with no errors.
Ran diagnostic tests on both HDs that I was using.
Placed a house fan in front of the board to negate any overheating issues.
Tried numerous optical drive and HD configurations.
Talked with my IT guy about the issues - he suspected the mobo
I know that having another stick of memory to test would have been preferable and better stress testing would have certainly ruled out the HD and RAM better... but at this point I have to believe that the motherboard is the issue. It just seems like the only likely culprit. Although, I guess I'll actually know once the replacement motherboard comes in.
If everyone goes well with the new board, awesome but regardless - thank you all for taking time to try and figure out what could/is the root of my problem.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.