I’m currently working on a standalone application which has to run fullscreen for several days. While running my machine overnight with the application I experience that in the morning the application has left fullscreen and switched from FullHD (1080p) to HDReady (720p). As the machine the application has to run will be not accessible without enourmous effort just restarting the whole thing is no solution.
I checked the logs and at some point the application starts to spam the following message:
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)
(Filename: Line: 1494)
[… this repeats alot …]
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)
(Filename: Line: 1494)
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
d3d: failed to lock level 0 of texture 115 [invalid call]
d3d: failed to lock level 0 of texture 117 [invalid call]
d3d: failed to lock level 0 of texture 119 [invalid call]
d3d: failed to lock level 0 of texture 121 [invalid call]
d3d: failed to lock level 0 of texture 123 [invalid call]
d3d: failed to lock level 0 of texture 125 [invalid call]
Skipped rendering frame because GfxDevice is in invalid state (device lost)
(Filename: Line: 1494)
HandleD3DDeviceLost
HandleD3DDeviceLost: needs reset, doing it
FullResetD3DDevice
ResetD3DDevice
dev->Reset
D3Dwindow device not lost anymore
Skipped rendering frame because GfxDevice is in invalid state (device lost)
(Filename: Line: 1494)
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)
(Filename: Line: 1494)
[… again this repeats alot …]
HandleD3DDeviceLost
HandleD3DDeviceLost: still lost
Skipped rendering frame because GfxDevice is in invalid state (device lost)
(Filename: Line: 1494)
I also checked Windows’ error log but it didn’t logged anything of importance. I also checked this thread from the forum, with no success.
Do you have any ideas how to fix this or at least how to handle this error properly.