RichM499
Daemon Poster
- Messages
- 783
- Location
- Spaceballs Mega-Maid
ok i've been through this on another post, and i'd like to delete the other thread but i cant=P
anyway i'd like some input if anyone knows anything
i use an asus a8v-x motherboard
corsair xms ddr400 ram
and athlon x2 3800+ (2.0ghz stock)
heres the thing, my ram maxed out at 212.5mhz (@166 in bios with 255 bus)
my hyperthreading bus worked fine at 1200mhz
and i eventually got the core up to 2.55ghz (255 busx10)
so the result was
2.55ghz cpu
1.019ghz hyperthreading
and 212mhz ram(@ 255mhz bus and 166mhz ram setting in bios)
(this means hyperthreading has some overhead to play with, and ram needs to be dropped to 133)
so i got it to 2.6, when i lowered the ram to 133, and raised the FSB to 260.
prime95 was flawless, and memtest worked fine
so i decided to go for 2.7ghz.. this is where things started getting weird
2.7ghz booted fine, memtest ran fine, Prime95 ran fine for nearly an hour.
but my asus probe2 software was acting really weird...
i was also using coretemp, and coretemp never had any issues
Asus probe 2 reported a huge 20c spike in the cpu temperature , and then it dissapeared when i freaked out and re-checked it to see if i was going crazy.
about 3 minutes later, Asus probe 2 reported that my chassis fan was spinning at 100rpm
(i would notice, its got 4 blue LEDS, and some red shiny spinny LEDS and stuff. it never slowed down....)
this motherboard automatically raises the core voltage (its 1.35v stock, and at my 2.55ghz settings, its hovering from 1.39v-1.42v)
so, i ignored it, and since prime95 was fine, and memtest was fine, my games worked fine, i decided to bump it to 2750..
as soon as i did, windows gave me the "windows/system is corrupt or missing"
i lowered it to 2600, got the same message
lowered it to stock, got the same message
so im wondering wtf went wrong
maybe the northbridge didnt like the auto-increase in voltage?
at 2.7 i cant be sure what the voltage was, i didnt write it down, and im not going to test it again untill i install another instance of windows (i'll use a blank windows install for testing, that way if i screw it up i still have this one)
thanks for any information
anyway i'd like some input if anyone knows anything
i use an asus a8v-x motherboard
corsair xms ddr400 ram
and athlon x2 3800+ (2.0ghz stock)
heres the thing, my ram maxed out at 212.5mhz (@166 in bios with 255 bus)
my hyperthreading bus worked fine at 1200mhz
and i eventually got the core up to 2.55ghz (255 busx10)
so the result was
2.55ghz cpu
1.019ghz hyperthreading
and 212mhz ram(@ 255mhz bus and 166mhz ram setting in bios)
(this means hyperthreading has some overhead to play with, and ram needs to be dropped to 133)
so i got it to 2.6, when i lowered the ram to 133, and raised the FSB to 260.
prime95 was flawless, and memtest worked fine
so i decided to go for 2.7ghz.. this is where things started getting weird
2.7ghz booted fine, memtest ran fine, Prime95 ran fine for nearly an hour.
but my asus probe2 software was acting really weird...
i was also using coretemp, and coretemp never had any issues
Asus probe 2 reported a huge 20c spike in the cpu temperature , and then it dissapeared when i freaked out and re-checked it to see if i was going crazy.
about 3 minutes later, Asus probe 2 reported that my chassis fan was spinning at 100rpm
(i would notice, its got 4 blue LEDS, and some red shiny spinny LEDS and stuff. it never slowed down....)
this motherboard automatically raises the core voltage (its 1.35v stock, and at my 2.55ghz settings, its hovering from 1.39v-1.42v)
so, i ignored it, and since prime95 was fine, and memtest was fine, my games worked fine, i decided to bump it to 2750..
as soon as i did, windows gave me the "windows/system is corrupt or missing"
i lowered it to 2600, got the same message
lowered it to stock, got the same message
so im wondering wtf went wrong
maybe the northbridge didnt like the auto-increase in voltage?
at 2.7 i cant be sure what the voltage was, i didnt write it down, and im not going to test it again untill i install another instance of windows (i'll use a blank windows install for testing, that way if i screw it up i still have this one)
thanks for any information