- Joined
- Feb 13, 2001
- Location
- Twin Cities
Some of my Christmas Bonus was burning a hole in my pocket, so despite Ed's advice, I dove in and purchased a K8N Neo2 Platinum and 90nm Athlon64 3200+.
I have always used either Abit or ASUS motherboards because I've never had a problem that I didn't cause with those brands in the 7 of so motherboards I have gone through over the evolutionay process these past 7 years or so living on the bleeding edge. I went with MSI because I dearly love the Nvidia chipset and only they and Gigabit offer the NF3-Ultra. Since I had money tied up in my Radeon 9800XT I did not want to wait for the NF4 entrants with their abandonment of the AGP bus.
I got the K8N Neo2 Platinum and Athlon64 3200+ this past Friday from Monarch. I replaced my existing NF7-S and Barton with it and installation went great. I reinstalled XP SP2 on my SATA array, along with the current chipset drivers painlessly. After reloading all my apps, it ran fine aside from an occasional stutter start that required turning off the PSU and trying to start it again. It ran fast and furious Friday evening, Saturday, Sunday and Monday. No sweat getting through Memtest86, Prime95, 3D Mark, etc.
On Tuesday, after several stutter starts in a row, I had all I could take and started troubleshooting. I rechecked all my connections, cleared the CMOS memory, but to no avail. The voltages on my Antec True550 were well within tolerance. I tried measuring the Vdimm, Chipset and Core voltages during the brief power-up, but the sample rate on my Fluke DMM was too slow. So, I hooked up the 4-Trace digital Storage scope and found that the core voltage was only getting up to 1.083V as opposed to the minimum of 1.45V needed for the 90nm Athlon64. Unfortunately, after stutter starting the system on and off about 20 times during troubleshooting, it got worse. It would power up and not shut down quickly as before. It just powered up and failed to enter POST. The core voltage was still only 1.083V. I called Tech Support at Monarch and after establishing that I wasn't some Joe SixPack we arrived at the mutual agreement that given the setup worked fine for three days and now the Vcore was stuck being too low, that the motherboard was defective and probably not the CPU. I sure hope so, because they issued me an RMA to send back the just the motherboard, which is in transit as I write this.
I did a lot of searching around the forum circuit regarding this stutter start issue and found I am not alone. Most of the posters had their problem resolved by replacing the board, but a few had the problem on the second board as well. Some found it related to using the Antec Truepower PSU (like me). Some found it related to using an older PS2 Keyboard (like me) and some never figured out the cause. Hopefully the replacement motherboard will work better though I must admit, when it was working, the MSI board was great. The manufacturing quality was good and it came with about any possible accessory you could possibly need to get it going.
I've always had good service from Monarch, but then I never got anything from them that required an RMA. Hopefully, that process will continue to go as well as it has started out.
More after my replacement arrives and I get my system back together.
Hoot
I have always used either Abit or ASUS motherboards because I've never had a problem that I didn't cause with those brands in the 7 of so motherboards I have gone through over the evolutionay process these past 7 years or so living on the bleeding edge. I went with MSI because I dearly love the Nvidia chipset and only they and Gigabit offer the NF3-Ultra. Since I had money tied up in my Radeon 9800XT I did not want to wait for the NF4 entrants with their abandonment of the AGP bus.
I got the K8N Neo2 Platinum and Athlon64 3200+ this past Friday from Monarch. I replaced my existing NF7-S and Barton with it and installation went great. I reinstalled XP SP2 on my SATA array, along with the current chipset drivers painlessly. After reloading all my apps, it ran fine aside from an occasional stutter start that required turning off the PSU and trying to start it again. It ran fast and furious Friday evening, Saturday, Sunday and Monday. No sweat getting through Memtest86, Prime95, 3D Mark, etc.
On Tuesday, after several stutter starts in a row, I had all I could take and started troubleshooting. I rechecked all my connections, cleared the CMOS memory, but to no avail. The voltages on my Antec True550 were well within tolerance. I tried measuring the Vdimm, Chipset and Core voltages during the brief power-up, but the sample rate on my Fluke DMM was too slow. So, I hooked up the 4-Trace digital Storage scope and found that the core voltage was only getting up to 1.083V as opposed to the minimum of 1.45V needed for the 90nm Athlon64. Unfortunately, after stutter starting the system on and off about 20 times during troubleshooting, it got worse. It would power up and not shut down quickly as before. It just powered up and failed to enter POST. The core voltage was still only 1.083V. I called Tech Support at Monarch and after establishing that I wasn't some Joe SixPack we arrived at the mutual agreement that given the setup worked fine for three days and now the Vcore was stuck being too low, that the motherboard was defective and probably not the CPU. I sure hope so, because they issued me an RMA to send back the just the motherboard, which is in transit as I write this.
I did a lot of searching around the forum circuit regarding this stutter start issue and found I am not alone. Most of the posters had their problem resolved by replacing the board, but a few had the problem on the second board as well. Some found it related to using the Antec Truepower PSU (like me). Some found it related to using an older PS2 Keyboard (like me) and some never figured out the cause. Hopefully the replacement motherboard will work better though I must admit, when it was working, the MSI board was great. The manufacturing quality was good and it came with about any possible accessory you could possibly need to get it going.
I've always had good service from Monarch, but then I never got anything from them that required an RMA. Hopefully, that process will continue to go as well as it has started out.
More after my replacement arrives and I get my system back together.
Hoot