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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-04-30T19:39:06+00:00

    Your right i am back again to same thing

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-30T19:40:20+00:00

    Yeah i have had a case its going on almost 3 months making no lead way sending logs try this try that its really frutrating

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-05-04T17:20:42+00:00

    Thanks Meathooks!  That solved my problem!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-05-06T17:04:33+00:00

    I have the same issue. Updated intel drivers didnt fix either.

    Got fed up with it, so disabled did "Disable hardware graphics acceleration" in Outlook Options > Advanced. Only a workaround.

    Havent seen the issue now for a week.

    Was 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