faulty CPU

[mb2]

i have an option of getting a T-bred 2600+ for just the price of P&P, but it is a little faulty i think the cache is burnt out and it fails prime 95 after a short while.. it reports on CPU-Z as a duron.. he put 2v through it (though the temps didn't go much above 50C apparently) is this likely to have burnt out the cache, and could it have caused any other problems?
is it likely that if i disabled the L2 cache, it would work ok? (as a duron)..
is it possible the L1 cache, or anything else is damaged, and can you disable the L1 cache (would it give a serious performance hit?).
is L2 cache disabling available in the bios in most motherboards? or all? or a select number? how about the NF7?
how about L1?

i think it runs ok when its not OCed? is this normal and therefore is it likely to be cache the problem?

 

[3LEMENT0]

I wouldn't wanna waste my time on a chip that I know will give me problems...but that's just me.....

 

[Nemesis2038]

I had something similar happed to me in the days of the P90 when the cpu cooler froze up from dust/dirt. Disabling the cache in the bios corrected it but it was a dog after that. That was definatly a toasted chip but still worked.

I would say if your overclocking it still drop it back down and see if that cures the problem.

You can then attempt to work your way up from there. Sometimes if you bluescreen windows XP at the wrong point from too much of an overclock the OS becomes unstable. In most cases the OS is corrupt not the chip.

I highly suggest before overclocking installing the OS and GHOSTING the image to another drive and verifying stability with something like Prime. Then Work with your overclock and if you bluescreen a few times restore the OS from the ghosted image. Because you may be thinking your overclocking too far when its that one time you went too far and corrupted your OS or Application.

I usually never go above the 1.85V on an AMD chip because I havent seen much overhead you can get from there going higher without dealing with heat issues for a minature amount of more performance that is just a drain on the wallet for special cooling. I dont do water so thats not my area.

1.85v allows you to run the chip cooler and quieter. Going above that usually only yeilds around 100mhz more but then cooling is a pain unless you like jet noise. 1.85 I can have virtual silence only hearing the case fan or power supply. Sometimes I can hear the hard drive work. Thats worth the 100mhz decrease.

 

[jiffylube1024]

Originally posted by: mb2
i have an option of getting a T-bred 2600+ for just the price of P&P, but it is a little faulty i think the cache is burnt out and it fails prime 95 after a short while.. it reports on CPU-Z as a duron.. he put 2v through it (though the temps didn't go much above 50C apparently) is this likely to have burnt out the cache, and could it have caused any other problems?

Yes, most definately. 2v can and will fry any Tbred CPU (especially a mobile one). It's amazing that it didn't take the rest of the CPU with it.

is it likely that if i disabled the L2 cache, it would work ok? (as a duron)..

It could work, but not as a Duron. Durons also have L2 cache, just less of it (64K for the older ones; I think newer Durons have 128K or 256K of L2).

is it possible the L1 cache, or anything else is damaged, and can you disable the L1 cache (would it give a serious performance hit?).

It's possible the L1 cache is damaged. There is no way to disable L1 cache, and if you did, it would be INSANELY SLOW. Think about it, if you disable L1 and L2 cache, every single CPU process would have to go through system memory (2-4GB/s of bandwidth vs. 16 GB+).

is L2 cache disabling available in the bios in most motherboards? or all? or a select number? how about the NF7?
how about L1?

I think L2 cache disabling is on most good boards; I'm pretty sure the NF7 has it. If not, there is software that can do it in Windows.

i think it runs ok when its not OCed? is this normal and therefore is it likely to be cache the problem?

Well, yeah! Of course it's normal for some chips to not run properly when overclocked.

Personally, I'd stay away from this 'damaged goods' CPU - even if it works it sounds like it will die soon, or at least lose even more functionality.

 

[mb2]

well.. it might have crap performace (not imo) but for the price of P&P i dont care.. i think it works ok when the OC is backed off from.. yea; at 200x10 w/ 1.7v it passes P95 for 10 hours with no errors..
since i'll be pairing it with a SDR/DDR motherboard.. i'll be able to upgrade the PC from a 400mhz celeron to a 2ghz+ duron (and the cache doesn't make much difference i dont think, it runs w/ 64kb of l2 cache) for just the price of a motherboard. should make a nice office PC.

'I wouldn't wanna waste my time on a chip that I know will give me problems...but that's just me..... ' seems like it wont.. and better than wasting my money IMO

it wasn't me who burnt out the CPU.. i'm just getting it free off someone who burnt theres.

its not a mobile t-bred.. although i was thinking of getting one of these aswell.. a 1500XP-M... should overclock to 2.3-2.5; and cost half of an XP-m. why would the mobiles fry earlier than the desktops?
its not the case with the barton mobiles.. they can take just as much voltage, they just dont need as much.
are u sure this is the case? someone testing one got it to post (but not into windows) @ 2.7ghz @ 2.0v.. using a 'heap HS rated to 2100XP' admittedly they didn't sustain it for long i guess.. but still.

 

[imported_michaelpatrick33]

if it runs prime fine for 10 hours at 200 x 10 w/1.7 take and leave it at that level and revel in free Mghrtz

 

[mb2]

if i were to run it at that.. would it be unlikely to die early? i dont want it to die if atall possible/ last as long as possible.

 

[imported_michaelpatrick33]

if it runs prime 95 for ten hours and you haven't disabled the L2Cache then it sounds like it should run fine and the L2 Cache is working fine

 

[mb2]

only 64kb of the l2 cache is reported as working [repoted as duron in CPU-Z].. rather than the 256kb it should have had working originally.. is it possible the whole lot works it just being reported wrong? or the guy using it has it set up wrong?
is it normal for it to disable some of its own cache if some of it isn't working?

and its not going to (likely to) die early right, providing i dont OC the hell out of it ?

mm free mhz lol