I've been having a problem where my Windows 10 PC would randomly become completely unresponsive, sometimes BSOD but other times just freezing where the monitor screen would retain the last frame but keyboard/mouse are totally unresponsive (or sometimes monitor goes black). Hard reset is required. This was at first every few months, then weeks, and now it's every 15-40 minutes. After testing other known good PSUs, graphics cards, RAM, and network cards, I moved onto seeing if my main NVME was the problem hence cloning my Windows install to a different NVME via Rescuezilla. I created a USB drive with Rescuezilla on it and booted it to start the clone.
Unfortunately, 4 seconds into 'Step 6: Cloning Disk', the screen has also completely frozen, keboard/mouse seem unresponsive just like in Windows. I'm thus unconvinced that this is actually Rescuezilla even though it could be a UI lack of update, not sure - it just seems wrong that it's saying 'Elapsed: 00:00:04' for the past 20 minutes. I didn't select the option to ignore bad sectors.
I'll be restarting it again soon, but wanted to check if this behavior is known when using Rescuezilla or if there are ways to run it that could avoid a freeze If not, this probably rules out the NVME drive being the problem (since it didn't boot from the NVME, but I could be wrong) and I'm a little stumped on what else the problem could be. If any PC builders read this, do you have any ideas? Can the motherboard itself cause something like this? It's got an AMD 5950x and GPU/CPU temps seem fine.
Last edit: Ryan W West 2024-03-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, there haven't been any freezes in 14 hours while idling in the BIOS msi motherboard setup menu. So perhaps the freeze was still related to the NVME hosting the Windows 10 install as the clone operation started reading from it right when the freeze occurred. This brings me back to my question of if this type of freeze in Rescuezilla can happen with NVMEs going bad and if there are ways around it.
Running CHKDSK on this NVME also stalls out at stage 4, though the windows progress spinner keeps spinning for days so at least that one isn't 'visually' frozen.
Last edit: Ryan W West 2024-03-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been having a problem where my Windows 10 PC would randomly become completely unresponsive, sometimes BSOD but other times just freezing where the monitor screen would retain the last frame but keyboard/mouse are totally unresponsive (or sometimes monitor goes black). Hard reset is required. This was at first every few months, then weeks, and now it's every 15-40 minutes. After testing other known good PSUs, graphics cards, RAM, and network cards, I moved onto seeing if my main NVME was the problem hence cloning my Windows install to a different NVME via Rescuezilla. I created a USB drive with Rescuezilla on it and booted it to start the clone.
Unfortunately, 4 seconds into 'Step 6: Cloning Disk', the screen has also completely frozen, keboard/mouse seem unresponsive just like in Windows. I'm thus unconvinced that this is actually Rescuezilla even though it could be a UI lack of update, not sure - it just seems wrong that it's saying 'Elapsed: 00:00:04' for the past 20 minutes. I didn't select the option to ignore bad sectors.
I'll be restarting it again soon, but wanted to check if this behavior is known when using Rescuezilla or if there are ways to run it that could avoid a freeze If not, this probably rules out the NVME drive being the problem (since it didn't boot from the NVME, but I could be wrong) and I'm a little stumped on what else the problem could be. If any PC builders read this, do you have any ideas? Can the motherboard itself cause something like this? It's got an AMD 5950x and GPU/CPU temps seem fine.
Last edit: Ryan W West 2024-03-22
Well, there haven't been any freezes in 14 hours while idling in the BIOS msi motherboard setup menu. So perhaps the freeze was still related to the NVME hosting the Windows 10 install as the clone operation started reading from it right when the freeze occurred. This brings me back to my question of if this type of freeze in Rescuezilla can happen with NVMEs going bad and if there are ways around it.
Running CHKDSK on this NVME also stalls out at stage 4, though the windows progress spinner keeps spinning for days so at least that one isn't 'visually' frozen.
Last edit: Ryan W West 2024-03-22