BSOD Bugcheck 0x00000133 after Modern Warfar

Hello,

I have been suffering from restarts after my modern warfare games (warzone matches) - During the game I get random moments where the FPS drops to 10-15fps for 10 seconds then goes back to 120+ but at the end of the game when i'm in lobby it will freeze then restart itself. I've checked the event viewer and it has given me "computer has rebooted from a bug check. The bugcheck was 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff80757573358, 0x0000000000000000).

I have attached the V2 Log here:
KURAN-MITX-(2020-07-07_18-28-48).zip - Google Drive

I rolled back my nvidia drivers however it still gives me this error.

Kind regards,
Kdiizle

Please post a share link for this memory dump: C:\windows\memory.dmp using one drive, drop box, or google drive

Code:

LastWriteTime       Size (MB) FullName             
-------------       --------- --------             
07/07/2020 18:16:05     930.6 C:\Windows\MEMORY.DMP

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) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) 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

Use this link as needed when posting results:
How to Change Post Editor to Source or WYSIWYG Mode at TenForums.com


13) Make sure that there is no over clocking while troubleshooting

Microsoft Windows [Version 10.0.18363.900]
(c) 2019 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 did not find any integrity violations.

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

Deployment Image Servicing and Management tool
Version: 10.0.18362.900

Image Version: 10.0.18363.900

[==========================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.900

[==========================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 ...
719104 file records processed.
File verification completed.
9925 large file records processed.
0 bad file records processed.

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

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

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

976166911 KB total disk space.
669194332 KB in 538222 files.
299532 KB in 104866 indexes.
0 KB in bad sectors.
855535 KB in use by the system.
65536 KB occupied by the log file.
305817512 KB available on disk.

4096 bytes in each allocation unit.
244041727 total allocation units on disk.
76454378 allocation units available on disk.

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

C:\Windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\KURAN-MITX\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|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>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}

C:\Windows\system32>

- - - Updated - - -

I can't seem to share my memory file as it is 'unreadable' in google drive - any way to go about this?

Save the memory dump to the downloads folder or desktop then post share link.

Here is a link to the memory dump:
MEMORY.rar - Google Drive

Multiple GPU drivers can be tested.
If multiple drivers result in BSOD then swap test or replace the GPU card.
For swap testing use either Nvidia or AMD.





1) 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

2) Turn off Windows updates of non-Microsoft drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10


3) Make a new restore point:
Create System Restore Point in Windows 10

4) uninstall the Nvidia GPU driver using DDU (display driver uninstaller)

5) re-install the Nvidia GPU driver from the Nvidia website
install a driver version different fro : 26.21.14.4587

6) make sure that you check the clean install box and if available install the physx driver.

Display Driver Uninstaller Download version 18.0.2.5 (or newer version if available)
Official Display Driver Uninstaller DDU Download

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

Download Drivers | NVIDIA
Download Drivers | NVIDIA

7) Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread


Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled or uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) after each BSOD use the reset command to turn off the tool
e) if the reset command does not work then use the bootmode command
f) only if both reset and bootmode command fail to turn off the tool then use restore
g) start with the 3 customized test settings in the Ten Forums link
h) increase the customized test settings up to the 19 customized test settings in the Microsoft link
i) report any performance problems or very slow boot so that the customized settings can be modified

Code:

Name                    : NVIDIA GeForce RTX 2060
DeviceID                : VideoController1
PNPDeviceID             : PCI\VEN_10DE&DEV_1F08&SUBSYS_37551462&REV_A1\4&1FC990D7&0&0019
VideoProcessor          : GeForce RTX 2060
CurrentRefreshRate      : 60
VideoModeDescription    : 1920 x 1080 x 4294967296 colors
AdapterRAM              : 4293918720
DriverVersion           : 26.21.14.4587
InfFilename             : oem19.inf
InstalledDisplayDrivers : C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9952681a7bb1dfac\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9952681a7bb1dfac\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9952681a7bb1dfac\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_9952681a7bb1dfac\nvldumdx.dll
InstallDate             : 
DriverDate              : 03/04/2020 01:00:00
Status                  : OK
StatusInfo              : 
LastErrorCode           : 
ErrorDescription        :

Code:

nvlddmkm.sys Fri Apr  3 13:22:01 2020 (5E879AE9)

Hi there, I have ran the verifier and updated graphics drivers to the newest ones however it isnt BSOD anymore - instead it just has a black screen and I have to force shutdown the PC (through the power switch). Regarding the memory logs, it is still from yesterday evening when the BSOD happened. I can supply these to you?

edit 1: furthermore I checked the event viewer and I'm getting this error now: The device HID-compliant headset (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 4 more times. Please contact the device manufacturer for more information about this problem.
This has happened twice today when playing warzone

Please upload new V2 and memory.dmp.

Microsoft updates their database for windbg debugging of windows crashes.

For user mode crashes > communicate with the manufacturer.

See step #7b.

What steps did you make with the tool?
How many BSOD were there?
How many non BSOD crashes were there?
How come V2 were not uploaded after each crash?

With the tool - I only checked non-microsoft drivers however I have now stopped it.
Here is the new V2: KURAN-MITX-(2020-07-08_13-45-36).zip - Google Drive
Here is the New memory: MEMORY.rar - Google Drive
Here is a Mini-dump (if needed): 070720-18937-01 (Minidump).rar - Google Drive

There was only 1 BSOD.
There was 3 non-BSOD (a black screen - had to force shutdown after finishing a modern warefare and during a game)

How many customized tests were used?

The logs indicated that windows driver verifier was not in use during the crash at Tue Jul 7 12:15:05.883 2020 (UTC - 5:00)

The goal is to produce windows driver verifier crashes > upload dump files.