SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Computer Learning

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: mappingworld who wrote (42490)8/5/2004 5:38:45 PM
From: maceng2  Read Replies (1) of 110652
 
The guys on that thread seem to be all over that MB problem..

"nxn" makes his announcement and leaves..

Hi everyone.... Thank you for all the great posts here first of all.

Here is something to help you even further. IT is the KM400 chipset that is the problem. It took until now for me to see the connection but I have been having problems with the FIC AM39 motherboards used in some computers here. The only thing that they really have in common with the SK43 motherboards is the chipset. I also figured out that the systems could be stable at 133 FSB but that is a pain. Every other comonent makes no difference. Since I have a dozen of these to test with I know this to be true.

Seeing all the COMMON troubles right down to the errors and resolution with the SK43 and the AM39 I can definitly say that I will not buy another system based on any VIA chipset for AMD K7 processors. All my SiS and nVidia systems are fine.

That is all


forums.sudhian.com

So, the answer is a BIOS change in your case. Change the FSB to 133 Mhz and all should be well.

hmmmmmm, my older MB has a Via chipset in too. I'll have to check what sort, just for future ref, I'm intending to be buying two new PC's sometime for my kids and networking the lot. This has been a most educational problem to look at. I am a AMD processor die hard btw -g-

Careful with that BIOS change, and I hope it works for you.
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext