Quote Originally Posted by aicjofs View Post
Now we are talking. That's what I was telling everybody in my last post you have to get the information directly to the BIOS team if the Tech Support is blocking you. Or at least the above ideas are the way things had to be addressed with MSI. It's not that the Tech Support dept doesn't want to help but their understanding level only goes so far. i.e. We aren't talking directly to the engineers who create C2D or BX2 we are talking to tech support which primary function is to maintain a product and secondary role is to feedback to the enginners MAJOR issues.

Blah blah about the C1E hardware locked. BIOS writing may be the most difficult coding on the planet. A BIOS engineer didn't put in a C1E "enable" "disable" in the BIOS on a whim or by accident if it was hardware locked. Just silly to even think that. You think the RM Clock coders work for Intel, no they found how to disable it by writing to a MSR in a white paper somewhere, it's probaly not even that big of deal to do, but it's not tech supports job to be writing CPU registers.

Another thing is a lot of people are mentioning overclocking to the tech support. To me this is like saying you had a few drinks to the cops, you are pretty much guilty of what ever happened to you. The C1E issue is there even and stock settings. IMO approaching it that way sends up more flags. "What our board is functioning weird at stock?!" That would get more attention from me then some guy who is overclocking and says he has an issue.

I'm not a know it all, not at all, but I spent at least 3 months battling MSI before we got a BIOS that helped and it wasn't by going the tech support route, and it started the same way this issue is bothering you guys right now when tech support is blocking.
What he said.

I never mention overclocking when talking to them but you DO have to have facts and a test case. For the C1E bug, I told them exactly what was happeneing, told them how I verified using the MSRs and gave them a walk through as to how they could duplicate it. Don't get mad or sarcastic or they turn off and don't get off topic. Eventually I got to someone on the phone who had a BX2 in front of them and walked through the issue. They acknowledged the issue but tried to tell me I shouldn't be disabling it. This is where you have to be nice and calm and bring them back to the point that this IS a BIOS feature and it does NOT work and insist that they report it.

Tell them specifically... "I disabled C1E and EIST in the BIOS but my multiplier and voltage continue to change. I have examined MSR 1A0 and verified that in fact C1E is still enabled even though it was disabled via the BIOS. If I manually disable it from utility programs, I get the correct behavior where the multipler and voltage are constant but this does not survive a reboot."

Also remember, the BIOS that was released yesterday was probably already baked when we first reported the problem. It's not like they have team dedicated to doing nothing but BX2 BIOS development.

Another thing to remember, although it was me that started the C1E thing, this is by no means a critical bug. It's an annoyance. Use RmClock and it will disable C1E whenever you reboot.