- Joined
- Apr 25, 2001
- Messages
- 15,722
Ok, just got some extra spicy e5649s in the board. Won't boot, I get a CF code. Cleared CMOS already. Any ideas?
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Bummer DooKey, mine are running just fine on the A50 bios. I just started overclocking it, 4GHz was easy. Time to push [H]arder.
![]()
Dunno, I am having a bitch of a time getting anything FAH stable. I'm scratching my head at the moment.Where do you recommend I start? Slight cpu voltage increase and bclk increase? That's what I'm going to try.
Have you backed the multiplier down to 12x to see what you can get out of the bclk? Memory is also tempermental in these things - try DDR-1066 with everything else memory-related at Auto. Check you actual Vtt and memory voltages - none of my boards have been that accurate on settings versus actual voltages. I would manually set IOH and both Vtts at 1.35, set the DRAM voltages to whatever gives you the correct voltage for your memory, multiplier at 12x, and start cranking up the bclk.
Just some thoughts.
Any more luck today DooKey? My goal of bigadv stable @ 4 GHz with our new E5649's is proving very difficult to reach. I think I am now bigadv stable at 3.6 GHz. If I can get at least 3.8 GHz, I'd be happy at this point. Just hope I don't have to settle for 3.6 GHz.
I've had my SR2 in a place where it seems like nothing is working right. Won't always boot, won't OC, etc.
Then, pulling the cmos battery out and letting it sit for about 12 hours to get its head right seems to fix the problem. Come back the next day and it's working like it should. Something must get fouled up in the BIOS or something from time to time. Seemed to happen a lot when I was switching CPUs regularly.
Scratch that, only made it through 12 frames of a 2685 @ 3.6 GHz before the machine rebooted itself.
Frustration continues. Boots into the OS fine at speeds approaching 4.4 GHz, runs IBT and Linpack fine at 4 GHz, SMP stable at 3.6 GHz but bigadv is still a problem. Back to the drawing board.
Shouldn't. E5649's have been a supported chip for several BIOS revisions now. A48 through A50 are all working fine here, having the most luck with A49 as I did before with my ES L5640's.I'm wondering if we need a microcode update in the bios for this extra spicy chip?
No stop errors, in every case it has been a spontaneous reboot or:@tobit - dumb question, but is it worth reseating your PSU cables, making sure all the extra plugs are in?
Are there stop errors being logged like #124 that could shed some light?
@tobit - dumb question, but is it worth reseating your PSU cables, making sure all the extra plugs are in?
Are there stop errors being logged like #124 that could shed some light?
@dookey - what stop error are you getting on the bsod?
DooKey, are your temps good? Does all the RAM show up in BIOS? Are the HSFs seated correctly and not touching the heatsinks around the socket? Is there any flex in the motherboard, or is it sitting on a hard surface? I had trouble with all these things, including running the mobo sitting on the box (which doesn't count as a hard surface).
Maybe you can post your BIOS settings, or link to a post from where you copied the BIOS settings. There are some buried gotchas in the SR-2 BIOS.
Not much progress here last night, still smp stable at 3.5 GHz but bigadv reboots itself (or mdrun 255 error) after a few frames.
Cooking at a BBQ today, heading outside to build a fire in the smoker now so I can't do much today so I am just going to let it crunch smp units all day.
I have it set at 18x in the A49 BIOS but it could very well be locked and the setting not working. I will check it out after this BBQ is over.Uncore 18x on BIOS A49 hacked or A50? (the only bios to let you change uncore)
I have it set at 18x in the A49 BIOS but it could very well be locked and the setting not working. I will check it out after this BBQ is over.
Yeah, I'm debating putting the E5530s back in the SR-2 since they did OC in it. Then I can put the E5649s in the ASUS board and run them stock. That's probably my best option.
Sounds like a better plan - and if its a ZN8A, they are good boards. Pity they don't OC