Help with a Bios Flash Question... (IN9 32X)

[subiesaurus rex]

I had a quick newbie question about bios flashes. I have been having some issues with my board so I went ahead and flashed it from the 1.1 to the 1.2 beta6 bios revision. I think that I may have forgotten to reset the cmos before flashing. Everything went without a hitch but now I am running into some funky issues. Pre-flash and things acting up I was able to run 9x356 to get 3.2ghz out of my E6600. Now I am barely able to hit 3ghz, with an 8x or 9x multiplier. Right Now, i am not completely stable running 8x375. I am planning on flashing the bios again tonight with a later beta bios. However my concern is that I am getting mixed reports of my Cpu speed. CPUz shows it exactly how I set it in my bios, as does the Abit uguru. But windows and Core Temp both show my system as having higher speeds. CPUz shows 8x375=3ghz, the abit uguru doesnt show the multiplier but shows 375. Then Core temp shows the system as 8x421=3.375ghz, and windows says its a 3.38ghz Cpu... Is there some crazy chance that the system took my old overclock and set that as "stock" so when i see 266mhz fsb, its actually running higher? I have never heard of this before but I dont if I have ever forgotten to reset the cmos before a flash! Any ideas would be greatly appreciated!!!

Ryan

[Lvcoyote]

Do a full cmos reset after the flash, not before. Personally I do a full clear before AND after. Make sure the system is not overclocked when you flash. Another important thing to remember..... always use the F10 key to save your BIOS changes or the uGURU settings and other things can get screwy. Also, I STRONGLY advise flashing with a floppy and not through Windows, especially if your using Windows Vista.

[subiesaurus rex]

I did a cmos reset After the flash but I am not sure if the system was overclocked when I did flash. I have alwasys cleared it before a flash but this time I think I may have forgotten. None the less when the multiplier is set to the stock 9x - everything reads fine, so the issue must be stupid programs displaying erroneous info.