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