Discussion A Cautionary Tale About Laziness and Skipping Steps

DSzymborski

Curmudgeon Pursuivant
Moderator
I had been having occasional freezes on getting into Windows in a Crosshair VIII Hero/5900X for a couple of months. It was only occasionally a problem and I don't reboot that often, so I let it go as this is the busiest part of the year for me, work-wise. But I decided to get down to the issue and found it was freezing up from failed Windows updates. I was unable to diagnose that so I figured I'd just do a quick wipe of Windows and reinstall.

So, I went to do that, and while installing Windows, it kept freezing. It did that with any storage drive installed and any install media made in multiple ways, no matter whether I used one stick of RAM or not. The panoply of LED codes was not particularly helpful. So finally, since I value my time a lot more than money, I went out and bought a Crosshair Dark Hero. I had a few USB power notices in the last six months, and since I'm always instantly suspicious of any power supply issues, I also hedged my bets and got a Corsair RMx 850 to replace my Super Flower Leadex III.

Everything installed and the exact same freezing was happening. So at this point, I was befuddled. I didn't think the behaviors indicated a GPU or CPU problem, but just in case, I first checked with the 1070 Ti I use for testing and while building and then the the 2200G I keep around for similar reasons. The problems persisted. I even tried installing Windows 10 and still had the freezing before I got to actually installing Windows.

At this point, I started thinking more about the issue. Both the Windows 10/11 had dates of early May and that's actually when I started having occasional freezing issues and update problems. The last time I updated the old motherboard's BIOS was when they first fixed that AMD problem of fTPM freezing Windows for a second a couple times a day, so the BIOS was well before this Windows update. So was the date of the BIOS on the new motherboard, which is basically a step-brother of the last one I had, so it's not bizarre that they may have a similar issue.

So, I finally did the basic thing that I advise people to do around here every week: if there's a stubborn problem, check if the BIOS is updated. And don't just assume the BIOS is current and that it could not be the problem. Like with all the directions in the NO POST checklist, to actually go down the list again item-by-time and actually check rather than nodding that you did that. I installed the April BIOS update for the motherboard and everything fired right up perfectly. So basically, it was a problem that I could literally have fixed in ten minutes, long before I started taking things apart, if I had just not skipped a basic step on my own. I simply didn't think there was any particular update that would have caused this issue, so rather than checking, I just relied on personal knowledge. There aren't any consequences outside of spending some extra money and wasting an entire weekend, but take this as a lesson for very experienced users troubleshooting their own problems: having knowledge shouldn't be a shortcut.

God this was embarrassing.
 
Last edited:
I think we all have at least one story such as this. I used to have my current ASUS x570-f motherboard freezing in BIOS but would boot to Win10 no problem, turns out that day one x570 BIOS's sucked and took me a week to figure that out. This was my first personal AMD system in many years, but still. Its embarrassing wasting hours on a problem solvable by a 10 minute BIOS flash. Its the first thing I do when I see any issues now, check the BIOS update lists...
 

DaleH

Notable
Mar 24, 2023
564
61
970
I had been having occasional freezes on getting into Windows in a Crosshair VIII Hero/5900X for a couple of months. It was only occasionally a problem and I don't reboot that often, so I let it go as this is the busiest part of the year for me, work-wise. But I decided to get down to the issue and found it was freezing up from failed Windows updates. I was unable to diagnose that so I figured I'd just do a quick wipe of Windows and reinstall.

So, I went to do that, and while installing Windows, it kept freezing. It did that with any storage drive installed and any install media made in multiple ways, no matter whether I used one stick of RAM or not. The panoply of LED codes was not particularly helpful. So finally, since I value my time a lot more than money, I went out and bought a Crosshair Dark Hero. I had a few USB power notices in the last six months, and since I'm always instantly suspicious of any power supply issues, I also hedged my bets and got a Corsair RMx 850 to replace my Super Flower Leadex III.

Everything installed and the exact same freezing was happening. So at this point, I was befuddled. I didn't think the behaviors indicated a GPU or CPU problem, but just in case, I first checked with the 1070 Ti I use for testing and while building and then the the 2200G I keep around for similar reasons. The problems persisted. I even tried installing Windows 10 and still had the freezing before I got to actually installing Windows.

At this point, I started thinking more about the issue. Both the Windows 10/11 had dates of early May and that's actually when I started having occasional freezing issues and update problems. The last time I updated the old motherboard's BIOS was when they first fixed that AMD problem of fTPM freezing Windows for a second a couple times a day, so the BIOS was well before this Windows update. So was the date of the BIOS on the new motherboard.

So, I finally did the basic thing that I advise people to do around here every week: if there's a stubborn problem, check if the BIOS is updated. And don't just assume the BIOS is current and that it could not be the problem. Like with all the directions in the NO POST checklist, to actually go down the list again item-by-time and actually check rather than nodding that you did that. I installed the April BIOS update for the motherboard and everything fired right up perfectly. So basically, it was a problem that I could literally have fixed in ten minutes, long before I started taking things apart, if I had just not skipped a basic step on my own. I simply didn't think there was any particular update that would have caused this issue, so rather than checking, I just relied on personal knowledge. There aren't any consequences outside of spending some extra money and wasting an entire weekend, but take this as a lesson for very experienced users troubleshooting their own problems: having knowledge shouldn't be a shortcut.

God this was embarrassing.
There are problems related to possessing a lot of experience in troubleshooting. One starts to make assumptions based on prior experience and then jumps to an erroneous conclusion without doing some of the steps. Many times the prior experience allows one to make a quick repair, but then there's always the time one gets led astray. That was an excellent description.
 

DSzymborski

Curmudgeon Pursuivant
Moderator
SO, the BIOS update DID fix it?
Alone?

DId you need to do a reset of ANY kind on the BIOS or CMOS for it to work itself out, or no? It's weird how it varies so much.

None, I was surprised, too.

I guess when life is good, it's best not to question why.

With so many different combinations of hardware and versions, I guess I shouldn't be too surprised. Certainly not the first time I had a rather unexpected solution, though it's one of my most annoyed ones.
 
Speaking of cautionary tales, I think California is about to experience it's largest non-disease related mass death of all time. I hope not, but I suspect that after so many years of the homeless never having to worry about anything, they will mostly ignore it, and will die.

I have been there. I know. It will happen. I'll explain another time, but I WILL explain, because you can't just say that and then not. And I know that area pretty well.

Downtown. El Cajon. South Bay. Los Colinas. Chula Vista. Mission. Balboa park. Even up into Alpine maybe. That whole area is about to see something that it NEVER had any idea might happen there, and that area has thousands and thousands of homeless in those areas. If they get hit bad, it will be terrible.
 
Last edited:
  • Like
Reactions: artk2219
Speaking of cautionary tales, I think California is about to experience it's largest non-disease related mass death of all time. I hope not, but I suspect that after so many years of the homeless never having to worry about anything, they will mostly ignore it, and will die.

I have been there. I know. It will happen. I'll explain another time, but I WILL explain, because you can't just say that and then not. And I know that area pretty well.

Downtown. El Cajon. South Bay. Los Colinas. Chula Vista. Mission. Balboa park. Even up into Alpine maybe. That whole area is about to see something that it NEVER had any idea might happen there, and that area has thousands and thousands of homeless in those areas. If they get hit bad, it will be terrible.
As somebody that lives in Huntington Beach I believe you are referencing flooding and other rain related natural disasters from the tropical storm? I am pretty sure very few fatalities will be reported. In my area we got considerably less rain than I expected.
 
  • Like
Reactions: artk2219
As somebody that lives in Huntington Beach I believe you are referencing flooding and other rain related natural disasters from the tropical storm? I am pretty sure very few fatalities will be reported. In my area we got considerably less rain than I expected.
Right. Overall, it was a collective sigh of relief. Had Cali got it as bad as they thought they might, it would have been a much different story. Thankfully, you guys didn't. Then again, they haven't really had time to check all the canals, sewers and other underground systems where a lot of homeless live or hang out. Those areas most likely became inundated even if what's above ground wasn't too bad.
 
20 minutes of: "Why won't this %^$% lawnmower start?!?"

"Oh, it's out of gas."
"But I hooked up the power cable to the back, the switch is on, connections are good, why wont this piece of junk turn on (proceeds to disassemble and reasemble it twice). Oh, huh, helps if the power cable is fully plugged into the socket duffus."

"But I swapped out everything around the distributor, relays, fuses, cables, plugs, ECU, valve cover gasket, distributor CAP, piece of junk still wont turn on. What if I swap out the distributor itself with the new one I've had sitting next to it for a month? Oh, huh, son of a $*&#"

Recently upgraded my wife's computer and it wasn't stable, updated the bios, updated the os, updated all the drivers, swapped the motherboard, 3 different graphics cards (Original card, new card, different new card), swapped the power supply, changed the ssd out and restored from an image, still freezing. Finally did a fresh install of windows and copied everything back over, oh hey everything works great now, sigh.
 
Last edited:
  • Like
Reactions: helper800