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

iorx · Jul 22, 2023

Hi,

As the title indicates, this started a couple of month ago. I suspect a Windows roll up update, but that's just a theory / thought.
Everything is updated. Windows Update is ok. I've re-installed the Microsoft Drivers support pack.

Sad picture

After every BSOD I force a "fsutil dirty set c:" and reboot once more to verify that the disk structure is still fine.

This comes out clean and without errors.

Code:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
Dism /Online /Cleanup-Image /AnalyzeComponentStore
Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase
SFC /ScanNow

I humbly asks for some brain picking here as I've run out of ideas and the Microsoft support case I've started doesn't go anywhere (they just tell me to re-image the machine, when I would like to get answers from my questions on "why" it BSODs), a get I strong feeling that they don't know what to do of the "bucket" of information delivered to them.

So my hope goes here to see if it's possible to identify the causing driver or if this is a hardware fault (suspect ram or such)

I have also started a post here, but not received any response yet. Surface Pro 8 BSOD, help to identify why?

My own attempt to analyze the dmp-file with windbg has lead me nowhere.

Please run the V2 log collector (If there were any problems running V2 then run DM. Please post images if there were problems running V2).
Ran as it should. I'll link to the file: MSP8-(2023-07-22_16-34-35).zip
If I can provide any more info please tell.
These files are available under Resources. It helps if your system is using the English language so that the logs can be read ( see here & here for help)
Missed to check this one collecting logs but it looks like it's in English. I'll dump a new if it's a not as it should.
Fill in the System Specs section of your profile with as much information as possible so that the analysts can determine if any components of your system are contributing to the problem. Remember to include details of your Power Supply Unit (PSU) for desktop systems.
Check!
Provide a brief summary of when the crash most often occurs and the particular circumstances (if any) that trigger it.
This is the tricky part, I haven't found a pattern here. Which apps running or an event related to a certain BSOD. Sorry.
Remove all overclocking on your system and confirm the BSODs still occur before posting here. (If you do not, you will be asked to do this as part of the troubleshooting process so it will save you time.)
Please let us know the age of your system and whether any of the components are still under warranty.
About a year to go on the warranty.

FreeBooter · Jul 22, 2023

The BSOD errors are mostly caused by faulty RAM module. I will recommend that you test the RAM using Windows Memory Diagnostic Tool or MEMTest86. For accurate results, be sure to test it with 8 passes. If you have more than 1 RAM stick, be sure to test it one at a time.

iorx · Jul 22, 2023

Thank you for your answer.

The machine has been stable before so I ruled out the ram faulty part, but maybe I should give that a serious run. I did that when the machine was new because of BSODs but I then isolated the crashes to power managment in a realtek driver and the BSODs went a way.

This time is different as the machine is running "naked", no peripherals besides a Bluetooth mouse.

The problem with running memory test och this machine is that it gets hot, hot as in "I'm a bit worried" and "burning your fingers touching it".

Regarding ram modules

It's configured as delivered and looking at the hw config it looks like one module only.

But I'll let it run a couple cycles with your recommendation of at least 8 passes. I'll put a fan blowing at the machine I think...

iorx · Jul 23, 2023

Hi again!

Used Windows Memory Diagnostics (WMD used below)

Maybe we're onto something here. Left it overnight. 9 cycles and Extended test was chosen.
When i woke up it was here.

I left it there for 40 minutes and it didn't progress. Even though it says clearly that it may appear inactive, it should have progressed I think. The F1 option to change settings was unresponsive, the little keyboard icon in the bottom right corner didn't respond. So I presume it had hung (correct?) and did a hard shutdown..

Give it, WMD, another run with Standard options (default) and 8 cycles (2 default) or should I try out MEMTest86?

On the positive side WMD didn't heat up machine as MEMTest86 did in previous tests.

FreeBooter · Jul 23, 2023

You should test memory with MEMTest86 for better result.

Use Memtest86+ disc to check system memory's (RAM's) for errors.

iorx · Jul 23, 2023

Hi!

Not been able to lure out any memory errors yet. Just did one cycle with MEMtest86+ and almost 400% with MemTest for Windows Download Page (which I read up on and should be good to find memory errors)

Had multiple instances running to allocate all memory and user all cores (the free version hints that you could do like that). This ran for several hours. No errors and no BSOD...

Note on MEMtest86+
When I deactivated secure boot my machines it wanted to recover/verify the bitlocker-key on next boot. Be sure to have this one documented and saved before turn secure boot off.

First attempt to create a bootable USB faild, I just took a FAT32 thumb I had. Did the below to get a working boot-stick.
Use diskpart to create the partition and make it active.
diskpart
"list disk" to see your drives
"sel disk" to select the USB-drive you planing to use.
"clean" total wipe of the drive (be sure that you've selected the right disk)
"cre part pri" to create a partition
"active" activate the partition to enable start on it
"format fs=fat32 quick" to format it.
"assign" to get a drive letter for it.
Now run the mt86plus_6.20_USB_Installer.exe and use the drive as destination.

I'm going to make MEMtest86+ loop tonight so it completes more cycles.

But I starting to think that the memory may not be the problem here as the machine was stable up until a month ago, aprox. I suspect a driver or something else is causing the BSOD. Got a vague feeling about Edge and Remote Desktop session, when I think back I've always had Edge and/or a couple Remote Desktop session running when it has done BSOD. Any logic to this?

The uploaded file contains some minidumps, does they give away whats happening? I couldn't figure it though.

Brgs and many thanks for reading and helping out.

FreeBooter · Jul 23, 2023

Let get the faulty hardware out of the way.

If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.
Look in Device Manager to see if any devices are marked with an exclamation point (!), which indicates a problem. Review the events log displayed in the properties for any faulting device driver. Try to update the related driver.
Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Look for critical errors in the system log that occurred in the same time window as the blue screen.
If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.
Install Windows updates.
If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.
Use SpeedFan to monitor temperatures in computers, overheating can cause BSOD.
Use CrystalDiskInfo to check SMART health report of the hard disk drive (HDD).

iorx · Jul 23, 2023

FreeBooter said:
Let get the faulty hardware out of the way.

If new device drivers or system services have been added recently, try removing or updating them. Try to determine what changed in the system that caused the new bug check code to appear.

Look in Device Manager to see if any devices are marked with an exclamation point (!), which indicates a problem. Review the events log displayed in the properties for any faulting device driver. Try to update the related driver.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Look for critical errors in the system log that occurred in the same time window as the blue screen.

If you recently added hardware to the system, try removing or replacing it. Or check with the manufacturer to see if any patches are available.

Install Windows updates.

If you are overclocking (pushing the components beyond their design) you should revert to default at least until the crashing is solved. If you don't know what it is you probably are not overclocking.

Use SpeedFan to monitor temperatures in computers, overheating can cause BSOD.

Use CrystalDiskInfo to check SMART health report of the hard disk drive (HDD).

Thanks again for the help.

Answers to the bullet list.

No new hardware added since and when this begun
All devices are OK in device manager
Can't identify any event that's related to driver problems
Hardware added. Nothing new, checked all existing and they're latest available.
WU is current, nothing new.
Overclocking, no. Don't even know if its even possible on this machine
Temperature. Uses Libre Hardware Monitor for this. Can't connect temperature with BSODs sadly. As a screenshot above shows it was at, I think, top temperature when running the memory tests in windows. It was at that temperature for hours while running the test.
Disk. No smart indicators shows that anything is bad or on it's way to go bad.

Code:

----------------------------------------------------------------------------
CrystalDiskInfo 9.1.1 (C) 2008-2023 hiyohiyo
                                Crystal Dew World: https://crystalmark.info/
----------------------------------------------------------------------------

    OS : Windows 11 Professional [10.0 Build 22621] (x64)
  Date : 2023/07/23 22:25:27

-- Controller Map ----------------------------------------------------------
 - Microsoft Storage Spaces Controller [SCSI]
 + Standard NVM Express Controller [SCSI]
   - HFM001TD3GX013N-SKhynix
 - Xvdd SCSI Miniport [SCSI]
 - Microsoft VHD Loopback Controller [SCSI]
 - SoftPerfect Virtual Bus [SCSI]

-- Disk List ---------------------------------------------------------------
 (01) HFM001TD3GX013N-SKhynix : 1020,2 GB [0/0/0, sq] - nv

----------------------------------------------------------------------------
 (01) HFM001TD3GX013N-SKhynix
----------------------------------------------------------------------------
           Model : HFM001TD3GX013N-SKhynix
        Firmware : 41001C20
   Serial Number : F****************Z
       Disk Size : 1020,2 GB
       Interface : NVM Express
        Standard : NVM Express 1.3
   Transfer Mode : PCIe 3.0 x4 | PCIe 3.0 x4
  Power On Hours : 7657 hours
  Power On Count : 138 count
      Host Reads : 13135 GB
     Host Writes : 16466 GB
     Temperature : 30 C (86 F)
   Health Status : Good (100 %)
        Features : S.M.A.R.T., TRIM, VolatileWriteCache
    Drive Letter : C:

-- S.M.A.R.T. --------------------------------------------------------------
ID RawValues(6) Attribute Name
01 000000000000 Critical Warning
02 00000000012F Composite Temperature
03 000000000064 Available Spare
04 00000000000A Available Spare Threshold
05 000000000000 Percentage Used
06 000001A45376 Data Units Read
07 0000020EEF8F Data Units Written
08 0000159EAD08 Host Read Commands
09 00001C83183F Host Write Commands
0A 00000000041B Controller Busy Time
0B 00000000008A Power Cycles
0C 000000001DE9 Power On Hours
0D 000000000029 Unsafe Shutdowns
0E 000000000000 Media and Data Integrity Errors
0F 000000000000 Number of Error Information Log Entries

FreeBooter · Jul 23, 2023

I'm no expert when it comes to BSOD i believe @zbook can help you with this error message then me.

iorx · Jul 24, 2023

Great, more brains are always welcome! Hope zbook have time to have a look then.

Think we maybe can rule out the RAM on the machine, this ran without errors all night (what I can see).

FreeBooter · Jul 24, 2023

Looks good i just DM @zbook hopefully if he is not busy he will help out.

zbook · Jul 24, 2023

Part of the collected log files were in another language and were not able to be scanned.

There were many WHEA reports.

What is the Surface Pro 8 warranty status?

1) Run through these steps:

Fix common Surface problems using the Surface app and Surface Diagnostic Toolkit - Microsoft Support

Access, download, or run the Surface app and the Surface Diagnostic Toolkit to help find and solve Surface problems.

support.microsoft.com

2) Run Tune up plus > post a share link into this thread using one drive, drop box, or google drive

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

3) Test the computer first using Windows driver verifier (WDV) to rule out misbehaving drivers.

Enable and Disable Driver Verifier in Windows 10

How to Enable and Disable Driver Verifier in Windows 10

www.tenforums.com

Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

start the testing with these settings:
a) Test all non-Microsoft drivers
b) test no Microsoft drivers
c) start the testing with the 3 customized tests in the TF link

If there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive

For any BSOD post a new V2 share link into the newest post

Code:

Event[56255]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-07-22T16:23:29.0050000Z
  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[56256]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-07-22T16:23:29.0050000Z
  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[56257]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-07-22T16:23:29.0050000Z
  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[56258]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-07-22T16:23:29.0050000Z
  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[56259]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-07-22T16:23:29.0050000Z
  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[56260]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-07-22T16:23:29.0050000Z
  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.

1A
3B
141

iorx · Jul 25, 2023

Hi thanks for dropping by!

I'll answer what I can here to begin with, and have some q.

Eventlogs in correct language, English. This was harder than I though, I really can't get it to "speak" English. I've changed everything to en-US, default, administrative settings. But still I find Swedish with in the evenlogs. Any tricks here? The baseinstall is Swedish.
I read through the language-change guide and used extensive google-fu.
But should I really remove the base language?
This one should be the "holy grail" to get eventlog and other suborn apps to use the language specified, in my case it doesn't work.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MUI\Settings PreferredUILanguages en-US

Warranty is valid until: 2024-08-15

Have ran them both. Nothing reported or fixed what I can understand.
I had a run through with these when I initilized the case with microsoft (who has gone radio silence when I replied to their fix-solution "re-image" with that I wanted to know what was causing this before wiping the machine.)
Dumb question. Should I be able to use my elevenforum credential there? Your link to Tune Up Plus is behind a logon.
Not there yet.

Note/thoughts: Bought a new SSD to have some options / possibilities here, a 1TB 2230 Corsair MP600 (needs the Power-pci-settings-fix to be stable I've read) to re-image on that one and see if I can get a BSOD then, on a "new". I feels not so fun starting over with a new install as all config, tools and tweaks need to be done all over again, it takes days to prep this machine I think...
If I can get a stable machine on that then I may not need to waste your precious time here.

And of course my machine hasn't visited BSOD-land since I started this thread...

zbook · Jul 25, 2023

These are tuneup plus links:

Tuneup_plus_log.bat

【Last updated on February 18, 2022】
.
For non-members:

Tuneup_plus_log.zip

【Extract the batch file from the ZIP file】

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Some hardware stress testing may be performed after WDV testing.

iorx · Jul 25, 2023

FYI, both link requires login. No big deal, I registered an account there too.

zbook · Jul 25, 2023

This link was designed for those that have already logged on to EF and were not able to logon to TF.

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

iorx · Jul 25, 2023

Tune Up logs.

Code:

 Microsoft Windows 11 Pro  Version 22H2 (OS Build 22621.1992)
 
==================================================================

    Started on 2023-07-25 at  8:01:33,29
    
        [SFC /ScanNow]
    
Beginning system scan.  This process will take some time.

Results:
 
Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on 2023-07-25 at  8:03:13,44

        [DISM /online /cleanup-image /ScanHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22621.1992
 
No component store corruption detected.

The operation completed successfully.
 
==================================================================

    Started on 2023-07-25 at  8:04:15,38

        [DISM /online /cleanup-image /RestoreHealth]

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22621.1992
 
The restore operation completed successfully.

The operation completed successfully.
 
==================================================================

The second "SFC /ScanNow" was skipped, as the first output the following:

Windows Resource Protection did not find any integrity violations.
 
==================================================================

    Started on 2023-07-25 at  8:05:08,88

        [ChkDsk /Scan] 
 
The type of the file system is NTFS.
Volume label is Local Disk.
 
Stage 1: Examining basic file system structure ...
1232128 file records processed.                                                       
File verification completed.
Phase duration (File record verification): 28.35 seconds.
22624 large file records processed.                                   
Phase duration (Orphan file record recovery): 8.31 milliseconds.
0 bad file records processed.                                     
Phase duration (Bad file record checking): 0.03 milliseconds.
 
Stage 2: Examining file name linkage ...
395813 reparse records processed.                                     
1552466 index entries processed.                                                       
Index verification completed.
Phase duration (Index verification): 21.83 seconds.
0 unindexed files scanned.                                       
Phase duration (Orphan reconnection): 5.95 seconds.
0 unindexed files recovered to lost and found.                   
Phase duration (Orphan recovery to lost and found): 0.09 milliseconds.
395813 reparse records processed.                                     
Phase duration (Reparse point and Object ID verification): 903.99 milliseconds.
 
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 50.76 milliseconds.
160170 data files processed.                                           
Phase duration (Data attribute verification): 0.07 milliseconds.
CHKDSK is verifying Usn Journal...
35102520 USN bytes processed.                                                           
Usn Journal verification completed.
Phase duration (USN journal verification): 104.08 milliseconds.

Windows has scanned the file system and found no problems.

No further action is required.
 
995018751 KB total disk space.
695808944 KB in 915705 files.
610100 KB in 160171 indexes.
0 KB in bad sectors.
1690903 KB in use by the system.
65536 KB occupied by the log file.
296908804 KB available on disk.
 
4096 bytes in each allocation unit.
248754687 total allocation units on disk.
74227201 allocation units available on disk.
Total duration: 57.20 seconds (57205 ms).
 
==================================================================
 
    Started on 2023-07-25 at  8:06:18,69
 
AutoReboot   
 
FALSE       
 
==================================================================
 
        [Set AutoReboot = False]
 
Updating property(s) of '\\MSP8\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
AutoReboot   
 
FALSE       
 
==================================================================
 
DebugInfoType   
 
2             
 
==================================================================

        [Set DebugInfoType = 7]

Updating property(s) of '\\MSP8\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\WINDOWS|\\Device\\Harddisk0\\Partition3"'
Property(s) update successful.
==================================================================
 
DebugInfoType   
 
7             
 
==================================================================

        [WMIC PageFile list]

AllocatedBaseSize=32768
CurrentUsage=60
Description=C:\pagefile.sys
InstallDate=20220521193524.093446+060
Name=C:\pagefile.sys
PeakUsage=129
Status=
TempPageFile=FALSE
 
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                     
 
==================================================================

        [Set AutomaticManagedPagefile = True]

Updating property(s) of '\\MSP8\ROOT\CIMV2:Win32_ComputerSystem.Name="MSP8"'
Property(s) update successful.
==================================================================
 
AutomaticManagedPagefile   
 
TRUE                     
 
==================================================================

        [BcdEdit /enum {badmemory}]

RAM Defects
-----------
identifier              {badmemory}
isolatedcontext         Yes
badmemorylist           0x62057b
 
==================================================================

    Finished on 2023-07-25 at  8:06:20,59
    It took 4 minutes and 47 seconds to complete the operations.

zbook · Jul 25, 2023

When ready please start WDV.

The opening post share link is no longer working.

Please make sure that the V2 and other share links remain available during the thread.

Post a new V2 share link into the newest post.