Question Game Crashes

[IG agar]

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

 

[Eximo]

Have you tried updating the BIOS? Memory compatibility fixes are usually part of BIOS updates.

Memory controller is inside the CPU these days. Could be the sign of a bad CPU. Can't rule out the motherboard itself either.

I would start with a BIOS update, then run something like MemTestx86 outside of windows to see how it behaves. If it passes that, then you may have a corrupt OS from the first potentially bad memory.

 

[IG agar]

I think I have updated bios.. Also I'll just say What has happened to me in the past 1 year so you could tell me which 1 might be the issue. Cause I have warranty for every product but I dont wanna go to the shop and claim 3 hardwares. Installed os twice with actual key

When 2 ram sticks = Crash every 10 mins + bsod
when only 1 stick = No bsod but game crashes very rarely

So I replaced both sticks but same thing happens.

Also There is no lag or frame drop but game works for few mins but suddenly closes the game to desktop.

 

[Eximo]

You can try potentially increasing the DRAM voltage slightly, or tuning the memory to a lower speed.

You'll need to find some evidence of where the problem is coming from. Have you tried swapping out each stick individually, or just always using the one stick in the same slot? If you can get the system to boot with memory in the other channel and it works, that would narrow it down to the CPU having a bad channel or the motherboard slots for that channel having a problem.

You can also try removing and reinstalling the CPU in case it is just a bad connection. Too tight of a CPU cooler can also cause issues, so removing it, checking the CPU, and putting it back together may solve the problem.

A lot to try before throwing the parts cannon at it.

 

[Ralston18]

Seconding @Eximo

Find some evidence of where the problem is coming from.

Look in Reliabililty History/Monitor and Event Viewer for error codes, warnings, and even informational events just before or at the times of BSODs and crashes.

Start with Reliability History/Monitor. Much more end user friendly and the timeline format may reveal a pattern.

Event Viewer requires more time and effort to both navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Error IDs may or may not be directly helpful. However they may provide a clue or two.

= = = =

Also - update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

What games are being played?

= = = =

As another immediate thing you can do:

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all cards, connectors, RAM, jumpers, and case connections are fully and firmly in place. Check case/front panel connections as well.

Use a bright flashlight to inspect for signs of damage.

 

[IG agar]

You can try potentially increasing the DRAM voltage slightly, or tuning the memory to a lower speed.

You'll need to find some evidence of where the problem is coming from. Have you tried swapping out each stick individually, or just always using the one stick in the same slot? If you can get the system to boot with memory in the other channel and it works, that would narrow it down to the CPU having a bad channel or the motherboard slots for that channel having a problem.

You can also try removing and reinstalling the CPU in case it is just a bad connection. Too tight of a CPU cooler can also cause issues, so removing it, checking the CPU, and putting it back together may solve the problem.

A lot to try before throwing the parts cannon at it.

Thank you for responding... IDK what the DRAM voltage should be for my parts So can you please tell me with the parts that I Have?
Ram: corsair vengeance 16gb ddr5 5200mhz
CPU: Ryzen 9 7900x
Motherboard: Gigabyte b650 gaming x AX
PSU: Cooler master 750w gold

Memory speed is at 4800 already.
Also changed 6 different sticks (Same corsair ram) so No ram problem then
I will probably carry this pc to the shop and try swapping ram slots and adjust cpu cause when I tried that last time I messed up.

 

[IG agar]

Seconding @Eximo

Find some evidence of where the problem is coming from.

Look in Reliabililty History/Monitor and Event Viewer for error codes, warnings, and even informational events just before or at the times of BSODs and crashes.

Start with Reliability History/Monitor. Much more end user friendly and the timeline format may reveal a pattern.

Event Viewer requires more time and effort to both navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

Error IDs may or may not be directly helpful. However they may provide a clue or two.

= = = =

Also - update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

What games are being played?

= = = =

As another immediate thing you can do:

Power down, unplug, open the case.

Clean out dust and debris.

Verify by sight and feel that all cards, connectors, RAM, jumpers, and case connections are fully and firmly in place. Check case/front panel connections as well.

Use a bright flashlight to inspect for signs of damage.

Hey Thank you for the reply.. My specs are:
Ram: corsair vengeance 16gb ddr5 5200mhz
CPU: Ryzen 9 7900x
Motherboard: Gigabyte b650 gaming x AX
PSU: Cooler master 750w gold (new)
GPU: RTX 4070ti
windows 10 (Real not fake btw)
adata XPG s70 blade 1tb nvme
seagate sata 4tb hdd
All the products are new 10 months old no second hand
Games Crashed (Pretty much every game) : World war z, Watch dogs 2, Dead by daylight, Satisfactory, valorant

Games been crashing since day 1 of this pc so probably not any dust or debris or even any damages.


Yes I have got some errors in event viewer but Sometimes I got nothing and sometimes different error. These Are some of the error

The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3

Graphics Exception: SKEDCHECK02_LOCAL_MEMORY_LOW_SIZE failed

The message resource is present but the message was not found in the message table



The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3

Graphics Exception: ESR 0x407020=0x802200 0x407028=0x0 0x40702c=0x352f35a 0x407030=0x0

The message resource is present but the message was not found in the message table

The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3

Error occurred on GPUID: 100

The message resource is present but the message was not found in the message table

 

[Ralston18]

Re: "nvlddmkm"

https://malwaretips.com/blogs/nvldd...-,Nvlddmkm.,to system instability and crashes.

Be sure to look for other similar links.

Try the built in Windows troubleshooters. The troubleshooters may find and fix something.

Also try "dism" and "sfc /scannow".

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

 

[IG agar]

Re: "nvlddmkm"

https://malwaretips.com/blogs/nvlddmkm-sys-bsod-what-it-is-how-to-fix-it/#:~:text=sys?-,Nvlddmkm.,to system instability and crashes.

Be sure to look for other similar links.

Try the built in Windows troubleshooters. The troubleshooters may find and fix something.

Also try "dism" and "sfc /scannow".

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

I have done every scan and dism and new os. Literally everything also nvlddmkm error happened only once out of like 20 crashes. I feel like it is defo related to hardware but dont know which one

 

[Ralston18]

Next step then:

Look in Reliability History/Monitor and Event Viewer for error codes, warnings, and even informational events that occured just before or at the time of those other 19 crashes.

Reliability History/Monitor is end user friendly and the timeline format may reveal some patterns.

Event Viewer requires more time and effort to navigate and understand.

To help:

How To - How to use Windows 10 Event Viewer | Tom's Hardware Forum (tomshardware.com)

You can click any given entry for more details. The details may or may not prove helpful.

Overall, to me anyway, increasing numbers of errors and varying errors is a sign of a faltering or failing PSU.

However, if the most of the error codes are identical then the meaning of those codes will prove helpful.

Take your time, no need to rush, make note of error codes. Especially critical (red circle X).

 

[IG agar]

Thank you for replying.. I have been using event viewer for months but for me it doesn't show some game crash errors. But for context Im gonna say what has happened to me till now.

When 2 ram sticks installed: BSOD and Game crash every 10 mins
when 1 sticks = no BSOD but rare game crash (game crash once a month). But I have changed both sticks. Individually it works fine (So no Ram problem)
That's kinda weird and IDK what to do.

 

[Ralston18]

This motherboard?

https://download.gigabyte.com/FileL...1501_e.pdf?v=6f6656dcd5e62bb6edd30d09b072c24e

[Do verify that I found the applicable User Manual.]

Review the entire User Manual to double check all connections and configurations.

Then take a closer look at Section 2-4 "Installing the Memory". Be very sure that the installed RAM is indeed supported, correctly installed (slot placements), and correcty configured accordingly.

Note the guidelines.

Be sure to check Gigabytes' website for any RAM related updates, changes, or corrections.

 

[IG agar]

This motherboard?

https://download.gigabyte.com/FileL...1501_e.pdf?v=6f6656dcd5e62bb6edd30d09b072c24e

[Do verify that I found the applicable User Manual.]

Review the entire User Manual to double check all connections and configurations.

Then take a closer look at Section 2-4 "Installing the Memory". Be very sure that the installed RAM is indeed supported, correctly installed (slot placements), and correcty configured accordingly.

Note the guidelines.

Be sure to check Gigabytes' website for any RAM related updates, changes, or corrections.

Thank you again for taking ur time to help me. Tonight I'm gonna go through the whole of user manual. Also played for 2 hrs of games today and it did not crash (pc's are weird man)