Gaming PC with BSODs and no solutions

aescat · 02 Oct 2020

Hello! My name is Adrian, I built a gaming PC just two weeks ago, and I hadn't any problem until four days ago where BSODs started to come up.

PC:
AMD Ryzen 7 3700X
B550 Aorus Elite
Corsair Vengeance 2x8 RGB DDR4
MSI NVIDIA 1070ti
SSD Samsung 850 Evo 500gb
WD 1TB
Logitech 513 Keyboard
Logitech G203 Mouse
Windows 10 Pro installed in the SSD
HyperX Cloud 2 as primary and only sound output

I've seen a lot of BSODs code_errors:

hypervisor_error
kernel_security_check_failure
invalid_lock_release
bad_pool_caller
apc_index_mismatch
page_fault_in_nonpaged_area
IRQL_not_less_or_equal
and many more...

I think I've tried everything:

Reinstalling Windows (like five times) and trying different ISOs
Repairing Windows
Updating windows, even the optional updates
Updating every driver
Updating the firmware of motherboard, right now it has the F10 version (latest). (Downloaded from Aorus website)
Memtest86, nine passes, 18 hrs of testing without errors
Chkdsk command
/scannow command
DISM commands
Update drivers with Driver Booster Pro
Change energy settings
Enter in safe mode (it's more stable, but I got BSODs)
Doing a clean boot
Installing the latest Nvidia driver (456.55)
Installing AMD ryzen master
Installing APP Center from Aorus website

The crazy part of all of this is that these BSODs are so sporadic. I even played COD: Warzone for 4 hrs yesterday without any problem, but if I'm at desktop doing things, could be opening folders, winDbg Preview, Paint or whatever... I get BSODs.

I get screen freezes sometimes, and the only way to get unstuck is to power off pressing the button for a few seconds.

I will leave you here a drive folder with screenshots, reports and the V2 Log collector folder:
report gaming pc - Google Drive

Thanks, I'd appreciate so much your help.

Ztruker · 02 Oct 2020

14 Bluescreen entries detected ...
9 Unique Bug Check codes: 03b 00a 07f 004 139 162 1a1 113 005

P1: 0X0000003B 02/10/2020 05:24 P. M. P1: 0X0000003B 02/10/2020 05:24 P. M.
P1: 0X0000000A 02/10/2020 04:29 P. M. P1: 0X0000000A 02/10/2020 04:29 P. M.
P1: 0X0000003B 02/10/2020 04:24 P. M. P1: 0X0000007F 02/10/2020 04:24 P. M.
P1: 0X0000003B 02/10/2020 04:24 P. M. P1: 0X0000007F 02/10/2020 04:24 P. M.
P1: 0X00000139 02/10/2020 03:43 P. M. P1: 0X00000139 02/10/2020 03:43 P. M.
P1: 0X00000162 02/10/2020 03:08 P. M. P1: 0X00000162 02/10/2020 03:08 P. M.
P1: 0X00000113 02/10/2020 02:29 P. M. P1: 0X00000113 02/10/2020 02:29 P. M.

These look like duplicate entries but looking at the WER data they are not.

Looks to be a problem with your video card or driver:

Code:

fffff803`462673e8  fffff803`4a3b5ee4Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvmdi.inf_amd64_1b09d1209c6a0b92\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

First, try uninstalling it with DDU then reinstalling it.

Remove and install latest Nvidia drivers:

Even though you already have the latest driver, get the latest driver for your Nvidia card again here: NVIDIA Driver Downloads
Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

Then do a custom install of only the Nvidia Graphics and PhysX driver.

See if that gets rid of the problem.

Are you doing any overclocking, GPU, CPU or RAM? If yes, reset everything to nominal and test. If things run better then you can start tweaking again a little at a time until you find the best settings for your system.

Do you have another PCI-E slot you can try the Nvidia card in?

aescat · 02 Oct 2020

Ztruker said:

14 Bluescreen entries detected ...
9 Unique Bug Check codes: 03b 00a 07f 004 139 162 1a1 113 005

P1: 0X0000003B 02/10/2020 05:24 P. M. P1: 0X0000003B 02/10/2020 05:24 P. M.
P1: 0X0000000A 02/10/2020 04:29 P. M. P1: 0X0000000A 02/10/2020 04:29 P. M.
P1: 0X0000003B 02/10/2020 04:24 P. M. P1: 0X0000007F 02/10/2020 04:24 P. M.
P1: 0X0000003B 02/10/2020 04:24 P. M. P1: 0X0000007F 02/10/2020 04:24 P. M.
P1: 0X00000139 02/10/2020 03:43 P. M. P1: 0X00000139 02/10/2020 03:43 P. M.
P1: 0X00000162 02/10/2020 03:08 P. M. P1: 0X00000162 02/10/2020 03:08 P. M.
P1: 0X00000113 02/10/2020 02:29 P. M. P1: 0X00000113 02/10/2020 02:29 P. M.

These look like duplicate entries but looking at the WER data they are not.

Looks to be a problem with your video card or driver:

Code:

fffff803`462673e8  fffff803`4a3b5ee4Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvmdi.inf_amd64_1b09d1209c6a0b92\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

First, try uninstalling it with DDU then reinstalling it.

Remove and install the latest Nvidia drivers:

Even though you already have the latest driver, get the latest driver for your Nvidia card again here: NVIDIA Driver Downloads
Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

Then do a custom install of only the Nvidia Graphics and PhysX driver.

See if that gets rid of the problem.

Are you doing any overclocking, GPU, CPU or RAM? If yes, reset everything to nominal and test. If things run better, then you can start tweaking again a little at a time until you find the best settings for your system.

Do you have another PCI-E slot you can try the Nvidia card in?

Thank you so much for helping me. But It didn't work:

I entered in safe mode, uninstalled drivers with DDU & restart (recommended). After restart (with ethernet cable disconnected) I installed the latest driver, restart again. I got blue screens.
I did the same but installing a previous version of Nvidia drivers, and it didn't work.

FYI just before doing all of this, I was preparing the files to make the uninstall with DDU, and my mouse started to work slow and it got freeze suddenly. I thought it was a freeze again, but I realized that the keyboard was still working, I could navigate the UI with the arrows and tab... So I changed the USB of the mouse to another one, but the mouse didn't turn on the lights! like it was dead. I tried changing the USBs of my keyboard too, and again, the keyboard was dead too. I had to force a restart from the button. I thought that my mouse was the problem and I tried using another, but I got blue screens again.

Before all of this and reading your answer, I tried doing stress tests with Prime95 and FurMark. I didn't get any problem, nothing... this is too weird.

Nothing is overclocked, and I don't have another PCI slot for this GPU. I don't know what is happening, and I got a lot of BSODs more!

UPDATE: I leave you here another V2 Log

Ztruker · 03 Oct 2020

The most recent dump: 10/3 12:11AM

Code:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff88ed0a4c5f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88ed0a4c548, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

These general troubleshooting tips may be helpful.

If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.
Look in Device Manager to see if any devices are marked with the exclamation point (!). Review the events log displayed in driver properties for any faulting driver. Try updating the related driver.
Run a virus detection program. Viruses can infect all types of hard disks formatted for Windows, and resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

Check for firmware updates for the Samsung SSD. I believe you do this with Samsung Magician.

Check for system file corruption, then run Driver Verifier.

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file. Collect and post output as shown.

Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

aescat · 03 Oct 2020

Ztruker said:

The most recent dump: 10/3 12:11AM

Code:

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff88ed0a4c5f0, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88ed0a4c548, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved

Check for firmware updates for the Samsung SSD. I believe you do this with Samsung Magician.

Check for system file corruption, then run Driver Verifier.

Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file. Collect and post output as shown.

Driver Verifier

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

Ok, so:

I don't have any device error in Device Manager
I have the latest firmware for my SSD, checked in Samsung Magician

This is the output of Tuneup.bat:

Code:

###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="DESKTOP-J5KOLH4" get AutomaticManagedPagefile
wmic Computersystem where name="DESKTOP-J5KOLH4" set AutomaticManagedPagefile=True
wmic Computersystem where name="DESKTOP-J5KOLH4" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.1110

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.1110

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  424704 file records processed.
File verification completed.
  9537 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  260 reparse records processed.
  614500 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.
  260 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  94899 data files processed.
CHKDSK is verifying Usn Journal...
  34860992 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 487376548 KB total disk space.
  61764396 KB in 315965 files.
    230432 KB in 94900 indexes.
         0 KB in bad sectors.
    542660 KB in use by the system.
     65536 KB occupied by the log file.
 424839060 KB available on disk.

      4096 bytes in each allocation unit.
 121844137 total allocation units on disk.
 106209765 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
TRUE


C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\DESKTOP-J5KOLH4\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\DESKTOP-J5KOLH4\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>wmic pagefile list /format:list


AllocatedBaseSize=2944
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20201002093833.608750-180
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-J5KOLH4" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-J5KOLH4" set AutomaticManagedPagefile=True
Updating property(s) of '\\DESKTOP-J5KOLH4\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-J5KOLH4"'
Property(s) update successful.

C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-J5KOLH4" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
Press any key to continue . . .

Well, I had a lot of problems with the Driver Verifier and it was so hard to stop it, but I could see something. I couldn't reach desktop, a BSOD came up as soon as I typed my password. The error was:

DRIVER_VERIFIER_DETECTED_VIOLATION
what failed: gdrv2.sys

I got that BSODs so many times trying to restart windows and stoping the verifier...
I understand this driver is related with Gigabyte, I found this for instance: GDRV.SYS/ BSOD | GIGABYTE USA Forum

So I tried to uninstall all Gigabyte related starting with APP Center and all of its utilities. I'm still getting BSODs

I don't know if I'm wrong, it's just a theory, but I think every BSODs come up when I use the mouse... (I tried changing it in every USB socket and even I tried with another mouse I have). If I keep using only the keyboard after restarting the PC I don't get BSOD, at least I think it's more stable, as soon as I start using the mouse, it's just a matter of time, maybe seconds to get a BSOD. But I don't know, it's a theory.

So, I'm still experiencing Blue screens after uninstalling Gigabyte software. I will leave you here 2 V2 Logs, one after experiencing the gdrv2.sys error and another one after uninstalling gigabyte software.

memory dmp: MEMORY.DMP - Google Drive

Thanks!

Ztruker · 03 Oct 2020

Did you uninstall RGB Fusion as well? That seems to be the one causing all the problems.

See here: Random BSODs with unknown cause

See if that allows you to run Driver Verifier so we can see what other problematic drivers there are, if any.

zbook · 03 Oct 2020

First scannow:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Code:

Windows Resource Protection did not find any integrity violations.

Plankton · 03 Oct 2020

Just skimming through the threads....I see no mention of a PSU....what make/model and wattage? Next is; do you have the 2 PCIe PSU power cables connected to your GPU.

aescat · 04 Oct 2020

Ztruker said:

Did you uninstall RGB Fusion as well? That seems to be the one causing all the problems.

See here: Random BSODs with unknown cause

See if that allows you to run Driver Verifier so we can see what other problematic drivers there are if any.

I don't have RGB Fusion installed.

I run again Driver verifier and after restarting and a few minutes a BSOD came up but not showing the driver, just another:
DRIVER_IRQL_NOT_LESS_OR_EQUAL

I leave you here the V2 log.

Right now I'm not having BSODs... just the mouse gets "laggy/slow" sometimes and after a while using the pc it freezes and I have to restart it from the button. The performance is slow, could be the Driver verifier that is still running.

These are the errors I see in the Event Viewer, these are only warnings, errors, and critical errors, they repeat every time I restart the pc:

Code:

error: Unloading the performance counter strings for service WmiApRpl (WmiApRpl) failed. The first DWORD in the Data section contains the error code.

error: The performance strings in the Performance registry value is corrupted when process Performance extension counter provider. The BaseIndex value from the Performance registry is the first DWORD in the Data section, LastCounter value is the second DWORD in the Data section, and LastHelp value is the third DWORD in the Data section.

error: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00001f80004f00ca, 0x00000000000000ff, 0x0000000000000000, 0x00001f80004f00ca). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 7dc9d845-bcc8-4e62-a0a5-29db26989491.

error: Audit events have been dropped by the transport. 0

error The previous system shutdown at 8:57:09 AM on ‎10/‎4/‎2020 was unexpected.

warn: The driver \Driver\WudfRd failed to load for the device HID\VID_0951&PID_16A4&MI_03&Col02\8&2dfa5f00&0&0001.

critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

warn: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscDataProtection
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

warn: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

warn: The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.SecurityAppBroker
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

warn: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
and APPID
{316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user DESKTOP-J5KOLH4\Adrian SID (S-1-5-21-2610935113-1007700664-3001876731-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.449_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

warn: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-J5KOLH4\Adrian SID (S-1-5-21-2610935113-1007700664-3001876731-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

warn: Windows Hello for Business provisioning will not be launched.
Device is AAD joined ( AADJ or DJ++ ): Not Tested
User has logged on with AAD credentials: No
Windows Hello for Business policy is enabled: Not Tested
Windows Hello for Business post-logon provisioning is enabled: Not Tested
Local computer meets Windows hello for business hardware requirements: Not Tested
User is not connected to the machine via Remote Desktop: Yes
User certificate for on premise auth policy is enabled: Not Tested
Machine is governed by none policy.
See https://go.microsoft.com/fwlink/?linkid=832647 for more details.

warn: The driver \Driver\WudfRd failed to load for the device HID\VID_0951&PID_16A4&MI_03&Col02\8&2dfa5f00&0&0001.

error: Faulting application name: Explorer.EXE, version: 10.0.18362.997, time stamp: 0x2419a7bd
Faulting module name: windows.storage.dll, version: 10.0.18362.1082, time stamp: 0xa8db3b62
Exception code: 0xc0000005
Fault offset: 0x000000000016fc3b
Faulting process id: 0x13b8
Faulting application start time: 0x01d69a44e68b271a
Faulting application path: C:\WINDOWS\Explorer.EXE
Faulting module path: C:\WINDOWS\System32\windows.storage.dll
Report Id: 1db7fe79-91c8-4022-b904-5cc2cfea6d86
Faulting package full name:
Faulting package-relative application ID:

critical: The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.

critical: A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.

error: The RasMan service depends on the SstpSvc service which failed to start because of the following error:
The operation completed successfully.

error: Session "Microsoft.Windows.Remediation" failed to start with the following error: 0xC0000035

error: The RasMan service depends on the SstpSvc service which failed to start because of the following error: The operation completed succesfully.

- - - Updated - - -

Plankton said:

Just skimming through the threads....I see no mention of a PSU....what make/model and wattage? Next is; do you have the 2 PCIe PSU power cables connected to your GPU.

Hello! thank you for helping me. My PSU: Sentey SDP750-SS 750W. And yes, I have the 2 PCIe PSU power cables connected. I could play warzone with 140 FPS without problems, bugs, stuttering, nothing.

UPDATE: I got another BSOD without driver in the blue screen. Just a IRQL_NOT_LESS_OR_EQUAL. I'll leave the V2 log of that one too

Ztruker · 04 Oct 2020

You can also try uninstalling AMD Ryzen Master. It's not requires software. See if that makes a difference.

AMD Ryzen Master 2.3.0.1591 Advanced Micro Devices, Inc. 2020/10/02

You can always reinstall it if you need it.

I would also uninstall:

Driver Booster 8
RivaTuner Statistics Server 7.2.3

When you reinstalled Nvidia driver after removing it with DDU, did you do a custom install of only the Nvidia Graphics and PhysX driver? If not, try that, see if it makes a difference..