I'd never seen this before trying to set up a RAID stripe on a Shuttle SN45G V3. I can install Win XP one one drive no problem but as soon as I try to install on a RAID array I either get blue screen or a hang at MUP.SYS. I've tried shuttle support (which is 100% useless) and the laterst Nforce RAID drivers from Nvidia (made it worse)

Any ideas

Rod

Nudge:

Your problem is, as you suspect, related to the different mobo chipset and related drivers. I am about to go through that process myself in a few days, and have been doing research to figure out the best way to attack it. I've seen several sites that recommend an "upgrade in place" install. This site has the most user-friendly walkthrough of how to do that: http://www.theeldergeek.com/replace_motherboard.htm

Jim

Hi guys,
I have recently expirenced the same problem as you describe on my home computer.
I have no idea what the cuase was. My last boot was successfull, my system seemed completely stable, and on my last windows session i installed no new hardware, software, or other. So when I booted my computer in the mornig to this problem I was completely shocked and left scratching my head.
Im my case, i can guarentee that it is not a vcard error, nor is it a HDD failure, or hardware failure of any sort. I know my computer VERY well, and anything of that nature I would be allerted to immediatly.
So this is what my morning has been like so far.
Created a MS Dos boot disk and booted into compand prompt, only to find that my HDD drive is no longer there!!! No well thats not true really, the HDD drive is there, it has just been relabled from C: and D: drive, and now my USB card is the c: drive and my HDD, well.. I havnt found it yet. I removed the UBS disk, and pain persisted.
I read in the previous posts, to enter system recovery and disable mup.sys, no such luck because my registry doesnt exist anymore and needs to be rebuilt... so it looks like another format for me.... YAY!!!! ---> not
- Thats my thought for the day. And remember, take care of yourselves, and your computers. Goodbye

For what it's worth, I finally figured out why my hard drives were causing the hang after mup.sys: The 80-pin IDE cable was bad. How'd it go bad? I dunno. It's not like I was in there yanking it around or anything.

Bottom line: You can know your hardware like the back of your hand...and not really know your hardware. I'd have never guessed in a million years that my IDE cable was bad. I only managed to figure it out by accident while I was moving the drives (and cables) to a new machine.

Good luck to everyone searching for their gremlins. Hope you find 'em and wipe 'em out!

Jim

I just got this behavior today after installing a new SATA CDROM drive connected to the nForce SATA0. (It did not happen when connecting to the Si3114 SATA chip.) I was able to recover by disabling all SATA support in the BIOS (which I wasn't using at all before this new drive).

I should probably add that my motherboard is a new Gigabyte GA-K8NXP-SLI and the new drive is the Plextor PX-716SA (DVD/CD-RW). Also, I just realized I only read the first of many pages of discussion in this thread. Apologies in advance for any redundancies. (I'm new from a Google search.)

In case anyone needs the information, this issue was resolved for me by rolling back to the original Microsoft drivers, replacing Device Manager / IDE ATA/ATAPI controllers / NVIDIA CK804 ADMA Controller (v2.7). To obtain access to the driver at all, I had to unplug the Plextor 716SA so I could boot with SATA support enabled in the BIOS.

Bottom line: The NVIDIA nForce4 driver for Windows XP does not provide compatible SATA support for the Plextor 716SA DVD/CD-RW drive (with or without its jumper installed).

ITS YOUR BIOS SETTINGS~!!!!!!!!!!!

forget the sys file- go into to bios and play around til you find a setting that makes it work. I am susopecting something to do with PCI or PnP

but I got it working and I am not getting paid any extra to find out why (maybe later)

I do not subscribe to your theory. Before I solved the problem by reverting to the default Windows-XP driver (as instructed by Plextor technical support, which was great, by the way), I tried every permutation of BIOS settings pertaining to the nForce SATA ports. There really were very few settings to try. If you have a specific recommendation, and there is an advantage in using it, I'll be happy to give it a try and report my results.

When NVIDIA gets around to debugging its driver, it would be nice to have a post here on what was wrong.

It just occurred to me that the poster before me could have been replying to a post earlier than mine. In that case, I would only say that the Windows XP boot seems to hange at Mup.sys when an I/O bus hangs for ANY reason. Just look over the many posts above to become convinced of this. While a BIOS error can certainly cause a hang, it can also be caused by many kinds of hardware failure and/or incompatibility.

I agree...there is nothing wrong with mup.sys if it shows it..That means it has loaded..i have the same problum and have been trying to figure out what is wrong with my system..See mup.sys is the last thing that loads before you get your welcome screen.That means that it can be many diffrent things that are going wrong exspecially if there is only one log in name and you go straight to your desktop during you boot up.. For me i know it's not hardwair or a bios problum..Easy way to check is take the hard drive out of the system you are working on put it in as a slave drive in enougher computer see if it works. You can even run it as a master drive and try to load the OS on a diffrent computer..You'll must likely get it to hang at the same spot..So if it helps stop focasing on mup.sys and look for other causes

Also just to add if you change you bios not to restart on a system error you might see that you get a stop:c000021a fatal system error and alot of time this relates to a hotfix update 890859. That's not always the case but has seemed to work for some. SO try uninstalling that update (ge hre to find out how http://windowsxp.mvps.org/spuninst.htm). It might work for you but you need your windows XP cd to get into the recovery console. For me i'm waiting to get that CD from the person i'm fixing the computer for so i don't know if it will work for me but it's worth the try if you have hit a dead end.

I recently repaired my parents' Celeron 1.7 Desktop unit with 256 MB ram running Windows XP Home encountered the same problem. I had to fix this pronto as this acts as the dial up gateway for the wifi lan.

Initial problems:
A. Freezes at mup.sys on safe boot up

B. Freezes at black boot up screen displaying Microsoft Windows on normal boot.

I surfed all the websites with this topic and tried all their recommendations with these results:
1. boot using winxp disc, select recovery mode and disable mup.sys --- boot up froze somewhere at another file
2. disabled usb in bios --- no effect
3. re-seated all the IDE cables and swapped IDE cables
4. My own test: removed hard disk, put it in an external usb2 enclosure and attached it to my WinXP Home laptop. Times like this I pat give myself credit for having an external 3.5" enclosure because it allowed me to attach the drive to m laptop and:
a. perform virus scanning --- no virus detected
b. do a scandisk of the drive--- no disk errors noted
c. copy mydocuments folder into my laptop
d. locate the file storage area of Outlook (dad's email program) and saved the folder containing his emails
e. copy folders containing mom's programs that could run simply by creating shortcuts to their exe files

Then I followed another post and followed other posts which suggested
5. copy mup.sys from another computer / win xp home CD --- no effect

I then reinstalled the hard disk into the desktop and tried other proposed solutions:
6. boot from XP boot disk and try to log into windows --- nothing happened
7. boot using winxp disc, select recovery mode and repair MBR --- nothing happened
8. boot using winxp disc, select recovery mode and repair boot sector --- was no longer able to boot up until black window boot up screen nor boot up on safe mode

After #8 I was stuck and so I had no choice but to Format the hard disk! There might have been other solutions but my frustrations were about a foot above my head. Anyhow I had backed up all the folders that I deemed as important and so Format hard disk I did.

After formatting, I installed XP, activated it. Then I returned all of the files and folders that I had copied to my laptop. YES!!!

Desktop PC was ok until 4 days later (today) it locked up again on the boot screen. It also locked up on mup.sys on safe boot. Is there no end to this?!!!

Then it hit me. I noticed that the black boot up screen of Windows was a bit dim so I was left with 2 choices: monitor is on the brink or PC power supply is on the brink. My rationale for suspecting the power supply unit is that when it begins to act up, the PC tends to do all sorts of crazy things. As for the monitor, the display of the boot up screen appeared dim.

Anyway, I got another monitor from another PC and tested it. Same effect: dim Windows screen; boots up but froze at mup.sys on safe mode. Conclusion: monitor is probably okay.

So I got my screwdriver and pulled out the power supply unit. It said 300 watt max. I put in its place a spare 400 watt max power supply unit. Boot up was uneventful. I was not convinced so I shut down the PC and repeated the bootup procedure... still uneventful. So far I have done boot-shutdown for 10 times and all have been uneventful. PC works fine and presently is acting as my outgoing dial up server (house has wifi lan but outgoing is a measly dial up PC hehe).

Sigh. If I trusted my instincts and swapped the power supply unit before trying #8 I probably would not have formatted the disk and lost other programs (whose installer discs got misplaced).
I would therefore highly recommend a power supply swap before trying a repair boot sector or even repair mbr. Oh well, "Stupid is as Stupid does" --Forrest Gump.

Addendum
Only problem I notice with that PC is occasionally when I try to dial out and it seems to freeze at opening port (prior to modem dialing out). When this happens even shutdown takes forever. So I told my dad that when he notices this he is better off pressing the powerbutton for 5 seconds to shutdown the PC. The succeeding bootup is uneventful and when dialing out the opening port returns to normal state (flashes for a second then dials out).

Cheers.

al

sorry double post

Al;

I had a post earlier about hardware recognition by the system board being slow and XP,s HAL finding the hardware that wasn't present when the system completed POST. Mine was easy though because I noticed the BIOS hardware collection on boot and the missing "old timing" CDROM. Fortunately I had a system board setting to force that IDE to an explicit CDROM (not AUTO) and the trouble cleared.

I do believe all these posts are relevant to hardware/flash and HAL because the fix always seems to be a hardware issue or a driver issue or something pertinent to the hardware itself.

Now your screen dimming problem. When my system booted if the screen presented an initial bright rolling ball the system failed to boot. If it was dim and slowly (2 sec) brightened it booted fine.

I'm really surprised MS hasn't come out with a statement on this mup+ thing (meaning beyond mup.sys). There's a lot of people having this problem.

I was talking about my wife's computer in the last post and since then have bought a de-celleron Compac/
HP. She had trouble booting on the old 10gig drive (the system with the aforementioned CDROM problem that I literally had to kickstart and decide to rebuild or buy new. That's the second PC I ever bought since the MS-DOS days. I'm still the slave IT here though. HA. HA. "Ink, paper, printer, Word, Excel, PowerPoint etc. Honey" No offense to the women on this.

Yup the boot screen starts out dim then becomes brighter in a normal boot up process.

What happened today was that it would freeze up while the boot up screen was still dim. At first I thought the videocard might be overheating so I shut off the PC for 1 1/2 hours but upon reboot,the same thing happened. That's when I started suspecting either the monitor or the power supply unit as a possible cause as the XP home re-install was barely 3 days old.


Wayne wrote:

Now your screen dimming problem. When my system booted if the screen presented an initial bright rolling ball the system failed to boot. If it was dim and slowly (2 sec) brightened it booted fine.

I have been reading this for about an hour and here is the order in which you should attempt to resolve the problem: Let me know where yours gets fixed.

· Remove any USB devices attached (very possible)
· Reset ESCD in your BIOS (very possible)
· Disable ACPI in the power management section of the BIOS (very possible)
· Reset BIOS (could'nt hurt)
· Disable MUP in recovery console. (MUP is not the problem, but try it if you want to, possible problems in the future, not fixing the real issue)
· Run chkdsk /p in recovery console. (this assumes that your hard drive could be bad)
· Move memory to another slot. (querky, not fixing the real problem)
· Move PCI cards out or in a different slot. (same as above)
· Bad CPU’s (most likely not, CPU's have a very low fault percentage)

I would recommend step 2 be "disconnect all IDE / SATA devices except for the boot device". In my case it was a bad IDE cable causing the hang, and replacing it with a new cable solved the problem, so this step should be included somewhere.

Jim

Yes, my problem was a hung SATA bus as well. It worked to disable the SATA controller chip in the BIOS, and it also worked to disconnect the disk drive.

UPDATED FIXES IN EASY ORDER:

>>· Change IDE, Serial ATA cables. (very possible)
>>· Remove any USB devices attach. (very possible)
>>· Reset ESCD in your BIOS. (very possible)
>>· Disable ACPI in the power management section of the BIOS (very possible)
>>· Reset BIOS (could'nt hurt)
>>· Disable MUP in recovery console. (MUP is not the problem, but try it if you want to, possible problems >>in the future, not fixing the real issue)
>>· Run chkdsk /p in recovery console. (this assumes that your hard drive could be bad)
>>· Move memory to another slot. (querky, not fixing the real problem)
>>· Move PCI cards out or in a different slot. (same as above)
>>· Bad CPU’s (most likely not, CPU's have a very low fault percentage)

FYI.... I removed my USB devices and it booted up perfect. I have not tested putting them back in.