Just built a new PC and it's been running fine until getting a BSOD today after a game crashing a few times. Attached the V2 and DM zips, hoping someone knows what the cause may be.
Attachment 240300
Attachment 240301
Please ensure that you check for and install any available Windows Updates
There are 2 AMD chipset devices that don't have drivers installed. Please visit the MSI support website for your motherboard and install ALL of the latest updates (to include the AMD chipset/devices drivers).
Code:PCI Device PCI\VEN_1022&DEV_148A&SUBSYS_7C021462&REV_00\4&D573D7&0&0039 The drivers for this device are not installed. PCI Device PCI\VEN_1022&DEV_1485&SUBSYS_7C021462&REV_00\4&1FDE7688&0&0041 The drivers for this device are not installed.
With ALL of those updates, test and see if the BSOD's stop.
If they don't, I'd suggest running Driver Verifier as the next step.
Good luck!!!
EDIT: FYI - I suspect these libraries/drivers as they've had BSOD issues in the past:
WinRing0x64.sys Wed May 1 22:19:47 2013 (5181CD43)
NTIOLib_X64.sys Sun Jul 9 22:13:57 2017 (5962E2E5)
Please run driver verifier using the following settings for 48 hours.
- Special Pool
- Force IRQL checking
- Pool Tracking
- Deadlock Detection
- Security Checks
- Miscellaneous Checks
- Power framework delay fuzzing
- DDI compliance checking
Warning: driver verifier could cause boot issues and/or performance issues.
- Make sure that you have recovery media, if needed you can create it.
- Configure a restore point prior enabling driver verifier.
Resetting driver verifier options (recommended in this order)
- In normal mode open an administrator command prompt and enter the below command
- In safe mode open an administrator command prompt and enter the below command
- On 3 boot failures, you'll boot automatically to the recovery options,
- click Troubleshoot
- go to the advanced options
- choose command prompt
- enter the below command
- Boot with the recovery media, see above 4 steps in option 3.
- Via the recovery options or recovery media, select a restore point prior enabling driver verifier
Code:verifier /reset
Crashed when running driver verifier
- Reset driver verifier
- Boot in normal mode if necessary
- Follow Blue Screen of Death (BSOD) Posting Instructions to provide the requested logs
Extra information about driver verifier
When you run driver verifier, there are two things you're looking out for
1. Driver verifier won't find any driver violating something and thus in the time you need to run it there won't be a crash
2. Driver verifier will find a driver violating something and thus the system will crash.
The end result of driver verifier is either of the two, but when driver verifier finds something your system will BSOD.
Driver verifier essentially validates selected drivers on selected actions, this validation adds some delay to actions performed in the background which results in a performance decrease that many people notice. This is called stress testing drivers and depending on quite a few factors this performance decrease is worse for some than for others, and some won't even notice a difference.
Depending on the drivers selected, it is possible that some of the selected drivers are so-called 'boot' drivers, meaning they load when your system is booting. If these drivers don't pass a validation check, your system will crash, but since the drivers are loading at boot, your system will basically be in a boot loop. That is one of the risks involved and the most important one. Of course, there are various methods to recover from it.
If you want visual confirmation that driver verifier is actually running, copy/paste the following command in powershell or command prompt
If the command gives a result similar to this, it means driver verifier is running.Code:verifier /query
Quote