Game Crashes
Game Crashes
Hey its been a Year since I have bought my new pc. It used to BSOD and game crashes almost every 10 mins. I then did a windows memory diagnostic tool and It showed me that there was a problem with the ram. So I changed both sticks but I still got the same game crashes and bsod But For some reason if i remove 1 stick I get less game crashes. Also Its not anything related to software I feel like.
This is the new crash report (I can also send old reports for more context)
For analysis of this file, run !analyze -v
ntdll!NtWaitForSingleObject+0x14:
00007ffd`8ea4d064 c3 ret
0:023> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Fault
Value: Read
Key : Analysis.CPU.mSec
Value: 531
Key : Analysis.Elapsed.mSec
Value: 14828
Key : Analysis.IO.Other.Mb
Value: 19
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 29
Key : Analysis.Init.CPU.mSec
Value: 187
Key : Analysis.Init.Elapsed.mSec
Value: 28373
Key : Analysis.Memory.CommitPeak.Mb
Value: 668
Key : Failure.Hash
Value: {b880b459-66c5-2609-4da4-2db681e2bb39}
Key : Timeline.OS.Boot.DeltaSec
Value: 98677
Key : Timeline.Process.Start.DeltaSec
Value: 194
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 5.4.0.0
FILE_IN_CAB: UEMinidump.dmp
CONTEXT: (.ecxr)
rax=00000000ffffffff rbx=000001a090839ed0 rcx=0000000000000000
rdx=000001a040c28090 rsi=000001a0a3daee90 rdi=000001a0a3df3080
rip=00007ff6192aef33 rsp=0000008e102ff200 rbp=0000008e102ff220
r8=0076006e0065002e r9=0000008e0e55d690 r10=0000008e0e55d658
r11=0076006e0065002e r12=0000008e0e55d658 r13=000001a004f4efe8
r14=00000000fdbfa177 r15=0000008e0e55d640
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
_Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x1acaeb:
00007ff6`192aef33 4d8b5b20 mov r11,qword ptr [r11+20h] ds:0076006e`0065004e=????????????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff6192aef33 _Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x00000000001acaeb)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
PROCESS_NAME:
READ_ADDRESS: ffffffffffffffff
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
STACK_TEXT:
0000008e`102ff200 00007ff6`192b5d08 : 0076006e`0065002e 000001a0`35f70900 000001a0`a3df3080 000001a0`43f846f0 : Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x1acaeb
0000008e`102ff260 00007ff6`192929b3 : 00000000`00006e93 00000000`00006e93 00000000`00006e93 0000008e`0e55d418 : _Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x1b38c0
0000008e`102ff3d0 00007ff6`158cebdf : 0000008e`0e55d370 00000000`00000000 00000000`00000000 00000000`00000010 : Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x19056b
0000008e`102ff560 00007ff6`158cf0ad : 000001a1`057115a8 000001a0`055b3d00 00000000`00000000 00007ff6`14f0980f : Shipping!FSVGFDenoiser::GetWrappedDenoiser+0x28cf3f
0000008e`102ff6b0 00007ff6`14e9ee7d : 000001a1`057115a8 00007ff6`25c67200 00000000`00000000 000000e5`c07b6f8d : Shipping!FSVGFDenoiser::GetWrappedDenoiser+0x28d40d
0000008e`102ff6e0 00007ff6`14e9ec93 : 000001a0`03c75d80 000001a1`057115a8 00000000`00000005 00007ff6`20cddc20 : Shipping!png_write_chunk_end+0x6c19dd
0000008e`102ff760 00007ff6`14e9fd2c : 000001a1`057115a8 0000008e`102ff808 00000000`00000000 00007ff6`25c67200 : Shipping!png_write_chunk_end+0x6c17f3
0000008e`102ff7a0 00007ff6`170cf237 : 000001a0`45208f00 000001a0`03c75d80 000001a0`06204e00 0000008e`000003b9 : Shipping!png_write_chunk_end+0x6c288c
0000008e`102ff850 00007ff6`152f1e67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : Shipping!FSVGFDenoiser::GetDebugName+0xbdac83
0000008e`102ff890 00007ff6`15d0be0d : 00000000`00000000 00000000`00000000 00000000`00000001 00007ff6`15d0bc09 : Shipping!png_write_chunk_end+0xb149c7
0000008e`102ff8f0 00007ff6`15d0bb3b : 00000000`00000001 000001a0`45952bc2 000030af`0014caaa 00000000`00000008 : Shipping!FSVGFDenoiser::GetShadowRequirements+0x100c81
0000008e`102ff920 00007ff6`15d0b99e : 00000000`00000000 000001a0`45952b16 000001a0`04d20bc0 000001a0`04d20bc0 : Shipping!FSVGFDenoiser::GetShadowRequirements+0x1009af
0000008e`102ff950 00007ffd`8e3d7344 : 000001a0`04d20bc0 00000000`00000000 00000000`00000000 00000000`00000000 : Shipping!FSVGFDenoiser::GetShadowRequirements+0x100812
0000008e`102ff9b0 00007ffd`8ea026b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
0000008e`102ff9e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
STACK_COMMAND: ~23s; .ecxr ; kb
FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_Shipping.exe!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 5.4.0.0
FAILURE_ID_HASH: {b880b459-66c5-2609-4da4-2db681e2bb39}
Value: 5.4.0.0
FILE_IN_CAB: UEMinidump.dmp
Have you considered updating the BIOS? Memory compatibility improvements are often included in BIOS updates. The memory controller is now integrated within the CPU, which might indicate a faulty CPU or even the motherboard itself. I suggest beginning with a BIOS update, then using tools like MemTestx86 outside of Windows to assess performance. If it succeeds, it could point to a corrupt operating system stemming from problematic memory.
I believe my bios have been updated. Also, I’d just like to share what’s happened over the past year so you can help identify which one might be causing the problem. I have a warranty on every product, but I don’t want to go to the shop and claim three devices. I installed the OS twice using the original key. When using two RAM sticks, the system crashes every 10 minutes plus BSOD, while with only one stick it doesn’t crash but the game freezes very occasionally. After replacing both sticks, the issue still occurs. Also, there’s no lag or frame drops, but the game runs for a few minutes before suddenly closing the desktop.
You might consider slightly adjusting the DRAM voltage or adjusting the memory speed. Look for clues about the issue by testing each stick separately or using a different channel. If the system boots with the other channel, the problem likely lies with the CPU's channel or the motherboard slots. You can also attempt to remove and reinstall the CPU to check for connection issues, and ensure the cooler fits properly. It may take some trial and error before you need to replace parts.
Please let me know the DRAM voltage you have available for your build. I can help you with the parts you currently possess.
Here’s a revised version of your text:
Hey, thank you for your response.
My system specs are as follows:
- RAM: Corsair Vengeance 16GB DDR5 5200MHz
- CPU: Ryzen 9 7900X
- Motherboard: Gigabyte B650 Gaming X AX
- Power Supply: Cooler Master 750W Gold (new)
- GPU: RTX 4070 Ti
- Operating System: Windows 10 (real, not fake)
- Storage: ADATA XPG S70 1TB NVMe, Seagate SATA 4TB HDD
All items are brand new and were purchased within the last ten months.
I’ve experienced crashes in several games: World War Z, Watch Dogs 2, Dead by Daylight, Satisfactory, and Valorant. These issues started from the very beginning, so it’s unlikely there was any dust, debris, or damage.
There are some errors in the Event Viewer, but sometimes nothing appears and other times different messages show up. Some of the errors I’ve noticed include:
- The description for Event ID 13 from the source nvlddmkm isn’t available. It could be because the relevant component isn’t installed or the installation is corrupted. You can try reinstalling or fixing it locally.
- If the event happened on another machine, the display details should have been saved with it.
The following details were recorded with the event:
- Device: Video3
- Graphics Exception: SKEDCHECK02_LOCAL_MEMORY_LOW_SIZE failed
- Message Resource: Present, but not found in the table
- Description for Event ID 13: The component isn’t installed or installation is corrupted. You can fix it on your PC.
- Error on GPUID: 100
- Message Resource: Present, but not found in the table
If the event came from another computer, make sure to save the display information with it.
Check for related links and use the built-in Windows troubleshooters. They might resolve the issue. Also consider running "dism" and "sfc /scannow". Refer to the provided articles for guidance.
Thank you for your reply. I've been using the event viewer for several months, but it doesn't display some game crash errors. To give you a clear picture of what's happened so far.
Initially, when two RAM sticks were installed: I experienced BSOD and game crashes every 10 minutes.
After switching to one RAM stick at a time, there was no BSOD, but occasional game crashes occurred about once a month.
However, after replacing both sticks, everything worked properly (no RAM issues).
That's quite unusual and I'm not sure what to do next.
This motherboard?
https://download.gigabyte.com/FileL...15...09b072c24e
[Make sure you found the relevant User Manual.]
Go through the entire User Manual to confirm all connections and settings.
Then carefully examine Section 2-4 "Installing the Memory". Ensure the RAM you installed is compatible, properly placed, and correctly set up.
Follow the instructions.
Also, check Gigabytes' website for any updates, changes, or corrections regarding RAM.