Dual Core CPU is stuck at ONE core! (HELP!!!)

az123

Honorable
Aug 4, 2013
56
0
10,630
(Sorry that this is so long, didn't expect it to be :/)

Hello, I've been really frustrated since I got my new processor which is a 1045t .

http://www.newegg.com/Product/Product.aspx?Item=N82E16819106012

My PC model: ET1331G-03w
Motherboard model: MCP61PM-GM
BIOS: AMI P01-A2L

I have a 430watt PSU installed and used to have a 6670 core edition installed. A friend gave me his GeForce GTX 550ti which obviously bottlenecked my computer because of my CPU. So I ended up getting this CPU without really doing research on my mobo since I didn't have knowledge on it, (but now I understand.)

If you looked at my mobo you can see that it can only supports up to 89 watts. Which is just like 4-6 watts off. So I thought about underclocking my CPU but I cannot edit any of my CPU settings in my BIOS. So I'm stuck there. When I try to run AMD OverDrive I can't open it because it says "AMD OverDrive cannot detect supported AMD chipset on this computer." which I don't understand because obviously I have an AMD CPU. Unless it's not meant for it.

And I also believe that my motherboard and CPU aren't compatiple since my mobo recognizes my CPU as this . . .
http://puu.sh/93MWg.png

"Dual-Core AMD Opteron(tm) Processor 130400 Dial- 804MHz"
So then I just gave up running at 804Mhz since it was so damn slow and put back my old CPU which is a AMD Athlon II X2 235e.

Anyways when I put back my old CPU I noticed that my CPU was running at 100 percent (the majority of the time) and when I went to msconfig to just check if my CPU was running on two cores and I see that it was on 1, I tried changing it and I see that only one core is available. I went to Device Manager to see if both of my CPU cores are on there, AND THERE WERE. So now I'm just really confused and now I really need help. Yeah, that's pretty much it. Thanks.


 
Solution
1) I don't agree with the above. For one thing, his system WAS working and he's gone back to the original CPU. He shouldn't be having issues.

2) If the CPU wasn't supported it shouldn't even boot. The CPU model needs to be in the BIOS. That's the reason Asus created BIOS Flashback that doesn't need a CPU to flash the BIOS. It's because unrecognized CPU's won't even let the computer start at all.

So again, if the computer boots the CPU isn't the issue.

3) SOFTWARE appears to be your problem. Not in order:
a) Try removing/reinstalling motherboard drivers such as the MAIN CHIPSET etc. (from motherboard support site)

b) If you have a SPARE drive, unhook other drives then install Windows + drivers long enough to confirm the TASK MANAGER...

Jake Lloyd

Reputable
Feb 27, 2014
291
0
4,960
While you are able to fit a AM3 CPU into a AM2 socket, you're not going to get the wattage needed, as you have found out. You did luck out in that it actually booted, but it is going to misinterpret the CPU as... something else. If you can't update the BIOS anymore, then it's time to get a new MB.
 
1) I don't agree with the above. For one thing, his system WAS working and he's gone back to the original CPU. He shouldn't be having issues.

2) If the CPU wasn't supported it shouldn't even boot. The CPU model needs to be in the BIOS. That's the reason Asus created BIOS Flashback that doesn't need a CPU to flash the BIOS. It's because unrecognized CPU's won't even let the computer start at all.

So again, if the computer boots the CPU isn't the issue.

3) SOFTWARE appears to be your problem. Not in order:
a) Try removing/reinstalling motherboard drivers such as the MAIN CHIPSET etc. (from motherboard support site)

b) If you have a SPARE drive, unhook other drives then install Windows + drivers long enough to confirm the TASK MANAGER shows the currect number of CPU's. Don't Activate, this is just to see if the basic hardware is working.

c) Flash the BIOS if newer exists (not to recognize CPU, just in case of other issues)

d) Clear the CMOS (See motherboard manual) and redo any necessary BIOS settings

e) Make sure that your BIOS isn't set to only one core (doubt it).

f) Burn an UBUNTU disc and boot to it (don't install) then see if it works and how many cores are being used (Google for how to view the equivalent of Task Manager).

 
Solution