I originally posted this in overclocking, given the problem, but it was suggested that the post would be better placed here
Three years ago I put together a core duo 6600 system with an Asus P5B deluxe MB and 2 gigs of G.Skill PC2 6400 RAM -After assembly it booted right up without any need to tinker with the bios- It has functioned well for all that time -
I recently wanted to upgrade to a quad core 9300 CPU - In order to do that I needed to upgrade my Bios to 1238 which supports that chip. - I followed the instructions to the letter, including setting the MB to defaults (F5) , flashing the bios, again resetting bios and then after shutting down, disconnecting the power for a minute. The chip change was of course no biggie-BUT now - The system on boot, freezes at the bios sign on screen, if I disconnect the power it will then boot and give an error message that "overclocking has failed" (I have never overclocked anything). I can then continue the boot even so (f2) or (F1) pop into the bios. If I go on to boot windows the computer functions normally for extended periods. When I shut down and reboot - it again freezes at the bios menu again until I again shut down and disconnect power for a minute- I can then boot into the bios or Windows
I never checked the memory settings pre bios upgrade since I didnt have to do anything when I assembled the system (I copied the other settings down)
I have noticed this:
My Bios after multiple resets to default, reports
Configure Dram by SPD - enable
CAS# lat -5
RAS to CAS delay 6
RAS Precharge 6
RAS activate to precharge 15
Write recovery 6
DRAM tRFC 42
DRAM tRRd 10
Rank write to read delay 10
Read to precharge delay 10
Write to precharge delay 1
Static read
CPU ID (after a successful boot) reports
FSB DRAM 1:1
CAS Latency 4
RAS-CAS# delay trcd 4
RAS#Precharge trp 4
cycle time tRAS 10
command rate 2t
JEDEC #1 JEDC#2
4 5
4 5
4 5
10 15
14 21
This is very different from what the bios is set to. I suspect my default memory timings are now being set wrong by the bios at boot. Am I right??
I have never messed with the bios- What do I do to fix this?? Do you need more info to help me figure this out?
Steve
Three years ago I put together a core duo 6600 system with an Asus P5B deluxe MB and 2 gigs of G.Skill PC2 6400 RAM -After assembly it booted right up without any need to tinker with the bios- It has functioned well for all that time -
I recently wanted to upgrade to a quad core 9300 CPU - In order to do that I needed to upgrade my Bios to 1238 which supports that chip. - I followed the instructions to the letter, including setting the MB to defaults (F5) , flashing the bios, again resetting bios and then after shutting down, disconnecting the power for a minute. The chip change was of course no biggie-BUT now - The system on boot, freezes at the bios sign on screen, if I disconnect the power it will then boot and give an error message that "overclocking has failed" (I have never overclocked anything). I can then continue the boot even so (f2) or (F1) pop into the bios. If I go on to boot windows the computer functions normally for extended periods. When I shut down and reboot - it again freezes at the bios menu again until I again shut down and disconnect power for a minute- I can then boot into the bios or Windows
I never checked the memory settings pre bios upgrade since I didnt have to do anything when I assembled the system (I copied the other settings down)
I have noticed this:
My Bios after multiple resets to default, reports
Configure Dram by SPD - enable
CAS# lat -5
RAS to CAS delay 6
RAS Precharge 6
RAS activate to precharge 15
Write recovery 6
DRAM tRFC 42
DRAM tRRd 10
Rank write to read delay 10
Read to precharge delay 10
Write to precharge delay 1
Static read
CPU ID (after a successful boot) reports
FSB DRAM 1:1
CAS Latency 4
RAS-CAS# delay trcd 4
RAS#Precharge trp 4
cycle time tRAS 10
command rate 2t
JEDEC #1 JEDC#2
4 5
4 5
4 5
10 15
14 21
This is very different from what the bios is set to. I suspect my default memory timings are now being set wrong by the bios at boot. Am I right??
I have never messed with the bios- What do I do to fix this?? Do you need more info to help me figure this out?
Steve
Facebook
Twitter