| 1 |
On 17/04/2022 18:28, Mark Knecht wrote: |
| 2 |
> Echoing Jack's comment, I'm not sure this is a heat |
| 3 |
> sink problem. Misoperation at the time of letting |
| 4 |
> go of the reset button prior to POST. If the machine is |
| 5 |
> starting cold a processor wouldn't overheat that fast but |
| 6 |
> I haven't yet read all of your thread. |
| 7 |
> |
| 8 |
> I think there's also an opportunity here to do some sort |
| 9 |
> of remote debug with you if we can find anything that does |
| 10 |
> boot. |
| 11 |
|
| 12 |
On quite a few occasions I've had machines that won't boot. Memory is |
| 13 |
notorious for causing a black screen on boot, no beeps, no nothing. |
| 14 |
|
| 15 |
My first PC (Cyrix 686) eventually cured itself after I'd reseated the |
| 16 |
memory 3 or 4 times. This machine, I nicked its 2x8GB for another |
| 17 |
machine and replaced it with 2x16GB - that took several reseats before |
| 18 |
it eventually worked. I'm sure I've had others ... |
| 19 |
|
| 20 |
Okay, if Jude is blind he wouldn't see if the problem is "nothing |
| 21 |
happening", but on any machine that won't do anything that is the first |
| 22 |
suspect... |
| 23 |
|
| 24 |
The other thing is, if the mobo and processor aren't bought as a |
| 25 |
"matched pair" you could get hit like I did with the first incarnation |
| 26 |
of this machine - the mobo and cpu were allegedly compatible, but the |
| 27 |
bios wasn't - I had to RMA the mobo, they upgraded the bios, and then |
| 28 |
everything allegedly was hunky dory. I still haven't rebuilt that mobo |
| 29 |
though ... |
| 30 |
|
| 31 |
Cheers, |
| 32 |
Wol |
Archives