Game: Arc 130V crashes after extreme slowdown during cutscene #938

Open
opened 2026-11-15 21:57:22 +00:00 by BeanIssues · 2 comments
Collaborator

Reported by Marco Loves 360 on Discord

Longshot version

nightly-189-aa95d35f (source 719431ac)

Channel

Nightly

What happened

Longshot slowed to a crawl during a cutscene, continued moving very slowly for a while, then crashed. The crash report says: “The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game.” The crash record reason is device lost.

Where in the game

During a cutscene; exact scene not provided.

How often

The player reports being stuck on the cutscene a few times before it eventually crashed. Exact frequency not provided.

Graphics card and driver version

Intel(R) Arc(TM) 130V GPU (8GB), Intel Corporation 101.9175

CPU, RAM and operating system

Intel(R) Core(TM) Ultra 5 226V (8 threads), 16 GB, Windows 11 (build 26200)

Settings

Player reports using 6 GB dedicated VRAM, leaving 10 GB RAM, and 50% resolution scaling. The generated crash report also lists output_res=1920x1200, resolution=4, upscaling=0, threaded_rendering=0, and memory_budget=1.

longshot_log.txt

The game log records that the GPU finished nothing for 30 seconds, followed by GPU hang and device lost. The crash report shows uptime of 1416 seconds. See attached game log.

Longshot #878 reports a device-lost crash on an Intel Arc 140V with the same driver version, but on a different model and at a different point in gameplay.

Reported by [Marco Loves 360 on Discord](https://discord.com/channels/1569849200047427645/1569849200617726065/1571644328365789328) ### Longshot version nightly-189-aa95d35f (source 719431ac) ### Channel Nightly ### What happened Longshot slowed to a crawl during a cutscene, continued moving very slowly for a while, then crashed. The crash report says: “The graphics driver failed. Update your graphics driver, and turn off overlays and tools hooked into the game.” The crash record reason is `device lost`. ### Where in the game During a cutscene; exact scene not provided. ### How often The player reports being stuck on the cutscene a few times before it eventually crashed. Exact frequency not provided. ### Graphics card and driver version Intel(R) Arc(TM) 130V GPU (8GB), Intel Corporation 101.9175 ### CPU, RAM and operating system Intel(R) Core(TM) Ultra 5 226V (8 threads), 16 GB, Windows 11 (build 26200) ### Settings Player reports using 6 GB dedicated VRAM, leaving 10 GB RAM, and 50% resolution scaling. The generated crash report also lists `output_res=1920x1200`, `resolution=4`, `upscaling=0`, `threaded_rendering=0`, and `memory_budget=1`. ### longshot_log.txt The game log records that the GPU finished nothing for 30 seconds, followed by `GPU hang` and `device lost`. The crash report shows uptime of 1416 seconds. See attached game log. ### Related issue [Longshot #878](https://git.magicbean.dev/MagicBeanDev/Longshot/issues/878) reports a device-lost crash on an Intel Arc 140V with the same driver version, but on a different model and at a different point in gameplay.
Author
Collaborator

Files from the Discord report:

Files from the Discord report: - [longshot_log.txt](https://git.magicbean.dev/attachments/bb332731-ffe6-48ec-8c02-244ebbc77587) - [report-20261115T214255Z.txt](https://git.magicbean.dev/attachments/3f336083-44db-469a-92a2-a66d525f36b1)

i tried again and crashed earlier, might be running out of ram?

i tried again and crashed earlier, might be running out of ram?
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot#938
No description provided.