Client suddenly freezes on specific game (D3D Frame query timed out)

I’ve recently started playing Arsenal and I’ve really enjoyed it but strangely, it keeps on freezing mid-game with a (Not Responding) in the tab. I thought it had to do with Arsenal being a high-performance game so I tried out other high-performing games such as Those Who Remain and The Wild West but then it does not freeze as Arsenal does.

I’ve also tried messing with the graphics settings since my graphics card is an Intel and my RAM is only 8GB but even at a 1, the same problem occurs. With a 5, Those Who Remain and The Wild West do not crash at all.

Specs:

  • Operator: Windows 10 Pro
  • Processor: Intel(R) Core™ i5-3320M CPU @ 2.60GHz 2.60GHz
  • RAM: 8GB (7.70GB Usable)
  • Graphics Card: Intel(R) HD Graphics 4000
  • Approx Total Memory: 1792MB

Log before freeze:

1597471305.63362,3590,6 WARNING: D3D Frame query timed out, has device hung?
1597471310.63322,3590,6 WARNING: D3D Frame query timed out, has device hung?
1597471315.63319,3590,6 WARNING: D3D Frame query timed out, has device hung?
1597471320.63333,3590,6 WARNING: D3D Frame query timed out, has device hung?

5 Likes

You could try switching the graphics mode in rendering settings if no fix is found yet
image

2 Likes

I’ve changed my Graphics Mode to OpenGL yet the same error still occurs on the same game. I haven’t tried the other modes yet though.

2 Likes

Are your Intel HD Graphics drivers up to date?

2 Likes

Sorry for the very late reply.

I’ve updated my drivers and the same error still occurs.

2 Likes

I had this happen to me and I have PM’d Roblox internal’s, and the trick was to turn your graphics down to 5 bars or below, although I didn’t get a official solution from Roblox themselves, I realised that my problem was overclocking my GPU, which is apparently too much for Roblox to handle :expressionless:. (Considering other triple A games handle it fine)

2 Likes

Getting this cursed issue on every single game that uses future lighting, can’t play anything for 20 minutes without D3D pooping its pants (another common problem I had but so far haven’t had in a while is “Unable to create D3D device: 8007000e”)

1 Like

Sorry for the bump, but I recently started to have this issue on certain roblox games. And with it, the time between joining and crashing gets smaller, smaller and smaller.

I’ve checked log files each time and can’t find any correlation with anything in logs with the crash. This has been happening for 7 days now.

1 Like