Surface Laptop 3 - Event 4101 "Display driver igfxn stopped responding and has successfully recovered."

Anonymous
2020-03-11T18:20:46+00:00

Hi Everyone,

Has anyone been seeing intermittent Event 4101 "Display driver igfxn stopped responding and has successfully recovered" on surface laptop 3? 

Tried all the surface diagnostics tools - all clean. Uninstalled device, reinstalled. - no joy. 

Not had the laptop that long so not sure if updating to the latest surface firmware is the cause. 

Not sure where to go from here. It happen maybe once every few days of constant use - very brief display blanking then recovers. 

Is this a driver issue with the latest intel build? Or hardware issue? Nothing else wrong with the laptop.

Surface | Surface Laptop | Display and screen

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

104 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-05-13T13:33:00+00:00

    have you run a run sfc /scannow (as administrator) ? Of all the changes ive made this is the one that seems to have worked but to be honest I've lost track of what i did and when.

    Regardless, Microsoft should take this issue more seriously. Also take a look at your plugged in power setting and ensure its at best performance. I've seen some of my users experience a higher frequency of the issue when set to lower performance in plugged in mode

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-05-13T13:19:22+00:00

    I can't imagine this is a batch issue either. I've installed the new Intel driver (May 2020) now, and can't get 100% stability and still getting the odd 4101 errors (Display driver igfxn stopped responding and has successfully recovered). I've gone back and turned off graphics acceleration in Office again. Be nice if Microsoft had some opinion on this, and when it might be addressed as it might be a driver/firmware combo that ultimately solves. This issue has been going on for months sadly.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-05-12T16:50:07+00:00

    i dont think its a batch issue i think its a driver intel just released another new driver i am in process of testing it. https://downloadcenter.intel.com/download/29557?v=t

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-05-12T16:49:59+00:00

    Hi John,

    I've not seen the issue for 3 weeks now. Not sure exactly which of the following (or combination) has solved it but here's what I have done so far:

    - run sfc /scannow (as administrator) . 

    • Installed intel command centre as disabled panel refresh (on battery and plugged in)
    • disabled hardware acceleration on all office apps (including teams and outlook) and browsers (edge and chrome)
    • updated the latest intel drivers (Version: 27.20.100.8187 released 5th may)

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2020-05-12T16:33:30+00:00

    I have had this issue for several months. i have rebuilt the laptop and it resolves for a very short period of time then reverts to the same issue and logs the same event. Its now getting very frustrating.

    Do we have a timeline for how long this could take to resolve? 

    Is the batch of devices for this model @fault?

    Was this answer helpful?

    0 comments