• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

overclocking - OS dependency

kornermi

Member
I have win98/win2k dual booting system. (Aopen AX6BC+PII350) I recently added redhat linux 7, so it is actually triple booting. As you may have guessed, since I installed win2k, I rarely boot into win98 anymore. Supiriority of win2k was just that obvious. I only use win98 when I watch TV on matrox marvel g200tv. Matrox offers only beta version driver for win2k so far.

Anyways, I recently acquired good quality memory sticks(133Mhz infineon and Mosel Vitelic), and just out of curiosity, overclocked the cpu by increasing fsb from 100 to 133Mhz, anticipating some smoke coming out of the computer. Well, it just worked fine. No extra cooling. 33% increase. Under win2k, that is. Linux works fine, too. However under win98, things are very sluggish, and even crash quickly. I came back to 100Mhz fsb, and win98 got back to normal. Hm.. I thought overclocking is only matter of hardware, but does it also have something to do with the operating system?
 
There is a dependency, but personally I have found Win2k to be most difficult. Try increasing the voltage slightly, if you havent already and maybe they will both be stable. 🙂
 
Some guy had the same problems with an overclocked Athlon. He had somep probs witht the registry and sometimes there would be boot problems.
 
A reason why your system might seem to be more stable under win2k is that win2k issues an idle process. This makes the cpu runs a bit cooler when it's not at 100% usage. Win98 does not have this process so at idle the cpu will run alot hotter. I would run some more extensive tests in win2k to make sure your system is 100% stable. Best test is to run a cpu stress test for like 6 hours. Also if you're agp is overclocked i would run q3 for like 6 hours.
 
I have had the opposite experience, in that a dual-boot system I had would easily o/c in Win98 but not in Win2K. This was on a Via 133a chipset system, however, and I did not have the same experience in BX or 815E. I'm not completely convinced that the OS is the problem, I think a well sorted out system of a stable chipset, good ram and cpu will run anything. In the upgrade did you add anything else, a PCI card for example that could cause a problem with the clock?
 
Back
Top