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-04-13T07:49:11+00:00

    Having the exact same issue, is there any update e.g. WIP on fixing this issue?

    Would be great if this issue can be looked at and an official response from MS.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-04-01T08:44:12+00:00

    Hi Noel,

    Some further information. In the application event log you will probably find event 1001 "Windows Error reporting" the following at exactly the same time as the system event 4101:

    Fault bucket , type 0

    Event Name: LiveKernelEvent

    Response: Not available

    Cab Id: 0

    Problem signature:

    P1: 141

    P2: ffffcd8a8dcb2010

    P3: fffff802302e2e20

    P4: 0

    P5: 1b8

    P6: 10_0_18363

    P7: 0_0

    P8: 256_1

    P9: 

    P10:

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-04-01T06:35:16+00:00

    Hi Noel_F,

    Glad to hear that im not the only one experiencing this issues. Like i mentioned it affect all latest intel surface products in my organisation.

    The other thing i have recently noticed and something to look out for - when the issue happens the thumbnail app preview on the desktop taskbar activates without any hovering over the taskbar app icon.  I'm going to see if switching to "best performance" appearance solves this issue and gives a clue to the root cause of the issue.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-03-31T22:53:14+00:00

    I'm just jumping into this thread aswell - I've noticed the same issue on my Surface Laptop 3 (i7, 16Gb).

    I'm running the Windows Insider (slow ring) on mine though, but am using the latest drivers & firmware for the device.   

    I suspect it's a driver issue as like Carlo_GLA mentioned, it's very random.  Sometimes it will happen several times in a row, sometimes I only notice it happening once that day.

    I also have the same alert in the System Event Log.  "Display driver igfxn stopped responding and has successfully recovered" Event ID 4101

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-03-27T08:57:20+00:00

    Hi Janette,

    I have an update with this issue. First of all, my company has now noticed the same issue on all 4 of surface products: 1 Surface Pro 7 (i7 intel) and 3 x surface i5 intel models. Exact same symptoms:

    1. Screen very briefly blanks out for about 1 sec
    2. Event log shows the same error Event 4101: "Display driver igfxn stopped responding and has successfully recovered."

    Each one of these surface products were purchased from different suppliers at different time. The only commonality between all of these products are they are Intel versions of the the surface lineup. We also have an AMD surface laptop 3 that does not exhibit the issue. 

    I suspect this issue is more widely experienced by other surface users but because its quite infrequent and short lived its not being reported widely. I think Microsoft need to investigate this issue urgently and issue a fix.

    Can you suggest where we go from here?

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments