RussianBlue
10-21-2002, 07:51 AM
High guys, fairly new in these parts but not completely wet behind the ears. I could use a little help here on a few things...
Details of my first 'successful' overclocking experience:
ABIT KD7-RAID
AGOIA Y 0213 1600@1920@1.9vcore 9.5 x 202FSB
SLK-800 w/ Vantec Tornado
512 XMS3200C2 @ 2.9v 202FSB CAS2 2T
Abit Siluro MX440 till my Golden Sample returns
Antec Truepower 430
Ran 6 hours of Prime95, multiple 3DMark loops (i.e. stable enough for me : )
Memory has been burned in at 2.9v for about 36 hours at 202 FSB with Sandra Memory burn-in wizard @1.9 GHZ
Problem
Can't seem to get the memory to go any higher than 202, even with these semi-weak timings and haven't been able to test thoroughly because....
...my FSB being so far out of whack is corrupting my Windows system files every time I crank up the FSB one more tick. This requires me to re-format and re-install, a pain obviously with Win XP. Also a pain with Win2000. There's got to be an easier way to repair. I know you guys don't have to re-install every time you hit a FSB that doesn't work. Do you??
After first install I Ghosted the good XP partition to a .ISO file and tried to restore it (restored 'partition from image'), and it helped a little, I got to the Windows 'Knight-Rider' screen, but couldn't get in and had to re-format.
I've tried the XP recovery console, but don't really understand it - tried Fixboot, Chkdsk and few other commands to no avail.
So I really can't isolate that it's the memory as I haven't even had a chance to adjust much of anything before crashing in my FSB experimentation.
Another question:
Which is the most stable bus to work off of when experimenting with high FSBs? IDE, PCI, or RAID. Where should I install my hard drive and OS which will be affected least by the high FSB?
Interesting side note - I was able to run my TEKRAM U160 SCSI card and 15k Cheetah up to about 190 FSB on the PCI bus and then the same thing happened when i upped the FSB a few ticks- a corrupted System 32/Config file (pretty sure that was the one).
My questions in summary
Likely it's the memory or the KD7 maxed out (or neither)?
Best way to restore a windows install after FSB HD corruption?
What's the most stable bus to work off of, IDE PCI RAID?
All suggestions appreciated in advance!!
Details of my first 'successful' overclocking experience:
ABIT KD7-RAID
AGOIA Y 0213 1600@1920@1.9vcore 9.5 x 202FSB
SLK-800 w/ Vantec Tornado
512 XMS3200C2 @ 2.9v 202FSB CAS2 2T
Abit Siluro MX440 till my Golden Sample returns
Antec Truepower 430
Ran 6 hours of Prime95, multiple 3DMark loops (i.e. stable enough for me : )
Memory has been burned in at 2.9v for about 36 hours at 202 FSB with Sandra Memory burn-in wizard @1.9 GHZ
Problem
Can't seem to get the memory to go any higher than 202, even with these semi-weak timings and haven't been able to test thoroughly because....
...my FSB being so far out of whack is corrupting my Windows system files every time I crank up the FSB one more tick. This requires me to re-format and re-install, a pain obviously with Win XP. Also a pain with Win2000. There's got to be an easier way to repair. I know you guys don't have to re-install every time you hit a FSB that doesn't work. Do you??
After first install I Ghosted the good XP partition to a .ISO file and tried to restore it (restored 'partition from image'), and it helped a little, I got to the Windows 'Knight-Rider' screen, but couldn't get in and had to re-format.
I've tried the XP recovery console, but don't really understand it - tried Fixboot, Chkdsk and few other commands to no avail.
So I really can't isolate that it's the memory as I haven't even had a chance to adjust much of anything before crashing in my FSB experimentation.
Another question:
Which is the most stable bus to work off of when experimenting with high FSBs? IDE, PCI, or RAID. Where should I install my hard drive and OS which will be affected least by the high FSB?
Interesting side note - I was able to run my TEKRAM U160 SCSI card and 15k Cheetah up to about 190 FSB on the PCI bus and then the same thing happened when i upped the FSB a few ticks- a corrupted System 32/Config file (pretty sure that was the one).
My questions in summary
Likely it's the memory or the KD7 maxed out (or neither)?
Best way to restore a windows install after FSB HD corruption?
What's the most stable bus to work off of, IDE PCI RAID?
All suggestions appreciated in advance!!