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
---------

 

[Bless6d]

I will try it and I will answer you tomorrow ! Thank you

 

[Bless6d]

heap corruption in the windows 32 bit subsystem.

am on 64-bit operating system

 

[Colif]

what fixes heap corruption?

its a memory error,

csrss.exe is the 32 bit subsystem? i thought it was the user environment..

This loads the Windows 32-bit subsystem (CSRSS.EXE). CSRSS.EXE is the user-mode portion of the Win32 subsystem (with WIN32.SYS being the kernel-mode portion which is loaded as part of the Csrss initialization process). Csrss is an abbreviation for Client/Server Run-time Subsystem and is an essential subsystem that must be running at all times. CSRSS.EXE is responsible for console windows, creating and/or deleting threads and some parts of the 16-bit virtual MS-DOS environment.

Understanding Windows Boot Process | Know IT Like Pro

Introduction In this article, you will get to learn and understand the Windows Boot Process. It is well known

knowitlikepro.com

am on 64-bit operating system

64bit has the ability to run 32bit programs, they in the syswow folder. I can't find a lot on the 32 bit subsystem

So how do you fix it?
we ran sfc/dism

do you run chkdsk?

 

[Bless6d]

do you run chkdsk?

Yes i did

 

[Colif]

my question was more at @johnbl who said it and ran away

not sure how to fix it. trying to figure out what tool to use.

 

[johnbl]

my question was more at @johnbl who said it and ran away

not sure how to fix it. trying to figure out what tool to use.

my question was more at @johnbl who said it and ran away

not sure how to fix it. trying to figure out what tool to use.

added more info to my last post.
Microsoft GameInput Application Reconfiguration Crashes Win 11 PC - Microsoft Community
from link I posted here is a claim to fix;
For anyone that might still be having this issue, I managed to "fix" it by uninstalling GameInput (via Apps & Features in Settings) and then completely removing Windows Gaming Services via Powershell. The main downside to this solution is that you will be unable to use the Xbox App, so if you regularly use GamePass, this might not be a viable option for you.

To remove WGS, use this:

Launch Powershell as an administrator, copy and paste the following command (in bold):
get-appxpackage Microsoft.GamingServices | remove-AppxPackage -allusers


I would not underestimate bios update fixes.
(i could not read the bios version from the dump)

 

[Colif]

googling gameinputsvc.exe

that was crashing on peoples PC a few weeks ago, it might have been fixed by a windows update so try updating windows.

C:\Windows\System32\xaudio2_9.dll

that is part of directX, I looked at it before

XAudio2_9.dll, also known as a XAudio2 Game Audio API file, was created by Microsoft for the development of Microsoft® Windows® Operating

 

[johnbl]

what fixes heap corruption?

its a memory error,

csrss.exe is the 32 bit subsystem? i thought it was the user environment..

Understanding Windows Boot Process | Know IT Like Pro

Introduction In this article, you will get to learn and understand the Windows Boot Process. It is well known

knowitlikepro.com

64bit has the ability to run 32bit programs, they in the syswow folder. I can't find a lot on the 32 bit subsystem

So how do you fix it?
we ran sfc/dism

do you run chkdsk?

in this case I think the heap corruption was a cpu instruction pointer placed in the heap then being invalid. I would think this case the bios update will be the real fix.

 

[johnbl]

I think removing the package is a work around. microsoft would push out fixes to files if it could but it can not force people to update the BIOS. The changes in the bios reflect changes in the interface specifications for the electronics. These are put out long before they are implemented to give time to get the motherboard vendors to do the bios updates. People just have to pick them up.
(and they generally don't until there is a problem)

 

[Bless6d]

Hello ! am back after updating the BIOS and playing the game nothing special just lot of game crashes 🙁

 

[johnbl]

Hello ! am back after updating the BIOS and playing the game nothing special just lot of game crashes🙁

look to see if any of your games create a log file or game crash dump file.
ie search your system for *.dmp files and *.log files
you can do this by starting cmd.exe as a admin then run these commands

cd c:\
dir /s *.dmp >c:\outfile.txt
notepad.exe c:\outfile.txt

then look at the list of dump files.

you can do the same with *.log to look at the list of log files
note: command can take a minute to run, it searches your entire c: drive

 

[Bless6d]

Yes I found a game crash minidump files ! kernel32 and ntdll problems

 

[johnbl]

Yes I found a game crash minidump files ! kernel32 and ntdll problems

put some up on a cloud server and share them out for public access and I will take a quick look in a debugger to see if i see something helpful.

 

[Bless6d]

put some up on a cloud server and share them out for public access and I will take a quick look in a debugger to see if i see something helpful.

Check it please : https://drive.google.com/drive/folders/1bSmxOH1oAxhabGwJJhkLusI62vXCI3Dc?usp=sharing
Thank You

 

[johnbl]

Check it please : https://drive.google.com/drive/folders/1bSmxOH1oAxhabGwJJhkLusI62vXCI3Dc?usp=sharing
Thank You

Something wrong with the processor conversion of 32 bit call to 64 bit calls. all crashes have similar root cause not related to the running game.

google how to force a memory dump using the keyboard, make the registry changes and force a kernel memory dump on a running system. Provide the kernel dump and I will take a look.

otherwise, reset BIOS to defaults, updated chipset drivers.
Also, I assume 32 bit games have previously worked on the cpu?
(just to make sure it is not a defective cpu)


Intel® Core™ i9-9900K Processor
this contains the current drivers for the CPU
you should run the intel processor diagnostics to see if it complains (it is on the second page of the website list)




notes:
valorant
data running as code, illegal instruction called.
system up 3 minutes
-------------
valorant stack corrupted illegal instruction called
system up 39 seconds
------------
fortnite 1 dump, stack corrupted then attempt to run data as code. FortniteClient_Win64_Shipping


---------
fortnite 2 dump system up timer 14 mins
FortniteClient_Win64_Shipping
code running outside module.
code running in 32bit subsystem then thunked to 64 bit.
C:\Program Files\Epic Games\Fortnite\FortniteGame\Binaries\ThirdParty\Discord\Win64\discord-rpc.dll Thu Oct 15 13:30:44 2020 (5F88B174)

C:\Users\semla\AppData\Local\Discord\app-1.0.9007\modules\discord_hook-1\discord_hook\e7081b4d927\DiscordHook64.dll Fri Oct 21 12:04:11 2022 (6352ED2B)

 

[Bless6d]

I turned XMP OFF in BIOS going down from 3600Mhz to 2133Mhz ! I played more then 6h without any crash !

Update : Edited RAM speed from 2133Mhz to 3200Mhz ! works good also

RAM : G.Skill Kit 16GB (2 X 8GB) DDR4 3600MHz Ripjaws V Red CL19

 

[SomeGuyonTHW]

could be a missing dll? I remember having issues with missing dlls and stuff a lot when it comes to Riot Games games

 

[Bless6d]

could be a missing dll? I remember having issues with missing dlls and stuff a lot when it comes to Riot Games games

I checked everything on dll files all good ! the problem was :

I turned XMP OFF in BIOS going down from 3600Mhz to 2133Mhz ! I played more then 6h without any crash !

Update : Edited RAM speed from 2133Mhz to 3200Mhz ! works good also

RAM : G.Skill Kit 16GB (2 X 8GB) DDR4 3600MHz Ripjaws V Red CL19