I finally got the parts from newegg and mushkin to build the following system 2 days ago:
Soyo Dragon Plus (original bios: k7vxa2ba1)
XP 1800+
Thermaltake Volcano 6 Cu
512MB 2.5-3-3 Mushkin value ram (1 stick)
ATI All-In-Wonder 128 Pro (PCI) 16MB
Western Digital 60GB 7200rpm HDD
Liteon 24/10/40 retail
Actiontek 56k hardware modem (Lucent chip)
Enhance PSU (ENP -730) & Chieftec case
2x Enermax Thermal Control case fans (80mm)
I have been spending over 15-18 hours each day since then to try to get this system running stably under win2k at nominal frequency (fsb=133, mem clk=133). just having a modem connection, I couldn't download larger benchmark suites/quake timedemo etc. so I have used SETI@home, prime95, ATI's video capture at full res (640x480, 22k-8bit audio) and last but not least BurnInTest. BurnInTest - by the way - is one of the best synthetic benchmarks i have seen to date. check it out to see how well it can stress a system as a whole.
below are my actions and findings summarized from past 2 days:
1. upgraded the bios to k7xva2ba2. some of the important BIOS settings were as follows:
cpu freqnecy select = 133
spread spectrum = disabled
system performance = normal
dram clock = 133 (even tried "dectect using SPD" option)
dram timing = manual --> the rest of the items in DRAM menu were left as they were (CAS=2.5/bank interleave=disabled/prechg to active(Trp)=3T/active to prechg(Tras)= 6T/active to CMD(Trcd) = 3T/DRAM queue depth=2 level/write recovery time=2T/dram cmd rate=2T cmd/dram dqs length = default
with this setup, the system posted, win2k was installed successfully, most of the relavent drivers were installed including via and the mother board components' drivers, ATI etc. no problem surfing the net, downloading and such daily multi-apps running. if i recall correctly, the system was also able to run sandra mem/cpu benchmarks at 133/133 and ran SETI@home without a glitch for over 10 minutes. however, come time for real stress test using BurnInTest, the system would freeze within less than 5 minutes (often within a minute) at max load and almost all benchmarks turned on. it also would freeze at times during video caputure using ATI and viewing the captured scene. it had a few random freezes aswell.
2. based on what a lot of people said in some posts at amdmb.com, i went ahead and downgraded my bios back to its shipped version (k7vxa2ba1) since the complain was that this was a lot more stable bios than the newer one.
with this bios, again the same behavior: system worked fine but would freeze when running the BurnInTest benchmark.
3. downgraded the fsb freq and dram clk to 100 each. ==> now the benchmark passed for the first time! though at 100MHz.
at this point, after wasting so much time after just getting a system stable, i am verymuch leaning toward RMAing the system board first thing mon/tuesday morning. this setup (unlike my ASUS setups in the past) has given me the worst nightmares yet.
NOTE: the system has never BSODed on me as yet! (interesting...) all i see is freezes/hangups.
can someone please comment on the BIOS settings/any tweaks I can do to the system to see if it has any chance of becoming stable??!! PLEASE, need some hints/clues as to why a perfectly good config would not be able to hold up for than just minutes under heavy load. i hope that based on some of your experiences and settings in BIOS/OS, i can make the system stable and prove that it's not the system board/bios.
thanks a lot for any help you can provide.
Soyo Dragon Plus (original bios: k7vxa2ba1)
XP 1800+
Thermaltake Volcano 6 Cu
512MB 2.5-3-3 Mushkin value ram (1 stick)
ATI All-In-Wonder 128 Pro (PCI) 16MB
Western Digital 60GB 7200rpm HDD
Liteon 24/10/40 retail
Actiontek 56k hardware modem (Lucent chip)
Enhance PSU (ENP -730) & Chieftec case
2x Enermax Thermal Control case fans (80mm)
I have been spending over 15-18 hours each day since then to try to get this system running stably under win2k at nominal frequency (fsb=133, mem clk=133). just having a modem connection, I couldn't download larger benchmark suites/quake timedemo etc. so I have used SETI@home, prime95, ATI's video capture at full res (640x480, 22k-8bit audio) and last but not least BurnInTest. BurnInTest - by the way - is one of the best synthetic benchmarks i have seen to date. check it out to see how well it can stress a system as a whole.
below are my actions and findings summarized from past 2 days:
1. upgraded the bios to k7xva2ba2. some of the important BIOS settings were as follows:
cpu freqnecy select = 133
spread spectrum = disabled
system performance = normal
dram clock = 133 (even tried "dectect using SPD" option)
dram timing = manual --> the rest of the items in DRAM menu were left as they were (CAS=2.5/bank interleave=disabled/prechg to active(Trp)=3T/active to prechg(Tras)= 6T/active to CMD(Trcd) = 3T/DRAM queue depth=2 level/write recovery time=2T/dram cmd rate=2T cmd/dram dqs length = default
with this setup, the system posted, win2k was installed successfully, most of the relavent drivers were installed including via and the mother board components' drivers, ATI etc. no problem surfing the net, downloading and such daily multi-apps running. if i recall correctly, the system was also able to run sandra mem/cpu benchmarks at 133/133 and ran SETI@home without a glitch for over 10 minutes. however, come time for real stress test using BurnInTest, the system would freeze within less than 5 minutes (often within a minute) at max load and almost all benchmarks turned on. it also would freeze at times during video caputure using ATI and viewing the captured scene. it had a few random freezes aswell.
2. based on what a lot of people said in some posts at amdmb.com, i went ahead and downgraded my bios back to its shipped version (k7vxa2ba1) since the complain was that this was a lot more stable bios than the newer one.
with this bios, again the same behavior: system worked fine but would freeze when running the BurnInTest benchmark.
3. downgraded the fsb freq and dram clk to 100 each. ==> now the benchmark passed for the first time! though at 100MHz.
at this point, after wasting so much time after just getting a system stable, i am verymuch leaning toward RMAing the system board first thing mon/tuesday morning. this setup (unlike my ASUS setups in the past) has given me the worst nightmares yet.
NOTE: the system has never BSODed on me as yet! (interesting...) all i see is freezes/hangups.
can someone please comment on the BIOS settings/any tweaks I can do to the system to see if it has any chance of becoming stable??!! PLEASE, need some hints/clues as to why a perfectly good config would not be able to hold up for than just minutes under heavy load. i hope that based on some of your experiences and settings in BIOS/OS, i can make the system stable and prove that it's not the system board/bios.
thanks a lot for any help you can provide.