• 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.

problems with duron on MSI K7tpro2

Cosmo

Senior member
Just upgraded to a duron 700 on a MSI K7tpro2 mobo. When I'm overclocking I can sometimes get the system to run just fine at 100Mhz*9 but other times it won't even post it just starts beeping when I power on.

Anyone familiar with this problem? Could it be that the L1 bridges are not properly connected? (I'm guessing I have to check this sooner or later but the orb is such a hassle to install)
 
First off, if the MB is beeping, doesn't that suggest a working processor? Try checking to see that the problem is not with the video card (it happened to be so for me once).
If you want to check the L1, then to get the orb on/off, get a second person. One person has to hold the orb evenly down, the other has to unhook the clip. Works much better than one person doing it with one hand. It may also be the PS, which can be fluctuating slightly with temperature, or even the temperature of the die at boot-time itself. Boosting the core voltage a couple of notches may make it stable in that case.
Hope this helps.
 
mindlink. thanks, a lot of suggestions there to keep me up another couple of hours.

With the beeping though, I think there's at least five or six stages the mobo goes through before cpu initialization. What's annoying is that I could boot earlier but not anymore😕
 
Does the video card initialize? Also, does the problem occur only when you OC or all the time? BTW, I put in the video card idea first because when my system's video card failed (wasn't in all the way), the system began beeping incessantly.
Side thought: I don't know the MSI beep codes, but a look in the manual might help narrow the problem.
Sorry to keep you up.

Regards.
 
Cosmo,

What do the DLEDS tell you? Mine either show and stop at 0110 (Processor Initialization) or 0100 (Memory Problem). I have the same problems with my pro2-A. First of I can do 10x100 but not all the time... when I can do it I can run Rc5 for 15 hours and play some UT for another 2 hours without a single reboot. Then when I do reboot it fails to POST. I know its not the Duron 800 I have because I tried on a friend's Abit KT7 and it does boots at 1050 and ran Prime95 Torture Test for a few hours without locking up. I don't think it has anything to do with the bridges otherwise why can I run at 10x100 for almost 18 hours then do a single reboot and it fail to POST? Also why can I always post at 9.5x105 but not at 10x100? I don't like 9.5x105 because my system tends to be buggy even at a measly +5FSB speed.



 
You bumping the voltage up enough? I know that i can't get 10x100 for my Duron 800 on K7T Pro2-A yet. I will probably connect the L7 bridges to get more voltage sometime next week. Too lazy to do it now.

If you can get to 9 for the clock multiplier then you should have connected the bridges properly. I know that when i didn't do it correctly i could only go up to 8.5 from default 8, and i could already do that without unlocking the cpu. I can get up to 9.5 now. I think this may be my limit though, because going to 10 has yet to work. Maybe you've hit your limit...
 
Back
Top