BSOD When Gaming

Good afternoon,

I have been experiencing a variety of BSOD issues. My drivers are up to date, Windows is up to date, etc. My gut is that it's an issue with the memory, but I want to be certain before replacing it.

Today's crashes, based on BlueScreenView, are a result of - USBXHCI.sys, FLTMGR.sys and dxgkrnl.sys.

My V2 Log can be found here - Log Collector-(2019-10-16_13-56-42).zip - Google Drive

I am running Windows 10 Ver 1809 (build 17763.805).

I will look in to your other suggestions!

- - - Updated - - -

I've confirmed I have the latest BIOS installed (V 1205) and have updated the chipset drivers.

Hi jazzyj,

Welcome to the TF BSOD forum.

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7

9) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

10) Make sure that there is no over clocking while troubleshooting.


11) Measure the GPU's temperatures at idle and under load

12) Ensure the GPU is free from dust build up and that the fan is working correctly

13) Reseat the GPU and check all connections are securely made

14) Check PSU voltages in BIOS
What are the BIOS 3.3, 5 and 12 voltage values?
What are the CPU voltage and frequency?


Post a share link using one drive, drop box, or google drive for: C:\windows\memory.dmp

Code:

Crash dump found at C:\WINDOWS\MEMORY.DMP
Creation date: 10/16/2019 13:15:21
Size on disk: 892 MB

15) Uninstall everything AMD using Display driver uninstaller and install new drivers from the the AMD website.

16) On the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

Official Display Driver Uninstaller DDU Download

Display Driver Uninstaller Download version 18.0.1.8 (or newer version if available)

Display Driver Uninstaller: How to use - Windows 7 Help Forums

http://support.amd.com/en-us

17) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Microsoft Windows [Version 10.0.17763.805]
(c) 2018 Microsoft Corporation. All rights reserved.

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.17763.771

Image Version: 10.0.17763.805

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

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

Deployment Image Servicing and Management tool
Version: 10.0.17763.771

Image Version: 10.0.17763.805

[===========================82.6%=============== ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

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 ...
773120 file records processed.
File verification completed.
34216 large file records processed.
0 bad file records processed.

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

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

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

124469247 KB total disk space.
97290024 KB in 477729 files.
308192 KB in 131614 indexes.
0 KB in bad sectors.
904447 KB in use by the system.
65536 KB occupied by the log file.
25966584 KB available on disk.

4096 bytes in each allocation unit.
31117311 total allocation units on disk.
6491646 allocation units available on disk.

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

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

C:\WINDOWS\system32>

- - - Updated - - -

Here is the Memory.dmp file - Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

The first scannow displayed:

Code:

Windows Resource Protection found corrupt files and successfully repaired them.

The second scannow displayed:

Code:

Windows Resource Protection did not find any integrity violations.

Restorehealth displayed:

Code:

Image Version: 10.0.17763.805

[===========================82.6%=============== ]
Error: 0x800f081f

The source files could not be found.

Find a flash drive that you can format (> or = 8 GB)

Create a bootable Windows 10 iso:

https://www.microsoft.com/en-us/soft...load/windows10
Download Windows 10 ISO File
Create Bootable USB Flash Drive to Install Windows 10

Perform an in place upgrade repair:

Repair Install Windows 10 with an In-place Upgrade

1) Attach the Windows 10 iso flash drive to any USB port
2) Open file explorer > this PC > C: > click on setup
3) follow the text and images in the in place upgrade repair link

Thanks for the assistance and apologies for the delay. Haven't had time to do the upgrade until now.

Once the in place repair is complete, are there any further steps? Or should that hopefully solve?

Or perhaps rerun the initial steps, hopefully with the missing files now in place?

After the in place upgrade repair use the computer for several days > upload a new V2
BSOD - Posting Instructions

Laith said:

Hi.
According to my analysis,

Code:

0: kd> lmvm KovaPlusFltrBrowse full module list
start             end                 module name
fffff802`2ff40000 fffff802`2ff43b00   KovaPlusFltr T (no symbols)           
    Loaded symbol image file: KovaPlusFltr.sys
    Image path: \SystemRoot\system32\drivers\KovaPlusFltr.sys
    Image name: KovaPlusFltr.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jan 25 05:23:58 2010 (4B5D9B6E)
    CheckSum:         000070F9
    ImageSize:        00003B00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

it seems as though the issue is with your ROCCAT Kone mouse driver.
As seen in the code snippet below, it is horribly out of date. Try uninstalling the driver, or upgrading it, to see if the issue persists. Hope this helps.

Huh, that's interesting. I was trying to utilise their mapping software the other day and found my mouse was unsupported. Maybe I overlooked some new drivers for it.