[SOLVED] "Application has been blocked from accessing graphics hardware" after waking from sleep

[pk1209]

Out of the blue (seemingly) have been getting this error message, but only seems to happen after waking from sleep.

PC is fine during gaming, and it's not a single application giving the error.

Specs:

Asus ROG Strix RTX 3090 OC

Asus ROG Z690 Maximus Hero

Intel 12900K

ROG Strix 1000W PSU

Corsair DOMINATOR PLATINUM RGB 32GB (2x16GB) DDR5 5600MHz C36

Water-cooler on a custom loop.

Done a bit of Googling and have tried:

sfc /Scannow
DISM commands
Clean driver install (via GeForce experience)
Changed XMP II to XMP I

Windows reinstall might be next step, but hoping to avoid that as only build the system a few months back!

Any help appreciated!

 

[Colif]

perhaps look in event viewer at time of the error and see if any events recorded that might show what is being stopped.

Most sleep related problems are drivers. Not just GPU drivers.

 

[pk1209]

Hmm... looks like it could be to do with the OVR Service Launcher, which Oculus... gone into Oculus software and there was a warning in the settings about it not being default OpenXR runtime... no idea what that means, but resolved that. Will keep an eye on it now

 

[pk1209]

So wasn't that... have removed my meagre overclock on the GPU, but that's been on and stable for 4 months. Suspect Windows reinstall needed...

 

[Colif]

you could run this and make it track dwm.exe and see what interacts with it just as you wake from sleep
https://docs.microsoft.com/en-us/sysinternals/downloads/procmon

not sure you can track dwm.exe but its worth a try. Its Windows Desktop Manager, it sits between windows and GPU drivers. If anything knows, it should.

 

[pk1209]

thanks, looks like I can track it, will give it a go

 

[Colif]

any results yet?

another thing to track might be nviddklm.sys which is the Nvidia driver, but I don't believe applications interact direct with GPU drivers.

 

[pk1209]

i ended up doing a full driver wipe with display driver uninstaller in safe mode, and then that seemed to have resolved it for 24 hours or so... but just happened again, this time not waking from sleep.

Will see what I get in procmon next time it happens

 

[pk1209]

unfortunately, proc mon crashed when i was trying to filter the data - there was a boat load of "WerFault.exe" in there...

 

[Ralston18]

Per @Colif 's suggestion keep an eye on Event Viewer.

You can also use Reliability History. Reliability History is a bit more user friendly and the presented time line format can be very revealing.

Look carefully at the first 24 hours and then for some error code, warning, or even an information event that was captured.

Remember that you can click on any given error to obtain more information. Unfortunately that additional information may or may not be helpful.

 

[pk1209]

Well... i had noticed that the first exe to trigger the error seemed to be the same each time... and then after that it was a bit of a free-for-all. I ended the tasks for the exe in question - ovrserver_x64.exe - which is part of the Oculus software. 24hours later, no issues, both waking from sleep or just in normal use (inc. gaming). So at the moment, I'm thinking that's the culprit...

 

[Colif]

One place it might give a clue is if you look in system information app
look at left hand colum, click on the + next to Software Environment
Click on Windows Error Reporting
now once the main window opens,
its dumb, the date order is in 1st number, not year... so just click on the type to sort them by Application Errors and WER - mine took a while to load so don't assume its stuck

now this is where werfault reports its errors. WER - Windows Error Reporting
So look through these and see if you can find anything that corresponds with the errors.
If you want, you can screenshot any results if you need help.

 

[pk1209]

thanks for the additional info... still no issues since I terminated ovrserver_x64.exe. Planning to not reboot for a few more days to see if that changes, at which point, i will restart and see if the issue comes back. Will try to see what I can correlate in the logs at that point.

 

[Colif]

i didn't notice that post lol.

 

[pk1209]

Well... colour me confused.... this just appears to have disappeared as quickly as it arrived! No material changes, everything running as it was before... and no more errors!?