I'm still poking around with finding the best speed combination with my comp I got two weeks ago, because I didn't like needing to run @ 2T command rate to do any decent CPU overclocking. (All the results I was getting before indicated I needed to use 2T, I have no idea why. I thought dividers were supposed to be simple; they definitely aren't. 
)
Anyway, I came up with 240HTT, x10 CPU, and a 9:10 memory divider (my RAM's only seems to be good up to 216. Boohoo.) I booted up and discovered that the RAM was @ 218 MHz for some reason. I've heard before that apparently the dividers don't really work off the CPU, and I have a RAM speed predictor program thingy that someone sent me; I figured 216 MHz (240*.9), the program predicted 217, and I got 218.2. I figured "what the heck" and started it running Prime95, it went for ~5 hours today and it was doing just fine. Bad things happened when I started running Trillian and looking in the task manager, but I figured that was to be expected when opening programs and playing around after all my mem was already eaten up. Still, knowing that eventually I'd get an error because my memory would crap out, I decided to drop the HTT to 238 before restarting Prime. I did, and lo and behold....Windows wouldn't even load!
I put it back to 240 HTT and booted into Windows no problem. I put it down to 239 HTT just to make sure something wierd(er) hadn't happened, and it too refused to finish loading Windows. Right now I'm typing with a 240 HTT.
Wierd, huh?
And any suggestions as to why this is, or how to stop it? I'm getting pretty tired of "guess the speeds that work!"
Other specs: 2x512 megs Geil Blue value 2.5-3-3-7, 1T, 2.8 volts, 9:10 divider. A64 3200+ @ x10 multiplier, default volts (2.4 set, 2.36 actual). DFI nf4 Ultra-D, defaults more or less with 240 HTT.
I was running 250x10, 5:6 divider, 2T for ~2 weeks on same volts, but it failed after 8.5 hours on some random Prime95 run and sent me looking for a better memory setting.
)Anyway, I came up with 240HTT, x10 CPU, and a 9:10 memory divider (my RAM's only seems to be good up to 216. Boohoo.) I booted up and discovered that the RAM was @ 218 MHz for some reason. I've heard before that apparently the dividers don't really work off the CPU, and I have a RAM speed predictor program thingy that someone sent me; I figured 216 MHz (240*.9), the program predicted 217, and I got 218.2.
I figured "what the heck" and started it running Prime95, it went for ~5 hours today and it was doing just fine. Bad things happened when I started running Trillian and looking in the task manager, but I figured that was to be expected when opening programs and playing around after all my mem was already eaten up. Still, knowing that eventually I'd get an error because my memory would crap out, I decided to drop the HTT to 238 before restarting Prime. I did, and lo and behold....Windows wouldn't even load!I put it back to 240 HTT and booted into Windows no problem. I put it down to 239 HTT just to make sure something wierd(er) hadn't happened, and it too refused to finish loading Windows. Right now I'm typing with a 240 HTT.
Wierd, huh?
And any suggestions as to why this is, or how to stop it? I'm getting pretty tired of "guess the speeds that work!"
Other specs: 2x512 megs Geil Blue value 2.5-3-3-7, 1T, 2.8 volts, 9:10 divider. A64 3200+ @ x10 multiplier, default volts (2.4 set, 2.36 actual). DFI nf4 Ultra-D, defaults more or less with 240 HTT.
I was running 250x10, 5:6 divider, 2T for ~2 weeks on same volts, but it failed after 8.5 hours on some random Prime95 run and sent me looking for a better memory setting.
Facebook
Twitter