Forums | Chat | News | Contact Us | Register | PSU Social |
PSU: No matter how many times you refresh, your quote won't be here.
Forums | Chat | News | Contact Us | Register | PSU Social |
Home | Forum | Chat | Wiki | Social | AGN | PS2 Stats |
|
|
|
Thread Tools | Search this Thread | Display Modes |
2005-02-21, 11:19 PM | [Ignore Me] #1 | ||
Second Lieutenant
|
Heres the deal, I installed and played KOTOR2 yesterday, predictably it crashed...so I rebooted, it crashed again...tried to reboot....tried to reboot...cant reboot, it gets stuck at Mup.sys driver, a useless novell network interface driver, that I dont need, yet somehow fucks up my boot sequence.
I've tried multiple things, booting from windows CD, booting from boot disks, safe mode, network boots, repairing windows installation, recovery console...etc etc. To no avail. To those of you that may be able to help, the most relevent piece of data about this problem seems to be the fact that the computer is unable to read my hardrive to go into the recovery cosole, it gets stuck at "scanning 28640mb on id1 blah blah blah" endlessly, I even let it go over night, it simply wont scan my harddrive. This leads me to think its a hard drive issue somehow caused by installing a new game, though WHY it would get stuck on mup.sys is beyond me. SO, does anyone have any bright ideas about what might be happening? the mup.sys bug is very common, but its extremely UNcommon that I cant boot to the recovery cosole. this is a shot in the dark, but I figure most of you fuck up your computers now and then, Im hoping this may ring a bell :/ EDIT: Im on my old 333mhz right now..Im surprised its still alive and working after all these years
__________________
+++++DATE: - Jungfrost polar base (Bernheart), 128.M41 Last edited by Wraithlord; 2005-02-21 at 11:20 PM. |
||
|
2005-02-21, 11:44 PM | [Ignore Me] #4 | ||
There are two ways you can fix this in my mind:
Fix-it-1: If you have another harddrive (harddrive 1)that your mobo will run boot off that then run a scandisk and fdisk on your hardrive (harddrive 2)that is not working properly. With that it should fix the problems and you can remove hard drive 1 and just use your harddrive 2 once again. Fix-it-2: if you are good with computers you can try this. boot of the CD and go load recovery console and type disable mup then enter. hope that helps |
|||
|
2005-02-23, 03:13 AM | [Ignore Me] #5 | ||
Second Lieutenant
|
well raven, I cant even access the recovery console, or I would have done that before, as it turns out, mup.sys is not the problem, but the driver that loads after it "amdagp.sys" is. Im going to hook it up to my other crappy computer with win95 on it tommorow and run disk dr. and scandisk and see if that helps
__________________
+++++DATE: - Jungfrost polar base (Bernheart), 128.M41 |
||
|
|
Bookmarks |
|
|