• 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.

920 lost a core..

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: RichUK
That is harsh. So it looks like it is damaged permanently?

Stevty, i think you should jump on the Yonah bandwagon, and get some OCing action out of that. When mobos and Yonah CPU's become available that is 😀

I most likely will give a dual core yonah a try, considering how well my Dothan OC's on stock voltage with that dinky little heatsink.

This just really sucks, I've never killed/damaged a CPU before, even my 266mhz pentium-2 thats been OC'd to 300mhz since 1998 is still chugging along.
 
Also, have you tried to underclock it; the high voltage may have caused instability but may still be able to run at a lower speed, say 2.5-2.6; you never know.
 
Originally posted by: Hard Ball
Also, have you tried to underclock it; the high voltage may have caused instability but may still be able to run at a lower speed, say 2.5-2.6; you never know.


I did actualy try to underclock it, but the motherboard won't let me lower the FSB below stock.
 
Well I tried it on my P5P800-SE. Same thing, windows crashes at the same exact place, with the stop 7F error, including safe mode. I can't disable the second core on that motherboard. Never killed a chip before but I guess there's a first time for everything :disgust:
 
Well I suppose when I get my taxes back, once some of the motherboards listed here become available, I'll get a dual core yonah and give it a try.
 
Originally posted by: stevty2889
Well I suppose when I get my taxes back, once some of the motherboards listed here become available, I'll get a dual core yonah and give it a try.

The AOpen 975Xa-YDG looks interesting.... Not enough VDIMM for my liking though.... I really do not care for the other SFF boards with the i945GT. Perhaps ABIT will throw a bone in with the i975X.... 😉

 
They are selling dual core yonah's on zipzoomfly, so as soon as one of these motherboards becomes available I'll pick one up.
 
Looks like the Aopen board may only support up to 266mhz FSB, so if I go with it, I'll get a 1.83ghz yonah, giving it the potential to reach about 2.9ghz. If yonah overclocks anywhere near as well as Dothan, it could potentialy do that on stock voltage.
 
Every generation of CPUs is different, especially when a new process manufacture is released. OCing chips like this type may be a big risk right now unless stock voltage is used. 65nm is really really tiny. It's bound to be really sensitive to voltage deltas and increased noise. This is a totally new generation of CPU technology and a lot of the old OC rules may not apply apply anymore. You pioneered one of these chips and you just got an arrow in the back.

I also think a problem is that while CPU technology has raced ahead, we're also using pathetically ancient PSUs that haven't substantially changed in 20 years. When you're working on the nanoscale like these chips are, there is no way to to truly know exactly what went wrong when a core goes. It might have nothing to do with any OCing practices. It could be a miniscule spike from the PSU or a rectifier.

All I know is, with 65nm or less, I doubt I'll ever OC those muvvas when I get them.

As they say in the cop shows, I'm sorry for your loss. I've also had some painful experiences lately.
 
I'm just wondering if my problem is related to the supposed bug with the 920/930 that was reported a while ago, I might play around with it some more to see if I can get my second core stable again. For now it's chugging along fine on a single core.

I might try it on my Asrock 775dual-880pro again, since I can underclock it on that motherboard. I can't underclock it on either of the Asus boards.
 
Well, after setting the vcore to 1.425v, and the PCIe to 105mhz, so far it's been dual prime95 stable for just over a 1h 20m with both cores. This chip is drivin me nuts..

EDIT: And still going after 2 hours..
 
I'm glad that eveything is back to normal.... 🙂 Hopefully, it will stay that way.... 😉

EDIT: "Normal" meaning both cores functioning @ 2.8GHz. Keep us posted on whether it will hold-up under OC'ing....
 
Yeah, I'm at stock speed, I was actualy at stock speed when the problem started. Not sure why it's working now, the only thing I did differant this time, is set the PCIe to 105mhz. Upping the vcore previously didn't help, trying it another motherboard didn't help, so it's strange that it's gone for 3 hours without a problem, since it didn't last 30 minutes before.
 
Originally posted by: stevty2889
Yeah, I'm at stock speed, I was actualy at stock speed when the problem started. Not sure why it's working now, the only thing I did differant this time, is set the PCIe to 105mhz. Upping the vcore previously didn't help, trying it another motherboard didn't help, so it's strange that it's gone for 3 hours without a problem, since it didn't last 30 minutes before.

glad to here you got your core back you going to oc again now?
 
Originally posted by: Cooler
Originally posted by: stevty2889
Yeah, I'm at stock speed, I was actualy at stock speed when the problem started. Not sure why it's working now, the only thing I did differant this time, is set the PCIe to 105mhz. Upping the vcore previously didn't help, trying it another motherboard didn't help, so it's strange that it's gone for 3 hours without a problem, since it didn't last 30 minutes before.

glad to here you got your core back you going to oc again now?

Gonna make sure it's stable at stock for at least 24 hours before I think about overclocking it again.
 
Originally posted by: stevty2889
Originally posted by: Cooler
Originally posted by: stevty2889
Yeah, I'm at stock speed, I was actualy at stock speed when the problem started. Not sure why it's working now, the only thing I did differant this time, is set the PCIe to 105mhz. Upping the vcore previously didn't help, trying it another motherboard didn't help, so it's strange that it's gone for 3 hours without a problem, since it didn't last 30 minutes before.

glad to here you got your core back you going to oc again now?

Gonna make sure it's stable at stock for at least 24 hours before I think about overclocking it again.

only 24hours? after all the trouble, test it with two instances of prime95 for like 24 hours and play around on the computer for a few days...perform a few restarts and cold boots...
 
Originally posted by: Unkno
Originally posted by: stevty2889
Originally posted by: Cooler
Originally posted by: stevty2889
Yeah, I'm at stock speed, I was actualy at stock speed when the problem started. Not sure why it's working now, the only thing I did differant this time, is set the PCIe to 105mhz. Upping the vcore previously didn't help, trying it another motherboard didn't help, so it's strange that it's gone for 3 hours without a problem, since it didn't last 30 minutes before.

glad to here you got your core back you going to oc again now?

Gonna make sure it's stable at stock for at least 24 hours before I think about overclocking it again.

only 24hours? after all the trouble, test it with two instances of prime95 for like 24 hours and play around on the computer for a few days...perform a few restarts and cold boots...

When I said stable for 24hours I did mean dual prime95 stable..not gonna do any restarts or reboots until it's been prime95 stable for at least 24 hours.

8 hours and still going..
 
Well I don't know whats differant, but it's been dual prime stable for 26 hours now..don't know what caused the problem, nor do I know why it started working again..
 
Back
Top