BSOD only while playing Call of Duty MW3 - Event ID 162 and 41 combo

cambo11 · Nov 13, 2023

Hello, hoping someone can help me here.

I've recently starting getting this issue while only playing Call of Duty Modern Warfare 3. I am suspecting it's my ram but I've done ram stress testing without any issues. It started after the latest windows update and nvidia driver.

It always starts off with a Event 162 on volume 3. Then a kernel-power event 41. BSOD error says "DRIVER VERIFIER DMA VIOLATION".

CPU: 13900k
GPU: 4090 RTX
Windows 11: Version 23H2 (OS BUILD 22631.2506)

Dump files here - BSOD - Google Drive

Any help is appreciated, thank you.

cambo11 · Nov 13, 2023

I've currently uninstalled the latest Nvidia Driver and reverted back to version 537.58 as I am suspecting it might be driver related.

zbook · Nov 13, 2023

When I was heading to bed the thread was seen.
The BSOD in August and one BSOD on 11/11 was caused by misbehaving Nvidia GPU drivers.

It's best to clean all driver files using DDU.

Later in the day I'll look at the remaining dump and other V2 files.

Display Driver Uninstaller: How to use

How to Use Display Driver Uninstaller to Uninstall any Installed Display Driver

www.sevenforums.com

Display Driver Uninstaller (DDU) download latest version 18.0.7.6

Official Display Driver Uninstaller (DDU) download website. DDU is a driver removal utility that can help you completely uninstall AMD/NVIDIA/INTEL graphics card drivers and packages from your system, trying to remove all leftovers (including registry keys, folders and files, driver store).

www.wagnardsoft.com

Download the latest official NVIDIA drivers

www.nvidia.com

Flashorn · Nov 13, 2023

Hi cambo!

There is a hotfix for the current dGPU driver here "

NVIDIA Support

nvidia.custhelp.com

There was another member who had the same and this hotfix served it's purpose.

zbook · Nov 13, 2023

The link posted by Flashorn is applicable as it is the installed version:

Code:

Name    NVIDIA GeForce RTX 4090
PNP Device ID    PCI\VEN_10DE&DEV_2684&SUBSYS_40BF1458&REV_A1\4&256A0AA8&0&0008
Adapter Type    NVIDIA GeForce RTX 4090, NVIDIA compatible
Adapter Description    NVIDIA GeForce RTX 4090
Adapter RAM    (1,048,576) bytes
Installed Drivers    C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_9d47b26dd41355d9\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_9d47b26dd41355d9\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_9d47b26dd41355d9\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_9d47b26dd41355d9\nvldumdx.dll
Driver Version    31.0.15.4608
INF File    oem72.inf (Section079 section)
Driver    C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_9D47B26DD41355D9\NVLDDMKM.SYS (31.0.15.4608, 56.01 MB (58,727,160 bytes), 11/11/2023 10:58 PM)

cambo11 · Nov 13, 2023

I did a DDU and tried the latest hotfix before posting here so the hotfix was causing the BSOD for me.

I'll keep testing the games with the older driver to see if it is resolved. Appreciate the help!

Flashorn · Nov 13, 2023

cambo11 said:
I did a DDU and tried the latest hotfix before posting here so the hotfix was causing the BSOD for me.

I'll keep testing the games with the older driver to see if it is resolved. Appreciate the help!

Is this the older CoD from 2011?
Did you play this game before without any problems?

cambo11 · Nov 13, 2023

Flashorn said:
Is this the older CoD from 2011?
Did you play this game before without any problems?

This is the latest 2023 CoD. I have not played it with older drivers since I usually update and the driver update came before the game launch.

I just had the same BSOD using the 537.58 but did not DDU. I have used DDU this time and will test again. I have not tried other games yet but will try to test in others later.

Flashorn · Nov 13, 2023

cambo11 said:
This is the latest 2023 CoD. I have not played it with older drivers since I usually update and the driver update came before the game launch.

I just had the same BSOD using the 537.58 but did not DDU. I have used DDU this time and will test again. I have not tried other games yet but will try to test in others later.

It could be the game itself as it is very new. I haven't played it yet. I usually wait a couple months for them to
sort out their woes. zbook will certainly have news for you as soon as he can.

cambo11 · Nov 13, 2023

Flashorn said:
It could be the game itself as it is very new. I haven't played it yet. I usually wait a couple months for them to
sort out their woes. zbook will certainly have news for you as soon as he can.

No worries and really appreciate the help. I just want to make sure I wasn't going crazy not being able to figure it out. :boom:

zbook · Nov 13, 2023

Uninstall or uninstall and reinstall the software related to these drivers:

atvi-randgrid atvi-randgrid \??\c:\programdata\battle.net_components\randgridauks\randgrid.sys

snapman Acronis Snapshots Manager c:\windows\system32\drivers\snapman.sys

Run ACP

msdt.exe -id SearchDiagnostic
msdt.exe -id DeviceDiagnostic

If available click view detailed information > post share links

Code:

Event[500]
  Log Name: Application
  Source: Microsoft-Windows-Search
  Date: 2023-10-18T03:11:46.5010000Z
  Event ID: 7042
  Task: Search service
  Level: Error 
  Opcode: N/A
  Keyword: Classic,
  User: N/A
  User Name: N/A
  Computer: Obert-PC
  Description:
The Windows Search Service is being stopped because there is a problem with the indexer: The catalog is corrupt.

Details:
    0x%08x (0xc0041801 - The content index catalog is corrupt.  (HRESULT : 0xc0041801))

cambo11 · Nov 13, 2023

Uninstalled the Acronis and reinstalled Battle.net. Both Diagnostics came out no issues.

devicediagnostic.pdf

drive.google.com

searchdiagnostic.pdf

drive.google.com

This is battlenet kernal driver for their ricochet anticheat system -> atvi-randgrid atvi-randgrid \??\c:\programdata\battle.net_components\randgridauks\randgrid.sys

zbook · Nov 13, 2023

There was limited information using google search for randgrid.sys.

Uninstall or uninstall and reinstall battle.net software.

Make a new restore point.

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

If there are any BSOD post a new V2 share link into the newest post.

cambo11 · Nov 13, 2023

Thank you. Will try playing the game later today after work. Will report back if BSOD is gone.

zbook · Nov 13, 2023

Closer monitoring and trends can be viewed using Reliability Monitor:

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

cambo11 · Nov 15, 2023

BSOD happened again playing Call of Duty MW3 using the older Nvidia 537.58 driver. I am starting to think it's just related to the game at this point. Any suggestions?

ubuysa · Nov 15, 2023

I have a couple of observations that may be important to you problem....

Observation 1: You have two SHPP41-2000GM drives in your system that appear to have a Windows system installed on them (they both appear to have the Windows UEFI partition structure). Are you running these in a RAID array (if so, why?), or are they two different Windows systems? Having more than one Windows system online can cause all sorts of problems.

Observation 2: The four most recent dumps (from 11th Nov) are all Driver Verifier generated 0xE6 DRIVER_VERIFIER_DMA_VIOLATION bugchecks. This indicates that the input/output memory management unit (the IOMMU) detected a problem in the way a driver was handling a direct memory access (DMA). Unfortunately the problem determination data in all these dumps is invalid. Using the (undocumented) value in argument 4 we get...

Code:

0: kd> dt _FAULT_INFORMATION_ARM64 4
nt!_FAULT_INFORMATION_ARM64
   +0x000 DomainHandle     : ????
   +0x008 FaultAddress     : ????
   +0x010 PhysicalDeviceObject : ????
   +0x018 InputMappingId   : ??
   +0x01c Flags            : _FAULT_INFORMATION_ARM64_FLAGS
   +0x020 Type             : ??
   +0x028 IommuBaseAddress : ??
Memory read error 000000000000002c

And this is of no help at all of course. Typically we would see the device object address in offset 0x010 which would point us at the failing device, but here we don't.

Why are you running Driver Verifier? More importantly, what Driver Verifier options are you selecting? To be of any use Driver Verifier needs to be run with very specific options selected.

If you disable Driver Verifier (verifier /reset) do you have any further problems?

zbook · Nov 15, 2023

For any BSOD please post a new V2 share link into the newest post.

cambo11 · Nov 15, 2023

ubuysa said:
I have a couple of observations that may be important to you problem....

Observation 1: You have two SHPP41-2000GM drives in your system that appear to have a Windows system installed on them (they both appear to have the Windows UEFI partition structure). Are you running these in a RAID array (if so, why?), or are they two different Windows systems? Having more than one Windows system online can cause all sorts of problems.

Observation 2: The four most recent dumps (from 11th Nov) are all Driver Verifier generated 0xE6 DRIVER_VERIFIER_DMA_VIOLATION bugchecks. This indicates that the input/output memory management unit (the IOMMU) detected a problem in the way a driver was handling a direct memory access (DMA). Unfortunately the problem determination data in all these dumps is invalid. Using the (undocumented) value in argument 4 we get...

Code:

0: kd> dt _FAULT_INFORMATION_ARM64 4 nt!_FAULT_INFORMATION_ARM64 +0x000 DomainHandle : ???? +0x008 FaultAddress : ???? +0x010 PhysicalDeviceObject : ???? +0x018 InputMappingId : ?? +0x01c Flags : _FAULT_INFORMATION_ARM64_FLAGS +0x020 Type : ?? +0x028 IommuBaseAddress : ?? Memory read error 000000000000002c

And this is of no help at all of course. Typically we would see the device object address in offset 0x010 which would point us at the failing device, but here we don't.

Why are you running Driver Verifier? More importantly, what Driver Verifier options are you selecting? To be of any use Driver Verifier needs to be run with very specific options selected.

If you disable Driver Verifier (verifier /reset) do you have any further problems?

Thank you for looking into this. I also recently did a memtest which had no errors for the ram.

1. Only 1 windows is installed on one of them. Not sure why the other is partitition that way but I can see it in the disk management now. I'll reformat it that drive so there's no conflicts.

2. This is the error I normally see when it crashes. I will go ahead and delete the settings and run that command to reset it.

Latest V2 - OBERT-PC-(2023-11-15_04-00-38).zip

zbook · Nov 15, 2023

Please make a new restore point.

Read this tutorial on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn how to recover from using the tool by booting into safe mode and running one or more of these ACP commands to turn off the tool:

verifier /reset

verifier /bootmode resetonbootfail

Start WDV with these test settings:

a) test all non-Microsoft drivers

b) test no Microsoft drivers

c) start the testing with the three customized tests in the Ten Forums link

Plan to run the tool for approximately 48 hrs with various customized tests.

If there is no immediate BSOD then open ACP and copy and paste:

verifier /querysettings

Post a share link into the newest post.

For any BSOD post a new V2 share link into the newest post.