Did you experience a BSOD while playing COD MW III?
Did you experience a BSOD while playing COD MW III?
I experienced a BSOD while playing COD MW III. After the game, I pressed Windows key to exit and then used Chrome to check my email. Occasionally, the game crashes when launching, which is common for COD but also reported by others. Here is the dump information: Microsoft ® Windows Debugger Version 10.0.21306.1007 AMD64. Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\*\Downloads\050924-7000-01.dmp]. The Mini Kernel Dump File shows only registers and stack trace available. The symbol search path is: srv*. The executable search path is: Windows 10 Kernel Version 22621 MP (32 procs) Free x64. Product: WinNT, suite: TerminalServer SingleUserTS. Machine Name: Kernel base = 0xfffff807`4d400000, PsLoadedModuleList = 0xfffff807`4e0134a0. Debug session time: Thu May 9 18:02:27.564 2024 (UTC - 4:00). System Uptime: 0 days 4:06:40.217. Loading Kernel Symbols ... Loading User Symbols ... Loading unloaded module list ... For analysis, run !analyze -v nt!KeBugCheckEx: The file contains a critical error. DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) occurred. This indicates an attempt to access an invalid address at an IRQL level too high, often due to improper driver addresses. If the kernel debugger is available, obtain a stack trace. Analysis details: Key values such as CPU time and memory usage were recorded. TAG_NOT_DEFINED_202b is marked as unknown. DUMP_FILE_ATTRIBUTES: 0x1808. Additional debugging info includes crash details, process name, crash count, and system flags. Notifications about blackbox tools and various error codes are included.
A malfunctioning driver attempted to access a null pointer, likely following an incident where it received corrupted data from its hardware. This seems to be a driver issue, though a more detailed analysis of the stack trace is necessary to identify the specific driver and cause.
It's not advisable to rely on a single test result when making a diagnosis; however, reviewing the data suggests this might point to a RAM problem rather than a driver issue. While the bugcheck shows an DRIVER_IRQL_NOT_LESS_OR_EQUAL error—commonly linked to faulty third-party drivers—the check doesn't reveal any such drivers in the preceding steps. The functions being invoked are all connected to memory access errors or their recovery processes.
I notice you have 32GB of RAM, split across two 16GB TeamGroup UD5 5200MHz modules. It would be wise to eliminate the XMP (or similar) overclock settings, as I suspect the base clock is around 4800MHz. Try running a BSOD test at that speed.
Also, consider using Memtest86 to stress-test your RAM. Perform the tests with XMP disabled and then with XMP enabled at 5200MHz.
Download
Memtest86 (free), use the extracted imageUSB.exe tool on a separate USB drive to create a bootable version. Running it on another PC would be safer until you're certain.
After completing the four iterations of the 13 different tests offered by the free version, restart Memtest86 and repeat the process once more. Even one bit error indicates a failure.
By the way, are you aware that some users report issues with the i9-14900KF CPU in certain games? Here are relevant links:
https://en.overclocking.com/intel-core-i...f-crashes/
https://www.xda-developers.com/intel-13t...n-crashes/
https://community.intel.com/t5/Proc...ue...-p/1596718
Thank you for the suggestion, but I wasn't aware there were issues with the i9-14900KF.
Yep. I've just seen another user on the Windows 10 forum with an i9-14900K having issues. Join the Intel forum and add your voice. I know that Intel have acknowledged that there is an issue but they're currently blaming motherboard vendors for being too aggressive with their BIOS settings. Some motherboard vendors are issuing Beta BIOS updates to mitigate these issues.
One workaround you might want to try is to disable hyperthreading in the BIOS. That seems to have stopped the crashes for many users.