Posted: 12/16/2008 8:01:39 AM EDT
|
Odd one.
My PSU fan pooped out and nobody in town had a 140mm so I made a temporary adapter for an 80mm to maintain airflow until a 140mm fan comes. During the diagnosis/replacement process I turned the computer on and off with no peripherals atached (i know... Windows is too finicky to not "shut down" properly...  ).
So.... now on bootup it gets to the "Windoes did not start successfully...) screen. If I choose "Start up normally" it gets to the Windows XP splash screen, hangs there for 3-5 minutes, flashes a BSoD for < 1 Millisecond and then reboots. If I choose "Safe Mode" it rolls through the drivers until it hits Mup.Sys and then freezes. I already chcked the seating of all cards and cables. all ok. So I googled a few things (i'm on my laptop) including "hangs on mup.sys" and found this page: mup.sys info which says I should disable mup.sys. or do about 20 other "fixes". I'd prefer a second opinion. WHAT DO I DO???? |
|
The main reasons for this Windows XP or Win 2000 boot hang or alleged mup.sys issue are:
Hard disk failure or corruption A corrupted registry or registry hive New hardware has been installed but not did not completely "Register or re-Register" correctly New hardware has been installed but it is faulty or failing The new hardware's driver or windows itself has been compromised (Disk data corruption or by a virus) or (rare) needs to be updated The power supply is marginal in output or failing (Common per user feedback) BIOS\ESCD\Motherboard chipset driver conflict with a component, its driver, or its registry data Existing hardware including the motherboard may have failed in a specific way but not catastrophically. In my experience, I have never found that the mup.sys driver is actually the cause of the problem but replacing it with a known good uninfected version won't hurt if just to exclude that possibility. Also, disabling the mup.sys driver by using the recovery console normally does not help either. Windows will then just hang at the driver that loads prior to mup.sys. If you are curious and want to know more about this driver check out the What is MUP.SYS and what does it do? section below. i bet your PSU is dead. when the fan went out it took some other shit inside with it. take it apart and check all the caps and resistors becuase i bet one of them is burned up. |
|
Quoted:
Yank drive.. Pull all your data.. then format and reinstall windows. I'd prefer a restorative approach. It's WAY too much hassle to reinstall everything (apple's "authorized computer" b.s., Microsoft flight sim makes me call them for a new code everytime I reinstall it, and about 50 other giant annoyances....). |
|
Quoted:
The main reasons for this Windows XP or Win 2000 boot hang or alleged mup.sys issue are: Hard disk failure or corruption A corrupted registry or registry hive New hardware has been installed but not did not completely "Register or re-Register" correctly New hardware has been installed but it is faulty or failing The new hardware's driver or windows itself has been compromised (Disk data corruption or by a virus) or (rare) needs to be updated The power supply is marginal in output or failing (Common per user feedback) BIOS\ESCD\Motherboard chipset driver conflict with a component, its driver, or its registry data Existing hardware including the motherboard may have failed in a specific way but not catastrophically. In my experience, I have never found that the mup.sys driver is actually the cause of the problem but replacing it with a known good uninfected version won't hurt if just to exclude that possibility. Also, disabling the mup.sys driver by using the recovery console normally does not help either. Windows will then just hang at the driver that loads prior to mup.sys. If you are curious and want to know more about this driver check out the What is MUP.SYS and what does it do? section below. i bet your PSU is dead. when the fan went out it took some other shit inside with it. take it apart and check all the caps and resistors becuase i bet one of them is burned up. Actually, it was working OK before the fan change, just making that "Chewbacca gargling gravel" noise, so I opted to change the fan to quiet it down. Upon completion, no love. I suppose that it's possible that it's shit out coincidentally to the fan change.. |
|
Boot off the windows xp CD.
Choose the "repair" option, it will load a command prompt window(recovery console). At the recovery console type in chkdsk /f /r This will scan your drive and fix the sector that went bad when you abruptly shut it off. I just fixed a computer with the same issue yesterday with this method. Good luck. Follow this article if you want all the info on what to do next. |
|
Quoted:
Quoted:
The main reasons for this Windows XP or Win 2000 boot hang or alleged mup.sys issue are: Hard disk failure or corruption A corrupted registry or registry hive New hardware has been installed but not did not completely "Register or re-Register" correctly New hardware has been installed but it is faulty or failing The new hardware's driver or windows itself has been compromised (Disk data corruption or by a virus) or (rare) needs to be updated The power supply is marginal in output or failing (Common per user feedback) BIOS\ESCD\Motherboard chipset driver conflict with a component, its driver, or its registry data Existing hardware including the motherboard may have failed in a specific way but not catastrophically. In my experience, I have never found that the mup.sys driver is actually the cause of the problem but replacing it with a known good uninfected version won't hurt if just to exclude that possibility. Also, disabling the mup.sys driver by using the recovery console normally does not help either. Windows will then just hang at the driver that loads prior to mup.sys. If you are curious and want to know more about this driver check out the What is MUP.SYS and what does it do? section below. i bet your PSU is dead. when the fan went out it took some other shit inside with it. take it apart and check all the caps and resistors becuase i bet one of them is burned up. Actually, it was working OK before the fan change, just making that "Chewbacca gargling gravel" noise, so I opted to change the fan to quiet it down. Upon completion, no love. I suppose that it's possible that it's shit out coincidentally to the fan change.. That fan could've been running slow for weeks prior and you'd never have a clue. Heat is bad for electronics (duh) It's quite possible and highly probable that the voltage regulators (pretty sensitive to overheating) are now unstable and there's too much fluctuation in the voltages getting to the mobo, etc. I'd replace it. They're cheap enough. Then use your winders cd and do a repair install. |
|
Quoted:
Yank drive.. Pull all your data.. then format and reinstall windows. that is one hours worth of work... Troubleshooting some wacked out BSOD will take much longer. I'd be inclined to agree. Plug your HD into another computer as a secondary, pull all your data that you can, then wipe that bad boy and start again... |
|
That fan could've been running slow for weeks prior and you'd never have a clue.
Heat is bad for electronics (duh) It's quite possible and highly probable that the voltage regulators (pretty sensitive to overheating) are now unstable and there's too much fluctuation in the voltages getting to the mobo, etc. I'd replace it. They're cheap enough. Then use your winders cd and do a repair install Entirely possible, but I've got around 6 fans throughout this beast, so even if it had seized the heat retention should've been pretty minimal. Won't rule it out, though. |
|
Quoted:
That fan could've been running slow for weeks prior and you'd never have a clue.
Heat is bad for electronics (duh) It's quite possible and highly probable that the voltage regulators (pretty sensitive to overheating) are now unstable and there's too much fluctuation in the voltages getting to the mobo, etc. I'd replace it. They're cheap enough. Then use your winders cd and do a repair install Entirely possible, but I've got around 6 fans throughout this beast, so even if it had seized the heat retention should've been pretty minimal. Won't rule it out, though. Make sure you boot into the recovery console and run the chkdisk command I mented in my post. It will take you 10 minutes to get this started, it's worth trying before you start taking drastic measures. |
|
Quoted:
Quoted:
That fan could've been running slow for weeks prior and you'd never have a clue.
Heat is bad for electronics (duh) It's quite possible and highly probable that the voltage regulators (pretty sensitive to overheating) are now unstable and there's too much fluctuation in the voltages getting to the mobo, etc. I'd replace it. They're cheap enough. Then use your winders cd and do a repair install Entirely possible, but I've got around 6 fans throughout this beast, so even if it had seized the heat retention should've been pretty minimal. Won't rule it out, though. Make sure you boot into the recovery console and run the chkdisk command I mented in my post. It will take you 10 minutes to get this started, it's worth trying before you start taking drastic measures. I'll go get it started now. |
|
Quoted:
Boot off the windows xp CD. Choose the "repair" option, it will load a command prompt window(recovery console). At the recovery console type in chkdsk /f /r This will scan your drive and fix the sector that went bad when you abruptly shut it off. I just fixed a computer with the same issue yesterday with this method. Good luck. Follow this article if you want all the info on what to do next. I tried it with a space before each slash and it said "parameter is not valid" then tried with no spaces and got "command not recognized".... |
|
Soopa Sweeeet! Ran chkdsk c: and it repaired 3 files, rebooted and up came windows. Restarted, chkdsk auto ran and fixed 3 or four corrupt files and I appear to be good to go. i am posting this from my desktop.
talk about an unpuckering! ETA Thanks for the help guys!!!! |
|
Quoted:
Soopa Sweeeet! Ran chkdsk c: and it repaired 3 files, rebooted and up came windows. Restarted, chkdsk auto ran and fixed 3 or four corrupt files and I appear to be good to go. i am posting this from my desktop. talk about an unpuckering! ETA Thanks for the help guys!!!! Glad I could help. I scored major points with my Wife's boss on 7am Monday morning doing the exact same thing. |
|
Quoted:
Quoted:
That fan could've been running slow for weeks prior and you'd never have a clue.
Heat is bad for electronics (duh) It's quite possible and highly probable that the voltage regulators (pretty sensitive to overheating) are now unstable and there's too much fluctuation in the voltages getting to the mobo, etc. I'd replace it. They're cheap enough. Then use your winders cd and do a repair install Entirely possible, but I've got around 6 fans throughout this beast, so even if it had seized the heat retention should've been pretty minimal. Won't rule it out, though. Make sure you boot into the recovery console and run the chkdisk command I mented in my post. It will take you 10 minutes to get this started, it's worth trying before you start taking drastic measures. Good call for sure. |