![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
kevineugenius
[H]ard|Gawd
- Joined
- Dec 9, 2006
- Messages
- 1,415
On a computer at work, a guy was in his email and when he opened an attachment (the email was from me, so I'm fairly certain it was virus-free; I sent it to multiple people and only his computer had problems) the computer rebooted itself. However, it won't boot all the way up. In safe mode, it gets to mup.sys and will go no further. I researched mup.sys for a long while before running safe mode on an identical PC, only to find that mup.sys was the last file in the list and is probably not the problem. There is a stop error flashed for a split second before it reboots, but I can't read any of it.
If you run the XP cd bootable (tried restore and tried to install fresh), it will load the RAID drivers (kind of older system) and then get a stop error saying that viamraid.sys caused the problem. However, when you boot into safe mode, viamraid.sys is like 6-7 up the list before the end, so I doubt that's the problem. To be sure, I copied that file from the working PC to the broken one via floppy disk, and it made no changes at all. Chkdsk and a few other utilities I downloaded to scan the hard drive get to around 26% then freeze.
I tried to use that hard drive in the working PC as a secondary drive, and the working PC will not boot with the drive attached. It is SATA, so I tried booting first, then attaching it. It sees it in device manager, but cannot access it and the computer runs horribly slow when I did that. Trying to boot from the non-working drive on the working computer resulted in the same stop error (presumably, since I can't read the error).
I am amazed that copying over viamraid.sys didn't fix the problem running the XP CDs recovery console, and at this point I'm out of ideas. The only thing on the drive worth keeping is a plethora of emails, which I don't even know how to recover without using Outlook's export utility, so it's probably futile unless I can somehow make the thing boot. I can get to a command prompt with NTFS support no problem.
Other things I tried: suggest in a huge thread about people saying they had problems with mup.sys (since it's the last file in the list, I bet 99% of them didn't have a mup.sys problem at all).
removed RAM chips one at a time
removed IDE cable from floppy drive and CD drive
reset video card (someone said agp440.sys came after mup.sys so I figured it was worth a try)
unplugged mouse and keyboard (someone said multiple keyboard drivers were their problem)
disabled USB support in BIOS (another suggested fix)
reset BIOS to defaults
tweaked BIOS to run only on the bare minimums
Just to be sure, I'd also like to ask if this syntax is correct for replacing a file, just in case I did it wrong...
>copy viamraid.sys c:\windows\system32\viamraid.sys
is what I typed, ">" being the command prompt and not something I typed.
If you run the XP cd bootable (tried restore and tried to install fresh), it will load the RAID drivers (kind of older system) and then get a stop error saying that viamraid.sys caused the problem. However, when you boot into safe mode, viamraid.sys is like 6-7 up the list before the end, so I doubt that's the problem. To be sure, I copied that file from the working PC to the broken one via floppy disk, and it made no changes at all. Chkdsk and a few other utilities I downloaded to scan the hard drive get to around 26% then freeze.
I tried to use that hard drive in the working PC as a secondary drive, and the working PC will not boot with the drive attached. It is SATA, so I tried booting first, then attaching it. It sees it in device manager, but cannot access it and the computer runs horribly slow when I did that. Trying to boot from the non-working drive on the working computer resulted in the same stop error (presumably, since I can't read the error).
I am amazed that copying over viamraid.sys didn't fix the problem running the XP CDs recovery console, and at this point I'm out of ideas. The only thing on the drive worth keeping is a plethora of emails, which I don't even know how to recover without using Outlook's export utility, so it's probably futile unless I can somehow make the thing boot. I can get to a command prompt with NTFS support no problem.
Other things I tried: suggest in a huge thread about people saying they had problems with mup.sys (since it's the last file in the list, I bet 99% of them didn't have a mup.sys problem at all).
removed RAM chips one at a time
removed IDE cable from floppy drive and CD drive
reset video card (someone said agp440.sys came after mup.sys so I figured it was worth a try)
unplugged mouse and keyboard (someone said multiple keyboard drivers were their problem)
disabled USB support in BIOS (another suggested fix)
reset BIOS to defaults
tweaked BIOS to run only on the bare minimums
Just to be sure, I'd also like to ask if this syntax is correct for replacing a file, just in case I did it wrong...
>copy viamraid.sys c:\windows\system32\viamraid.sys
is what I typed, ">" being the command prompt and not something I typed.