Soldato
Bummer 
-
Competitor rules
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Odd Phenom 9850 behaviour
- Thread starter NightmareXX
- Start date
So now presuming I have to return it in order to get a working one, how do I go about explaining what's wrong with it?
If I say to use Prime95 blend test and it crashes would that be proof enough or too specific to be looked at?
It's been working fine for 3 months and only started going funny today or I only noticed it today
If I say to use Prime95 blend test and it crashes would that be proof enough or too specific to be looked at?
It's been working fine for 3 months and only started going funny today
or I only noticed it today
just say sometimes it crashs when u doing things and you've tryed it in different system but same thing happens..
if u get a blue screen than take a photo of it.
they'll ask for the serial number of the cpu which lets them know how long left it as for warranty. so no need for proof of purchase.
9 out 10 amd won't test it, they'll just replace it..
if u get a blue screen than take a photo of it.
they'll ask for the serial number of the cpu which lets them know how long left it as for warranty. so no need for proof of purchase.
9 out 10 amd won't test it, they'll just replace it..
Last edited:
Soldato
Hi mate, how new is your build? I've got the M2N78-AM board myself and I had some "weird" graphics issues with it, basically I thought it was a RAM thing, I've maxed out the board with 8GB (4x2GB) and I had to swap out one of the RAM chips. But apart from that it's been okay, but you seem to have eliminated RAM as a problem. I can't see it being a CPU issue myself, IME they tend to be much more obvious.
Best of luck with it though
Well that PC is almost solely used for Rosetta@Home so I don't use it too much. CPU load is at 100% constantly though. It's about 3-4 months old.
The graphics problems are just a more obvious sign of the problem. It will fail a linpack test at stock settings which as far as I'm aware, no CPU ever should. The last few R@H units it did ended up in a computation error and as it relies on floating point calculations, it would suggest a CPU/memory problem.
I've checked the RAM by swapping it out with 2 separate sets, the stuff that was in there and the stuff in my server. I know both sets are clean as they both passed memtest. As I've then eliminated the RAM problem, that only leaves the CPU.
The graphics problems are just a more obvious sign of the problem. It will fail a linpack test at stock settings which as far as I'm aware, no CPU ever should. The last few R@H units it did ended up in a computation error and as it relies on floating point calculations, it would suggest a CPU/memory problem.
I've checked the RAM by swapping it out with 2 separate sets, the stuff that was in there and the stuff in my server. I know both sets are clean as they both passed memtest. As I've then eliminated the RAM problem, that only leaves the CPU.
Sent the chip back and they found it faulty so I've got a new one now 
Well got my new chip installed and on installation was working perfectly fine. I then fired up BOINC and left it to do it's thing. Checked it just now and it's doing exactly the same thing as the last one and because of that, it's now broken. AGAIN!
What're the chances of 2 processors failing with the same problem? What else could it be?
How can I test the motherboard, that being the only other component that could fail, without killing another CPU? Could one of the MOSFETS or something have died and keep killing the CPU when it draws that much power?
I presume a static shock from me to the processor could also kill it but giving exactly the same effects? Surely that isn't right.
What're the chances of 2 processors failing with the same problem? What else could it be?
How can I test the motherboard, that being the only other component that could fail, without killing another CPU? Could one of the MOSFETS or something have died and keep killing the CPU when it draws that much power?
I presume a static shock from me to the processor could also kill it but giving exactly the same effects? Surely that isn't right.
Last edited:
I tried that the first time and yet got the same problem. My friend pointed out to me, could the motherboard fry the CPU and render it unusable?