BSOD - usually under low load i.e. youtube playback in chrome

I have tried allsorts to try and diagnose this myself and asked around at tomshardware and was suggested to see what you guys could make of my issue.

I notice there is a reddit post suggesting that ryzen 3600 + b450 is falling foul of a windows update but I can't find a verifiable source on that.

I have ruled out RAM and PSU in my own tests, as you can see here

Logs Dropbox - DESKTOP-L4T6G98-(2021-02-03_16-39-37).zip - Simplify your life

I have just updated to latest windows 20H2 (build 19042) and last dump is different in that it blames usb; but I reckon that its probably the issue I've been having corrupting stack on its behalf. Current USBs are mouse, KB, headset and wireless xbox dongle. Previous dumps were windows 2004.

Thread at tomshardware: Question - BSOD (daily) during general use: fine in games (I suspect driver). | Tom's Hardware Forum

All the crash dumps prior to your most recent one related to the USB were caused by having Driver Verifier enabled with most of the standard settings checked. The latest crash dump shows that you have Verifier set to automatic checks only.

In your most recent crash the driver (mt7612US)for XBOX wireless dongle seems to be causing the crash. Try removing this dongle and seeing if the problem goes away.

Yes the logger trawled the folder and my previous dumps had all been replaced with driver verifier. I wont find some of my old dumps as I've since done re-install of motherboard drivers and win update. But I have a crash form this morning.
Minidump: Dropbox - 020421-10687-01.dmp - Simplify your life
I can re-run the logger but I haven't changed my system since my first post.

Let me know how you get on with the dongle removed.

Sadly that's not changed anything, that was the first time I saw a BSOD that actually pointed at a driver.

Todays crash looks like the usual:Dropbox - 020521-5187-01.dmp - Simplify your life

Do I need to redo the full log is is just posting the latest minidump ok?

adder0 said:

Sadly that's not changed anything, that was the first time I saw a BSOD that actually pointed at a driver.

Todays crash looks like the usual:Dropbox - 020521-5187-01.dmp - Simplify your life

Do I need to redo the full log is is just posting the latest minidump ok?

It's generally better to post a complete set of log files so that we can see the event logs as well. Thanks!

Ok new log. only last two crashes are relevant (already posted separately above) - older ones driver verifier was enabled.
Dropbox - DESKTOP-L4T6G98-(2021-02-05_19-53-02).zip - Simplify your life

New log with latest crashes.
Dropbox - DESKTOP-L4T6G98-(2021-02-08_08-28-35).zip - Simplify your life

- - - Updated - - -

Empirical note: seems like I'm having more crashes today. Could VPN for work be a factor. I don't use it at weekends and system seemed pretty stable then; but this is a random error so could have just been lucky then and unlucky now.

I am of the opinion that there is a problem that is fundamental to the AMD CPU/motherboards running the latest W10 operating system. There have been too many reports of problems for this to be an isolated case.

At the moment I am not sure what the solution is. I am suspecting hardware and so I can only suggest you run some hardware tests like Prime95 to see if you can reliably trigger the CPU to crash.

 CPU TEST

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

   Warning

Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

I've not been able to force a crash. Before coming here I had tried prime95, realbench, intel burn test and heaven they all ran fine.

I think the likeliness of it being a win 10 issue is high; but I can't find any official data from MS stating they are aware (and therefore will fix) and it's not affected all there must be a silicon lottery element too. I tried making a bug via feedback hub, but no response there. Sadly due to clean install I can't pinpoint update coinciding with reliability falling off a cliff.

AMD forums don't seem aware and also not very active if I'm honest. I'll see if I can get anything from AMD support direct. MSI support have been sluggish and haven't pointed a finger at MS.