X5660 cache and cores not showing in CPU-Z and OCCT

[hell_knight]

Hello guys!

I've just received an x5660 and put it in my x-58 sabertooth, replacing an x5650 that was a bit too hot for my taste.

Apparently while in bios it shows that the cache is recognized from L1 to L3 and all cores are active, when I open CPU-Z it shows only one core and 12 threads, and only detects L2 cache.

I've tried stress testing in OCCT but linpack only detects one core (Core0).

The X5650 that I replaced showed all info and was detected correctly by OCCT.

Regarding temps, only realtemp shows 6 cores while coretemp crashes. With the X5650 I've been using coretemp without issues.

Can you help me determine which could be the cause of the problem?

Thank you!!!

Specs:
X5660 - 4,3 Ghz (1.3v)
X58 Sabertooth (bios 1402)

 

[GhislainG]

If that CPU is officially supported by Asus, then I'd presume there's an issue with it.

 

[hell_knight]

It's strange because it's supported and it let me overclock it without issues

my cpu snapshot --> http://valid.x86.fr/tk5wyz

 

[GhislainG]

http://support.asus.com/Cpusupport/List.aspx?SLanguage=en&m=Sabertooth%20X58&p=1&s=29 doesn't show any Xeon processors. Where did you find the X5660 is compatible?

 

[hell_knight]

http://support.asus.com/Cpusupport/List.aspx?SLanguage=en&m=Sabertooth%20X58&p=1&s=29 doesn't show any Xeon processors. Where did you find the X5660 is compatible?

With the latest bios update that allows compatibility with 980x, asus support told me that the xeon would be compatible with the mobo. Also, dozens of other users have the same mobo and processor and run them without issues. I also tried an x5650 (the same as x5660 but different clock) and it showed all the info about the processor including caches.

Also in bios, it recognises all the caches (l1 to l3) and physical cores.

It's a weird thing, I reinstalled both Cpu-z and OCCT to no avail.

 

[GhislainG]

Then the X5660 isn't fully compatible or there's an issue with it.

 

[hell_knight]

Then I'll go with "partial compatibility" since it is working as it should

Thank you very much GhislainG!!!

 

[GhislainG]

That's probably what I'd also do if everything works fine and benchmarks meet expectations.