ground Posted April 23, 2022 Share Posted April 23, 2022 Insane :O Quote Link to comment Share on other sites More sharing options...
gtxx58 Posted April 23, 2022 Share Posted April 23, 2022 Just Awesome! Quote Link to comment Share on other sites More sharing options...
Crew Don_Dan Posted April 23, 2022 Crew Share Posted April 23, 2022 Nice one, Kai! Quote Link to comment Share on other sites More sharing options...
Eisbaer798 Posted April 24, 2022 Share Posted April 24, 2022 Thanks guys! Totally insane I'm still shocked Quote Link to comment Share on other sites More sharing options...
Noxinite Posted April 24, 2022 Share Posted April 24, 2022 (edited) I've had that once before, but I think I had it happen on a REX and I could never reproduce. Sweet score though! Edited April 24, 2022 by Noxinite Quote Link to comment Share on other sites More sharing options...
MaddMutt Posted April 24, 2022 Share Posted April 24, 2022 ^ I saw your other sub from the same board. Is this a problem -> quad core only works as a dual <- with the CPU’s or the board? IIRC these are 2 dual core CPU’s acting as a quad core. Can you set which 2 cores work in the bios? IIRC they use the FSB to communicate -> If set to high it is causing corruption in the data between dies? Next WR = SP 1m and 32m scores. Quote Link to comment Share on other sites More sharing options...
Eisbaer798 Posted April 25, 2022 Share Posted April 25, 2022 (edited) I still cant't undestand the error. It just happens random. I can't say whether it's due to the voltage being set too high or something else. It happens with one Quad CPU and not with the next. In the case of the Q9650 result, the board itself raised the boot FSB from 535 to 638MHz. Don't ask me why...I don't think there will be new SP1M or 32M records. I was just able to validate the high CPU clock before the system said goodbye with a blue screen. Further attempts with an FSB of 600 set in bios were unsuccessful. So I Think both dual-core chiplets are active if you set an FSB of 600 in the bios. And no, unfortunately you can't turn off CPU cores with a GB board. That only work with the rex which is again x48. Edited April 25, 2022 by Eisbaer798 Quote Link to comment Share on other sites More sharing options...
Guest Digg_de Posted April 25, 2022 Share Posted April 25, 2022 Cant remember how this popped up. 1. older bios 2. only kentsfield Quote Link to comment Share on other sites More sharing options...
Eisbaer798 Posted April 25, 2022 Share Posted April 25, 2022 (edited) Unfortunately, this option is missing in my bios. Have you any info what bios can it be? Edited April 25, 2022 by Eisbaer798 Quote Link to comment Share on other sites More sharing options...
Guest Digg_de Posted April 25, 2022 Share Posted April 25, 2022 Just one Bios Version older than the last Version. Quote Link to comment Share on other sites More sharing options...
Crew Antinomy Posted April 26, 2022 Crew Share Posted April 26, 2022 (edited) On 4/26/2022 at 12:21 AM, Eisbaer798 said: Unfortunately, this option is missing in my bios. Checked both F8c and F7 versions for EP45T-UD3P with Modbin, the menu is there. Try ctrl+F1 in main BIOS setup screen. Edited April 26, 2022 by Antinomy 2 Quote Link to comment Share on other sites More sharing options...
Eisbaer798 Posted April 28, 2022 Share Posted April 28, 2022 Thanks Antinomy I'll try that next week. It would be great if that would work! 1 Quote Link to comment Share on other sites More sharing options...
Eisbaer798 Posted May 17, 2022 Share Posted May 17, 2022 Ok guys, I`ve now tried something around. With Yorkfield CPUs (Q9650/Q9550 etc) the option does not appear in the Bios when pressing ctrl+F1. With Kentfield CPUs (Q6700/Q6600) the option appears in the Bios, but it does NOT disable any cores. With socket 771 dual core server CPUs (like Xeon 5150) the Bios option appears and cores can also switched off! 3 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.