Frequent crashes - report inside

[DrLove-2239]

As title says, constant crashes.

All bug reports contain these lines:

I 2023.03.18 22:47:15.507557 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:15.507781 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:15.951688 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:15.951921 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:16.856347 [Game] Prevented Error conversation line VO (CONVERSATION_SNO:HRO_BarbM_CantPickup) because a conversation is currently playing
I 2023.03.18 22:47:44.333975 [Game] Prevented Error conversation line VO (CONVERSATION_SNO:HRO_BarbM_NotEnoughCharges) because a conversation is currently playing
I 2023.03.18 22:47:53.522550 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:53.522785 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:58.640575 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:47:58.640804 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:48:04.474101 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:48:04.474322 [Game] Cannot create cloth on non-cloth sub-object 0x36c3b0f0 (Ractor name = #[0xcaea14b4]).
I 2023.03.18 22:48:08.950312 [Crash] Thread ‘JobWorker0’ handling fatal error
I 2023.03.18 22:48:08.953062 [Crash] UnhandledExceptionFilter
I 2023.03.18 22:48:08.953314 [Crash] Crashed thread: ‘JobWorker0’ (0x86c)
I 2023.03.18 22:48:08.953456 [Sigma] — OS memory stats -----
I 2023.03.18 22:48:08.953572 [Sigma] Virtual Mem Total: 69325.14 Mb
I 2023.03.18 22:48:08.953680 [Sigma] Virtual Mem Used: 38204.32 Mb
I 2023.03.18 22:48:08.953782 [Sigma] Virtual Mem Used by Process: 26342.29 Mb
I 2023.03.18 22:48:08.953882 [Sigma] Phys Mem Total: 65229.14 Mb
I 2023.03.18 22:48:08.953981 [Sigma] Phys Mem Used: 26880.30 Mb
I 2023.03.18 22:48:08.954081 [Sigma] Phys Mem Used by Process: 16851.38 Mb
I 2023.03.18 22:48:08.954177 [Sigma] — OS memory stats end-----
I 2023.03.18 22:48:08.954321 [Sigma] Opening dump file
I 2023.03.18 22:48:08.962441 [Sigma] Dump file opened
I 2023.03.18 22:48:08.962629 [Sigma] Starting dump
I 2023.03.18 22:48:09.495681 [Sigma] Saved dump file to ‘G:\Diablo IV - Beta\Fenris-0.dmp’

UNHANDLED EXCEPTION: ACCESS_VIOLATION (c0000005) at:
DBG-OPTIONS
DBG-ADDR<00007FF6E509E386>(“Diablo IV.exe”)
DBG-OPTIONS<>

[SiSo-2252]

@DrLove-2239

ACCESS_VIOLATION (c0000005) at:

I’ve got the same thing. Mostly in dungeons and instances. When I lower the graphics to Low get better but in High settings, I’m getting crash almost in every dungeon and sometimes in quest instances. For example, the last instance before Rathma cinematic I could not finish it on High setting.

[Irishwitch-1439]

This is beta right now the game is a memory hog for a lot of players with older computers myself included. Copy your crash reports and send them in. This is what beta access is for so they can find the problems and fix them. They WANT us to break the game so they can find solutions for the weak points.