crunk Posted July 17, 2008 Posted July 17, 2008 Hey guys, you all seem to be pretty computer savy so I thought I'd ask. My computer's pretty much fucked. I turn it on, and it loads up fine until i get to that windows loading bar.. it does a couple of laps on that then freezes. So I tried to run the computer in safe mode with networking, and it works fine... although it stalls for a good 45 seconds on a file called mup.sys So seeing that, I looked into it myself, googled around etc.. seems like a common problem.. but I'm not even sure if that is the problem? Anyone come across this or have any suggestions that won't involve wiping my computer? P.S. I can't find my windows cd, and i didn't previously backup any settings etc Quote
jitz Posted July 17, 2008 Posted July 17, 2008 The only real solution to the problem is format and start over. Nothing else will do jackshit. I assumed you've defragged, but even that will do very little if anything. Quote
Joe =/ Posted July 18, 2008 Posted July 18, 2008 http://www.aitechsolutions.net/mupdotsysXPhang.html So, What happens after we see the mup.sys driver load on a safe mode boot? The windows OS is looking in the registry, executing PnP (Plug and pray) and ACPI routines checking the components and resources found. It then starts these components possibly causing more draw on the power supply. Consider here the load of non-self-powered USB devices. If there are any unrecoverable problems here, that will cause the system to hang and it will look the same. - The system hangs during a safe mode boot after loading mup.sys! 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. Have you upgraded to any new hardware at all ? It might be useful sourcing a windows disc and then booting from the disc and selecting to repair windows - It's worth a shot. If that fails, try a different hard drive (i.e. a friends), and if there's no problems using the replacement hard drive you will be sure your own personal hard drive is the problem and the problem is not the result of other components within your computer (i.e. the list quoted mentions a power supply failure). I've read some user feedback on the problem on a website, and it seems that quite a few of the people said their power supply was the problem. Try replacing it if you are able to. Others fixed it via the following method; http://www.aitechsolutions.net/winxpnoboot.html Hope this helps ! - i'm sure you will be able to fix it, don't give up and re-format just yet. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.