| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 77894 | 2007-03-26 21:09:00 | PC Reboots during Bootup After Upgrade | Lockie (11715) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 536085 | 2007-03-26 21:09:00 | I Have had this problem with several PC's. Having installed a new motherboard, I rebooted the PC expecting XP to ask for new drivers, but it gets part way through the Windows bootup sequence then reboots... every time. Push F8 and select step by step. It gets to system32/Mup.sys, then "poof", reboot. Safe Mode works, but not much use. Recently tried updating the drivers for my nForce4 motherboard to version 6.86 and had the same problem at the same point in the boot sequence. Is this a fact of life and an XP reinstall required every upgrade, or am I missing something? Any help would be appreciated.:o |
Lockie (11715) | ||
| 536086 | 2007-03-26 21:30:00 | WinXP does not like new hardware like MBs added. It won't ask for drivers, if you had disable the Auto Reboot, you would see it stop at a BSOD. You can try doing a Repair Install on it but I'd say it still won't like it and you'll have to do a fresh install. |
pctek (84) | ||
| 536087 | 2007-03-26 22:00:00 | Thks, that confirms my fears... Have also found that there is an issue with the latest bundled nForce IDE driver that can cause the same problem on some motherboards. Long Live Linux! Cheers :) |
Lockie (11715) | ||
| 536088 | 2007-03-27 08:36:00 | I never install 3rd party IDE drivers, even if they tell you it will increase performance, especially on XP. (unless you have some really strange IDE controller and it's 100% necessary else windows can't see it or something) The first (and last) time I tried that was on Windows 95, which totally screwed the system and I had to reinstall. |
Agent_24 (57) | ||
| 536089 | 2007-03-27 11:13:00 | A repair install may work. I've had it work 8 times out of 10, so give it a go. You are always better off doing a fresh install though, no nasty remnants of your old system left over. |
trig42 (11325) | ||
| 536090 | 2007-03-28 11:40:00 | Just curious, presuming that the old MB was not U/S, would it have helped if the old MB drivers had been uninstalled before the new MB was installed? That way it wouldn't be trying to boot with the wrong drivers and might have found a better match. I assume that any new computer must boot initially without MB drivers then install them once the OS is up and running, or are they called for earlier in the boot process? Pardon my ignorance, but it seems to be a chicken and egg issue and i'd like to know what comes first on a new computer and a new OS installation. Cheers Billy 8-{) |
Billy T (70) | ||
| 536091 | 2007-03-28 20:32:00 | J would it have helped if the old MB drivers had been uninstalled before the new MB was installed? ) Good question, I've never tried that. SOunds logical. |
pctek (84) | ||
| 536092 | 2007-03-28 20:36:00 | sysprep is what you need for this sort of change. Its really designed for mass deployment but will work for cases like this as long as the HAL doesn't change. | gcarmich (10068) | ||
| 536093 | 2007-03-28 22:36:00 | not sure if that will do much as the hal can change with motherboard change. repair install restets the hal. | tweak'e (69) | ||
| 536094 | 2007-03-28 22:57:00 | The HAL changes of course for every hardware change...LOL | SolMiester (139) | ||
| 1 | |||||