• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Soyo Dragon 2 Plat board, bios issues (very strange and interesting)

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Morpherios

Registered
Joined
Sep 27, 2003
I've recently started to do some overclocking on my system which is using a 3.0 ghz p4, 800 fsb, and the 875 Dragon Platinum board. I have a set of OCZ PC4000 ram (512 mb each stick, total of 1 gb in dual chan), Antec 480 watt trueblue power supply, ATI Radeon 9800 XT, two 120 gb Maxtor 8 meg cache drives in raid stripe, etc. Decent system to be sure and I really had no problems with it until I started overclocking.

I'm not having trouble with the system due to the overclocking exactly, more that I've noticed problems with the system that weren't apparent until I started overclocking. Here's the list of things I've noticed.

1. My CPU VCore, regardless of what it's set to in the bios, never reports in the pc health monitor as what I set it as. For example if I max it out at 1.6, save and reboot, when I enter bios again health monitor lists the vcore at 1.55. Other settings have similar results. This is very aggrivating as I've managed to get my system to boot ok at 247 FSB (which puts the proc at around 3.67 ghz) But it will not remain stable and I feel that the extra .05 that I should be getting might make it stable. I can boot and run for a while at 242 FSB (putting proc at 3.63 or so) but eventually a game I'm running will just quit to desktop. I'm currently at 240 FSB, which is 3.60 ghz. This so far seems stable.

2. AGP voltage at it's lowest setting (not counting default) reports at .05 under what I set it at. By setting it to the next step up, in the bios (to effectively get it to what I want it to be, which happens to be .05 lower than what I just set it to) The health monitor reports .05 *higher* than what I set it at. Meaning I can't get a middle ground, I have to bump it up an entire .1 increment as opposed to .05.

3. The temp monitor in the bios (and of course then, in the windows temp monitors) reports a steady 44-45degrees C on the proc, regardless of strain or clock speed. The case temp fluctuates but seems too low to be a report on the proc (as if they'd gotten switched).

And not just that, but the small computer shop that I work at uses the same motherboard in a water cooled system as a demo machine. All the problems I've noted are present in that board also. In addition, we have a water cooling kit on that machine, as well as an external temperature monitor to check cpu temp (xazer 3 case using hardcano built in) and that reports much differently than the constant 44 degrees C on the proc.

I have the latest bios flash, the machine at work is using stock bios. So, is this a problem with this board, am I doing something wrong, I don't quite understand it but a friend has a brand new ABIT AC7-Max board for me if i want it, so I'm trying to decide if I want to swap it out since the soyo seems like it's got some design flaws. Anyone have any ideas?
 
These type of niggling refinement issues are typical of Soyo boards of recent years. I'd go for the the Abit in a heartbeat.
 
Ok then maybe I'll have to take his offer on that abit board. Next question, based on your opinion, do you think I'd be able to get my machine stable at a higher clock speed if I was able to put the vcore up to the appropriate levels, like the Soyo isn't allowing me to do? I had this 3.0 overclocked to about 3.4 before I even had to change the vcore, then it just quickly died out on me as I raised it. I can boot the damn system at 3.63 but it just isn't stable. I actually had to bump it all back to 3.57 now to keep it stable permanently, and it bugs me. I don't want to rip this board out of my system and put the abit in (which is goin to require a lot of work including rebuilding my raid array for the second time in 2 weeks) if it won't give me extra performance.
 
Back