re: Mup.sys but not at fault
Thursday, November 4, 2004 at 10:11 am Windows XP Annoyances Discussion Forum
Posted by I. Polendo
(1 messages posted)
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 (I. Polendo: Thu, Nov 4, 2004, 10:11 am) |
| |
| |
| |
Return to the Windows XP Discussion Forum
|
|