EXCEPTION_ACCESS_VIOLATION reading address 0xffffffff - UNREAL CRASH

[CapNcrush]

Hi,

Just purchased HLL today. The game always crashes around 10 minutes of game-play, with the UNREAL error prompt below showing on my screen:

LoginId:2d30489a4bc75c471d637093875288af
EpicAccountId:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffff

HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
kernel32
ntdll

- Already tried the following steps:

- Added antivirus exceptions to the game folder
- done SFCscans to drive folder
- disabled full-screen optimization
- manually reinstalled EasyAntiCheat

Whats the fix for this? Hope someone can help. Last thing I'd want is to refund a good game cause of a bug/glitch/comp issue.

[maldubious]

Team17_Assist の投稿を引用：

Hey, maldubious,

Thank you for trying those steps!
We're glad to hear that you were able to play for a little while without crashing!

Could you please share a dxdiag with us after the crash happens again and we can see if there is any error in your dxdiag that may help us pinpoint this?

Let's try running the game as an administrator:

1. Right-click the game in your Steam Library.
   
2. Go to Properties then the Local Files tab.
   
3. Click Browse Local Files.
   
4. Locate the game executable (the application).
   
5. Right-click it and go to Properties.
   
6. Click the Compatibility tab.
   
7. Check the Run this program as an administrator box.

And try running Steam as an administrator:

1. Navigate to your Steam install folder (Default: C:\Program Files (x86)\Steam).
   
2. Right-click the Steam executable.
   
3. Follow the above steps to set it to Run as Administrator
   
4. Restart Steam.

Get back to us when you can!

Regards,
Team17 Support

on the off chance that it helps, I pulled the dxdiag, but it wasn't until the following morning. i'll do that again next time it happens right afterwards. i'll try running as administrator for both steam and the game next time. thanks for your help as we go!
https://justpaste.it/aijhu

[maldubious]

maldubious の投稿を引用：

Team17_Assist の投稿を引用：

Hey, maldubious,

Thank you for trying those steps!
We're glad to hear that you were able to play for a little while without crashing!

Could you please share a dxdiag with us after the crash happens again and we can see if there is any error in your dxdiag that may help us pinpoint this?

Let's try running the game as an administrator:

1. Right-click the game in your Steam Library.
   
2. Go to Properties then the Local Files tab.
   
3. Click Browse Local Files.
   
4. Locate the game executable (the application).
   
5. Right-click it and go to Properties.
   
6. Click the Compatibility tab.
   
7. Check the Run this program as an administrator box.

And try running Steam as an administrator:

1. Navigate to your Steam install folder (Default: C:\Program Files (x86)\Steam).
   
2. Right-click the Steam executable.
   
3. Follow the above steps to set it to Run as Administrator
   
4. Restart Steam.

Get back to us when you can!

Regards,
Team17 Support

on the off chance that it helps, I pulled the dxdiag, but it wasn't until the following morning. i'll do that again next time it happens right afterwards. i'll try running as administrator for both steam and the game next time. thanks for your help as we go!
https://justpaste.it/aijhu

just tried to play as administrator both for steam and the game. was able to get into the game, change my graphics settings down from epic to high. got into a server. spawned, moved my vision and then the game crashed without any log popup. this seems to be the case now with the launch settings -dx12, i get no error log reports from the unreal engine anymore, it just crashes to desktop. here's the dxdiag
https://justpaste.it/aekxc

[maldubious]

maldubious の投稿を引用：

maldubious の投稿を引用：

on the off chance that it helps, I pulled the dxdiag, but it wasn't until the following morning. i'll do that again next time it happens right afterwards. i'll try running as administrator for both steam and the game next time. thanks for your help as we go!
https://justpaste.it/aijhu

just tried to play as administrator both for steam and the game. was able to get into the game, change my graphics settings down from epic to high. got into a server. spawned, moved my vision and then the game crashed without any log popup. this seems to be the case now with the launch settings -dx12, i get no error log reports from the unreal engine anymore, it just crashes to desktop. here's the dxdiag
https://justpaste.it/aekxc

just tried the following: uninstalled geforce experience. quit any other extra programs running, disconnected peripherals that aren't necessary (stream deck), took off the launch option "-dx12" from the steam side, made it 17 minutes into a game before the crash happened. this time the screen is frozen, for a minute and a half, before returning to desktop (no sound during that freeze either). here's the latest dxdiag report with this most latest crash event
https://justpaste.it/bqw50

[maldubious]

maldubious の投稿を引用：

maldubious の投稿を引用：

just tried to play as administrator both for steam and the game. was able to get into the game, change my graphics settings down from epic to high. got into a server. spawned, moved my vision and then the game crashed without any log popup. this seems to be the case now with the launch settings -dx12, i get no error log reports from the unreal engine anymore, it just crashes to desktop. here's the dxdiag
https://justpaste.it/aekxc

just tried the following: uninstalled geforce experience. quit any other extra programs running, disconnected peripherals that aren't necessary (stream deck), took off the launch option "-dx12" from the steam side, made it 17 minutes into a game before the crash happened. this time the screen is frozen, for a minute and a half, before returning to desktop (no sound during that freeze either). here's the latest dxdiag report with this most latest crash event
https://justpaste.it/bqw50

opting to try reinstalling windows and one by one reinstall steam and the game to see if it works on a completely clean install

[maldubious]

maldubious の投稿を引用：

maldubious の投稿を引用：

just tried the following: uninstalled geforce experience. quit any other extra programs running, disconnected peripherals that aren't necessary (stream deck), took off the launch option "-dx12" from the steam side, made it 17 minutes into a game before the crash happened. this time the screen is frozen, for a minute and a half, before returning to desktop (no sound during that freeze either). here's the latest dxdiag report with this most latest crash event
https://justpaste.it/bqw50

opting to try reinstalling windows and one by one reinstall steam and the game to see if it works on a completely clean install

Alright.. clean windows install. Only downloaded steam and HLL. Played one whole game! No issues. Maybe at one point there was a slight stutter but that was it. Then I plugged my microphone in, and went into options in game to set the microphone and thats when the first crash happened. So i unplugged the mic from the front USB and plugged it into the back, tried again. This time I got in game, was able to communicate with players, and play for maybe 5 minutes? before the game crashed again. Same crashes as before. Do you want my dxdiag again? I can copy and paste the error here to start:

Diagnostics
---------------

Windows Error Reporting:
+++ WER0 +++:
Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 1fe09603-e016-483f-a8b1-b46189569910

Problem signature:
P1: 141
P2: ffffcf0fea8d9460
P3: fffff8048ec4df70
P4: 0
P5: 2d08
P6: 10_0_22621
P7: 0_0
P8: 768_1
P9:
P10:


+++ WER1 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffcf0fea8d9460
P3: fffff8048ec4df70
P4: 0
P5: 2d08
P6: 10_0_22621
P7: 0_0
P8: 768_1
P9:
P10:


+++ WER2 +++:
Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0959b4af-4798-4652-8cf3-56fd169621fc

Problem signature:
P1: 141
P2: ffffcf0fead6b460
P3: fffff8048ec4df70
P4: 0
P5: b00
P6: 10_0_22621
P7: 0_0
P8: 768_1
P9:
P10:


+++ WER3 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffcf0fead6b460
P3: fffff8048ec4df70
P4: 0
P5: b00
P6: 10_0_22621
P7: 0_0
P8: 768_1
P9:
P10:


+++ WER4 +++:
Fault bucket 1358777808104071327, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: HLL-Win64-Shipping.exe
P2: 4.25.0.0
P3: 10.0.22621.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER5 +++:
Fault bucket 1302110189481585583, type 5
Event Name: crashpad_log
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.155.85
P3: InstallError
P4: 0x80040815
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER6 +++:
Fault bucket 1302110189481585583, type 5
Event Name: crashpad_log
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.155.85
P3: InstallError
P4: 0x80040815
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER7 +++:
Fault bucket , type 0
Event Name: crashpad_log
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.155.85
P3: InstallError
P4: 0x80040815
P5:
P6:
P7:
P8:
P9:
P10:


+++ WER8 +++:
Fault bucket 1590020078865273323, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: svchost.exe_StateRepository
P2: 10.0.22621.1
P3: 6dc5c2a5
P4: ntdll.dll
P5: 10.0.22621.900
P6: a97a9ed6
P7: 00000000000a7788
P8: c0000409
P9: 0000000000000023
P10:


+++ WER9 +++:
Fault bucket 1254400919335998288, type 5
Event Name: crashpad_log
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftEdgeUpdate.exe
P2: 1.3.155.85
P3: CriticalRequestError
P4: 0xa043081c
P5:
P6:
P7:
P8:
P9:
P10:

[Moe]

Same problem here. Just made the clean install of Windows 11.

https://justpaste.it/9zvmg

[maldubious]

I bought a replacement to the RAM, went from 3200mhz to 3600mhz of 32gb ddr4. so far so good, will update again later after further testing

[StaySharp04]

Crash too , help me plz

LoginId:811944cf487f4fd19a077991765ba6c7
EpicAccountId:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0xffffffff

HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
kernel32
ntdll

https://justpaste.it/9snxh

['Bacardi]

Delete Paks folders and verify integrity game files

[Team17_Service]

Hey @Moe and StaySharp04,

Thanks for getting in touch with us - sorry to hear you're having issues with crashes also.

Can you please confirm you have tried all steps provided previously in this thread please including what @'Bacardi has suggested?

To do this, please navigate to the following directory: Steam\steamapps\common\Hell Let Loose\HLL\Content and delete the Paks folder. 

Then please attempt to verify your files.

To do this:

1. Right-click on the game in your Steam Library
   
2. Choose Properties
   
3. Switch to the Local Files tab and press Verify integrity of game files...

If that doesn't work as well, then we would recommend running a memory test check. You can find a few options in this guide[www.howtogeek.com], thought it would be best if you could use MemTest86.

Please do get back to us and let us know how you get on!

@maldubious - we're really glad to see that your new RAM is seemingly working well with the game, we really appreciate you letting us know! We look forward to hearing back after you've been able to play some more!

Regards,
Team17 Support

[StaySharp04]

Team17_Service の投稿を引用：

Hey @Moe and StaySharp04,

Thanks for getting in touch with us - sorry to hear you're having issues with crashes also.

Can you please confirm you have tried all steps provided previously in this thread please including what @'Bacardi has suggested?

To do this, please navigate to the following directory: Steam\steamapps\common\Hell Let Loose\HLL\Content and delete the Paks folder. 

Then please attempt to verify your files.

To do this:

1. Right-click on the game in your Steam Library
   
2. Choose Properties
   
3. Switch to the Local Files tab and press Verify integrity of game files...

If that doesn't work as well, then we would recommend running a memory test check. You can find a few options in this guide[www.howtogeek.com], thought it would be best if you could use MemTest86.

Please do get back to us and let us know how you get on!

@maldubious - we're really glad to see that your new RAM is seemingly working well with the game, we really appreciate you letting us know! We look forward to hearing back after you've been able to play some more!

Regards,
Team17 Support

yeah, i do what you say.
but still not cool.
UE4 crash abot 20mins.
there is new crash report

LoginId:811944cf487f4fd19a077991765ba6c7
EpicAccountId:

LowLevelFatalError [File:Unknown] [Line: 26] Pak chunk signature check failed!

HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
kernel32
ntdll

I test for twice. once go BSOD once go UE4crash.
any other soluton?

[Team17_Assist]

Hey StaySharp04,

Thanks for your reply.

Did you remove the paks folder?
And what did the ram test show, please?

We can see that you also have two graphics cards, are you using SLI?
If so can you please disable this?

Please can you also make sure that the game is set to use one graphics card specifically?

For AMD:

Right-click your desktop, and select Catalyst Control Center.
1. From the Power drop-down menu, select Switchable Graphics.
   
2. Click Browse and navigate to select the program.
   
3. Click Power Saving or High Performance to select the graphics card to use for that specific application.

For Nvidia:

1. Right-click your desktop, and select NVIDIA Control Panel.
   
2. From the left, select Manage 3D Settings.
   
3. Select Program Settings and navigate to select the program. (If the program is not in the list, select Add > navigate to the folder ‘…\Steam\steamapps\common’, select the game name folder and then select the .exe.
   
4. Click High Performance to select the higher power graphics card to use for that specific application.
   Select Apply.

After the steps please retest the game to see if the problem still continues.

Regards,
Team17 Support

[StaySharp04]

ram test show all good no error.
Two gpu one is 7900x3d’s core gpu.
Another is nvidia 3080.
I will try fully reinstall game and disable amd gpu.
Thx for your attention

[StaySharp04]

Team17_Service の投稿を引用：

Hey @Moe and StaySharp04,

Thanks for getting in touch with us - sorry to hear you're having issues with crashes also.

Can you please confirm you have tried all steps provided previously in this thread please including what @'Bacardi has suggested?

To do this, please navigate to the following directory: Steam\steamapps\common\Hell Let Loose\HLL\Content and delete the Paks folder. 

Then please attempt to verify your files.

To do this:

1. Right-click on the game in your Steam Library
   
2. Choose Properties
   
3. Switch to the Local Files tab and press Verify integrity of game files...

If that doesn't work as well, then we would recommend running a memory test check. You can find a few options in this guide[www.howtogeek.com], thought it would be best if you could use MemTest86.

Please do get back to us and let us know how you get on!

@maldubious - we're really glad to see that your new RAM is seemingly working well with the game, we really appreciate you letting us know! We look forward to hearing back after you've been able to play some more!

Regards,
Team17 Support

Hello devs ，I fixed this issue.
is the Ram, increase Dram Timing make game stable.
maybe ram overheat or some other reason.
thanks for help~

[(604) GRIZZLY]

<?xml version="1.0" encoding="UTF-8"?>
<FGenericCrashContext>
<RuntimeProperties>
<CrashVersion>3</CrashVersion>
<ExecutionGuid>022BE2E045345C8024D8C680F52FEE53</ExecutionGuid>
<CrashGUID>UE4CC-Windows-D2364EE242E419808E8ACE8BE80A3CC6_0000</CrashGUID>
<IsEnsure>false</IsEnsure>
<IsAssert>false</IsAssert>
<CrashType>Crash</CrashType>
<ErrorMessage>Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x00000188</ErrorMessage>
<CrashReporterMessage />
<ProcessId>9148</ProcessId>
<SecondsSinceStart>83</SecondsSinceStart>
<IsInternalBuild>false</IsInternalBuild>
<IsPerforceBuild>false</IsPerforceBuild>
<IsSourceDistribution>false</IsSourceDistribution>
<GameName>UE4-HLL</GameName>
<ExecutableName>HLL-Win64-Shipping</ExecutableName>
<BuildConfiguration>Shipping</BuildConfiguration>
<GameSessionID />
<Symbols>**UE4*Release-4.25Plus-CL-0-Win64-Shipping</Symbols>
<PlatformName>Windows</PlatformName>
<PlatformNameIni>Windows</PlatformNameIni>
<EngineMode>Game</EngineMode>
<EngineModeEx>Unset</EngineModeEx>
<DeploymentName />
<EngineVersion>4.25.0-0+++UE4+Release-4.25Plus</EngineVersion>
<CommandLine>CommandLineRemoved</CommandLine>
<LanguageLCID>0</LanguageLCID>
<AppDefaultLocale>en-US</AppDefaultLocale>
<BuildVersion>++UE4+Release-4.25Plus-CL-0</BuildVersion>
<IsUE4Release>true</IsUE4Release>
<IsRequestingExit>false</IsRequestingExit>
<UserName />
<BaseDir>D:/steam/steamapps/common/Hell Let Loose/HLL/Binaries/Win64/</BaseDir>
<RootDir>D:/steam/steamapps/common/Hell Let Loose/</RootDir>
<MachineId>5725E46740A438478C9980A0A21552FB</MachineId>
<LoginId>5725e46740a438478c9980a0a21552fb</LoginId>
<EpicAccountId />
<SourceContext />
<UserDescription />
<UserActivityHint />
<CrashDumpMode>0</CrashDumpMode>
<GameStateName />
<Misc.NumberOfCores>6</Misc.NumberOfCores>
<Misc.NumberOfCoresIncludingHyperthreads>12</Misc.NumberOfCoresIncludingHyperthreads>
<Misc.Is64bitOperatingSystem>1</Misc.Is64bitOperatingSystem>
<Misc.CPUVendor>AuthenticAMD</Misc.CPUVendor>
<Misc.CPUBrand>AMD Ryzen 5 2600 Six-Core Processor</Misc.CPUBrand>
<Misc.PrimaryGPUBrand>Radeon RX 5500 XT</Misc.PrimaryGPUBrand>
<Misc.OSVersionMajor>Windows 10 (Release 2009)</Misc.OSVersionMajor>
<Misc.OSVersionMinor />
<MemoryStats.TotalPhysical>34286481408</MemoryStats.TotalPhysical>
<MemoryStats.TotalVirtual>140737488224256</MemoryStats.TotalVirtual>
<MemoryStats.PageSize>4096</MemoryStats.PageSize>
<MemoryStats.TotalPhysicalGB>32</MemoryStats.TotalPhysicalGB>
<MemoryStats.AvailablePhysical>0</MemoryStats.AvailablePhysical>
<MemoryStats.AvailableVirtual>0</MemoryStats.AvailableVirtual>
<MemoryStats.UsedPhysical>0</MemoryStats.UsedPhysical>
<MemoryStats.PeakUsedPhysical>0</MemoryStats.PeakUsedPhysical>
<MemoryStats.UsedVirtual>0</MemoryStats.UsedVirtual>
<MemoryStats.PeakUsedVirtual>0</MemoryStats.PeakUsedVirtual>
<MemoryStats.bIsOOM>0</MemoryStats.bIsOOM>
<MemoryStats.OOMAllocationSize>0</MemoryStats.OOMAllocationSize>
<MemoryStats.OOMAllocationAlignment>0</MemoryStats.OOMAllocationAlignment>
<NumMinidumpFramesToIgnore>0</NumMinidumpFramesToIgnore>
<CallStack>HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
HLL_Win64_Shipping
kernel32
ntdll</CallStack>
<PCallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e HLL-Win64-Shipping 0x0000000027ec0000 + d1d79a HLL-Win64-Shipping 0x0000000027ec0000 + 2d5dcde VCRUNTIME140 0x00000000c0d50000 + f0f0 ntdll 0x00000000d6830000 + a241f ntdll 0x00000000d6830000 + 514a4 ntdll 0x00000000d6830000 + a0f4e HLL-Win64-Shipping 0x0000000027ec0000 + 7510e9 HLL-Win64-Shipping 0x0000000027ec0000 + 86d4e9 HLL-Win64-Shipping 0x0000000027ec0000 + 2533321 HLL-Win64-Shipping 0x0000000027ec0000 + 21afdf9 HLL-Win64-Shipping 0x0000000027ec0000 + 2195a0c HLL-Win64-Shipping 0x0000000027ec0000 + 255bdcb HLL-Win64-Shipping 0x0000000027ec0000 + 2185f49 HLL-Win64-Shipping 0x0000000027ec0000 + 539b65 HLL-Win64-Shipping 0x0000000027ec0000 + 54058c HLL-Win64-Shipping 0x0000000027ec0000 + 5405fa HLL-Win64-Shipping 0x0000000027ec0000 + 54a42f HLL-Win64-Shipping 0x0000000027ec0000 + 2d55c02 KERNEL32 0x00000000d57d0000 + 17614 ntdll 0x00000000d6830000 + 526a1</PCallStack>
<PCallStackHash>DA39A3EE5E6B4B0D3255BFEF95601890AFD80709</PCallStackHash>
<Threads>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e HLL-Win64-Shipping 0x0000000027ec0000 + d1d79a HLL-Win64-Shipping 0x0000000027ec0000 + 2d5dcde VCRUNTIME140 0x00000000c0d50000 + f0f0 ntdll 0x00000000d6830000 + a241f ntdll 0x00000000d6830000 + 514a4 ntdll 0x00000000d6830000 + a0f4e HLL-Win64-Shipping 0x0000000027ec0000 + 7510e9 HLL-Win64-Shipping 0x0000000027ec0000 + 86d4e9 HLL-Win64-Shipping 0x0000000027ec0000 + 2533321 HLL-Win64-Shipping 0x0000000027ec0000 + 21afdf9 HLL-Win64-Shipping 0x0000000027ec0000 + 2195a0c HLL-Win64-Shipping 0x0000000027ec0000 + 255bdcb HLL-Win64-Shipping 0x0000000027ec0000 + 2185f49 HLL-Win64-Shipping 0x0000000027ec0000 + 539b65 HLL-Win64-Shipping 0x0000000027ec0000 + 54058c HLL-Win64-Shipping 0x0000000027ec0000 + 5405fa HLL-Win64-Shipping 0x0000000027ec0000 + 54a42f HLL-Win64-Shipping 0x0000000027ec0000 + 2d55c02 KERNEL32 0x00000000d57d0000 + 17614 ntdll 0x00000000d6830000 + 526a1</CallStack>
<IsCrashed>true</IsCrashed>
<Registers />
<ThreadID>9152</ThreadID>
<ThreadName>GameThread</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 X3DAudio1_7 0x00000000672a0000 + 98d5ffff</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>8852</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>X3DAudio1_7 0x00000000672a0000 + 7a7ef8c0 ntdll 0x00000000d6830000 + 297d003e ntdll 0x00000000d6830000 + 4750e0e0 ntdll 0x00000000d6830000 + 558ee71d Unknown 0x0000000000000000 + 1 ntdll 0x00000000d6830000 + 10ee888b X3DAudio1_7 0x00000000672a0000 + 37edf920 X3DAudio1_7 0x00000000672a0000 + 37edf928 ntdll 0x00000000d6830000 + 702146dd ntdll 0x00000000d6830000 + 2060d3e ntdll 0x00000000d6830000 + fb0ad ntdll 0x00000000d6830000 + c07cae6a</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>1940</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 Unknown 0x0000000000000000 + 464f XINPUT1_3 0x0000000000400000 + 589680</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>1068</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 Unknown 0x0000000000000000 + 4e1f XINPUT1_3 0x0000000000400000 + 589680</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>680</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 Unknown 0x0000000000000000 + 37490 XINPUT1_3 0x0000000000400000 + 589680</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>1372</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 Unknown 0x0000000000000000 + 270f XINPUT1_3 0x0000000000400000 + 589680</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>15252</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 Unknown 0x0000000000000000 + c7 XINPUT1_3 0x0000000000400000 + 589680</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>11424</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a89d9d8 X3DAudio1_7 0x00000000672a0000 + 7b5d0e20</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>13696</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e X3DAudio1_7 0x00000000672a0000 + 7a82b593 Unknown 0x0000000000000000 + 1d49b XINPUT1_3 0x0000000000400000 + 589680</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>14512</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d7e4 KERNELBASE 0x00000000d43b0000 + 77071 HLL-Win64-Shipping 0x0000000027ec0000 + d1d5b8 HLL-Win64-Shipping 0x0000000027ec0000 + d1dc73 HLL-Win64-Shipping 0x0000000027ec0000 + d17d5e HLL-Win64-Shipping 0x0000000027ec0000 + d1f6fe KERNEL32 0x00000000d57d0000 + 17614 ntdll 0x00000000d6830000 + 526a1</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>13000</ThreadID>
<ThreadName>Unknown</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e HLL-Win64-Shipping 0x0000000027ec0000 + d2141e HLL-Win64-Shipping 0x0000000027ec0000 + 1e8f795 HLL-Win64-Shipping 0x0000000027ec0000 + d1f767 HLL-Win64-Shipping 0x0000000027ec0000 + d17b81 KERNEL32 0x00000000d57d0000 + 17614 ntdll 0x00000000d6830000 + 526a1</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>1916</ThreadID>
<ThreadName>FChunkCacheWorker</ThreadName>
</Thread>
<Thread>
<CallStack>ntdll 0x00000000d6830000 + 9d144 KERNELBASE 0x00000000d43b0000 + 2306e HLL-Win64-Shipping 0x0000000027ec0000 + d2141e HLL-Win64-Shipping 0x0000000027ec0000 + bd1e8c HLL-Win64-Shipping 0x0000000027ec0000 + bd497c HLL-Win64-Shipping 0x0000000027ec0000 + d1f767 HLL-Win64-Shipping 0x0000000027ec0000 + d17b81 KERNEL32 0x00000000d57d0000 + 17614 ntdll 0x00000000d6830000 + 526a1</CallStack>
<IsCrashed>false</IsCrashed>
<Registers />
<ThreadID>1748</ThreadID>
<ThreadName>TaskGraphThreadNP 0</ThreadName>
</Thread>
<Thread>