Please register or login. There are 2 registered and 1311 anonymous users currently online. Current bandwidth usage: 1690.34 kbit/s November 23 - 07:03am EST 
Hardware Analysis
      
Forums Product Prices
  Contents 
 
 

  Latest Topics 
 

More >>
 

    
 
 

  You Are Here: 
 
/ Forums / Windows XP, 2000, 98 /
 

  Windows XP freezes at mup.sys, how do I fix it? 
 
 Author 
 Date Written 
 Tools 
Continue Reading on Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, Next >>
Jim Runkey Aug 26, 2006, 12:56am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Jennifer, in the BIOS there should be an option somewhere that says something like "On system halt," or "On fatal error," or "On system error," or something similar to that, and you will have a choice of multiple settings for that. Right now, it is set to "Restart" or "Reboot" or something similar. You need to change the setting to "Halt" or "Stop" or whatever choice will make the system NOT reboot when it encounters a fatal error (blue screen).

When you make that change in the BIOS, and then reboot, it will get to the point where the blue screen appears, and this time it will sit there until you turn the machine off or press the RESET button. That will give you time to read what the screen says, and write down the error message and the error number(s).

At that point, my best advice would be to search Google for the error number(s), and see if you can find some pages that explain the problem and how to fix it.

Good luck,
Jim

Want to enjoy less advertisements and more features? Click here to become a Hardware Analysis registered user.
Jennifer Rombrount Aug 26, 2006, 02:11am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Thank you for the advice, Jim.

I looked around the BIOS and I found a similar description called "Halt on --> All Errors/No Errors/All but Keyboard/etc." It was the only thing that remotely fits your description, so I gave it a shot. Unfortunately, it still gives me that infinite loop, how disappointing.

All this happened after I downloaded the Windows updates, so I'm really not sure what's going on, since the system was working fine before. (There was a similar issue in that I had the BSOD whenever I shut down my PC after exiting the Bitcomet program, but after I updated to the latest, there were no more problems. I'm not sure if it relates to this though.)

Chris McCreery Aug 30, 2006, 03:32pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Hey everyone,

I just got my comp back from the shop where I got my mobo and cpu installed into a new case. I took my SATA drive from my old computer and put it into the new one (its a 160GB SATA HD, though I'm not sure what brand). I reformatted it and installed Windows XP Pro on it, but when it boots and gets to the Windows XP screen (the one where the blue bars go accross to show that its loading) the screen goes dark, to where I can see a faint image of the Windows XP Pro loading screen, but never actually makes it past that...instead it just freezes. I can boot to safe mode on the computer, and it hasn't frozen on me in safe mode.

I'm using 2 cd drives, 1GB of DDR2SDRAM, an Asus M2NPV-VM mobo, and an AMD 64 3500+ CPU. Does anyone have any ideas as to how I can repair the issue? Thanks.

Mr MupSyset Sep 01, 2006, 07:33am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
I had the old Mup.Sys error four weeks ago and I'm still not getting anywhere fast in trying to fix it.

I've disconnected everything and done everything people have suggested on here - the mouse, the printer, the CD Rom drive, the DVD drive, the Zip drive, all the USB connections, all the cards, fiddling with the BIOS, replacing the battery - and i'm still sticking after it's loaded up Mup.Sys.

It's been a long time since I knew anything about computers, so it was a bit of a steep learning curve getting this far. Then I tried the recovery disk as I thought it might be the hard drive... this was okay until it went to 'repair' and asked for my administrator password for the computer. Having this password was news to me, and having exhausted all my usual passwords, none of them worked. So that wasn't very good... incidentally, if anyone knows how the hell I can find that out while being unable to get into Windows XP, I'd like to know!

Fortunately I have access to another (much slower) computer, so I tried putting the hard drive in there. I ran chkdisk and it reported no errors, so I thought I'd backup my vital files... except of course I couldn't, because access was denied on the folder! This was most upsetting... however, a search on here has offered some solutions and I'll try them at a later date.

However, this isn't helping me sort the problem. The computer had been locking on the Windows logo screen intermittently for quite a while, but it always worked after a reboot. But this one time it just locked up completely while I was on the desktop... and I haven't been allowed in since.

I would like to point out also at this point that my rig is now four years old, so I was thinking maybe the motherboard has just given up? Or the CPU? What about the power supply?

What does anyone suggest? Bearing in mind I've already exhausted my knowledge of computers!

Any advice would be appreciated.

Tom Burgmann Sep 02, 2006, 04:48pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
I had an IP conflict as my daughter returned from university and plugged in her laptop computer.
Unfortunately, my system which had been fine would not boot past the mup.sys screen.
That is how I ended up here trying to resolve the problem.
Hard drive scans using chkdsk had no solution when I booted to Safe Mode.
Finally Safe mode with networking showed the IP conflict.
Fixed the IP conflict and everything resolved to normal
I suspect that the Window XP WGA update "spyware" may have been involved.
Does anyone else have a similar story? Or am I just paranoid about the WGA update?

Hopefully this helps someone.

Chris McCreery Sep 02, 2006, 08:21pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Well, to be honest, I think you're just paranoid. Chances are the conflict had something to do with your own settings, as when I lived with my parents I had the same problem. We had 2 routers, one of which allowed for wireless connections. So when I had LAN parties my dad would have a IP conflict in the morning because of us being connected to it. Its just a matter of fixing your settings, because when my friends and I disabled our wireless connections it fixed the problem.

Tom Burgmann Sep 03, 2006, 01:48pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys Is WGA involved?
Fair enough - The simplest explanation is usually the most likely.
My concern with the Window Genuine Advantage (WGA) update is that it is reportedly designed to report
to the MS servers with every boot of windows XP. Hence an IP conflict prevents this login to MS.
Is it possible that this causes the system to properly function in safe mode but hang in normal?
I have not had time to replace the KB905474 update which causes this notification process to launch.
PS: I do have a legitimate copy of XP

Chris McCreery Sep 03, 2006, 02:33pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
I suppose its possible, but in XP you can boot to safe mode with networking. You should try that to see if your system hangs up again. If it does hang up, its certainly possible that the WGA crap is the problem.

Jim Runkey Sep 04, 2006, 08:50pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
My concern with the Window Genuine Advantage (WGA) update is that it is reportedly designed to report to the MS servers with every boot of windows XP. Hence an IP conflict prevents this login to MS.
Is it possible that this causes the system to properly function in safe mode but hang in normal?

If you're suggesting that MS is requiring your system to "call home" and verify it's legit before allowing a successful boot, you're being way too paranoid, and I can prove it:

Think of grandma jones, who boots up her machine to play solitaire occasionally. Every once in a while, she'll dial up to her ISP and check her email. If XP required a "call home" before it would even boot, how would poor grandma ever get far enough to dial up her ISP? She'd never even be able to play solitaire!

Now, maybe the hundreds of thousands of dial-up users are all offline now, and we don't know it because not one of them has figured out how to get their machine to boot so they can send an email to alert the rest of us. But the same thing would be happening to the millions of laptop users who try to boot up in a location with no network connectivity.

So it's silly to think XP would need to "call home" to validate itself every time prior to completing bootup. If that were the case, millions of machines would suddenly stop working, which would be front-page headline news all over the world, and there'd be a backlash like you wouldn't believe.

You've just got a configuration problem. There's no MS conspiracy at work here.

Tom Burgmann Sep 04, 2006, 10:07pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys Is WGA involved?
Please note item 2 below
" 2. Transmits data to a central computer. The WGA Validation Tool contacts a Microsoft server every time a PC is booted up and every 24 hours after that"


From: Brian Livingston [mailto:Editor@WindowsSecrets.com]
Sent: Thursday, June 15, 2006 6:04 PM
Subject: Genuine Advantage is Microsoft spyware [Newsletter Comp Version]

TOP STORY

Genuine Advantage is Microsoft spyware

By Brian Livingston

Windows Genuine Advantage — the controversial program Microsoft auto-installed as a "critical security update" on many PCs starting on Apr. 25 — not only causes problems for many users but has now been proven to send personally identifiable information back to Redmond every 24 hours.

This behavior clearly fits any plausible definition of "spyware." Some tech writers have said categorizing WGA as spyware is arguable. But I have no hesitation in calling the program a security nightmare that Microsoft should never have distributed in its present form.

In my May 25 newsletter, I called Microsoft's WGA download a "severe blunder." It causes serious problems for some legitimate Windows users and was sprung on customers with no notice other than a press release the day before.

No PC-using company that values security and reliability can allow a program like WGA to send data to a distant server, download additional software, morph its behavior, or remotely change the functionality of Windows (as I describe below). I don't believe individuals should put up with this, either.

Today, I'll explain the problems and let you know what you can do to fix them.

If the spyware label fits, wear it

In a statement released on June 8, Microsoft officially denies that WGA is spyware. Let's settle this question right off the bat so we can quickly move on to more important things.

Microsoft's denial is based on its own definition of spyware:

"Broadly speaking, spyware is deceptive software that is installed on a user's computer without the user's consent and has some malicious purpose. WGA is installed with the consent of the user and seeks only to notify the user if a proper license is not in place. WGA is not spyware."
This is patently absurd. Many spyware programs, such as peer-to-peer file sharing applications, are knowingly installed with the user's consent. The user downloads the software to get music, a screen saver, or whatever other benefit is promised.

What makes a program spyware, among other things, is that it operates in ways that aren't clearly disclosed before installation and it reports data back to a central server. Furthermore, this activity needn't be malicious. Many spyware programs do nothing more than serving up targeted advertising or tracking anonymous marketing behavior. If a user wants such tracking functions, they might be fine. But if the user wasn't clearly made aware of this, whether or not such software has a malicious purpose, it's still spyware.

The majority of published definitions of spyware focus the fact on that a program quietly gathers and transmits data. For example, here's an excerpt from the first definition returned by Google when define spyware is entered:

"Any software that covertly gathers user information through the user's Internet connection without his or her knowledge, usually for advertising purposes."
To help you understand the latest revelations about Windows Genuine Advantage's behaviors, let's walk through the latest facts that have been discovered about WGA.

What Genuine Advantage actually does

What we've found about WGA fits neatly into four behaviors that are typical of all spyware:

1. Lack of disclosure before installation. Windows users in the affected countries (U.S., U.K., Australia, etc.) who had Automatic Updates set to "auto-install" received WGA without user action, as though it was a critical security update — which it clearly was not. Even those users who ran Windows Update or Microsoft Update manually, however, were misinformed about what WGA would do. In 17 pages of screen shots, ZDNet blogger David Berlind demonstrates this, concluding:

"I was not asked for consent when the WGA Validation Tool — the one that, like spyware, phones home — installed itself. In fact, as can be seen from this screenshot which immediately preceded the automatic download and installation of the WGA Validation Tool, I could easily argue that I was misled into thinking I was going to download and install something else when in fact, I was downloading and installing, without my consent, software that apparently phones home."
A separate WGA Notification Tool is also downloaded. This program does not contact Microsoft's server, but merely displays warnings on a user's PC if a Genuine Advantage test is failed for whatever reason. After clicking several links in the manual download process, Berlind found only a vague explanation of WGA through what he calls a "circuitous route."

2. Transmits data to a central computer. The WGA Validation Tool contacts a Microsoft server every time a PC is booted up and every 24 hours after that. (Some of the earliest alarms about this were sounded by Lauren Weinstein, a co-founder of People for Internet Responsibility, in postings June 5 through 13.) WGA's "phone home" events, like all Internet packets, contain the IP address of the affected PC and the date and time, indicating when it booted up or had run for 24 hours. In addition, Microsoft's WGA director, David Lazar, told the Associated Press in a June 7 interview that the program also:

"...gathers information such as the computer's manufacturer and the language and locale it is set for."
This is enough data to easily identify individual PCs. And, of course, WGA can be modified remotely to collect additional information (as explained in point 3).

3. Downloads other software and morphs itself. WGA's daily contact with Microsoft's servers is specifically designed to allow the company to download new instructions. According to Microsoft's June 8 statement and Lazar's interview, this includes:

• Changing how often WGA contacts Microsoft's servers;
• Disabling features of WGA or disabling the WGA software entirely;
• Adding to the license keys that WGA treats as invalid; etc.

4. Cannot easily be uninstalled. No entry appears in the Add/Remove Software control panel for patches 892130 or 905474 — the Validation Tool and the Notification Tool. If you manually delete WGA's executable file, Windows regenerates it. (I'll discuss remedies for this below.)

Perhaps most shocking is a trait of WGA that most other spyware doesn't suffer from. WGA is beta software that even Microsoft doesn't consider ready for release.

Section 4 of the WGA Validation Tool EULA (End User License Agreement) states:

"4. PRE-RELEASE SOFTWARE. This software is a pre-release version. It may not work the way a final version of the software will. We may change it for the final, commercial version. We also may not release a commercial version."
Microsoft's June 8 statement confirms this by repeatedly calling the WGA rollout a "pilot program" or a "pilot version." Of course, "pre-release software" and "pilot version" mean exactly the same thing — beta.

At least that explains some of the many problems that Windows users are having with WGA.

Problems with WGA — and some solutions

It's important to remember that Windows Genuine Advantage is not an omnipotent, do-everything program. Its stated goals are simple. If an instance of Windows doesn't seem to have a valid license, (1) display notices to the user and (2) prevent any updates being downloaded from Microsoft.com except security upgrades that are rated "Critical."

Despite these limited tasks, WGA seems to cause a wide variety of headaches. Since my May 25 article appeared, I've collected reports from the field and from readers describing the following categories of issues:

1. False positives of legitimate copies of Windows. Numerous users report that WGA refuses to validate licensed copies of Windows that are unquestionably genuine. At Microsoft's official online forum called WGA Validation Problems, many people report problems even with packaged copies of Windows that were purchased directly from Microsoft.

2. No updates at all unless WGA is accepted. Although a WGA failure is supposed to only prevent affected users from downloading nonsecurity updates, many Windows Secrets readers report that legitimate copies of Windows refuse to display any updates except the WGA download — until the Validation and Notification Tools are installed. Phillip "Skip" Lehrfeld writes:

"I chose to download the Windows Genuine Advantage Validation Tool (KB 892130) on March 6, 2006. I followed this with Windows Genuine Advantage Notification (KB 905474) on May 4, 2006.

"On June 2, 2006, I was checking the Update site as I was informed that there was a new Critical update to be downloaded. I checked the site and it told me I could not get my update as I was missing a critical tool. I checked it out and it told me I was missing the Windows Genuine Advantage Validation Tool. I checked my history and sure enough I had installed it on March 6.

"OK, I will bite, and I downloaded it again. Yes, the number was KB 892130, the same as before. Then it wanted me to install the second one again. I installed Windows Genuine Advantage Notification, KB 905474, for the second time. Having installed the two for the second time, there were no new updates to install. Those were the updates to be installed. ...

"After the reinstallation, I checked the history section of the site and now I have the two updates installed twice successfully.

"I have an authorized copy of Windows XP and had no problems with the above events; but it leaves me to wonder what is going on and are they now doing something else to my system without revealing what is going on."

The redundant WGA install messages are probably caused by changed code that Microsoft wished to download to defeat some workarounds that disabled WGA.

Numerous other readers say that Microsoft's update site also reported to them that there were no patches except WGA, although important updates were, in fact, available.

3. "Notify only" options disabled. We have some reports that the "notify only" options in Automatic Updates are greyed out and can't be selected. G. Allen Taylor, M.D., writes:

"With regard to the OS updates, which I have so faithfully and obediently installed, I now suspect that one of them has 'grayed out' the Options menu in Windows Update on both my computers. "While formerly I could choose to automatically or manually download and/or install the periodic updates, I now have no choice on either of my computers. Whether I want them or not, all updates are downloaded when I'm online and installed then or the next time I reboot."
Dr. Taylor offers a fix, which involves the fact that a Group Policy was somehow enabled that prevents any option other than auto-updates.

The solution requires a change to Group Policy or the Registry. The procedures are described at the Windows XP MVPs site.

4. Reinstalls from valid CDs fail the Genuine Advantage test. By far the most serious side-effect of WGA is that it doesn't validate instances of Windows that are reinstalled, even when a genuine CD-ROM from a major computer maker is used. Lauren Weinstein writes:

"It appears that it is exceedingly common for repair operations to reinstall based on "cloned" or otherwise duplicated copies of the Microsoft OS, rather than try to restore or reauthenticate based on the original users' OS serial numbers or authentication codes. Original restore disks and key information cards/labels are frequently missing, making it difficult to duplicate the original authentication environment."
I've seen reports of this on Microsoft's own forum involving such cases as Best Buy's Geek Squad reinstalling Windows with the user's original, licensed Dell CD-ROM.

Despite all of the reported problems, Microsoft officials aren't very forthcoming on the subject of WGA. On June 9, I asked to interview David Lazar in Redmond and submitted a few questions in writing. Five days later, a spokesman replied, "Unfortunately, we will not be able to participate in this opportunity."

Many Windows users seem to be in denial that WGA could be spyware, because Microsoft is such a big, well-known company. Unfortunately, that was what people thought of the Sony BMG recording label before it started distributing music CDs last year with rootkit software that infected PCs.

I don't feel that Microsoft or Sony BMG are evil incarnate. But we must recognize that Microsoft is now just one more spyware distributor among the many we have to watch out for.

How to make sure WGA doesn't bite you

It's important not to panic about Windows Genuine Advantage. At this point, its worst side-effect is interfering with the normal patch process — but far more common is that it merely displays annoying warning messages for no apparent reason.

If you've already allowed WGA to install, I can't recommend that you try to uninstall it. That's because Microsoft has made a passing grade on Genuine Advantage a requirement for almost every kind of download you might want from Redmond. Without passing a Genuine Advantage checkup, most Windows users now can't get Internet Explorer beta 7, for example, although you might not care. But you just might have a good reason to install a newer, more secure version of Windows Media Player or any of dozens of other official updates.

If you insist on trying to uninstall WGA, the My Digital Life site has posted no fewer than 15 proposed hacks that attempt to circumvent Microsoft's anti-uninstall measures. Most of these methods no longer work, due to recent Microsoft code changes. Even if you did disable the app, it's pointless to have done so if you ever need to download any Microsoft widget some day that requires WGA. Again, I don't recommend that you bother trying to remove WGA if it's installed.

Instead, I strongly advise that you simply suppress WGA's negative side-effects:

Step 1. Stop the misleading installation of possibly unwanted programs. If you really don't need to download anything from Microsoft for a while, set the Automatic Updates control panel to Notify but don't download or install. When you're notified of new security updates, first read the free and paid versions of the Windows Secrets Newsletter for our reviews. Then manually run Microsoft Update and select only the patches that have no reported conflicts.

If Microsoft Update subsequently refuses to download patches you need, go ahead and accept the WGA installs, then take steps 2 and 3. Be aware that some programs, such as Microsoft's Windows Defender (formerly MS Antispyware Beta), won't update themselves unless Windows' auto-update is on. (Thanks to reader Raymond Combs for his research into this.)

Step 2. Disable WGA's incessant notifications. If WGA guesses, correctly or incorrectly, that your copy of Windows is unlicensed, it displays a warning at least once a day for 14 days, then once an hour after that. Fortunately, Microsoft has made it easy to disable all such warnings. Right-click the WGA logo in the system tray, then select Change notification settings. Turn off the display of notifications, click Save Settings, select I understand, and finally click Yes I'm Sure. Reboot the PC. The WGA logo will remain in the tray but notifications will no longer appear. The notices will come back, however, if you happen to install a future version of WGA from Microsoft.

Step 3. Prevent WGA from phoning home to Microsoft servers. The WGA process that calls out to its remote masters can be blocked by 2-way software firewalls such as ZoneAlarm and McAfee. To do so, simply deny the connection when your firewall pops up an alert about Windows Genuine Advantage trying to use the Internet. Alternately, hard-code a denial via the firewall's user interface. No ill effects of preventing WGA from establishing a connection have been reported.

This story has legs

I'm afraid I'll have more tales to tell in future weeks as the fallout expands. Microsoft executives seem totally oblivious to how much public trust they've squandered by installing WGA in a sneaky way. Microsoft has repeatedly assured users that Automatic Updates would only be used to download critical security fixes. "Delivering security updates right to your computer automatically," they said.

Abusing PC users' need for security patches is a betrayal that Microsoft can ill afford. Whoever the marketing geniuses are who've seized Microsoft's security infrastructure to push out spyware, they need to be fired.

I'm not holding my breath waiting for that. Instead, I'm researching a totally independent way for Windows users to keep their PCs tuned without depending on Microsoft Update at all. Stay tuned. END

Apologies for the long post. Here is the source of my original question.
Tom


Jim Runkey Sep 04, 2006, 10:35pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Yes, Tom. I'm very familiar with all that--it was big news months ago. The hubbub has died down quite a bit since then. The hubbub was mostly not about what WGA was actually doing, but rather the way that MS delivered WGA to the masses under the guise of a "critical security update" when in reality is was strictly an anti-piracy tool.

I'm not arguing that the software didn't tag up with MS on a daily basis (though MS has since changed the WGA behavior based on the public outcry so that it doesn't do that anymore).

But "WGA calls home" is COMPLETELY DIFFERENT from "WGA will cause your machine to malfunction if it can't call home". You asked if the latter could be the cause for your problem. I'm telling you why that can't be the case.

My point is that if the latter were true, you and a couple of tens of millions of users who don't have always-on Internet access would have machines that don't boot. If that ever happens, it will be the #1 story in every media outlet for days. Business productivity would be affected to a level that you could see it in the economy. The *global* economy!

That hasn't happened. Ergo, WGA is not causing machines to fail to boot if it can't call home. End of story.

(BTW, next time please just post a link, rather than an entire article. This thread it tough enough to wade through as it is!)

leon van hees Sep 10, 2006, 05:39am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Hi,

so I have read the whole 27 pages, and 4 cups of coffee later I still don't have the sollution to my problem ;)

Here's my story:

I thought about upgrading my old P4 2.4 gig rig to a conroe system, so I decided to hand the old one over to my parents, who are using an old atlon 700. Basically I am upgrading my whole pc, except for the HD's and the dvd burner, so I basically only took those out and left the rest the same... So now I am here at my parents,typing on the reassembled atlon 700, because somehow I can not get my system to work with their HD !!

The HD is obviously fine, since it works in the old system, but somehow it won't go past mup.sys on the p4 system... It won't even start in any of the safe modes, because I get the same deal...

I don't have a xp cd, because I left that at home, oh did I mention home is California and my parents live in the Netherlands, so I took the PC with me in the suitcase, put a bunch of socks and soft stuff in there to keep the HW from damaging and the pc was in a hardshell suitcase enclosed by sweaters and such...

Could it possibly be HW damage afetr all? I mean I can get into the BIOS, so that to me seams to mean that the MB is OK, I see stuff on my screen, that means the videocard is ok, and it find the memory on bootup, so that can't really be damaged either... If i only had my own HD, so I could verify that the system is OK ...

Anyways i just thought I'd trow in my slightly different mup.sys topic, to see if any of you guru's out there might be able to shine a light on it...

Thanks!

Leon

Jim Runkey Sep 10, 2006, 06:16am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
so I have read the whole 27 pages, and 4 cups of coffee later I still don't have the sollution to my problem ;) ... Anyways i just thought I'd trow in my slightly different mup.sys topic, to see if any of you guru's out there might be able to shine a light on it...

Leon, this is not a slightly different topic--there are several posts in this thread that directly address your question. You probably don't have any damaged hardware, but you're going to need an XP disk, because you're going to need to do a "repair install".

Bottom line: You can't just yank a WinXP boot harddrive out of a working computer and stick it into a machine with different mobo/CPU and expect it to work. This is a known behavior of WinXP--see the MS Knowledge Base article on the subject, here: http://tinyurl.com/j9u7 .

Try starting on p. 22, second post (Apr 22, 2006, 09:41 AM), and go from there.

Good luck,
Jim

stuart kahler Sep 16, 2006, 08:04pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
First post...
I was browsing for this same problem and found the solution that worked for me. Apparently there's no actual problem with mup.sys. It just happens to be the last file processed before starting into windows. My PSU had gone bad and could handle the load of processing the initialization files, but not switching into the desktop. Therefore I got a lockup right after mup.sys. Swapping the PSU out cleared the problem.

BTW, I was inspired to check the PSU after reading tons of articles by people who had swapped vid, mem, hd, lan, reformat with no success, but who never mentioned PSU or mobo. Also, the whole system started getting flaky after a major lightning storm, and finally quit booting at all a few weeks later.

bryan Wheeler Sep 17, 2006, 01:37am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Ok time for me to addin.

I am having the same issue. I swapped my two hard drives and re-installed windows on one but the other it is stopping at MUP.sys. I also have tried many different things and to no avail. I think the last one with the SUP was pretty close. I am pretty sure that it has something to do with xp and hardware. It also seems to be happening when people are doing swaps.

So anywayz back to what I have done. I have finally gone through and removed anything that is not needed. I have two hard drives. One is 160 and has the operating system on it. It works just fine and one machine than bring it to the other and it doesn't the second is an 80gb and it is blank. Whenever I plug in the 80 it won't go past the intro screen, when I plug in the 160 it goes all the way to the screen that says system didn't boot last time what would you like to do or by safe mode till MUP.

Ya I just can't figure out how to get it past this point. I went and got a power supply from a working machine and plugged it in and the computer still didn't work. And lastly I was just curios on the load level if it was the PSU so I loaded KNOPPIX (Linux os by CD only (hint: no hard drive needed)) and that worked just fine.

I really am stuck on this one.
Thanks so much for any help in advance
Bryan Wheeler

bryan Wheeler Sep 17, 2006, 01:40am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
oops sorry a little more information:

So I am trying to get the operating system on the 80gb and no matter what ide, power, jumper confige, quantity of items attached, etc I cannot get the system to boot past the Original boot (information page) with the 80gb.

thanks again,
Bryan Wheeler

Jim Runkey Sep 17, 2006, 03:23am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
I have two hard drives. One is 160 and has the operating system on it. It works just fine and one machine than bring it to the other and it doesn't...
Again, this is a known behavior with XP. You can't install the OS on one computer, then yank the hard drive and put it in a computer with different mobo/CPU, and expect it to boot. See my last post, just two posts before yours, Bryan.

...the second is an 80gb and it is blank. Whenever I plug in the 80 it won't go past the intro screen, when I plug in the 160 it goes all the way to the screen that says system didn't boot last time what would you like to do or by safe mode till MUP.
Okay, this may be a dumb question, but when you plug in the blank 80gb disk, do you have the XP install CD in a CD drive? In the BIOS, do you have the machine set to boot off the CD before trying to boot off any hard drive?

When you say it worked fine with KNOPPIX, are you saying that in the exact same hardware config, putting the KNOPPIX CD in the drive and hitting the reset button results in a good Linux boot, but then swapping the KNOPPIX disc for the XP install disc results in a hang at the end of the BIOS power-on self test screen?

Rocketman DC Sep 24, 2006, 08:58pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
what does mup do?
note i put the hd in another machine as slave and renamed mup.sys expanded mup.sy_ to mup.sys and put it where it belongrd. then did a file compare of mup.syy to mup.sys it says they are the same . good old ms. files is the same but it don't work. argh.


Are any of your peripherals acting funny? My system wasn't recognizing a CD-ROM drive (and then I had the mup.sys hang). When I took out the problem CD-ROM, my mup.sys problem disappeared! Someone, some where said to unplug and replug in drives. I thought that sounded weird, but when I removed and replaced my CD-R0M drive, my mup.sys problem disappeared. I think it hangs on mup.sys when a preripheral has a plug and play problem.

bryan Wheeler Sep 25, 2006, 06:42am EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
Well so as to my post. Yes I knew you couldn't do the swap thing, but I've actually had it work twice before. But my system is now working. When I swapped that 80gb into another computer it blue screened. So I bought a new hard drive plugged it in and it works like a charm now. So with my current studies on this case.

Test: Hard Drive, Power Supply, Newly added hardware, Check video card. Now if that doesn't work remove everything except what is needed to boot to windows. If that doesn't work your screwed :-)

good luck in your endevors,
Bryan Wheeler

John K Sep 25, 2006, 09:00pm EDT Reply - Quote - Report Abuse
Private Message - Add to Buddy List  
>> Re: Windows xp freezes at mup.sys
I have this problem to, i have a laptop which has Two Hard-Drives on it, If i reinstall windows on the windows harddrive will it keep all my other files on my other Hard-Drive?

John


Write a Reply >>

Continue Reading on Page: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, Next >>

 

    
 
 

  Topic Tools 
 
RSS UpdatesRSS Updates
 

  Related Articles 
 
 

  Newsletter 
 
A weekly newsletter featuring an editorial and a roundup of the latest articles, news and other interesting topics.

Please enter your email address below and click Subscribe.