June 2, 20205 yr No chance to make 2:3(266) or 5:8(333) to work? On some boards these (especially 5:8) seem much easier than other dividers.
June 2, 20205 yr 2:3 posts but freezes after usb init, 5:8 works but requires 7-7-6. I will re-run with another cpu and fresh windows installation, hopefully will make runs with both a.m. dividers.
June 3, 20205 yr Actually s266 2:3 direct boot @643 was doable before repair (SB swap) - I think I should just try different cpu, this one had issues starting from 625mhz on core0 and it is hard to tell cpu limit from potential issues with the board.
June 3, 20205 yr Author I'm amazed that you can get any form of FSB reliability above 600 with Wolfdale on single stage. It seems that no matter what I do, the behavior is only stable for me when the CPU is on LN2.
June 3, 20205 yr 1 hour ago, TaPaKaH said: I'm amazed that you can get any form of FSB reliability above 600 with Wolfdale on single stage. It seems that no matter what I do, the behavior is only stable for me when the CPU is on LN2. Preach, I never could get the REX to behave nicely. Well I managed to get 634 2:3 32M working nice with PSC, but it seems harder with hypers and never consistent.
June 3, 20205 yr @TaPaKaH what temps does your single stage do? On my single stage I can do 615mhz on most of my wolfdale chips but that is the limit of my p5e3
June 3, 20205 yr 10 hours ago, sale_quiche said: Nice mem wow Fake clock in cpuz, it is strap 400 2:3 being detected like this. 7 hours ago, TaPaKaH said: I'm amazed that you can get any form of FSB reliability above 600 with Wolfdale on single stage. For me, it is more about cpu/nb skews (>600 should be smth like 300/0, >625 300/100, >640 400/100) and gtl settings. This one was binned out of 4 samples, 3 are consistent @625mhz, 1 is failing even at 600.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.