Question All my games keep crashing without error?

[Bless6d]

This is the game crash dump


Microsoft (R) Windows Debugger Version 10.0.22621.755 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\semla\AppData\Local\VALORANT\Saved\Crashes\UE4CC-Windows-AF9625684504988BB09C2A96400EDE77_0000\UE4Minidumssp.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
Machine Name:
Debug session time: Sun Dec 4 18:10:33.000 2022 (UTC + 1:00)
System Uptime: not available
Process Uptime: 0 days 0:08:58.000
................................................................
................................................................
........................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(4e38.3f48): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtWaitForSingleObject+0x14:
00007ff85610ee84 c3 ret 0:000> !analyze -v ******************************************************************************* [LIST] [*]* [*]Exception Analysis * [*]* [/LIST] ******************************************************************************* *** WARNING: Unable to verify timestamp for XAudio2_7.dll KEY_VALUES_STRING: 1 Key : AV.Fault Value: Read Key : Analysis.CPU.mSec Value: 37890 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 59211 Key : Analysis.Init.CPU.mSec Value: 312 Key : Analysis.Init.Elapsed.mSec Value: 37827 Key : Analysis.Memory.CommitPeak.Mb Value: 577 Key : Timeline.Process.Start.DeltaSec Value: 538 Key : WER.Process.Version Value: 4.26.2.0 FILE_IN_CAB: UE4Minidumssp.dmp CONTEXT: (.ecxr) rax=0000000000071488 rbx=00000270682b4b20 rcx=0000000000000000 rdx=000000000001ecc0 rsi=00007ff7f84bf060 rdi=0000000000000000 rip=00007ff7f26e03fb rsp=000000d93cf7e760 rbp=3333333333333333 r8=0000010044765cfe r9=5555555555555555 r10=0000000000000004 r11=00000000a00f44f4 r12=0000000000000038 r13=0000000000000000 r14=0000000044765cce r15=0000000000078261 iopl=0 nv up ei pl nz na po nc cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206 VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xaa7a8b: 00007ff7f26e03fb 8b4a08 mov ecx,dword ptr [rdx+8] ds:000000000001ecc8=???????? Resetting default scope EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 00007ff7f26e03fb (VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0x0000000000aa7a8b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: 000000000001ecc8 Attempt to read from address 000000000001ecc8 PROCESS_NAME: VALORANT-Win64-Shipping.exe READ_ADDRESS: 000000000001ecc8 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: 000000000001ecc8 STACK_TEXT: 000000d93cf7e760 00007ff7f2a515b0 : 3333333333333333 00007ff7f859d6c0 0000000000000000 00007ff7f2708604 : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xaa7a8b 000000d93cf7e7b0 00007ff7f2a4934f : 00007ff7f859d6c0 00007ff7f2707e65 00007ff7f859d700 0000000000000000 : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xe18c40 000000d93cf7e820 00007ff7f13184b4 : 00000270ff56bc80 00000271005f8580 fffffffffffffffe 0000027011f03340 : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xe109df 000000d93cf7e860 00007ff7f29e3f77 : 000002703144ea00 00000270ff56bc80 00000270ff56bc80 0000000000000b19 : VALORANT_Win64_Shipping!AK::SoundEngine::UnregisterResourceMonitorCallback+0x66fb4 000000d93cf7e890 00007ff7f29ca2e6 : 0000001d9f58eb62 000000d93cf7e999 00000000000089e3 0000001d9f58eb5a : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xdab607 000000d93cf7e900 00007ff7f29ca470 : 0000000000000000 0000000000000000 ffffffffffffff00 00007ff7f8599c01 : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xd91976 000000d93cf7ea00 00007ff7f29b449a : 00007ff7f859a500 0000000000000001 0000001d9f533300 0000001d9f530e00 : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xd91b00 000000d93cf7ea60 00007ff7f29e4372 : 00007ff7f859a590 0000000000000000 00007ff7f859a500 0000001d9f50536a : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xd7bb2a 000000d93cf7eb10 00007ff7f46e4a84 : 000002707a0a99a0 000000d93cf7ebf0 0000000000000000 00007ff7f859a5a0 : VALORANT_Win64_Shipping!AK::WriteBytesMem::Clear+0xdaba02 000000d93cf7eb70 00007ff7f433a3a9 : 0000000000000002 0000000000000000 0000001d9f50160c 000000000000000c : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0xa08a74 000000d93cf7ec10 00007ff7f41bf3e8 : 0000000000000000 000000d900000001 0000000000000000 0000000000000001 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x65e399 000000d93cf7ee80 00007ff7f128ec52 : 00007ff7ef750000 0000001d9f4b8991 0000001d9f4b8800 000000d900000000 : VALORANT_Win64_Shipping!AK::WriteBytesCount::SetCount+0x4e33d8 000000d93cf7f020 00007ff7ef750000 : 0000001d9f4b8991 0000001d9f4b8800 000000d900000000 00007ff7f1289b20 : VALORANT_Win64_Shipping!AK::WriteBytesCount::Reserve+0x7262 000000d93cf7f028 0000001d9f4b8991 : 0000001d9f4b8800 000000d900000000 00007ff7f1289b20 0000000000000002 : VALORANT_Win64_Shipping 000000d93cf7f030 0000001d9f4b8800 : 000000d900000000 00007ff7f1289b20 0000000000000002 0000000000000000 : 0x0000001d9f4b8991
000000d93cf7f038 000000d900000000 : 00007ff7f1289b20 0000000000000002 0000000000000000 0000000000000000 : 0x0000001d9f4b8800 000000d93cf7f040 00007ff7f1289b1f : 0000000000000002 0000000000000000 0000000000000000 0000000000000000 : 0x000000d900000000
000000d93cf7f048 0000000000000002 : 0000000000000000 0000000000000000 0000000000000000 000002705b6a81f0 : VALORANT_Win64_Shipping!AK::WriteBytesCount::Reserve+0x212f
000000d93cf7f050 0000000000000000 : 0000000000000000 0000000000000000 000002705b6a81f0 0000000000000000 : 0x2


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: VALORANT_Win64_Shipping+aa7a8b

MODULE_NAME: VALORANT_Win64_Shipping

IMAGE_NAME: VALORANT-Win64-Shipping.exe

FAILURE_BUCKET_ID: INVALID_POINTER_READ_c0000005_VALORANT-Win64-Shipping.exe!Unknown

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 4.26.2.0

FAILURE_ID_HASH: {d5dda7b9-9874-6eca-bc31-b263f962724a}

Followup: MachineOwner
---------

 

[Ralston18]

Where did you get Valorant?

Source?

 

[Bless6d]

From the original site : https://playvalorant.com/en-us/

 

[Colif]

its a crash dump from the game, I don't think the windows debugger can get much out of it.

What are specs of the PC?

try this:

Right click start
choose terminal (admin)
if it doesn't open as powershell, click the drop down arrow in title row and pick from list


copy/paste this command into window:

Repair-WindowsImage -Online -RestoreHealth

and press enter

Then type SFC /scannow

and press enter

Restart PC if SFC fixes any files as some fixes require a restart to be implemented

First command repairs the files SFC uses to clean files, and SFC fixes system files

SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

not sure it will help

WARNING: Unable to verify timestamp for XAudio2_7.dll

that is part of DirectX.

try updating gpu drivers.

 

[Bless6d]

I already try it ! it doesnt work the games still crashing

PC specs :
i9 9900k
RTX 2070 Super
16Gb Ram 3600Mhz

 

[Colif]

can you look in System Information application
in the left column, click the + next to Software Environment
choose Windows error reporting
Don't click on the date header for the tight column as it will sort it strange

there are 2 types of errors that show here, Application errors & System errors.
can you see anything called a BEX Error or Pre Radar?

What PSU do you have?

 

[Bless6d]

No I olny see Application errors & Windows errors reporting & Application Hang

My PSU : Gigabyte G750H 80 Plus Gold 750W

 

[Colif]

that is a good thing.. although it still leaves me wondering.

I should have asked, what motherboard?
what temperatures are you getting?
I don't think its a driver as you would be getting errors.

what other games apart from valorant? One suggestion is reinstall game or change settings in game
have you changed page file size?

examples to show its not just you - valorant crash (no errors)
link 2

 

[Bless6d]

You can check it here : https://drive.google.com/file/d/1tBVu4kYyMyw0KC2jXcmtvEwN06zz7llT/view?usp=sharing

other crashed games : Fortnite ,Counter-Strike: Global Offensive, Apex legends ....
also Opera Gx browser

I did reinstall ALL of them but it still crash ! and I even did a Clean windows reset, Clean boot, CMD commands...

 

[Bless6d]

Driver or module in which error occurred:

ntdll.dll (ntdll!NtWaitForSingleObject+0x14)

Thats new Game Dump crashed also today : https://drive.google.com/file/d/1qoQ6oqyY1yg1k9JBr2Kbao5ZcZroIkXa/view?usp=sharing

 

[Colif]

try running this on both your ssd
open command prompt (admin)
type chkdsk x: /f and press enter - NOTE: Replace X with drive letter of the ssd
2 paragraphs may pop up, agree to run chkdsk on startup and restart PC to let it run

this is just in case:
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD -

that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
   
2. Navigate to C:\Windows\Minidump
   
3. Copy the mini-dump files out onto your Desktop
   
4. Do not use Winzip, use the built in facility in Windows
   
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
   
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
   
7. Then post a link here to the zip file, so we can take a look for you . . .
   

those game dumps mess up my driver listings as they add a bunch of things that aren't drivers. I am glad I remembered before it finished so I could run virtual machine in a shadow mode so it doesn't save changes. It did it again

conversion of dump

report - click run as fiddle to read


File: UEMinidump.dmp (Dec 9 2022 - 13:09:07)
BugCheck: [ ()]
*** WARNING: Unable to verify timestamp for nvwgf2umx.dll
*** WARNING: Unable to verify timestamp for DiscordHook64.dll
*** WARNING: Unable to verify timestamp for EOSSDK-Win64-Shipping.dll
*** WARNING: Unable to verify timestamp for discord-rpc.dll
*** WARNING: Unable to verify timestamp for GfeSDK.dll
*** WARNING: Unable to verify timestamp for MessageBus.dll
Probably caused by: (Process: FortniteClient-Win64-Shipping.exe)
Uptime: not Day(s), ?? Hour(s), ?? Min(s), and ?? Sec(s)

nvwgf2umx.dll = Nvidia
DiscordHook64.dll & discord-rpc.dll are obvious
EOSSDK-Win64-Shipping.dll = Elite Dangerous
GfeSDK.dll = Nvidia again
MessageBus.dll = Nvidia again

Problem could be discord maybe?
note: its not blaming FortniteClient-Win64-Shipping.exe, its just there should be a driver name after the colon and before the Process brackets. But as dump isn't normal, the format doesn't work. Its not written for game dumps.

 

[Bless6d]

Hello ! thanks for your time ! thats the windows minidump files : https://drive.google.com/file/d/1iE8i1zfwOs8hyOaUQsJUY_6mrbxdRVPp/view?usp=sharing

 

[Colif]

conversion of dump

report - click run as fiddle to read


File: 120822-11703-01.dmp (Dec 9 2022 - 08:58:30)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: ntkrnlmp.exe (Process: opera.exe)
Uptime: 0 Day(s), 4 Hour(s), 16 Min(s), and 22 Sec(s)

File: 120422-12218-01.dmp (Dec 5 2022 - 08:59:41)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
*** WARNING: Unable to verify timestamp for WdFilter.sys
Probably caused by: WdFilter.sys (Process: TiWorker.exe)
Uptime: 0 Day(s), 8 Hour(s), 21 Min(s), and 11 Sec(s)

WARNING: Unable to verify timestamp for WdFilter.sys << that is strange. that is windows defender causing that crash...
defender crashed windows update... windows generally doesn't do that

right click start button
choose terminal (admin)
if it doesn't open as powershell, click the drop down arrow in title row and choose from list
copy/paste this command into window: (if you type it, spacing is important)

Repair-WindowsImage -Online -RestoreHealth
and press enter

Then type SFC /scannow
and press enter

Restart PC if SFC fixes any files as some fixes require a restart to be implemented
First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11


have you run anti virus or malwarebytes?
try running this: https://www.bitdefender.com.au/solutions/free.html
gone back to looking at the 1985 driver as it shouldn't be showing, makes me wonder. some searches of it seem to indicate its been used for some attacks this year. It seems it is used to send messages between sensors.

 

[Bless6d]

Repair-WindowsImage -Online -RestoreHealth Result :
Path :
Online : True
ImageHealthState : Healthy
RestartNeeded : False

SFC /scannow Result :
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.


and the Game still crashes and closes unexpectedly ! I think its a software bug

 

[Colif]

try updating Intel network drivers, here under LAN - https://www.msi.com/Motherboard/MPG-Z390-GAMING-PLUS/support#driver
they could be involved in both crashes.

I think its a software bug

it probably is. Just need to find it.

 

[Colif]

not sure if it means anything but I found the same Microsoft driver on 2 peoples PC today.

Mar 20 1985

wtd.sys

Generally Microsoft drivers don't show in the 3rd party driver list, so it made me look... alas, I can't find a great deal about it. It appears to be a kernel driver.

try running the anti virus scans I suggested. Most of results online for that file are this month so makes me wonder if there is a virus pretending to be it or something.
It might not be anything.

 

[Bless6d]

I try it and i entered again to play the game but same problem the game crashed with this dump : https://drive.google.com/file/d/1Dp25GI5y9hYb_lAGL1kt7lPbmdWSkPRf/view?usp=sharing

 

[Colif]

is that a game dump or a mini dump?
the program I use really isn't any good for game dumps. The results don't tell me anything.

No I olny see Application errors & Windows errors reporting & Application Hang

maybe I didn't explain it well enough, BEX & Pre Radar will be showing as a windows error reporting line.
like for instance the 2nd one on my print out

so perhaps look again

 

[Bless6d]

I understand ! after a re- check i found RADAR_PRE_LEAK and BEX64 on windows error reporting event name

 

[Colif]

My PSU : Gigabyte G750H 80 Plus Gold 750W

it could be PSU. How old is it?

A BEX error is a “Buffer Overflow Exception”. This error is typically raised when Microsoft Windows detects that a program tries to put more data than possible in a region of memory. This is the computer equivalent of overfilling a glass with water until the water spills over

Pre Radar are memory leaks but in the games, not windows. Windows recognises the programs are trying to use more ram than they should be and closes them.

I believe that other people say they are signs of a bad PSU.

 

[Bless6d]

it could be PSU. How old is it? : 1 Year

 

[Colif]

might not be...
I only suggested it as last person with those errors ended up with a bad psu.
that was a few days ago... so it was fresh in my mind. I didn't want to waste time looking for software solutions when it might be hardware.

goes looking for other reasons

this is for pre radar:
Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

It doesn’t delete anything, it just stops non Microsoft programs running with start. Easy to reverse.

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.


BEX:
try running chkdsk on your c drive, it could be corrupted files.
i don't suppose they all steam games - https://windowsreport.com/steam-error-bex/

 

[Bless6d]

I suffered with this problem more than year ! I took this pc to the manufict he fixed it and when I asked him he told me it was a windows bug then I started playing games without any crashes and before 6 months I reseted windows then I got a lot of crashes as it was before !

 

[Colif]

i edited my last post... i do that, add to answers.

both of those are application errors. The BSOD are windows but programs just crashing isn't usual.

i don't think its ram but try running this overnight and see for sure
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.
Memtest is created as a bootable USB so that you don’t need windows to run it

 

[johnbl]

heap corruption in the windows 32 bit subsystem.
I would suggest updating bios and reinstalling or updating sound drivers.

my last look into a similar issue turned out to be a outdated sound software for directional audio. the software came from the motherboard vendor and there was no vendor update. I ended up finding a copy that worked from the microsoft catalog.

symptom was I would start a game and it would just exit after a few minutes. (no error recorded)

googling gameinputsvc.exe and heap corruption (from error code)
Microsoft GameInput Application Reconfiguration Crashes Win 11 PC - Microsoft Community

note: hard to figure out since you need a Full memory dump to see into the 32bit subsystem with the kernel debugger.
best to update bios, update any sound drivers. remove any old add on sound drivers that you really do not require.

i might be looking at these two files as a source of the issue:
C:\Windows\System32\xaudio2_9.dll F9FA6D67 (This is a reproducible build file hash, not a timestamp)
C:\Program Files\Epic Games\Fortnite\Engine\Binaries\ThirdParty\Windows\XAudio2_9\x64\xaudio2_9redist.dll Wed Jan 15 14:35:21 2020

(just a guess, one look like a replacement for the other)

you might also uninstall and reinstall the microsoft audio compression driver.
msacm32.drv
and msacm32.dll
C:\Windows\System32\MSAudDecMFT.dll Fri Nov 5 07:12:05 2032

Media Foundation Audio Decoders file reporting a bad date.

I don't look at the 32bit subsystem very often these just be normal quirks that seem abnormal to me.

maybe go into windows control panel, find turn windows features on or off find the media features, uninstall windows media player then reinstall it to refresh the install.

note: looks like there were bios updates for audio devices and for the intel storage subsystem (if you are using it)
no real details on what was changed. audio bios update was in january of last year.