All of a sudden I've run into a weird problem. My overclock is being ignored in Windows. My settings are being saved in the BIOS and during POST I can see the correct frequency, however, as soon as I boot into Windows, CPU-Z displays my info as if I was running at stock settings. Benchmarks also run as if I was running stock settings.
This wasn't always the case. Originally I was running my E2180 at 3.5 GHz (350x10) at 1.46V. The only thing I can think of that changed recently is I updated the BIOS on my Abit IP35-E to the current latest (15). However, I was still able to OC after this as I set my E2180 to 3.0 GHz (300x10) at 1.25V. Another thing that happened afterward which may have caused damage to my CPU is I accidently left my fans off (damn fan controllers) for an extended period while I was formatting my hard drive. I know it at least reached 70C because my motherboard's alarm was on but it probably didn't exceed 80C because at that temp my motherboard would have shutdown automatically. I didn't actually run CPU-Z after this happened so I can't be sure that this is the cause. I first noticed this when I wanted to bump back my CPU to 3.5 GHz from 3.0 GHz.
Oh yea. Even though CPU-Z shows my FSB as 200 MHz regardless of what I set in the BIOS, Vcore still reflects my settings. So it'll show 1.46V and still be at 200x10. Memory timings also reflect my settings.
Anyone have a clue why this is happening?
Relevant specs are:
E2180 with TRU-120 Extreme
Abit IP35-E
PC Power & Cooling 610W PSU
2x 1 GB Patriot DDR2 800 MHz Memory
This wasn't always the case. Originally I was running my E2180 at 3.5 GHz (350x10) at 1.46V. The only thing I can think of that changed recently is I updated the BIOS on my Abit IP35-E to the current latest (15). However, I was still able to OC after this as I set my E2180 to 3.0 GHz (300x10) at 1.25V. Another thing that happened afterward which may have caused damage to my CPU is I accidently left my fans off (damn fan controllers) for an extended period while I was formatting my hard drive. I know it at least reached 70C because my motherboard's alarm was on but it probably didn't exceed 80C because at that temp my motherboard would have shutdown automatically. I didn't actually run CPU-Z after this happened so I can't be sure that this is the cause. I first noticed this when I wanted to bump back my CPU to 3.5 GHz from 3.0 GHz.
Oh yea. Even though CPU-Z shows my FSB as 200 MHz regardless of what I set in the BIOS, Vcore still reflects my settings. So it'll show 1.46V and still be at 200x10. Memory timings also reflect my settings.
Anyone have a clue why this is happening?
Relevant specs are:
E2180 with TRU-120 Extreme
Abit IP35-E
PC Power & Cooling 610W PSU
2x 1 GB Patriot DDR2 800 MHz Memory
Facebook
Twitter