Hi all,
I've just installed XP Home ed on a duron 950 machine, running a Shuttle AK31 Rev 3 board, and 256 MB of Kingston PC2700 DDR. Here's my situation: Last night I was attempting to overclock the system, and it seems that every time I bumped the FSB past 150, the system would hang or get some type of sporadic error. What surprises me is that I have successfully run 512 MB of DDR at 157 MHz on a AK31 Rev 2 board, using an Athlon 1.33 266 fsb CPU. One stick was regular Micron, and the other was Crucial. See my confusion? Two presumably mismatched sticks can run at 157 MHz on an older motherboard with an inferior northbridge chipset, but 1 stick of pc 2700 can't make it past 150 on a KT266A-based board. (on both setups, all memory settings were at their most aggressive except for the command rate-it was set to 2T in both instances. Additionally, on the duron/AK31 Rev 3 setup, the que depth (something like that) was set to 4. This setting is unavailable on my Rev 2 board) Some more system info: The graphics card on the duron/rev 3 setup is a radeon 8500. Surely that should tolerate fsb's well past 150? The only other difference between the two systems is a home pna network adapter card I installed on the duron system that didn't exist on the athlon/rev 2 system. Could this be causing data corruption?
Finally, the OS: Is XP tremendously more sensitive to memory errors (assuming that memory errors are in fact my problem) than other OS's? After one overclocking-induced crash, XP suddenly demanded that I activate the software. That installation was about 20 minutes old. I noticed that the system clock was way off then, so I'm assuming that the incorrect time/date is what made XP demand to be activated, but why would overclocking make the time/date settings change?
(in case anyone is wondering, the reason my XP is not activated is that I'm about to change all sorts of hardware in the computer, and I don't want to lock myself into a configuration that may not be the same in a few weeks.)
I've just installed XP Home ed on a duron 950 machine, running a Shuttle AK31 Rev 3 board, and 256 MB of Kingston PC2700 DDR. Here's my situation: Last night I was attempting to overclock the system, and it seems that every time I bumped the FSB past 150, the system would hang or get some type of sporadic error. What surprises me is that I have successfully run 512 MB of DDR at 157 MHz on a AK31 Rev 2 board, using an Athlon 1.33 266 fsb CPU. One stick was regular Micron, and the other was Crucial. See my confusion? Two presumably mismatched sticks can run at 157 MHz on an older motherboard with an inferior northbridge chipset, but 1 stick of pc 2700 can't make it past 150 on a KT266A-based board. (on both setups, all memory settings were at their most aggressive except for the command rate-it was set to 2T in both instances. Additionally, on the duron/AK31 Rev 3 setup, the que depth (something like that) was set to 4. This setting is unavailable on my Rev 2 board) Some more system info: The graphics card on the duron/rev 3 setup is a radeon 8500. Surely that should tolerate fsb's well past 150? The only other difference between the two systems is a home pna network adapter card I installed on the duron system that didn't exist on the athlon/rev 2 system. Could this be causing data corruption?
Finally, the OS: Is XP tremendously more sensitive to memory errors (assuming that memory errors are in fact my problem) than other OS's? After one overclocking-induced crash, XP suddenly demanded that I activate the software. That installation was about 20 minutes old. I noticed that the system clock was way off then, so I'm assuming that the incorrect time/date is what made XP demand to be activated, but why would overclocking make the time/date settings change?
(in case anyone is wondering, the reason my XP is not activated is that I'm about to change all sorts of hardware in the computer, and I don't want to lock myself into a configuration that may not be the same in a few weeks.)