CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,212
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
Anecdotal observations suggest that after a complete power down, the motherboard's firmware performs a more exhaustive restart procedure. One step in the procedure appears to be a full scan for any hardware changes that might have taken place. As a result, any 'state of the system' parameters stored in CMOS are removed and re-created. This has the effect of "detoxifying" a number of corrupted system state parameters.Hi Casey. So I followed these instructions up to Reset CMOS the easy way and that seems to have worked. I haven't experienced the same problem again, and hopefully it will stay that way.
Is there somewhere I can read about why this worked/why it was a possible solution? I'd like to understand that, given that fixes that involve literally unplugging it and plugging it back in aren't very satisfying.
Whenever we install or remove any device connected to the motherboard (SATA hard drive, NVMe M.2 drive, PCIe cards, USB devices connected to F_USB header) we must not only shut down, but remove the power cable (or flip the power switch on the power supply). Failure to do so can corrupt the firmware's state information.And now for a few questions about getting more info when troubleshooting:
I've experienced 3 or so kernel panics when starting up that have all been remedied by just shutting my machine off and trying to boot again. While I did take a picture of my screen the last time it happened, the string before the line about reporting the panic to apple was "@kec.Libm 1". If/when this happens again, where can I find the whole log? I haven't seen anything in /Library/Logs/DiagnosticReports referencing a panic.
One other time my whole system froze and I had to force shutdown. When I booted back up I also looked in the same folder for any logs that may have been generated but found none. Is there anything else I could be doing to gain more insight?
If the system freezes during use, that is a different problem and may be due to the application you were using at the time, or it may be due to a device driver for a connected peripheral.