Game crashes

[IGagar]

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.Bucket
Value: INVALID_POINTER_READ_c0000005_FortniteClient-Win64-Shipping.exe!Unknown

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
FortniteClient_Win64_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 (FortniteClient_Win64_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: FortniteClient-Win64-Shipping.exe

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 : FortniteClient_Win64_Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x1acaeb
0000008e`102ff260 00007ff6`192929b3 : 00000000`00006e93 00000000`00006e93 00000000`00006e93 0000008e`0e55d418 : FortniteClient_Win64_Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x1b38c0
0000008e`102ff3d0 00007ff6`158cebdf : 0000008e`0e55d370 00000000`00000000 00000000`00000000 00000000`00000010 : FortniteClient_Win64_Shipping!FSVGFDenoiser::SupportsScreenSpaceDiffuseIndirectDenoiser+0x19056b
0000008e`102ff560 00007ff6`158cf0ad : 000001a1`057115a8 000001a0`055b3d00 00000000`00000000 00007ff6`14f0980f : FortniteClient_Win64_Shipping!FSVGFDenoiser::GetWrappedDenoiser+0x28cf3f
0000008e`102ff6b0 00007ff6`14e9ee7d : 000001a1`057115a8 00007ff6`25c67200 00000000`00000000 000000e5`c07b6f8d : FortniteClient_Win64_Shipping!FSVGFDenoiser::GetWrappedDenoiser+0x28d40d
0000008e`102ff6e0 00007ff6`14e9ec93 : 000001a0`03c75d80 000001a1`057115a8 00000000`00000005 00007ff6`20cddc20 : FortniteClient_Win64_Shipping!png_write_chunk_end+0x6c19dd
0000008e`102ff760 00007ff6`14e9fd2c : 000001a1`057115a8 0000008e`102ff808 00000000`00000000 00007ff6`25c67200 : FortniteClient_Win64_Shipping!png_write_chunk_end+0x6c17f3
0000008e`102ff7a0 00007ff6`170cf237 : 000001a0`45208f00 000001a0`03c75d80 000001a0`06204e00 0000008e`000003b9 : FortniteClient_Win64_Shipping!png_write_chunk_end+0x6c288c
0000008e`102ff850 00007ff6`152f1e67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : FortniteClient_Win64_Shipping!FSVGFDenoiser::GetDebugName+0xbdac83
0000008e`102ff890 00007ff6`15d0be0d : 00000000`00000000 00000000`00000000 00000000`00000001 00007ff6`15d0bc09 : FortniteClient_Win64_Shipping!png_write_chunk_end+0xb149c7
0000008e`102ff8f0 00007ff6`15d0bb3b : 00000000`00000001 000001a0`45952bc2 000030af`0014caaa 00000000`00000008 : FortniteClient_Win64_Shipping!FSVGFDenoiser::GetShadowRequirements+0x100c81
0000008e`102ff920 00007ff6`15d0b99e : 00000000`00000000 000001a0`45952b16 000001a0`04d20bc0 000001a0`04d20bc0 : FortniteClient_Win64_Shipping!FSVGFDenoiser::GetShadowRequirements+0x1009af
0000008e`102ff950 00007ffd`8e3d7344 : 000001a0`04d20bc0 00000000`00000000 00000000`00000000 00000000`00000000 : FortniteClient_Win64_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


SYMBOL_NAME: FortniteClient_Win64_Shipping+1acaeb

MODULE_NAME: FortniteClient_Win64_Shipping

IMAGE_NAME: FortniteClient-Win64-Shipping.exe

STACK_COMMAND: ~23s; .ecxr ; kb

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_FortniteClient-Win64-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}

 

[xrobwx71]

Follow these instructions please. Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8(.1), 7 and Vista

 

[IGagar]

Follow these instructions please. Blue Screen of Death (BSOD) Posting Instructions - Windows 11, 10, 8(.1), 7 and Vista

I dont get BSOD. My Game crashes

 

[xrobwx71]

The instructions are for the section, not what you think might or might not be happening. When a user follows the instructions, it gives us a plethora of information that gets us closer to a diagnosis. The information may tell us why your game is crashing.

 

[IGagar]

Thank you for responding. Agree with you on that but Can i Do this after I get more crashes cause I used to get crashes every day for the last 6 months but for past 2 months it has happened only once so I wanna see If it was natural game crash or something wrong with the pc. Basically I'll try to play more games for more hours to see if its my pc. Also Do i lose any files while testing?

 

[ubuysa]

We don't ask people to follow our BSOD Posting Instructions just to be difficult. It's much easier for you to do one upload of all the important troubleshooting data than to have us keep coming back asking for different data every day.

I appreciate that you are frustrated by this issue and that you have your own thoughts on what might or might not be the cause, but if you've come here asking for help then we ask that you trust us to help you, so if we ask for a data upload we really do need to see it. If you are concerned about the data that will be uploaded you can find a full description of what data is collected here. Most files in the upload are txt or html files so you can easily see what we will see. Please DO NOT change or delete anything however.

 

[Corday]

Bringing this thread up to date, OP posted this on the other forum April 12th:

"my motherboard goes with ram. Also updated new chipset and gpu driver. So basically There was 1 crash in the last 2 months but before That I used to crash every 10 mins. So I'm Gonna play different games and more hrs to see if I can get crashes. If yes then ima do what sysnative asks. Also thank you for taking ur time to reply '

 

[IGagar]

We don't ask people to follow our BSOD Posting Instructions just to be difficult. It's much easier for you to do one upload of all the important troubleshooting data than to have us keep coming back asking for different data every day.

I appreciate that you are frustrated by this issue and that you have your own thoughts on what might or might not be the cause, but if you've come here asking for help then we ask that you trust us to help you, so if we ask for a data upload we really do need to see it. If you are concerned about the data that will be uploaded you can find a full description of what data is collected here. Most files in the upload are txt or html files so you can easily see what we will see. Please DO NOT change or delete anything however.

Thanks a lot :) yea I trust you guys but I just wanna see if it was an actual crash like i have been getting back in the days or It was a random 1 time crash. So Right now I'm testing my pc by playing and rendering videos to see if a crash occurs. I just dont wanna waste ur guys time if it was a normal 1 time crash

 

[ubuysa]

No problem. Just be sure to upload the SysnativeBSODColletionApp output if you do need to post again.