Firefox blocked from accessing graphics hardware?

I’ve lately starting this week gotten notifications from Windows that Firefox.exe has been blocked from accessing graphics hardware. Anyone else see the same message? What can one do about that?

I got those a few times after I took Lenovo’s TB3 dock into use. After I installed Intel’s Thunderbolt software/driver I haven’t seen that issue pop up again.

ok, but in this case I’m using only the V - no thunderbolt hardware connected. Windows reliability monitor indicates some hardware errors, so might be something with a driver. Also noticed that the defragmenter was running, which I turned off immediately. Weird that it was running as Windows usually detects SSDs.

When it happended to me, Event Viewer had also few entries in it about it.

Windows Logs > System:

  • Warning / Application firefox.exe has been blocked from accessing Graphics hardware.
  • Warning / Display driver igfx stopped responding and has successfully recovered.
  • Warning / Display driver igfx stopped responding and has successfully recovered.
  • Warning / Display driver igfx stopped responding and has successfully recovered.

Windows Logs > Application:

Had 4 Information events from the same moment, with similar contents. Here’s one of them:

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffff848917710010
P3: fffff80abe1257e0
P4: 0
P5: 530
P6: 10_0_16299
P7: 0_0
P8: 256_1
P9: 
P10: 

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20180316-2302.dmp
\\?\C:\WINDOWS\TEMP\WER-6543156-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9C2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9C2.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9D2.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_4d7b377540f256a340d14689a984cec059b93fd2_00000000_2e27e9e1

Analysis symbol: 
Rechecking for solution: 0
Report ID: d3d09530-94d5-406f-8fc1-ddd9d11dbbeb
Report Status: 4
Hashed bucket: 

If you have similar events, perhaps that watchdog crash dump file could give more insight what has gone wrong.

caused by igdkmd64.sys dated 28.02.2018 16:14:41 so apparently intel graphics driver

new driver version 23.20.16.4982 dated 08.03.2018 seems to fix the issues for me, so this can be closed as solved.

2 Likes