• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dude, where's my core

Hi guys,

I have a core2duo e4300 procc. and asus p5b vanilla motherboard...

For some days i've noticed, that Intel TAT shows one of my core grayed out, like this
TAT.jpg

It wasn't always like that, earlier both cores were available, and I was able to stress them using it.
Also System Information in BIOS shows Count=1 in Processor, I think earlier it used to be 2(maybe someone can confirm?)

However I can see both cores in Windows Task Manager, and other core activity also shows up...I'm using WinXP Prof. SP2

I was using BIOS 1101 but after arrival of problem, I've upgraded to latest 1202 Bios, but it dosen't help and also I've done a fresh install of windows too, but that too isn't helping...

So any ideas, what's causing this..?

Regards,
 
lol, nice thread title.

as for your problem, i dunno, its weird that it shows temps though. but since you can see core activity in task manager, what i would do is run some kind of benchmark that really takes advantage of dual cores. if it gives you about an equivalent score for an e4300 then you'll know both cores are active, and if it gives you a much lower score (bit more than half probably), then you'll know it's not using both cores. find that out before you do anything else.
 
Yeah, nice idea, i'll report in w/ results asap..

EDIT: Okay, I used superprime, and results of benchmark shows I can use the 2 cores... :beer:
Still would like know, why's TAT acting weird..?
 
lol, no idea...but if i were you i wouldn't even care, because if it were me trying to fix it would inadvertently mess up something else lol. if it works, don't mess with it. glad to hear that it does work, though.
 
Originally posted by: MarcVenice
Could 1 of the cores actually die, because of overclocking, leaving the other 1 intact ?

no, it just wouldn't be a stable overclock; if you overclocked it enough to 'kill' one of them, then you're not very good at overclocking because it would be very unstable long before you reach that limit.
 
Originally posted by: MarcVenice
Could 1 of the cores actually die, because of overclocking, leaving the other 1 intact ?

Well I've OCed it, but haven't gone past 2.6GHz, that too not for long time 'cause i'm on stock cooler, the system was perfectly stable though..

The rest of the time, I let AI NOS handle the overclocking, it automatically clocks the chip at 2162MHz(20% higher) when CPU load increases

Originally posted by: f4phantom2500
lol, no idea...but if i were you i wouldn't even care, because if it were me trying to fix it would inadvertently mess up something else lol. if it works, don't mess with it. glad to hear that it does work, though.

That's what I was doing till now, until I noticed the proccessor count in BIOS also as 1,
I'm pretty sure it used to appear as 2 earlier....the TAT bug(if u may call that), was discovered by me a month ago..
But I guess i'll continue it that way only, since I've made sure, its working..
 
what do you see when you go into the Device Manager do you see ACPI Uniprocessor PC or ACPI Multiprocessor PC ?
 
Originally posted by: MarcVenice
what do you see when you go into the Device Manager do you see ACPI Uniprocessor PC or ACPI Multiprocessor PC ?

^ This is an important question posted by Marc.

Also, You can use CPU-Z to see if it recognizes two cores.
 
Originally posted by: Amaroque
Originally posted by: MarcVenice
what do you see when you go into the Device Manager do you see ACPI Uniprocessor PC or ACPI Multiprocessor PC ?

^ This is an important question posted by Marc.

Also, You can use CPU-Z to see if it recognizes two cores.

Well both recognize the two cores 😕
Wonder what's screwing up TAT, its no Windows related fault, 'cause i've done a fresh install...
 
Back
Top