(First Ever?) Qx9650 3 cores dead, 1 alive!

[Broly]

Never heard of this happening until today.
The kicker? I never exceed any voltages that were specified on the box.
Meaning I never went over 1.3625 vcore, or 1.36 VTT.
I never fooled with settings I wasn't familiar with...
THe results?:

[jamieuk23]

overclock the 1 core and see how much you can push it

[ZenEffect]

overclock the 1 core and see how much you can push it

:rofl:

my thoughts exactly!

[LivingL@rGe81]

You sure its not a damaged windows driver or a bios setting?

Very sad to lose a top spec processor using such low voltages!

[Broly]

Nope, nto a damage windows driver for sure
I made sure the bios settings are okay, and this is kind of odd to happen, but then again I should have seen ti coming..

:banana::banana::banana::banana:ed up no doub.t

[jcool]

Considering your mobo, NOT fooling with all the voltage options was the mistake you made.
For example if you leave VTT on auto the stupid mobo will raise it automatically as you overclock. If you go to a moderate 3,6Ghz, thinking all is well because you only need a low Vcore, your "OC-friendly" Asus boards upps the VTT for you to around 1,5V - which would have been too much even for a 65nm in the long run.
But it kills 45nm almost instantly. Go thank Asus for your almost-dead CPU.

So remember: ALWAYS set the lowest possible setting on ALL voltage options manually if you have to use Asus mobos.
Do NOT leave them on auto. I have seen the Maximus Formulas giving 1,6V+ vNB just because I went from FSB333 to 400.

[SF3D]

Hi!

Easiest solution is to go in to bios and check your CPU settings. There might be 3 cores disabled and only one core is left to use :) Check that please.

[Broly]

Hi!

Easiest solution is to go in to bios and check your CPU settings. There might be 3 cores disabled and only one core is left to use :) Check that please.

I already did check that.
I said that didn't I?

[knopflerbruce]

Is RMA an option?

This is why I don't use an ASUS mobo if I have other options (like a DFI:D)

It would be fun if the auto settings could actually kill the board itself, just because of that increasing voltage.:rolleyes:

If I were you I'd buy a CHEAP dual core, just to see if it has both cores "enabled". (I think you get the idea...)

[Broly]

heheheheheh
I have instant instore replacement.
These :banana::banana::banana::banana::banana::banana::b anana:s will cry
They are gonna accuse me of overclocking but they can't prove it so screw them. They owe me a new chip
I paid 100 dollars on top of this chip to make sure I'd get instore replacement :)

[jcool]

It would be fun if the auto settings could actually kill the board itself

Oh you better believe that they can. Most Asus mobos will be dead long before that superfluous voltminder LED goes to red :rolleyes:
Not counting extreme cooling, of course.

[G H Z]

I think someone msconfigged you ;)

[[XC] gomeler]

I think someone msconfigged you ;)

Agreed, this looks more like a software issue than 3 dead cores. Your chip won't suddenly just drop 3 cores, it might have a core or two that's considerably less stable, but not simply stop working. The big indicator is 3 cores.. having a die with half of it working.. no.

[SoF]

now that the chip is f*cked up anyway - give it some juice, make it cold and kick the hell out of it :D

PS: but I start to agree with a f*cked up driver and/or win... ;)

[rob[GL]]

owned

[Broly]

If it was a software issue then alot of programs can bypass that.
Eg. Everest or CPUz can tell me my ram's real timings when the 790i had the cas7 bug where it wouldn't display.
It sure felt like a single core too, boots were slower and things were choppy/slow.

Ifit was an msconfig error I'd know, it's not like I open shoddy porn exe files. I know how to keep my system properly running and I checked everything.

Sure doesn't seem like an msconfig error to me.

[Luka_Aveiro]

Run 3dmark 2006 cpu test and post the score here.

[Cpt.Planet]

Again its most likely a Bios/OS issue. Go ahead and pull the cpu out and the cmos battery out. Let them sit out for 10-15 minutes then go ahead and put it back together. Then boot from a Live Linux or a Bart PE live XP cd and see how many cores it sees.

[Xenogias]

also pull it out and make sure you don't have any missing pins on the zif or pads on the chip.

[NuT]

RMA the board, I had the same prob before and it was the board. :(

[OBR]

you have to test that CPU on another mobo. I am sure this is ACPI software related problem (maybe data corruption). I remember the same thing, reinstall Windows helps me ...

[Leeghoofd]

I second a reinstall... prolly borked or corrupt install of some sort... nothing wrong with the CPU

[makaka]

Yeah me too i am pretty sure that this is a ACPI windows problem , make a clean reinstall .

[Lestat]

its not ACPI
ACPI is IRQ steering for the most part.
its the HAL file chosen by the system during the intial install. F5 during the windows pre-installation bootup lets you choose the configuration to use. (same time and place you hit F6 to isntall raid drivers) well for XP and Win2K atleast.
the sytem probably used the wrong hal file for the install.
or if its an old install when the system booted for the first time it installed the Single core ACPI HAL file.

go to device manager, click the + sign next to 'Computer', tell us what it says.
it SHOULD SAY
ACPI MULTIPROCESSOR PC
if it says anything else then it the wrong HAL file.
http://img354.imageshack.us/img354/8959/200805231112ui5.jpg

[Lestat]

If you need to change the HAL file
right click the item which you see under computer.
Choose Update Driver
Tell NO for checking the internet for a driver click next
click 'Install from a specific location' click next
click 'Don't search, i will choose the best driver to install' click next
You should then see this screen
http://img354.imageshack.us/img354/2553/200805231117pq7.jpg

choose 'ACPI Multiprocessor PC'
Click next and follow the steps and then reboot.
once you reboot you should see 4 cores in device manager and also task manager.


one thing no one has asked is what does your bios say when the system boots (during the POST screen)
it will tell you the type of processor and how many cores it see's along with the amount of ram and speed.

[Shocker003]

Again its most likely a Bios/OS issue. Go ahead and pull the cpu out and the cmos battery out. Let them sit out for 10-15 minutes then go ahead and put it back together. Then boot from a Live Linux or a Bart PE live XP cd and see how many cores it sees.

+1 :up:
Just try what he wrote, i believe it will solve your problem. This happened to to me while i was using P5N-E. I have posted about this issue before, http://www.xtremesystems.org/forums/showthread.php?t=165984 But in my case i it was a driver issue.;)