I have confirmed 3 people now who have clocked past 500FSB ALL with v1.0 of this board and 6 users all with v1.1 who can't get anywhere near it. It is annoying that certain reviews of this board have gone out when they are only review samples as it gives off a false impression.
I know a bios may fix it but am not very confident about this as had a similar issue with an abit board a few years back and it was fixed with another board revision. I never bought another board from them after this and the same thing will happen with MSI as well off to asus methinks.
Just found tweaktowns review where it states its the final version although it is v1.0 and gues what goes past 500FSB.
Originally Posted by Splynncryth Not all the code in your BIOS comes from the mainboard OEM or the BIOS vendor. Being an Intel chipset, there is one critical piece of code called the memory reference code that comes from Intel, so there is usually some delay in the problem being found and when the mainboard manufacturer can actually get the fix into their BIOS. So unfortunately, it isn't totally up to MSI, they depend on other companies and have to live with their schedules too.
The base code of the BIOS generally would come from the chipset manufacturer, yes - just as in the case of Nvidia chipsets. However, if it was solely a base code problem, then all or at least most implementations of the chipset would suffer the same problems. In this case, a product from MSI based on the chipset in question seems to have issues with reaching 500MHz FSB - but products from Gigabyte and Asus, for instance, do not seem to have as much trouble in this department although based on the same chipset. Hence it would strongly suggest an issue with MSI's circuit board design and/or BIOS optimisations - not to mention a somewhat rushed product testing phase. If they manage to tune the latter to work well with the former, great, but if not then we might not see a fix until another board revision comes out.
Bindibadgi: ISL6336 it is then! :p Spanking new, supports up to 6 phases under VR11.1 (ISL6327 is similar except that it's a VR11 device).
Originally Posted by stele The base code of the BIOS generally would come from the chipset manufacturer, yes - just as in the case of Nvidia chipsets. However, if it was solely a base code problem, then all or at least most implementations of the chipset would suffer the same problems. In this case, a product from MSI based on the chipset in question seems to have issues with reaching 500MHz FSB - but products from Gigabyte and Asus, for instance, do not seem to have as much trouble in this department although based on the same chipset. Hence it would strongly suggest an issue with MSI's circuit board design and/or BIOS optimisations - not to mention a somewhat rushed product testing phase. If they manage to tune the latter to work well with the former, great, but if not then we might not see a fix until another board revision comes out.
Sorry, didn't mean to imply that it is solely an MRC problem, only that BIOS is a complex beast and not all of it is under the control of the OEM. I'm sure they are doing everything they can to resolve the issue, but if they need to pressure an outside source for help, it just makes the process take longer.
Comments 26 to 28 of 28
I know a bios may fix it but am not very confident about this as had a similar issue with an abit board a few years back and it was fixed with another board revision. I never bought another board from them after this and the same thing will happen with MSI as well off to asus methinks.
Just found tweaktowns review where it states its the final version although it is v1.0 and gues what goes past 500FSB.
The base code of the BIOS generally would come from the chipset manufacturer, yes - just as in the case of Nvidia chipsets. However, if it was solely a base code problem, then all or at least most implementations of the chipset would suffer the same problems. In this case, a product from MSI based on the chipset in question seems to have issues with reaching 500MHz FSB - but products from Gigabyte and Asus, for instance, do not seem to have as much trouble in this department although based on the same chipset. Hence it would strongly suggest an issue with MSI's circuit board design and/or BIOS optimisations - not to mention a somewhat rushed product testing phase. If they manage to tune the latter to work well with the former, great, but if not then we might not see a fix until another board revision comes out.
Bindibadgi: ISL6336 it is then! :p Spanking new, supports up to 6 phases under VR11.1 (ISL6327 is similar except that it's a VR11 device).
Sorry, didn't mean to imply that it is solely an MRC problem, only that BIOS is a complex beast and not all of it is under the control of the OEM. I'm sure they are doing everything they can to resolve the issue, but if they need to pressure an outside source for help, it just makes the process take longer.