cpu prime stable, memory memtest stable, is windows corrupted?

[frozndevl]

Okay, I was able to get my processor prime stable at 285x10 @ 1.35x110% with a low memory divider. I then moved onto my memory settings and was able to get it overnight memtest stable. Of course, when I started to try to get into windows, my comp would reboot sometimes, so I figured it was just not Windows stable. I play around a bit and then decide to reload optimized defaults.

I reboot again and once I get into windows, it randomly reboots again. At this point, I could use some assistance. My guess is that somehow during my testing, it corrupted windows, but could it be anything else? I wouldn't really enjoy performing a repair install, but I could if needed

Genie BIOS Settings:

FSB Bus Frequency.............................  -  285
LDT/FSB Frequency Ratio.......................  -  3x
CPU/FSB Frequency Ratio.......................  -  10x
PCI eXpress Frequency.........................  -  101Mhz

CPU VID StartUp Value.........................  -  1.500v

CPU VID Control...............................  -  1.35
CPU VID Special Control.......................  -  110%
LDT Voltage Control...........................  -  1.20v 
Chip Set Voltage Control......................  -  1.60v
DRAM Voltage Control..........................  -  2.60v

DRAM Configuration Settings:

DRAM Frequency Set............................  -  180=RAM/FSB:09/10
Command Per Clock (CPC).......................  -  Enable 
CAS Latency Control (Tcl).....................  -  3
RAS# to CAS# delay (Trcd).....................  -  4
Min RAS# active time (Tras)...................  -  8
Row precharge time (Trp)......................  -  4    
Row Cycle time (Trc)..........................  -  10 Bus Clocks
Row refresh cyc time (Trfc)...................  -  14 Bus Clocks
Row to Row delay (Trrd).......................  -  03 Bus Clocks
Write recovery time (Twr).....................  -  02 Bus Clocks
Write to Read delay (Twtr)....................  -  02 Bus Clocks
Read to Write delay (Trwt)....................  -  03 Bus Clocks
Refresh Period (Tref).........................  -  3684 Cycles
DRAM Bank Interleave..........................  -  Enabled

DQS Skew Control..............................  -  Auto
DQS Skew Value................................  -  0
DRAM Drive Strength...........................  -  weak4
DRAM Data Drive Strength......................  -  level 1
Max Async Latency.............................  -  8
DRAM Response Time............................  -  Normal
Read Preamble Time............................  -  5 nano
IdleCycle Limit...............................  -  256 Cycles
Dynamic Counter...............................  -  Disable
R/W Queue Bypass..............................  -  16 x
Bypass Max....................................  -  07 x
32 Byte Granularity...........................  -  Disable(4 Bursts)

[trismegistus]

Try reseting cmos.Could be that windows is corrupted.You should always keep pci bus at stock speed.Did you lock agp\pci bus?

[frozndevl]

I am doing an 8 hour CMOS clear right now since it wouldn't stay in windows long enough for me to use it remotely. PCI-x speed shouldn't be an issue. Also, its been at 101Mhz and it was running fine at 290x10 with low memory settings.

Also, to add to things, one time in the series of reboots, it said that a corrupted registry entry was corrected. Maybe it wasn't corrected fully.

[trismegistus]

I had the problem with corrupted registry entry that was "corrected",but it only made things worse.If that cmos thing doesn't work reinstall windows.

[frozndevl]

Well, I never thought I would be thankful for Windows. A system restore solved the problem, so I am right back where I started. Now if only I can avoid corrupting it again

[trismegistus]

Glad you have solved it.Just in case for future,don't up pcie bus cuz it will not bring you any noticable improvement.Maybe the prob wasn't that,but just in case.

[frozndevl]

I've heard that one is up for debate, the pci-x upping. Over at dfi-street they have had some success uppping it by 1 or 2 mhz on these boards.