Curious issue with 45nm dual core

[Dr. Spankenstein]

It seems to be operating as only one core when multi-threaded programs kick in.

My motherboard isn't giving me the option for CPU Multi-threading (which should become available if the CPU supports it.) I've already went about loading the lates BIOS for the X38-DQ6, so that isn't the issue.

I've pulled the proc and gave the pads a good wipedown with acetone in case there was any TIM or dielectric grease left from the previous owner who had this chip operating under a TEC. Still no option in BIOS.

Another curiosity is in Everest is when I'm running Orthos, only one core shows loaded.

http://img.techpowerup.org/080501/Dual Core.jpg

This is compounded by the fact that my CPU scores in 3DM06 and Vantage are lower than my old E6600.

I've even gone so far as to uninstall the processors in the Device Manager in hopes that it would recognise them correctly.

I'm going to clear CMOS adn see if that cleans anything up, but in the meantime if anyone can think of what else might be happening, please let me know.

Thanks.

[blkhogan]

Hmmm.... Ive had problems with everest reporting correctly in the past. It doesnt show hardly anything with my new mobo. Have you tried any other reporting software?

[hat]

what does task manager say?
your E6600 was 3.75GHz, this is only 3.16 ;)
it's just a lower FAB process, not a different arch.

[Nitro-Max]

My GA-965P-DQ6 board was fine with my Q6600 so i really cant see it been the bios unless its a 45nm issue? have you tried resetting the cmos.

have you tried any of the beta bioses?

Could it be a os thing? did you try a fresh instal when you changed the cpu?

ctrl + f1 for advanced menu in bios?

cant think of anything more hope you get it sorted soon.

[MadCow]

Well does Orthos progress on both cores? If it does then it's just Everest screwing up like it usually does.

[panchoman]

looks just like everest, try using task manager.

[Frogger]

Dead core ???? possible.. can you check it in another MB to confirm?

[panchoman]

dr. s, you aren't using any emulation programs right? like vmware, virtual pc, etc.

[Dr. Spankenstein]

Dead core ???? possible.. can you check it in another MB to confirm?

This was what I was trying to determine. I'm curious if it would work in my old 975XBX.

Orthos does report the test progressing on both cores for a couple of min., but fails becuase of the horrible vdroop on this mobo (Testing 4.25GHz: 1.412 BIOS, 1.408 CPU-z idle, 1.376 load) :shadedshu It actually drooped less with EIST enabled and LLC disabled!

This is the board I JUST got back from RMA, thanks Gigabyte!:rolleyes:

To be fair, the only thing I'm going by is 3DM06. Looks like it kicks into a lower power/multi state right iin the middle of some test. The scores and framerates confirm this, unless during the CPU I wanted to see how the increased speed would effect my score. Then it seemed to go to hell from there.

Reinstalled 06, updated video drivers, flashed to latest mobo BIOS, reset CMOS. Same chugging and total drop of framerates in the same parts of the tests.:banghead:

Gonna have to try a fresh OS install.

Thanks everyone for your help and suggestions!

[Nitro-Max]

Hope you get it sorted m8 good luck

[Dr. Spankenstein]

Thanks man, so do I!

BTW, love your new avatar!

[Frogger]

This was what I was trying to determine. I'm curious if it would work in my old 975XBX.
975xbx should have a bios update that would allow that proc to work ... have a look over at intel

[D4S4]

Everest says - PIII Xeon, 3166MHz stock clock :wtf:

[Dr. Spankenstein]

Yeah, probably time to get a "fresher" version of Everest. :rolleyes:

@ Frogger,

The release notes only go so far as to state "updated processor support" but no specifics. This BIOS was from Sept. 07!

[Darknova]

Everest says - PIII Xeon, 3166MHz stock clock :wtf:

Because the Core 2 duo is essentially a highly tweaked P3 :D

And I've not experience that issue. The latest version of Everest I have is 4.50.1330 and that detects everything fine.

[lemonadesoda]

1. Try the tool at www.hwinfo.com

2. Go to BIOS and disable speedstep, just in case the mainboard isnt managing it properly

3. Run temp monitor program... perhaps there is a fault with IHS, or your heatsink, or your FAN (did you plug it in ... sorry to ask... or is it cable fouled?), and thermal protection is kicking in. Try http://www.cpuid.com/hwmonitor.php

[Dr. Spankenstein]

I will try HWINFO. Thanks for the link. Is there something I should be looking for that would give a definitive answer?

I have been monitoring core temps with Real Temp. There was a variance between core temps, but I saw the same behavior with the E6600. I just never bothered to look at how large the discrepancy was, that could be a valuable clue right there.

I've got a Tuniq on it temporarily while I test it out. The fan is plugged into the CPU_fan header and is working.

[Frogger]

Any update on this proc prob ????

[Dr. Spankenstein]

Yeah, it took a clean OS reinstall to clear it up. Just goes to show you how tenacious those leftover drivers can be!

Anyhoo, testing dual Prime95 the second core or Core1 (the one that was dropping out during benching earlier) is curiously the first one to error each time!

Running 4.275GHz @ 1.440V w/450FSB temps never get above 57C on air.

Does a lower multi require less volts for the CPU since the burden is shifted more to the NB? I've always wondered about that...

BTW, thanks for the concern.:toast:

[spearman914]

Everest readings are not that accurate. It once read E8400 as a E1280.

[Dr. Spankenstein]

Seems the versions that Expreview and tom's hardware are running don't have the same issues we share.

...but I won't be shelling out for that prog in my lifetime!:rolleyes: