Forum Home
Press F1
Thread ID: 62006	2005-09-23 23:23:00	Will not start in safe mode.	RichardR-S (8905)	Press F1

Post ID	Timestamp	Content	User
390390	2005-09-23 23:23:00	New motherboard cpu and xp installation worked. Installed new power supply and additional ram which showed ok in post message. Now goes to Start normally/Last known setup/Safe mode screen. When using "Last known setup" I get a blank screen. When using "Safe mode" it stops at "Partition 1, Windows sys. 32/Drivers Mup.sys. I was told by supplier of above parts to leave running (could take 12 hours) and system will correct itself. Ran for 17 hours in vain. Should I re-format the hard drive (again)? Thanks	RichardR-S (8905)
390391	2005-09-23 23:50:00	What the heck. "Leave running for 12 hours and system will correct itself"? What a load of CRAP,drivell, nonsence, garbage complete bull*****. Don't get any further advice from this guy as he clearly knows nothing. I am assuming you are using Windows XP?. (Windows 2000 has same issue) CAUSE (in basic Lingo) Windows XP does NOT like changeing shipset accross motherboards. Example. Your old Motherboard may have had a VIA chipset and your new one has a Nforce4 chipset. If you change your motherboard for the same type of chipset it would have probably been ok. SOLUTION Run a Repair install on Windows XP with your XP driver CD. You do not need to re-install a repair install will correct it.	Battleneter (60)
390392	2005-09-24 00:12:00	New motherboard cpu and xp installation worked. Installed new power supply and additional ram which showed ok in post message. Should I re-format the hard drive (again)? Thanks i think the person has already formated the previous installation :)	dbs (8785)
390393	2005-09-24 00:48:00	What the heck. "Leave running for 12 hours and system will correct itself"? What a load of CRAP,drivell, nonsence, garbage complete bull*****. Don't get any further advice from this guy as he clearly knows nothing. Actually he's not entirely full of it. See here: www.hardwareanalysis.com I've had PCs do that - well not the error, just on install sit and think about it for a bit then continue. Not for that long though - I'd give it 1 hour max. Reset the BIOS, and try some of the suggestions in that link.	pctek (84)
390394	2005-09-24 23:50:00	Actually he's not entirely full of it. See here: www.hardwareanalysis.com I've had PCs do that - well not the error, just on install sit and think about it for a bit then continue. Not for that long though - I'd give it 1 hour max. Reset the BIOS, and try some of the suggestions in that link. Well I have to say this suggetion is as good as saying "rub creme on it". Hard to beleive anyone that truly knew what they were doing would advise someone to "wait 12 hours" as it may improve, very funny though. I guess he may have been trying to blow the person off till the weekend and then sort out the problem on Monday lol. **Read the orginal post carefully, he has just changed his motherboard and has not tried a reinstall yet, to me this is not rocket science, Windows XP craps out with new chipsets, of course ive only seen this about 300000 times (slight exageration maybe), ill go with my solution on this one. "Mup.sys" is where I EXPECT XP to stop after a chipset change, very very common.	Battleneter (60)
390395	2005-09-24 23:55:00	i think the person has already formated the previous installation :) "Should I re-format the hard drive (again)? Thanks" The actual error suggests he has not, but I admit you could take this either way.	Battleneter (60)
390396	2005-09-25 04:28:00	All the advice given is sound... although I would have to say that "leave for 12 hours" bit is very dodgy. Having said that my own personal view on this sort of issue is to format the drive and do a fresh install of XP. That way all new hardware is detected and you don't have the remains of your old system anywhere so that provides a good starting platform for whatever else you want to do. As I said just my personal opinion. cheers chiefnz	chiefnz (545)
1