Reply to thread

Message

<blockquote data-quote="doveman" data-source="post: 776323" data-attributes="member: 67412">I've got a Biostar TA790GXBE with an Athlon II X4 630, which works fine at stock settings and indeed overclocks very nicely up to 250FSB, which is perfectly stable. The problem is, if I overclock the FSB at all, even to 205, when resuming from standby I only see the desktop for a couple of seconds before the PC resets and I get a POST error saying &quot;&quot;Too many cold reset due BIOS POST. System might be incorrectly overclocked&quot;.So if you want to overclock the FSB at all, these boards are useless for HTPC purposes (or any other where you might want to resume from standby). Hibernate works of course as the PC's POSTing anyway, so I can at least use that for scheduled recordings, but it's no use if I want to Standby the PC to save power but be able to quickly resume it to watch TV, check the EPG, etc as it takes almost as long as booting from cold!I have to say that this may be an AMI BIOS issue, but it does seem to be more of a problem on Biostar boards for some reason.</blockquote>

[QUOTE="doveman, post: 776323, member: 67412"] I've got a Biostar TA790GXBE with an Athlon II X4 630, which works fine at stock settings and indeed overclocks very nicely up to 250FSB, which is perfectly stable. The problem is, if I overclock the FSB at all, even to 205, when resuming from standby I only see the desktop for a couple of seconds before the PC resets and I get a POST error saying ""Too many cold reset due BIOS POST. System might be incorrectly overclocked". So if you want to overclock the FSB at all, these boards are useless for HTPC purposes (or any other where you might want to resume from standby). Hibernate works of course as the PC's POSTing anyway, so I can at least use that for scheduled recordings, but it's no use if I want to Standby the PC to save power but be able to quickly resume it to watch TV, check the EPG, etc as it takes almost as long as booting from cold! I have to say that this may be an AMI BIOS issue, but it does seem to be more of a problem on Biostar boards for some reason. [/QUOTE]

Verification