• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

new cpu

dbrons

Member
OK I put in the new e8500, (pulled out e6850)
started up and the BIOS recognized the new CPU but Windows Vista wont start
after fooling with the BIOS settings a while I was able to get it to run in safe mode

I used safe with networking and I'm posting from my rig right now.

this is Asus P5E. BIOS 7102 latest.
I used defaults to get this running. Earlier I got a message "overclock failed" but I hadn't set any overclock I don't think.

Any suggestions for settings I should use?
Dave

 
Your E6850 has a multi of 9 and your E8500 has a multi of 9.5. go into bios and double check that you have your multiplier set to .5 and reset your bios to default levels. 🙂
 
hmmm, tried reseating Ram, It's running now at 9.5 X 266 when I put it to 333 it says overclock failed. Is there some fsb setting that is messing this up?

I think it will run at 333X9.5 but only in safe mode
 
Have you adjusted your voltages? Don't use auto. Set your vcore to what your cpu vid is. Make sure that you have your ram set to the proper voltages also. Check that you are not oc'ing the pci-e, set it to 100mhz.
 
Besides voltages, make sure your RAM timings are correct for 333 FSB. If you have 4GB of RAM, you may need extra voltage on the RAM and MCH. You may also need to loosen the timings.
 
Thanks guys. Yep, it was the vcore. Auto was wrong for some reason. I set it to 1.2v and suddenly everything is working 😀

Just bumped it to 380X9.5 3.6ghz and seems good. I did up the Ram voltage too. I'm going to go back now and see what speed the Ram is running.

But thanks! Wow it looked for sure like the fsb was wrong or something. I never touched the vcore setting with my other processor.....I never would have thought that was it.....
Dave
 
Back
Top