Recurring ntoskrnl.exe crashes and BSODs on a new PC with random BugCheck causes and different drivers - help needed!

Repost from Reddit. These are things I found out:

1. RAM profile settings have no effect. I'm waiting for thermal paste to test CPU voltage and frequency adjustment as a solution.
2. The problem usually happens when watching movies via YouTube, or from HDD with MPC-HC. The only game that crashed the OS for me was Minecraft with metric ton of mods - it's both CPU and memory heavy. I played KSP 1.10.1 with metric ton of mods with no problems.
3. Epic Game Store app causes even more BSODs. Almost no problems with Steam.
4. Neither SFC, CHKDSK, nor DISM solves any problems. This is also not a RAM problem at all. Clean OS install doesn't solve it.
5. Switching power profile in Windows power settings from AMD balanced to Microsoft balanced makes the OS slightly more stable. Slightly.
6. The type/value of bugcheck error related to ntoskrnl, as far as I can tell, doesn't really matter. I did a bit debugging on the memory dumps Windows provides. It looks like ntoskrnl.exe messes up some data stored either in cache or in RAM. Usually some register data is missing from the dump. This data corruption happens on kernel level causing CPU/system to loose track of which program has which memory reserved, what interrupts are set up, and where code execution should go after tripping one or returning from Interrupt Service Routine, data structures get mangled. Dumps indicate that web browser is usually the victim, sometimes Steam app or EGS app, on rare occasions a driver gets chewed up too. I neither have skills nor source code to solve this problem.
7. The suggestion that locking CPU clock might fix it points to the way clock boosting is managed by OS. I think the problem is caused by the way OS is handling the clock change. I think it goes like this (it's my idea supported only by my imagination and knowledge developed while programming 8-bit microcontrollers):

• Kernel registers a need for some clock boosting or throttling back.
• Kernel sends command to the hardware. It doesn't stop normal code execution.
• Hardware changes the clock and VCore accordingly. This happens between two clock cycles.
• If this happens while CPU is fetching data between cache and RAM or between cache and registers, data gets sometimes mangled due to sudden voltage change.
• This causes execution of current opcode command to go wrong. CPU detects problem, throws an error and halts normal code execution. It switches to Kernel Interrupt Service Routine for that error.
• Kernel ISR can't recover from data mangling, throws a bugcheck error and dumps memory.
• On reboot the clock and voltage is reset.

Locking the clock causes hardware to ignore any clock change commands from Kernel. BIOS updates for some motheboards probably include a fix - hardware waits for completion of opcode command execution, locks the CPU, changes the clock and voltage, resumes. The way we do it with microcontrollers.

Mind you, this is only my theory, and I have no proof to support it.

For now the only solution is to lock the clock, update everything, including BIOS, and hope that M$ will fix their kernel-level software, as the solutions provided in firmware/drives provided by manufacturers are just workarounds for the root cause.

If anyone wants, I can provide more minidumps and memdumps I collected since reinstalling the OS...

yes, i saw you on reddit. I am the one who asked you if this is a cpu problem or a code problem.

I don't think this is an AMD specific issue - I have been getting random BSoDs like most people on here - using BlueScreenViewer to see that ntoskrnl.exe + 3f5780 is the culprit - but my chipset is Intel (i9 10900k, nvidia RTX 3080, 16GBx2 DDR4/3000MHz ADATA XPG Z1, ASUS PRIME Z490-V ATX motherboard). Also a new PC built last November (2020).

My BSoDs also happening every few hours, sometimes when I'm browsing, sometimes gaming, sometimes when my PC is idle. Almost all my crashes come with the DPC_WATCHDOG VIOLATION 0x133 error message, but occasionally my PC just locks up with no BSoD and I have to manually restart.

Things I've tried so far that haven't fixed it:

• Updating all drivers, both automatically through Windows Update and also manually
• Running Mem Test / CHKDSK / SFC scan with 0 issues
• Stress test CPU / GPU with Furmark and other software
• Swapping out my GPU (RTX 3080) with an older card (GTX 960)
• Swapping out integrated wifi adapter to PCIe one, then also a USB adapter - also trying old & new drivers for each one
• Update my BIOS (ASUS Prime z490)
• Completely reinstall Windows 10 with fresh drive

None of these things worked - for a while I was getting BSoD every few days and I could tolerate it, but now it happens every few hours and its incredibly frustrating. The things I haven't tried yet, but will later today:

• Use RAM sticks one at a time to see if either are faulty, though I've run the MEM TEST multiple times with 0 issues so I doubt this is the problem
• Manually set CPU speed? I've never done this before, and I don't overclock, so I have a feeling this isn't it either - but it has helped some people it seems, so I will at least try it!

I have done all of the above (except downclocking or manual clocking the cpu, as i refuse to see loosing tons of performance as a "solution") plus replacing rams and gpu.

The only think that worked so far was replacing ny 3600xt with a 3600. It didnt crash in 18 hs. So i took the 3600 back to the person who borrowed me the chip and sent my b550 and 3600xt to rma.