Mick wrote: > On Sunday, 10 June 2018 14:06:22 BST Alan Mackenzie wrote: > >> The shop I bouught everything from seems to have gone out of business, >> with both its telephone number and its website having been down for a >> sustained period. So I'm unlikely to be able to get the processor >> exchanged for an unbuggy one. Shelling out for a new processor out of my >> own pocket seems too much of a long shot to justify the money (~400 >> Euros) and the time. >> >> So it's looking like I'm not going to be getting the problem fixed any >> time soon. :-( > All may not be lost, yet. > > Since this is arguably a manufacturing fault of the CPU, you should have some > consumer rights over it. Try contacting AMD directly for RMA, as long as it > is still under the *manufacturer's* warranty and you have your receipt. >
Plus trying to talk to them may lead to them knowing what the problem is. Whether it is mobo or CPU, knowing which one would help. They may have heard of this issue before. To, OP. I was hoping you found a solution. Maybe you will at some point, You have certainly eliminated a lot of potential causes. I can't recall if you have or not, have you tried a different version of the kernel? In the past, I've upgraded to a new kernel and it be buggy. I go back to a older version until I see a new update then try again. Generally it works. Don't know if it was a kernel bug or just some stray code that something didn't like but . . . Dale :-) :-)
