Problem one: Windows blue screen crashing on clean install with brand new computer.
This one killed me for a good nine hours. I went over everything, tested everything. Mobo brand new, CPU, new, Memory, certified and tested Corsair DDR2-800. Check everything 10 different times. Nothing. BSoD. So, I got on the MS site, and did a lot fo digging for the error codes. Turns out that regardless fo what your hardware says you can do, Windows XP will BARF huge chunks on install if you don't have all drives set for CS with the jumpers. Proper MA/SL will not work. After install, it's fine, but not during. Fixed Jumper, system rocks like you wouldn't believe.
Problem 2: System fired after updating Bios
This one for the past 6 hours had me going ballistic as only a computer can make me. I followed the proper bios updateing to the letter. Everything went fine. No errors, no problems. System restarted normally.
Got the Asus splash page and...... and...... nothing. Quietly purring. Tab - nothing. Del - nothing.
Managed to get to the post screen by hooking up a classic Keyboard (I will launch nukes at any mobo manf. that decides to start omitting the PS/2 keyboard jack) abd hold Tab while powering on. Cpu detected just fine. Ram detected just fine. Froze after that.
So, I started hacking everything apart, stripping the system. Yanked battery, reset bios with jumper. Tried booting with the CLRCMOS on because some boards will drop you into bios recovery mode. Nada. Finally I yanked all teh USB, printer, etc cords and tried again.
Perfect boot to post.
Don't know why, but that got it working.
Haven't tried rebooting with all the USB cords in, but i suspect now that the bios settings are in place, it'll be fine.
Good times.
--S
This one killed me for a good nine hours. I went over everything, tested everything. Mobo brand new, CPU, new, Memory, certified and tested Corsair DDR2-800. Check everything 10 different times. Nothing. BSoD. So, I got on the MS site, and did a lot fo digging for the error codes. Turns out that regardless fo what your hardware says you can do, Windows XP will BARF huge chunks on install if you don't have all drives set for CS with the jumpers. Proper MA/SL will not work. After install, it's fine, but not during. Fixed Jumper, system rocks like you wouldn't believe.
Problem 2: System fired after updating Bios
This one for the past 6 hours had me going ballistic as only a computer can make me. I followed the proper bios updateing to the letter. Everything went fine. No errors, no problems. System restarted normally.
Got the Asus splash page and...... and...... nothing. Quietly purring. Tab - nothing. Del - nothing.
Managed to get to the post screen by hooking up a classic Keyboard (I will launch nukes at any mobo manf. that decides to start omitting the PS/2 keyboard jack) abd hold Tab while powering on. Cpu detected just fine. Ram detected just fine. Froze after that.
So, I started hacking everything apart, stripping the system. Yanked battery, reset bios with jumper. Tried booting with the CLRCMOS on because some boards will drop you into bios recovery mode. Nada. Finally I yanked all teh USB, printer, etc cords and tried again.
Perfect boot to post.
Don't know why, but that got it working.
Haven't tried rebooting with all the USB cords in, but i suspect now that the bios settings are in place, it'll be fine.
Good times.
--S
posted by:
|
SF Bay Area
|
-
Re: Some recent discoveries of mine...
Mon, November 26, 2007 - 7:45 PMI've seen this behavior on fresh built machines if you have the USB devices connected while installing the OS and during the initial device discovery on the first boot. On a couple of occasions I have had stable machines go tits up after plugging in a "plug'n'play" device like a printer or scanner and suddenly work when I unplug them. Load the drivers first then try again and there is no problem.
Sadly, XP's plug'n'play doesnt always work as advertised... So general rule of habbit is to disconnect all USB devices until after I finish installing and patching a new or refreshed system.
As for the drive's set to CS, I've actually had more issues with CS set drives than I have with hard setting them to master/slave... Western Digital drives are the worse when it comes to making sure you have the drives set single or master/slave... I do remember a few Linux distro's having issues with drives set to CS and fail to install or run a couple of years back. So force of habbit I just hard jumper all my drives now and never trust "CS".
