search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.38k stars 1.07k forks source link

Bodycam (2406770) #7851

Open Polyfish0 opened 4 months ago

Polyfish0 commented 4 months ago

Compatibility Report

System Information

I confirm:

steam-2406770.log

Symptoms

The game runs first perfectly fine and after ~10 minutes it crashes.

Reproduction

Just play. I played the game on fullscreen with WQHD on a 4K monitor with FSR3 enabled

kisak-valve commented 4 months ago

Hello @Polyfish0, friendly note that the attached Proton log isn't for this game.

Polyfish0 commented 4 months ago

Oh sorry I thought it was the right one. I fix it now

Edit: I am playing since the notice and it did not crashed once. Just as an update. I deleted every proton log after the upload. That's the reason why I need a new log

Malixulo commented 4 months ago

Don't worry, I have a nice log for the same or a visibly similar issue.

Compatibility Report

Name of the game with compatibility issues: Bodycam Steam AppID of the game: 2406770

System Information

GPU: NVIDIA GeForce RTX 4070 Video driver version: NVIDIA 550.90.07 Kernel version: 6.6.34-1-lts Link to full system information report as Gist: Proton version: Experimental

I confirm:

steam-2406770.log

Symptoms

Appears to run great until; the game will suddenly and consistently crash within about ten minutes of gameplay

Reproduction

Simply play for a short period

kisak-valve commented 4 months ago

Hello @Malixulo, wine: Call from 00006FFFFFC1CE87 to unimplemented function api-ms-win-appmodel-unlock-l1-1-0.dll.IsDeveloperModeEnabled, aborting looks like a line of interest in your log, but the log makes it seem like that's not fatal. There's also hints of libav and nvapi64 having a hard time.

Polyfish0 commented 4 months ago

Hello @kisak-valve. I got now the right log. I updated the link in my original post and here is it again steam-2406770.log

Baduk07 commented 4 months ago

### Game crash randomly :

[Uploading steam-2406770.log…]()

1666.215:0130:0218:warn:seh:dispatch_exception backtrace: --- Exception 0xc0000005. 1666.215:0130:0218:trace:seh:dispatch_exception code=c0000005 flags=0 addr=00006FFFFC7E32C4 ip=6ffffc7e32c4 1666.215:0130:0218:trace:seh:dispatch_exception info[0]=0000000000000000 1666.215:0130:0218:trace:seh:dispatch_exception info[1]=00006ffffc93f750 1666.215:0130:0218:warn:seh:dispatch_exception EXCEPTION_ACCESS_VIOLATION exception (code=c0000005) raised 1666.215:0130:0218:trace:seh:dispatch_exception rax=00006ffffffa4260 rbx=0000000019430ab0 rcx=000000002bbbfe50 rdx=00006ffffc93f750 1666.215:0130:0218:trace:seh:dispatch_exception rsi=0000000000000000 rdi=00006ffffc93f758 rbp=000000002bbbfea0 rsp=000000002bbbfdd8 1666.215:0130:0218:trace:seh:dispatch_exception r8=0000000019430ab0 r9=0000000000000000 r10=0000000103b9e5f0 r11=0000000000000202 1666.215:0130:0218:trace:seh:dispatch_exception r12=0000000000dc89d0 r13=000000002bbbfe50 r14=000000002bbbff28 r15=0000000000dc89c0 1666.215:0130:0218:trace:seh:call_vectored_handlers calling handler at 00006FFFFD31B3E0 code=c0000005 flags=0 1666.215:0130:0218:trace:seh:call_vectored_handlers handler at 00006FFFFD31B3E0 returned 0 1666.215:0130:0218:trace:seh:call_vectored_handlers calling handler at 00006FFFFD6AC050 code=c0000005 flags=0 1666.215:0130:0218:trace:seh:call_vectored_handlers handler at 00006FFFFD6AC050 returned 0 1666.215:0130:0218:trace:seh:call_vectored_handlers calling handler at 00006FFFFD92C770 code=c0000005 flags=0 1666.215:0130:0218:trace:seh:call_vectored_handlers handler at 00006FFFFD92C770 returned 0 1666.215:0130:0218:warn:seh:virtual_unwind backtrace: 00006FFFFC7E32C4: L"chrome_elf.dll" + 00000000000832C4. 1666.215:0130:0218:trace:unwind:RtlVirtualUnwind type 1 rip 6ffffc7e32c4 rsp 2bbbfdd8 1666.215:0130:0218:trace:unwind:dump_unwind_info func 8320d-83787 1666.215:0130:0218:trace:unwind:dump_unwind_info unwind info at 00006FFFFC84B5D8 flags 1 prolog 0x0 bytes function 00006FFFFC7E320D-00006FFFFC7E3787 1666.215:0130:0218:trace:unwind:dump_unwind_info handler 00006FFFFC7E3830 data at 00006FFFFC84B5E0 1666.215:0130:0218:trace:seh:call_handler calling handler 00006FFFFC7E3830 (rec=000000002BBBFBB0, frame=000000002BBBFDD8 context=000000002BBBF110, dispatch=000000002BBBEFE0) 1666.215:0130:0218:trace:unwind:RtlVirtualUnwind type 0 rip 6ffffc7e32c4 rsp 6ffffffa4260 1666.215:0130:0218:trace:unwind:dump_unwind_info func 8320d-83787 1666.215:0130:0218:trace:unwind:dump_unwind_info unwind info at 00006FFFFC84B5D8 flags 1 prolog 0x0 bytes function 00006FFFFC7E320D-00006FFFFC7E3787 1666.215:0130:0218:trace:unwind:dump_unwind_info handler 00006FFFFC7E3830 data at 00006FFFFC84B5E0 1666.215:0130:0218:trace:seh:call_handler handler at 00006FFFFC7E3830 returned 1

_1666.215:0130:0218:err:seh:call_stackhandlers invalid frame 00006FFFFFFA4268 (000000002B042000-000000002BBC0000) 1666.215:0130:0218:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception.****

1666.409:0124:0128:fixme:kernelbase:AppPolicyGetProcessTerminationMethod FFFFFFFFFFFFFFFA, 0000000000B9FEB0 1666.412:0440:0938:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker" 1666.413:0440:0934:warn:threadname:NtSetInformationThread Thread renamed to L"ThreadPoolForegroundWorker"