Question I had a BSOD while playing COD MW III ?

[CryptoKali]

I recently had a BSOD while playing COD MW III. I was playing COD and then I hit windows key to tab out and use chrome to check my email.

I do have crashes when launching the game most of the time but, it's COD not properly optimized and other people have this issue also.

Here is the dump, what does this mean?

1. Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
2. Copyright (c) Microsoft Corporation. All rights reserved.
3. 
   
4. 
   
5. Loading Dump File [C:\Users\*\Downloads\050924-7000-01.dmp]
6. Mini Kernel Dump File: Only registers and stack trace are available
7. 
   
8. Symbol search path is: srv*
9. Executable search path is:
10. Windows 10 Kernel Version 22621 MP (32 procs) Free x64
11. Product: WinNt, suite: TerminalServer SingleUserTS
12. Machine Name:
13. Kernel base = 0xfffff807`4d400000 PsLoadedModuleList = 0xfffff807`4e0134a0
14. Debug session time: Thu May 9 18:02:27.564 2024 (UTC - 4:00)
15. System Uptime: 0 days 4:06:40.217
16. Loading Kernel Symbols
17. ...............................................................
18. ................................................................
19. ................................................................
20. .........
21. Loading User Symbols
22. Loading unloaded module list
23. ..........
24. For analysis of this file, run !analyze -v
25. nt!KeBugCheckEx:
26. fffff807`4d818040 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffef0a`165770c0=000000000000000a
27. 4: kd> !analyze -v
28. *******************************************************************************
29. * *
30. * Bugcheck Analysis *
31. * *
32. *******************************************************************************
33. 
    
34. DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
35. An attempt was made to access a pageable (or completely invalid) address at an
36. interrupt request level (IRQL) that is too high. This is usually
37. caused by drivers using improper addresses.
38. If kernel debugger is available get stack backtrace.
39. Arguments:
40. Arg1: 0000000000000000, memory referenced
41. Arg2: 0000000000000002, IRQL
42. Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
43. Arg4: 0000000000000000, address which referenced memory
44. 
    
45. Debugging Details:
46. ------------------
47. 
    
48. 
    
49. KEY_VALUES_STRING: 1
50. 
    
51. Key : Analysis.CPU.mSec
52. Value: 2467
53. 
    
54. Key : Analysis.DebugAnalysisManager
55. Value: Create
56. 
    
57. Key : Analysis.Elapsed.mSec
58. Value: 3022
59. 
    
60. Key : Analysis.Init.CPU.mSec
61. Value: 1437
62. 
    
63. Key : Analysis.Init.Elapsed.mSec
64. Value: 16092
65. 
    
66. Key : Analysis.Memory.CommitPeak.Mb
67. Value: 81
68. 
    
69. 
    
70. TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
71. 
    
72. 
    
73. DUMP_FILE_ATTRIBUTES: 0x1808
74. Kernel Generated Triage Dump
75. 
    
76. BUGCHECK_CODE: d1
77. 
    
78. BUGCHECK_P1: 0
79. 
    
80. BUGCHECK_P2: 2
81. 
    
82. BUGCHECK_P3: 8
83. 
    
84. BUGCHECK_P4: 0
85. 
    
86. READ_ADDRESS: fffff8074e11c4a8: Unable to get MiVisibleState
87. Unable to get NonPagedPoolStart
88. Unable to get NonPagedPoolEnd
89. Unable to get PagedPoolStart
90. Unable to get PagedPoolEnd
91. unable to get nt!MmSpecialPagesInUse
92. 0000000000000000
93. 
    
94. PROCESS_NAME: chrome.exe
95. 
    
96. BLACKBOXBSD: 1 (!blackboxbsd)
97. 
    
98. 
    
99. BLACKBOXNTFS: 1 (!blackboxntfs)
100. 
     
101. 
     
102. BLACKBOXPNP: 1 (!blackboxpnp)
103. 
     
104. 
     
105. BLACKBOXWINLOGON: 1
106. 
     
107. CUSTOMER_CRASH_COUNT: 1
108. 
     
109. TRAP_FRAME: ffffef0a16577200 -- (.trap 0xffffef0a16577200)
110. NOTE: The trap frame does not contain all registers.
111. Some register values may be zeroed or incorrect.
112. rax=0000000000000083 rbx=0000000000000000 rcx=dc82dbaa4bfd0000
113. rdx=ffffeb75badd67f8 rsi=0000000000000000 rdi=0000000000000000
114. rip=0000000000000000 rsp=ffffef0a16577390 rbp=000000011f14b800
115. r8=ffffeb7589300230 r9=ffffeb75badd6000 r10=ffffeb7580000000
116. r11=fffff8074e069400 r12=0000000000000000 r13=0000000000000000
117. r14=0000000000000000 r15=0000000000000000
118. iopl=0 nv up ei ng nz na pe nc
119. 00000000`00000000 ?? ???
120. Resetting default scope
121. 
     
122. IP_IN_FREE_BLOCK: 0
123. 
     
124. FAILED_INSTRUCTION_ADDRESS:
125. +0
126. STACK_TEXT:
127. ffffef0a`165770b8 fffff807`4d82de69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
128. ffffef0a`165770c0 fffff807`4d829305 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000000ff : nt!KiBugCheckDispatch+0x69
129. ffffef0a`16577200 00000000`00000000 : ffffc584`1f14b780 000024c0`08df7000 00000000`00000001 ffffeb12`00000000 : nt!KiPageFault+0x485
130. 
     
131. 
     
132. SYMBOL_NAME: nt!KiPageFault+485
133. 
     
134. MODULE_NAME: nt
135. 
     
136. IMAGE_NAME: ntkrnlmp.exe
137. 
     
138. IMAGE_VERSION: 10.0.22621.3527
139. 
     
140. STACK_COMMAND: .thread ; .cxr ; kb
141. 
     
142. BUCKET_ID_FUNC_OFFSET: 485
143. 
     
144. FAILURE_BUCKET_ID: AV_CODE_AV_NULL_IP_nt!KiPageFault
145. 
     
146. OSPLATFORM_TYPE: x64
147. 
     
148. OSNAME: Windows 11
149. 
     
150. FAILURE_ID_HASH: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}
151. 
     
152. Followup: MachineOwner

 

[CodeConnoisseur]

A faulty driver tried to dereference a null pointer, potentially after that driver received bad data from its hardware. Probably a driver bug, but you'd need to examine the stack trace further to know exactly which driver and why.

 

[ubuysa]

Upload the dump (and any other recent dumps) to a cloud service with a link to them here.

 

[CryptoKali]

A faulty driver tried to dereference a null pointer, potentially after that driver received bad data from its hardware. Probably a driver bug, but you'd need to examine the stack trace further to know exactly which driver and why.

How would I do that?

Upload the dump (and any other recent dumps) to a cloud service with a link to them here.

Here is the dump, https://drive.google.com/file/d/1ilTMjYhxzhkCAHOqeJDtG3Jg7C7FtiCN/view?usp=sharing

 

[ubuysa]

It's never wise to make a diagnosis based on just one dump, but having looked through the dump I think this is more likely to be a RAM issue than a bad driver. It's true that the bugcheck is a DRIVER_IRQL_NOT_LESS_OR_EQUAL which is typically caused by a bad third-party driver, but in this case there are no third-party drivers called in the lead up to the bucheck. The Microsoft functions that are being called are all related to either memory access failures or the recovery from them.

I can see that you have 32GB of RAM installed in two 16GB TeamGroup UD5 5200MHz sticks. The first thing I suggest you do is to remove the XMP (or similar) overclock on the RAM, I suspect the base clock speed is 4800MHz. See whether it BSODs at that setting.

I also suggest you run Memtest86 to stress test your RAM, both with XMP disabled and with XMP enabled at 5200MHz...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

BTW You do know there is an issue with the i9-14900KF CPU (which you have) in some games?
https://en.overclocking.com/intel-core-i9-14900k-13900k-kings-of-crashes/
https://www.xda-developers.com/intel-13th-gen-14th-gen-crashes/
https://community.intel.com/t5/Proc...ue-with-proc-I9-14900K-crash-BSOD/m-p/1596718
I know that Intel are encouraging motherboard vendors to adopt new, more stable, BIOS settings for these particular CPUs. It may well be that the problem you have is caused by this CPU instability.

 

[CryptoKali]

It's never wise to make a diagnosis based on just one dump, but having looked through the dump I think this is more likely to be a RAM issue than a bad driver. It's true that the bugcheck is a DRIVER_IRQL_NOT_LESS_OR_EQUAL which is typically caused by a bad third-party driver, but in this case there are no third-party drivers called in the lead up to the bucheck. The Microsoft functions that are being called are all related to either memory access failures or the recovery from them.

I can see that you have 32GB of RAM installed in two 16GB TeamGroup UD5 5200MHz sticks. The first thing I suggest you do is to remove the XMP (or similar) overclock on the RAM, I suspect the base clock speed is 4800MHz. See whether it BSODs at that setting.

I also suggest you run Memtest86 to stress test your RAM, both with XMP disabled and with XMP enabled at 5200MHz...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

BTW You do know there is an issue with the i9-14900KF CPU (which you have) in some games?
https://en.overclocking.com/intel-core-i9-14900k-13900k-kings-of-crashes/
https://www.xda-developers.com/intel-13th-gen-14th-gen-crashes/
https://community.intel.com/t5/Proc...ue-with-proc-I9-14900K-crash-BSOD/m-p/1596718
I know that Intel are encouraging motherboard vendors to adopt new, more stable, BIOS settings for these particular CPUs. It may well be that the problem you have is caused by this CPU instability.

Thanks for the tip, and no I did not know there were problems with the i9-14900KF.

 

[ubuysa]

Thanks for the tip, and no I did not know there were problems 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.

 

[CryptoKali]

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.

Alrighty, thanks.