Printable View
The first time you have the option for a repair, just press ENTER, not the "R" key, because it will open a DOS prompt where you, indeed, can open the necessary comands.
After that, it will continue and check for previous installations. If it finds a previous install, choose the correct one (in case of multi boot) and then, you can choose Repair (pressing "R" key). Installation will then continue, and so on...
I never had any problems with a repair, using Raid for almost 2 years now.
Which SATA's are you using...SATA's 1&2 do not have a working lock so they tend to get corrupted at high FSB...use 3 or 4 if you are not...these SATA's are locked...Quote:
Originally Posted by kickassclone
Also try using BIOS 1.36b...the extra over volt options do work...and is the only BIOS that has allowed me to benchmark with 5-3-3-2.5/1:1 at 275FB/3X HT
^^ What he said. Make sure you are using the right SATA ports, 2 are not locked and that will happen everytime.
Like I said in the other thread, you should be testing DDR clock maxes at 8x or 9x multi, to eliminate your CPU limit and discover your mem limit.
And as the Jupiler said, don't use the recovery console, hit enter to install windows, then you will be given the option for automatic repair.
Don't get discouraged! Your memory has a long way to go, but you have to work out the other system issues to get it to max out.
I corrupted the system config file. I inserted the xp disk and booted from the cd and went through all the mtions of installing windows from the cd. When it asked to "repair" an install by pressing "r" that is what I did and immediately I was booted to the dos prompt c:> I tried this at least 10 times and everytime it would not repair anything. What could be the problem?Quote:
Originally Posted by Torin
This is normal if you press "r" the first time. It boots you to the dos prompt.Quote:
Originally Posted by kickassclone
Don't press "r" the first time it asks you if you wanna repair XP. Just press enter and continue.
It's only the second time you have the option to choose "repair", that you have to press "r". (it will check for previous installations) This will repair you installation, and should normally not boot you back to the dos prompt.
Or does this happen the second time too? Because your post is a bit confusing.
Quote:
Originally Posted by Jupiler
If you press enter it installs xp. I do not recall it ever asking if you want to repair a "second" time after you hit enter to install the os.
So what you are saying is that you boot from the xp cd and wehn it asks to install or repair or exit you press enter to install xp. After that it will ask you to repair your install a second time and not go through with the actual installation from pressing enter.
If this is what you mean I only hit hit repair the FIRST time it askes after the initial boot up from the cd. I did NOT press enter like I was just installing the os for the first time. Dam I might have just wasted all my data for nothing if this is the case
:eek:
At what FFT size do you get these errors?Quote:
Originally Posted by kickassclone
The repairs the other poster mentioned is the one that comes when you go ahead like you were trying to install XP again. Dont use the first repair option, select installation and you will be offered another option to repair which doesnt go to DOS and will repair automatically and most of the times it will fix the problems.
it restarts and then gives you a dos prompt? :confused:
i never heard of that...
dont clock n raid! you should have known better :P
so now whats the status?
the cpu isnt the problem but its the mem?
did you ever get the speed your trying stable with other memory?
ask a friend to lend his memory and see whether it fixed the problem...
I cant affirm that this is 100% true, but it is very possible. MSI K8N Neo2 may have a problem with NewCastle cores.
I have the same problem as you. My BH5 can do 255MHz memtest and on other rigs, but in windows I cant do over 220MHz 2-2-2-7 on this board. And, my WindowsXP Currupts so easily!
I am almost sure that the Neo2 as a compatibility problem with NewCastle. And I'm pretty sure that if MSI knows this problem, a BIOS could repair it.
Quote:
Originally Posted by skate2snow
If the board is made for socket 939 and the 3500+ is a socket 939 then why should there be a problem with the 3500+ which is meant to go in a desktop mobo like the neo2. My newcastle cpu works fine I just wanted a better oc outta it than I am getting. I could always just buy an fx-55 but since the fx-57 is gonna be out in the summer I will wait and then have the best amd offers.
Quote:
Originally Posted by scottk
I get these errors in about 15 seconds after starting p95. These occur almost immediately.
It is not as simple as that, it is a whole coding story.
And this is about the only logical explanation.
Do you try the guide from the OS forum? Otherwise its in my sig. for future use :)
i have tried several times to run prime95 and i get the same errors as in the first post.
my system:
dfi lanparty pro 875b
3.0es
mushkin pc3200 level II [bh5] 4x256
i have all settings set at default.
i have run memtest86 for 60 passes with no errors.
any advice as to why i keep failing prime95 would be appreciated.
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.
[Wed Jan 26 21:53:54 2005]
FATAL ERROR: Rounding was 0.5, expected less than 0.4
Hardware failure detected, consult stress.txt file.