I heard from Gigabyte tech support and had to go into more detail on the problem. They had a hard time with the apparent 31-day cycle of the non-start event. This has pretty much baffled everyone. I held off updating the BIOS until I could hear from them and will wait another day or two. There is no urgency here, knowing how to get the machine back. If it hasn't been solved by the beginning of August, I am going to try simply unplugging for a few minutes before what I have been doing.
I will post again when I hear back from Gigabyte.
I thank EB-1 and others for the insight offered. Some of my concerns with incompatibility have been lessened.
I wanted to update my communications with Gigabyte.
They want me to pull one stick of RAM and place it in a slot, then try in another slot. I have asked for further guidance on the expected re-occurrence on August 5.
"I don't know if I mentioned, if it occurs on the expected date, I will attempt to simply unplug the machine for a few minutes instead of the normal procedure of removing the GPU.
There are no settings or scheduled tasks that would cause the system to stop booting specifically on the 31st day. The reason we asked about the status LEDs during the no‑boot event is because you reported that the board was stuck on the DRAM LED.
When the DRAM LED is active, it means the motherboard is not detecting or training the memory at that moment. Even if the issue only appears once every 31 days, intermittent memory‑training failures can still occur due to slot sensitivity, marginal contact, or CPU‑socket pin alignment. These problems do not always present daily—they can surface only under certain reboot or training conditions.
Because the LED indicates a memory‑detection failure, we asked you to focus on the memory path:
Testing A2 and B2 individually
Inspecting the CPU socket pins for any irregularities
These steps are necessary to confirm whether the intermittent DRAM hang is caused by the DIMM slots, the memory modules, or the CPU‑socket interface.
It appears the 31-day cycle has been broken. If following the pattern, August 5th should have been the day the computer didn't boot normally. I have looked at various things in PowerShell, the Event Viewer, and run scripts over the past month, viewing and/or correcting errors. I believe the likely fix was, first, resetting the CMOS, and second, reseating the RAM sticks, performing tasks Gigabyte had me do to attempt to troubleshoot the issue.
The machine is booting and shutting down faster than before. The thread is done.
Glad to hear you have it resolved Personally, I grew tired having to deal with issues like this over the many years of building PC's. Made the switch to MAC. Life has been less complicated since. YMMV
It's not about Apple, it's about buying a pre-built vs. self-built machine. Many of us have corporate machines that run various OS (not just Windows) and various programs that have a warranty and support program, sometimes on site. If tech support cannot fix it over the phone or reinitialize it has to go in for service or replacement just like Apple or any other prouduct.
I generally advise those not familiar with a technology to buy products from someone local or pre-built with warranty and support. I enjoy working with compuuters, but some don't. OTOH, I don't like working with automobiles. If you ask me to change any fluids or filters, I'd pay just about anything to avoid it.
schlotz wrote:
Glad to hear you have it resolved Personally, I grew tired having to deal with issues like this over the many years of building PC's. Made the switch to MAC. Life has been less complicated since. YMMV
As I'm now on the backside of my 72nd trip around the sun, I don't want to learn a new system, but my machine is less than a year old, also. This is number five since 2014, and the first time I have had this kind of problem.
Windows updated last night when I shut down, so I was a bit nervous at startup this morning, but here I am.