Does anyone else get this error when you push too far? It says you can run the XP repair utility, so what does everyone else do? reformat?
Printable View
Does anyone else get this error when you push too far? It says you can run the XP repair utility, so what does everyone else do? reformat?
repair utility. It copies all of the necessary files onto your HDD so you have a working windows again.
i get that all the time when i'm ocing...just up the vcore and you should be fine.
Yep same here. However, running Win2k usually gets other crap outs as well. I wouldn't even worry about it. I just turn off, and start up again, all is well. :D
Your data is not corrupted. Just increase the voltage on the proc and that should fix it. It might also be a low vdimm. Try increase voltage in the memory too
O.K... I reset to defaults, and I still get the error. I can boot from the XP cd-rom, and rhen I hit "r" for repair, so it asks me which o.s. I want to log onto. There is only 1, which is Xp, so I choose it, and it brings up a C:windows:\ command prompt. How do I repair from here? I can type help, and it lists a bunch of commands, but how do I get it to copy the system32 files? If I try the copy command, it says, "bad command"? Any ideas? This happens to me every time I try for 200fsb in the sig rig. My cpu is at 2.1v (temps at 55 idle:( ) and my vdimm is at 2.85. My chipset voltage is at 2.8, and my agp voltage is at 1.8. I can push them all a little higher, but I have a stick of pc3200 in, which should do 200fsb anyway.. (apparently its not??)
folder.
this has saved my bacon a number of times.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Boot to the XP cd and when you see the Welcome to setup press the letter R
You will get a dos prompt
Then type "chkdsk /p" without the quotes and hit enter
When that is done type "fixboot" and hit enter
"Y" and enter at the prompt
Then type "exit" and hit enter
The system will now reboot into Windows
If for some reason that don't work for you, you can boot to the recovery console like above and...
Type "chkdsk /r" then enter
When done type "exit" and hit enter.
This will take longer, but the system should boot back into Windows.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
There are other commands that are available too, just look at the listings when in the recovery console. Restore system files would be another one to try.......................
if this or other restoring doesn't work, then you can do an overinstall on your present OS, all your data will be saved as long as you don't reformat, duh. you will have to do your tweaks and prolly some shortcut repairs, but it will do the trick as long as your NTFS volume is not going bad (very bad juju).
good luck
baldy
Didn't work. It did find errors on the disk during both sequences, though. I know it's not my memory, because it's pc3200. I also know it's not the CPU, because I dropped my multiplier to 10, which booted at 2000mhz (xp2400 stock), and after I reformatted, it did it again.. corrupted the disk. Because I lack a pci/agp bus lock, It has to be the hard drive, which is running at 40mhz, instead of 33. Well guys, now I'm gonna get my 8RDA out and see what it will do. This rig went 13.0 X 192 fsb for a total of 2500mhz. My mem bandwidth was 2825meg/sec with 2-3-3-2-2 timings. I guess I hit the ceiling... Thanks for your help, guys!:)