re: Mup.sys but not at fault
Friday, November 5, 2004 at 3:20 am
Windows XP Annoyances Discussion Forum
Posted by Keith
(9 messages posted)
I got the dreaded reboot loop on my AMP XP1800 system about a week ago. I read most
but not all posts from this thread and tried some if not all possible solutions.
I was lucky and XP would start after a few restart loops. I checked the CMOS changes
suggested but found my system already had the settings suggested.
I tried a "repair" for XP but things just got worse, I tried a spare HDD and fresh
install of XP; No good started getting a blue screen crash/memory dump.
Installed Windows 98 onto the spare HDD, still crashed.
After changing out and testing all components I was left with the solution that the
motherboard (or cpu) was at fault.
I installed a new motherboard and set the CPU external frequency to 133.33MHz as
per the old motherboard. Still crashed. I then tried a Win98 install and got an
error that Microsofts Knowlage base suggested could be an incorrect CPU external
frequency. I set the motherboard frequency back to 100MHz. Things are now stable
and back to normal except....
My CPU is now running at 1150MHz instead of 1500MHz.
Conclusion;
This was a hardware fault caused by the CPU, although stable now it will probably
start failing again.
Good luck to anyone with the Mup.sys or reboot loop, this must just be a common symptom
from many varied faults.
Only systematic troubleshooting will find a solution although ideas given in this
thread certainly helped me.
Thanks to all
On Thursday, November 4, 2004 at 10:11 am, I. Polendo wrote:
>It took a while to read all messages. Anyway, same problem with me. I will try to
>keep this simple.
>
>The common factors I noticed:
>1. Most used AMD processors, but there are some Pentiums in there.
>2. Lot of people had this problem after connecting a device, be it pci, usb or 1394.
>3. Lots of people got around solving this issue by disabling the anpi (sp?) on the
>BIOS.
>4. Partial solutions involved disconnecting and reconnecting power, changing ram
>sticks to different slots, and disabling a controller which might have the ! sign
>on the hardware device, but eventually the problem came back.
>
>My situation:
>
>1. Bought a Compaq box, and installed same day a Tv tuner pci card, extra HD, 512
>MB of RAM.
>2. My PC started restarting at the beginning when it's loading XP.
>3. Called Compaq support and troubleshoot the problem to no avail solution. They
>suggested to take out the extra RAM that I bought and if the problem persisted to
>take the box to an authorized center.
>4. Started troubleshooting with the RAM, taking out the HD and PCI Tv card. Just
>when something appeared to be the fault of the problem , eventually the problem
came
>back.
>5. Managed to get into XP my disabling the anpi thing in the BIOS and noticed that
>my 1394 controller (managed by the motherboard) had the ! sign. I disabled it in
>Windows.
>6. No problems after that --- but then again this isn't supposed to be happening
>since I had to disable the 1394 for this conflict to stop.
>7. After reading all this posts I figured that the 1394 isn't supposed to be at
fault..
>it could have been anything from a pci card to a HD to a USB which could be causing
>the conflict.
>8. Unplugged the PC, took out the battery, changed the jumpers from the CMOS to
discharge
>the memory.
>9. Plugged back in and now my 1394 is recognized, without a conflict and without
>the restarting problem.
>
>Conclusion:
>I suggest to read the motherboard manual and look for instructions on how to clear
>the CMOS memory on your specific case. Do so and try.
>
>ps: it took me 2 months to fix this issue without the help from the manufacturer.
|
All messages in this thread [show all]
 |  | |  | re: Mup.sys but not at fault (Keith: Fri, Nov 5, 2004, 3:20 am) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|
