My neighbor bought a Sager 4760 for college through PC-Torque at my suggestion. He isn't the most tech-savvy, so he calls me when he has a problem.
He said he woke up, turned on his comp, it made a clicking sound, started to boot and said "Operating system not found" or something to that effect. He took it to the campus tech support folks, recreated the error, and they said his hard drive probably crashed. He called me to find out about return options and procedure and I explained the RMA stuff but asked to take a look at it over the thanksgiving break to see if there's anything I could do.
Well, when he brought it over today, it started to boot. It got to the WinXP splash screen with the Knight Rider thing on the bottom, but then it rebooted without notice. It brought up the "safe mode" screen and I selected "safe mode with command prompt". It proceeded to list all the drivers it was loading and hung at MUP.sys. I can't remember if it rebooted on its own or if I had to ctrl+alt+del. Anyhow, I searched MUP.sys on the internet. The solutions I found had to do with everything from USB 2.0, to the BIOS (on this forum concerning Alienware), to a faulty CD-Rom. I tried disabling the USB controller in the BIOS but it still wouldn't boot all the way into windows.
I then put in the recovery CD to try to do an overwrite on the windows system files (repair?). The repair console just gave me a bunch of commands like format and fixboot, but nothing to actually reinstall. I did run chkdsk, which found some errors on the disk, but, unlike scandisk, there was no option to try to repair the errors.
Convinced that the HD was the problem, I thought about trying to pull out the HD to get the data onto another comp and then sending in the whole thing for a replacement HD. But, before I did that I searched MUP.sys in Microsoft's Knowledge Base. It told me that the "Multiple UNC (uniform naming convention) Provider (MUP) is a network resource locator that runs in kernel-mode memory in Windows NT." Since applications use UNC or WNet API to access resources on the network, this gave me the idea to check the internal wireless. I switched it on and pressed power. It booted into windows!
So, the comp is working now. However, I'm still quite curious as to what was the problem, and what I should do about the errors on the HD.
Any ideas are appreciated.
He said he woke up, turned on his comp, it made a clicking sound, started to boot and said "Operating system not found" or something to that effect. He took it to the campus tech support folks, recreated the error, and they said his hard drive probably crashed. He called me to find out about return options and procedure and I explained the RMA stuff but asked to take a look at it over the thanksgiving break to see if there's anything I could do.
Well, when he brought it over today, it started to boot. It got to the WinXP splash screen with the Knight Rider thing on the bottom, but then it rebooted without notice. It brought up the "safe mode" screen and I selected "safe mode with command prompt". It proceeded to list all the drivers it was loading and hung at MUP.sys. I can't remember if it rebooted on its own or if I had to ctrl+alt+del. Anyhow, I searched MUP.sys on the internet. The solutions I found had to do with everything from USB 2.0, to the BIOS (on this forum concerning Alienware), to a faulty CD-Rom. I tried disabling the USB controller in the BIOS but it still wouldn't boot all the way into windows.
I then put in the recovery CD to try to do an overwrite on the windows system files (repair?). The repair console just gave me a bunch of commands like format and fixboot, but nothing to actually reinstall. I did run chkdsk, which found some errors on the disk, but, unlike scandisk, there was no option to try to repair the errors.
Convinced that the HD was the problem, I thought about trying to pull out the HD to get the data onto another comp and then sending in the whole thing for a replacement HD. But, before I did that I searched MUP.sys in Microsoft's Knowledge Base. It told me that the "Multiple UNC (uniform naming convention) Provider (MUP) is a network resource locator that runs in kernel-mode memory in Windows NT." Since applications use UNC or WNet API to access resources on the network, this gave me the idea to check the internal wireless. I switched it on and pressed power. It booted into windows!
So, the comp is working now. However, I'm still quite curious as to what was the problem, and what I should do about the errors on the HD.
Any ideas are appreciated.
)?
