Microsoft Surface Pro 8 and BSODs since a couple of month back

FreeBooter · Aug 5, 2023

You are very welcome!

zbook · Aug 5, 2023

If there are drivers that you want to keep for a clean install then they can be backed up to another drive or the cloud.

Backup and Restore Device Drivers in Windows 11 Tutorial

This tutorial will show you how to back up and restore all 3rd party device drivers on your Windows 10 and Windows 11 PC. If you clean install Windows, you will need to install drivers for each device in the system. Some of these device drivers may no longer be available from the manufacturer...

www.elevenforum.com

This is a link for corrected and uncorrected hardware errors:

Hardware Errors and Error Sources - Windows drivers

Hardware Errors and Error Sources

learn.microsoft.com

In two to three weeks post a new V2 share link.

The computer is under warranty.

Unknowns:

1) What happens to corrected hardware errors over time?

A corrected error is a hardware error condition that has been corrected by the hardware or the firmware by the time that the operating system is notified about the presence of the error condition.

a) Do they indicate that one or more of the hardware components is suboptimal?
b) Do they indicate that one or more of the hardware components may have a shortened use?
c) Do they only report a finding that can be ignored?

iorx · Aug 17, 2023

Hi ladies and germs!

Sorry, I have to report that I've had a couple of BSODs since last time posting here. But they all happened when I had OpenVPN running. So, that is something, maybe a pattern here. I've upgrade 2.6.5 to 2.6.6, but just got a BSOD again.
It had been running great without problem when not having OpenVPN-tunnels active. I've tormented my machine as usual both CPU and memory wise, but without VPN active it looks like it's stable.

This is rather low priority now as you awesome people have invested lots of time in this already. Attaching latest V2 and a complete memory dump if anyone feel the urge to have a look. I'm pretty certain that this is related to some combination of my wifi-drivers and OpenVPN. Search high & low on OpenVPN BSODs issues but haven't come up with any recent reports of that happening.

sp8-bsod

Folder

1drv.ms

Brgs!

zbook · Aug 17, 2023

Please contact the computer manufacturer for Return Merchandise Authorization (RMA)

08/16 BSOD bugcheck 1A
08/17 BSOD bugcheck F7

Code:

Event[61101]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-17T20:39:02.7140000Z
  Event ID: 3
  Task: N/A
  Level: Information
  Opcode: Information

  Keyword: WHEA Error Event Logs,
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: msp8
  Description:
Det har uppstσtt ett maskinvarufel. Det finns information om felet i datasektionen i den hΣr hΣndelsen.

Event[61102]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-17T20:39:02.7170000Z
  Event ID: 3
  Task: N/A
  Level: Information
  Opcode: Information

  Keyword: WHEA Error Event Logs,
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: msp8
  Description:
Det har uppstσtt ett maskinvarufel. Det finns information om felet i datasektionen i den hΣr hΣndelsen.

Event[61103]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-17T20:39:02.7170000Z
  Event ID: 3
  Task: N/A
  Level: Information
  Opcode: Information

  Keyword: WHEA Error Event Logs,
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: msp8
  Description:
Det har uppstσtt ett maskinvarufel. Det finns information om felet i datasektionen i den hΣr hΣndelsen.

Event[61104]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-17T20:39:02.7170000Z
  Event ID: 3
  Task: N/A
  Level: Information
  Opcode: Information

  Keyword: WHEA Error Event Logs,
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: msp8
  Description:
Det har uppstσtt ett maskinvarufel. Det finns information om felet i datasektionen i den hΣr hΣndelsen.

Event[61105]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-17T20:39:02.7170000Z
  Event ID: 3
  Task: N/A
  Level: Information
  Opcode: Information

  Keyword: WHEA Error Event Logs,
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: msp8
  Description:
Det har uppstσtt ett maskinvarufel. Det finns information om felet i datasektionen i den hΣr hΣndelsen.

iorx · Aug 17, 2023

I'll do. Think this thread is proof enough to justify a hardware replacment.

Thanks again!

zbook · Aug 17, 2023

You're welcome.

These were the latest BSOD:

Code:

Event[61065]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-17T20:38:59.1120000Z
  Event ID: 1001
  Task: N/A
  Level: Fel
  Opcode: Information
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: msp8
  Description:
Datorn har startats om efter fels÷kningen. Fels÷kningen var: 0x000000f7 (0x00000000000000fa, 0x0000fc988f3bdafa, 0xffff036770c42505, 0x0000000000000000). Innehσllet dumpades och sparades i: C:\WINDOWS\MEMORY.DMP. Rapport-ID: 3ecdc4fa-78ae-4158-b286-bdd95d84856b.

Code:

Event[55267]
  Log Name: System
  Source: volmgr
  Date: 2023-08-16T00:29:21.7690000Z
  Event ID: 161
  Task: N/A
  Level: Fel
  Opcode: N/A
  Keyword: Klassiskt,
  User: N/A
  User Name: N/A
  Computer: msp8
  Description:
Ett fel uppstod som gjorde att det inte gick att skapa en dumpfil.

Code:

Event[55357]
  Log Name: System
  Source: Microsoft-Windows-WER-SystemErrorReporting
  Date: 2023-08-16T00:29:37.2800000Z
  Event ID: 1001
  Task: N/A
  Level: Fel
  Opcode: Information
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: msp8
  Description:
Datorn har startats om efter fels÷kningen. Fels÷kningen var: 0x0000001a (0x0000000000061941, 0xffff96884310ca70, 0x0000000000000009, 0xffffcb0de8544300). Innehσllet dumpades och sparades i: C:\WINDOWS\MEMORY.DMP. Rapport-ID: 9d0ee0d5-8cf1-4dde-a69a-c94b439d9ec9.

Code:

Event[60985]
  Log Name: System
  Source: volmgr
  Date: 2023-08-17T20:38:45.4560000Z
  Event ID: 161
  Task: N/A
  Level: Fel
  Opcode: N/A
  Keyword: Klassiskt,
  User: N/A
  User Name: N/A
  Computer: msp8
  Description:
Ett fel uppstod som gjorde att det inte gick att skapa en dumpfil.

Code:

Event[21058]
  Log Name: System
  Source: volmgr
  Date: 2023-08-07T07:04:56.4250000Z
  Event ID: 161
  Task: N/A
  Level: Fel
  Opcode: N/A
  Keyword: Klassiskt,
  User: N/A
  User Name: N/A
  Computer: msp8
  Description:
Ett fel uppstod som gjorde att det inte gick att skapa en dumpfil.

x BlueRobot · Aug 18, 2023

iorx said:
It had been running great without problem when not having OpenVPN-tunnels active. I've tormented my machine as usual both CPU and memory wise, but without VPN active it looks like it's stable.

If it's remained stable without OpenVPN then that is most likely the issue and would explain the NDIS related bugchecks from earlier. I'm not sure if this is too helpful, but the VPN I used at my previous job was WatchGuard and I never had any issues with that. It worked flawlessly on Windows 10 and Windows 11. I'm not sure if it has a free option unfortunately.

Download, Install, and Connect the Mobile VPN with SSL Client

This topic describes how to download and install the Mobile VPN with SSL client. This topic also describes how to use the client to connect to a private network.

www.watchguard.com

Stop 0xF7s are usually always driver-related but unfortunately you can only usually debug them when you have "Special Pool" enabled in Driver Verifier.

Here's from the Stop 0x1A which you had:

Rich (BB code):

3: kd> .trap ffffcb0de8544300
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff96884310ca40 rbx=0000000000000000 rcx=ffff96884310ca40
rdx=000000000000004c rsi=0000000000000000 rdi=0000000000000000
rip=fffff8042108d940 rsp=ffffcb0de8544498 rbp=0000000000000000
 r8=00000000000001c8  r9=0000000000000000 r10=0000000000000000
r11=ffff9688212b80e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
Netwtw10+0x4d940:
fffff804`2108d940 488b4130        mov     rax,qword ptr [rcx+30h] ds:ffff9688`4310ca70=ffff96884157d650

It looks like we page faulted when the IRQL level was too high, this is going to be a driver-related bug for sure.

Rich (BB code):

3: kd> !irql
Debugger saved IRQL for processor 0x3 -- 2 (DISPATCH_LEVEL)

That driver is your Intel network adapter driver too.

If you're going to do an RMA, they will probably ask what the issue is and if you mention that it seems to only crash with OpenVPN then they will probably just ask you remove that instead. I would personally use different VPN software and see if it works with that before writing off the machine. That's your decision though.

iorx · Sep 4, 2023

Hi folks!

Begin to respond to the above regarding OpenVPN. Thank you for analyzing my logs/dmp.
I'm not sure, but it could be related to that I usually have lots of stuff running when I need to connect to customers, maybe that in combination lured the problem out. I had BSODs when not OpenVPN was active too, but not as frequent.
All my customer run OpenVPN as a roadwarrior solution, no problem there. I run it on a couple of other machines, no problems (Thinkpad Carbon, Thinkpad T14s gen 2, Thinkpad X1 Yoga 3rd Gen, Microsoft Surface Book 3...)

But to the point, I got a replacement sent to me after I did a hardware RMA of the unit. It was an "advanced replace" as Microsoft calls it, they send out a replacement unit, you swap unit and send back the faulty one. They had already imported the new HWID into to my tenant (Office 365/AzureAD/EndPoint/Intune) so I just took my existing SSD and put it into the new machine and got it running (some quirks at first logon because of the membership in azure and the new serialnumber, but then everything was fine.)

This has been running without BSODs or any trouble since the replacement (2023-08-31), this is with the exact same OS-install that the faulty machine was running. So, can't rule out that it actually was faulty hardware.

And once again, can't thank everybody enough for going through this with me! THANKS! Without you I had probably still been fighting with support to get them to accept the RMA-replacement.

Case resolved and I got a stable machine again, with and without peripherals (eGPU-case with Nvidia GPU and GB NIC on thunderbolt. USB-C hub with security Card-reader, Webcam and more.)

Brgs!