Event ID 20 - WHEA-Logger - AMD Northbridge

But you got the fix yes?  Disable Quick Start Up in Power Options

Yup I saw that and I'm grateful for the guys who found that workaround but disabling a feature hardly qualifies as a fix, it's kind of beheading to cure headaches.

I posted a feedback in the "windows feedback" app with that thread's title but I can only do it for the french support, you guys should do the same and upvote it to the top so microsoft sees it and and provides a permanent fix.

I've been banging my head against the desk for almost three months now with this issue.  Thank you so much for finding a fix, though!

I do like the analogy about an extreme fix for headaches... though this fix has cured one of my own, that's for sure.  I also agree AMD and Microsoft really should have found an actual fix for this by now.  C'est la vie.  I'm just happy to no longer live in fear of this issue.  A few weeks ago, the crash happened during an update, and I couldn't even boot to Windows in Safe Mode or to the command prompt.  Such a hassle.  Glad I make backups.

After that, I wiped the drive and started from scratch, only for it to reboot again.  With the fastboot disabled, though, so far so good.  Thank you again!  I have no idea how fastboot and the AMD Northbridge would be connected.  Maybe someday we'll know.

I think you need to update the BIOS on your system to the newest one b/c with fast boot its much faster then the original AMD BIOS can handle I believe is why I think dont know if that is correct just thinking why fast boot would affect your system is all.   Does anyone else have this thought also here ?

I'll offer my explanation, based on reading a LOT of these posts, and on some (very limited) experience with microprocessor architectures and designs, and some with OS internals.

"Fast Boot" has nothing to do with the speed of the hardware.  It is all about how the operating system is loaded into memory and executed.

"Cold, slow boot" means that first, the Kernel is loaded. Then it loads, piece by piece, all of the tens of thousands of parts of the operating system, using the Registry to guide its work. It has to link things together, resolve addresses for where things are going to live, set up all of the hardware interfaces and controls...  This is what has to be done for a reboot when you've installed new software, or new hardware, or updated a driver or a part of the OS or one of its many, many utilities.  "Where do I put this new thing?" is a question the OS load has to ask and answer, constantly.

Now... when you shut down... hibernate causes that fully-linked-together, everything-loaded image of the working, in-RAM, in-virtual-memory operating system to be saved to a hibernate file.  If you re-awaken from hibernation, all that happens is that this hibernate image file is loaded quickly into memory, and then the loader assumes it's a good image and turns control over to it.

Windows has had hibernation since XP. (It is NOT "sleep," just to confuse things further.  Sleep requires power to stay on to your RAM; Hibernate does not.)

"FAST BOOT" is just powering on your machine and using the last hibernation image to load the system with.

So why are AMD processor machines crashing, perhaps every 10th or 50th fast boot?  I suspect that there is a very low-level hardware feature in these processors that is subtly different than the Intel designs, in ways that 99% of the time don't matter. But that 1%... if that's an instruction pre-fetch cache, for example, that is not initialized the same way, or initialized in ways that change as you change the order of doing things on your computer... then, you get a hardware fault that interrupts the system and causes an emergency shutdown.

I'm one of those happy campers who set his wife's AMD machine to "slow boot," and since then we have not had a repeat of this problem.

I hope this makes sense.  I consider spending two to three minutes extra per day (we only cold boot once a day) a small price to pay for not losing work.  If we had to travel and were constantly turning that machine on and off for a few minutes, and needed fast boot, we'd have to choose between convenience and risk.

Questions, comments, corrections always welcomed,

Mike