Page 1 of 1

Why won't Intel fix the Bad Axe 2 C1E/EIST problem???

Posted: Thu Oct 18, 2007 1:08 pm
by Pez D Spencer
I noticed that even after disabling C1E and EIST in the BIOS the CPU still uses it. The only way I've found to make it go away is to use RMClock. I've looked around the net and it seems like this has been a problem with these boards since they came out. It seems like by now Intel would have done something about it.

I couldn't figure out why my CPU kept throttling down even though I had both C1E and Speedstep disabled in the BIOS. Another user on this board mentioned RMClock and after running it I could see that C1E and EIST were both still running. I noticed that using RMClock to turn off C1E stops the throttling even though EIST is still running. I don't know all the ins and outs of C1E and EIST but I understand that they are similar although they function slightly different. Apparently having just EIST running doesn't cause throttling.

With that said, I did some benchmarks using Everest and found that there is no performance loss with C1E running. I suppose that with a very high overclock and super-duper voltages C1E might become a problem, but I haven't seen any so far. However, it seems that Intel would have done something about this by now. Surely someone has let them know about it.

I suppose this is a problem with all 975XBX2 boards and not just a few. The fact that I only found one post here and a couple others around the net about it makes me think that perhaps it might be a bug that only affects some Bad Axe 2 boards? I don't know, you tell me. If you're an owner of a 975XBX2, do you expereince this C1E problem?

Re: Why won't Intel fix the Bad Axe 2 C1E/EIST problem???

Posted: Thu Oct 18, 2007 3:56 pm
by IRQ Conflict
I haven't found that speed step or C1E was ever a problem with my mild overclock It keeps the heat and power usage to a minimum when not loaded.

As to why Intel has not addressed certain issues with this board, I think code names such as X38, X48 and 1333 FSB DDR3 PCI 2.0 ect might have something to do with it. You can safely consider the BadAxe 2 redundant. Intel does.

Re: Why won't Intel fix the Bad Axe 2 C1E/EIST problem???

Posted: Sun Feb 10, 2008 9:48 am
by Dandruff
anyone tried it with the latest bios? can c1e be disabled properly now?

Re: Why won't Intel fix the Bad Axe 2 C1E/EIST problem???

Posted: Mon Feb 11, 2008 3:36 pm
by Dandruff
ok, tried it and seems to be working fine!

Re: Why won't Intel fix the Bad Axe 2 C1E/EIST problem???

Posted: Thu Feb 14, 2008 12:20 pm
by IRQ Conflict
Good stuff! Well, it's valentines day, wheres the love Intel? :P