@Bulldog72
THX for your accommodation.
Any news on the real time overclocking/voltage utility from DFI ?
Getting back to this, the reason why DFI doesn't offer such a utility is that such programs have to work in tandem with the BIOS. As the BIOS for a given board gets changed, such programs need to also be revised to keep up with BIOS development. Basically this has the effect of slowing down the BIOS release schedule as the MB maker needs to keep up with the software as well.
I have worked at 3 MB makers for the last 10 years and I have seen them all experiment with such "real-time" programs over the years and it always ended the same. At first the "program" is launched with much media fanfare and it seen as a great "extra" by the public. However over time the software revisions start to lag behind the BIOS releases. They get further and further apart and the problems start to compound, until eventually the software is hopelessly outdated, and the whole thing gets abandoned.
Keep in mind that BIOS development is not always a smooth, predictable process. If it was it would be easy to plan and match software development, but the reality is different. Often issues come to light after a board has been launched into the market, that require an
immediate BIOS release. It can't wait until some software gurus get everything all matched up.
There are a few other reasons, but this is the main one. That said, never say never. Perhaps such a program will be released by DFI one day, but I don't see it happening anytime soon.
DFI Support Europe.
---------- Post added at 09:24 ---------- Previous post was at 09:11 ----------
@Bulldog: Any Idea why that happens with nonOC? If high voltages or clocks: I guess everybody could at least understand that some Board get burned. But in this cause the board just got burned after first installation without any OC from what I can read in that users posts. Compared to other cases it is not as much damage so from the pictures I would say: Early status (but also defect)?
And: Thanks for the information
Actually I do have some ideas why this has happened on what seems to be a nonOCed board, that fit in with my theories about what is wrong with the Foxxconn sockets. However I don't have any hard proof, and never will I'm afraid. Lets just say I'm not entirely surprised this has happened.