My HD went bad and it seems like there is a processor problem with some AMD processors. The core voltage seems to drop and then the clock falls off and strange things happen. From a quick look at the AMD boards, it seems this happens in 8 core processors. Strange this did not happen when I did not have the new 560's in the computer??

Sorry to have not had the forethought to shut down GPU processing as I was too involved with restoring the system as it also caused (apparently) bad writes to the HD. There are just too many errors on the GPU (down to one as apparently one just stopped working).

I am going to persue this problem on the AMD site as the voltage needs to be stabilized before I can even attmept to look for the erros from the GPU.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I've had a similar issue with one of my AMDs, I traced it back to a slightly soft motherboard voltage regulator - not soft enough to cause under voltage trips, but soft enough to give some very strange results (I hasten to add this in not on one of my crunchers but another machine that works for its living) Cure was a bit of very delicate soldering assisted by lots of expletives...

(Tip of the year: GTX560s do NOT like strong sweet coffee, nor do their hosting motherboards...)

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I've had a similar issue with one of my AMDs, I traced it back to a slightly soft motherboard voltage regulator - not soft enough to cause under voltage trips, but soft enough to give some very strange results (I hasten to add this in not on one of my crunchers but another machine that works for its living) Cure was a bit of very delicate soldering assisted by lots of expletives...

I do not think that could be it, I have now tried the 560s in two different computers with different CPUs and MBs.

But it may be the 560 that is causing this as that is the only common factor. No that is not true, I think the Power Supply is the same. I am not certain if I tried a different one or not. I will have to check that out as soon as I get a chance.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

What power supply are you using, as those cards can be very picky about them.

Cheers.

---

What power supply are you using, as those cards can be very picky about them.

Cheers.

Sorry to take so long in replying but right after this posting I went to the hospital and am just getting back.
I am using an ULTRA 1400......but the 560s are history. One seemed to just fail so I continued on the other one and it also just failed.

I have to get at sending them back....

This particular computer basically was down for a month as I had a system HD failure on it and when I went to restore the image backup it would not restore. Between over 2 weeks in hospital and really in a bad way, I could not work on the computer. Finally got the restore to work this past Saturday and now have just a spare video card processing away on this computer now. Upgrades will have to wait until I get back from a trip to visit with my daughter.

Problem was that the image was created from a UEFI system drive and when I put a new HD on, it would initialize as BIOS and you have to have the new drive UEFI as well.......then you have to have the CD drive UEFI as well and use the Windows OS install disk, not the Restore Disk that you have created. There is no way in the UEFI BIOS to actually designate what the drive will be, so it was a lot of doing this and that. Putting on an external CD drive, which came up as UEFI (for what reason I do not know) was what got me going. Doing a Windows install from that drive made the OS Drive, C:, a UEFI drive so I was able to proceed from there with the restore.

Oh yes, I will probably not go with the same video cards.........even though I found out what the problem was, it was the Cool & Quiet setting in the BIOS which for some reason is partially on by default even in the none basic setup. That kept the voltage flat and the cores were processing perfectly after I disabled that, but the fluctuating clock speed had caused some bad writes to the HD and that is why I had to replace it.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Problem was that the image was created from a UEFI system drive and when I put a new HD on, it would initialize as BIOS and you have to have the new drive UEFI as well.......then you have to have the CD drive UEFI as well and use the Windows OS install disk, not the Restore Disk that you have created. There is no way in the UEFI BIOS to actually designate what the drive will be, so it was a lot of doing this and that. Putting on an external CD drive, which came up as UEFI (for what reason I do not know) was what got me going. Doing a Windows install from that drive made the OS Drive, C:, a UEFI drive so I was able to proceed from there with the restore.

My MB is a UEFI as well , I wonder if that could be the problem I have been having with my system as posted in :

http://setiathome.berkeley.edu/forum_thread.php?id=71372

---

Floyd, it does not look like it could be as it will either work or not. If you look at your disk in Disk Management it will show the "hidden" system partition as UFI. It is a different Boot Manager and will either work or not, it will not be intermittent. (I had read you thread before and did not think it applied).

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours