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

zbook · Jul 25, 2023

The latest V2 appears to be before running the tuneup plus script.

Please run the script again then post a new V2 share link into the newest post.

iorx · Jul 25, 2023

Hi again!

Now got a active WDV running as I understand. Checked all drivers that didn't have Microsoft as it maker.

Code:

Verifier Flags: 0x00100610

  Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Verified Drivers:

    spvdbus.sys
    npcap.sys
    ovpn-dco.sys
    wintun.sys
    tap0901.sys
    igdkmdn64.sys
    iaisp64.sys
    tbtbusdrv.sys
    ialpss2_i2c_tgl.sys
    intelthcbase.sys
    netwtw10.sys
    teedriverw10x64.sys
    ialpss2_uart2_tgl.sys
    intcaudiobus.sys
    ialpss2_gpio2_tgl.sys
    nvvad64v.sys
    nvmoduletracker.sys
    nvvhci.sys
    iactrllogic64.sys
    intcoed.sys
    ov5693.sys
    ov13858.sys
    vd55g0.sys
    rtkvhd64.sys
    intcusb.sys
    intcbtau.sys
    ibtusb.sys
    iacamera64.sys
    speedfan.sys
    spvve.sys
    librehardwaremonitor.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys

Other changes to the system.
Now running with and USB-C external screen also, the BSODs has happened with and without the screen connected so I don't consider it a parameter.
Also, the whole system was migrated to the new SSD, MP600 Corsair, with DiskGenius Free.

No BSODs before or after activating WDV. Of course it's stable when I got professional help to have a look at it, it doesn't dare to do a hick-up now!

I'll leave WDV running for a while. Saw something about 48h was enough. Any other recommendations here?

Brgs!

iorx · Jul 25, 2023

Sorry bout the old V2, now there is a new there.
Missed moving the previous run from desktop to the OneDrive-folder, modded the script so they now end up in the shared folder.

OneDrive

Sign in to your OneDrive cloud storage and Office Online.

1drv.ms

Note: Think the machine became a little quicker with the new SSD. Now I can pop in the old one and do some heavy experimenting if that is required.

Thought: Think I mentioned this. But I almost always have Edge Dev and a couple RDP-sessions going, haven't had them running at the same degree troubleshooting. But could for example Edge cause a BSOD? It should be running in user space and not be able to, or?
And also, is there any way I can see what software was running when it BSODed?

zbook · Jul 25, 2023

Turn off WDV.

Run tuneup plus to modify the default computer settings > post a share link into the newest post > make a new restore point > post a new V2 share link into the newest post

Plan to run WDV with various customized tests after the above steps.

After WDV testing plan to test hardware.

iorx · Jul 26, 2023

OneDrive

Sign in to your OneDrive cloud storage and Office Online.

1drv.ms

Folder with all files generated.

WDV off, confirmed and a reboot.

TuneUp:

Code:

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        2022-02-18     18:14          26165 Tuneup_plus_log.bat

Resulting Tuneup.log is in the folder now.

Restore point. Done.

V2 log:
(Output after it finished and I press enter "[process exited with code 4294967295 (0xffffffff)]")
\sp8-bsod\MSP8-(2023-07-26_07-31-30).zip now in the folder.

zbook · Jul 26, 2023

Please restart WDV with these customized tests:

Code:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.

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

iorx · Jul 26, 2023

Just so interpret your post correctly. I should check all the above tests like this?

iorx · Jul 26, 2023

I ran it with the same subset of drivers as before but with the above settings. No BSOD.
Result:

Code:

Verifier Flags: 0x001a0fbb

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [X] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.all

  Verified Drivers:

    spvdbus.sys
    npcap.sys
    ovpn-dco.sys
    wintun.sys
    tap0901.sys
    igdkmdn64.sys
    iaisp64.sys
    tbtbusdrv.sys
    ialpss2_i2c_tgl.sys
    intelthcbase.sys
    netwtw10.sys
    teedriverw10x64.sys
    ialpss2_uart2_tgl.sys
    intcaudiobus.sys
    ialpss2_gpio2_tgl.sys
    nvvad64v.sys
    nvmoduletracker.sys
    nvvhci.sys
    iactrllogic64.sys
    intcoed.sys
    ov5693.sys
    ov13858.sys
    vd55g0.sys
    rtkvhd64.sys
    intcusb.sys
    intcbtau.sys
    ibtusb.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    iacamera64.sys
    speedfan.sys
    spvve.sys
    librehardwaremonitor.sys

zbook · Jul 26, 2023

1) Make a new restore point.

2) Restart WDV with all customized tests except:

[ ] 0x00000004 Randomized low resources simulation.

Run WDV for 24 hours.

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.

3) After completing WDV testing:

a) post a new V2 share link into the newest post

b) Open administrative command prompt and copy and paste:

bcdedit /enum {badmemory}

bcdedit /deletevalue {badmemory} badmemorylist

bcdedit /enum {badmemory}

To copy type:
ctrl + a
ctrl + c

To paste into this thread type:
ctrl + v

Or post a share link into this thread using one drive, drop box, or google drive.

4) Monitor the computer using reliability monitor:

View Reliability History in Windows 11 Tutorial

This tutorial will show you how to view reliability history for your Windows 11 device. The Reliability Monitor provides a system stability overview and details about events that impact reliability. It calculates the Stability Index shown in the System Stability Chart. Reliability Monitor...

www.elevenforum.com

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

iorx · Jul 27, 2023

I was on my way to ask for a pause in this case as the machine hadn't encountered any BSODs since the memory tests... But...

Code:

The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000061941, 0xffffa90010b6b1e8, 0x0000000000000009, 0xffff900351d16a80). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 5a975974-9cac-4fae-9d7c-de3bd084d804.

I hadn't come around to enable the above settings with verifier. But will do it now. For what it's worth, a new V2 log is in the folder.

A question on the running verifier. When checking which drivers, should I continue to check all non-microsoft ones?

iorx · Jul 27, 2023

I had to work a little bit. Have had 2 or 3 BSODs in a row. It was stable for almost 1.5 day before that. What's different is that I got more stuff running while working. RDCman (sysinterals), OpenVPN with an active tunnel and Edge Dev) is what I can see is different from how I've used the machine when it's not BSODing. Last 1.5 days I've mostly worked in Office, Outlook and Teams.

Code:

Verifier Flags: 0x03bfefbb

  Standard Flags:

    [X] 0x00000001 Special pool.
    [X] 0x00000002 Force IRQL checking.
    [X] 0x00000008 Pool tracking.
    [X] 0x00000010 I/O verification.
    [X] 0x00000020 Deadlock detection.
    [X] 0x00000080 DMA checking.
    [X] 0x00000100 Security checks.
    [X] 0x00000800 Miscellaneous checks.
    [X] 0x00020000 DDI compliance checking.

  Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [X] 0x00000200 Force pending I/O requests.
    [X] 0x00000400 IRP logging.
    [X] 0x00002000 Invariant MDL checking for stack.
    [X] 0x00004000 Invariant MDL checking for driver.
    [X] 0x00008000 Power framework delay fuzzing.
    [X] 0x00010000 Port/miniport interface checking.
    [X] 0x00040000 Systematic low resources simulation.
    [X] 0x00080000 DDI compliance checking (additional).
    [X] 0x00200000 NDIS/WIFI verification.
    [X] 0x00800000 Kernel synchronization delay fuzzing.
    [X] 0x01000000 VM switch verification.
    [X] 0x02000000 Code integrity checks.

  Internal Flags:

    [X] 0x00100000 Extended Verifier flags (internal).

    [X] Indicates flag is enabled.

  Boot Mode:

    Persistent

  Rules:

    All rules are using default settings

  Extensions:

    wdm: rules.all
    ndis: rules.default

  Verified Drivers:

    spvdbus.sys
    npcap.sys
    ovpn-dco.sys
    wintun.sys
    tap0901.sys
    igdkmdn64.sys
    iaisp64.sys
    tbtbusdrv.sys
    ialpss2_i2c_tgl.sys
    intelthcbase.sys
    netwtw10.sys
    teedriverw10x64.sys
    ialpss2_uart2_tgl.sys
    intcaudiobus.sys
    ialpss2_gpio2_tgl.sys
    nvvad64v.sys
    nvmoduletracker.sys
    nvvhci.sys
    iactrllogic64.sys
    intcoed.sys
    ov5693.sys
    ov13858.sys
    vd55g0.sys
    rtkvhd64.sys
    intcusb.sys
    intcbtau.sys
    ibtusb.sys
    dump_dumpstorport.sys
    dump_stornvme.sys
    dump_dumpfve.sys
    iacamera64.sys
    spvve.sys
    librehardwaremonitor.sys
    ndis.sys
    netadaptercx.sys
    mbbcx.sys
    wificx.sys
    wdiwifi.sys

And a new V2 log in the folder.

iorx · Jul 27, 2023

Whoho! That made it BSOD on startup. Then followed by repeated fails on start up until I ended up in repair and was offered to go back to a restore point. Accepted that and it booted into Windows again. But got lots of strange error when it tried starting UWP-apps, like the Terminal and Store...

3a) New file in folder MSP8-(2023-07-27_22-43-10).zip
3b)

Code:

>bcdedit /enum {badmemory}

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

>bcdedit /deletevalue {badmemory} badmemorylist
The operation completed successfully.

>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
isolatedcontext         Yes

zbook · Jul 28, 2023

Please post new share links for:

1) V2
2) Tuneup plus

iorx · Jul 28, 2023

New files here now: sp8-bsod

zbook · Jul 28, 2023

Some testing may be repeated.

There are 8 RAM modules.

Please remove all modules so that they are reseated and test 4 modules at a time in the same DIMM.

Make sure that there are 8 or more passes.

It sometimes takes passes into the 20's to find malfunctioning RAM.

Take pictures > post images or share links into this thread.

Memtest86+ | The Open-Source Memory Testing Tool

Memtest86+ is an advanced, free, open-source, stand-alone memory tester for 32- and 64-bit computers (UEFI & BIOS supported)

memtest.org

MemTest86+ - Test RAM

Test your RAM with MemTest 86+

www.tenforums.com

iorx · Jul 28, 2023

On replacing memory modules, I need to quote HAL the AI in the movie "2001: A Space Odyssey (1968)", "Sorry Dave, can't do that"

Surface Pro 8 models come with onboard dual-channel 4267 MHz LPDDR4x memory and there is no additional RAM slot for expansion. So make sure you purchase a Surface Pro 8 model with the right amount of memory (8GB, 16GB, and 32GB).

MEMtest86, it had a run before and passed 9 passes. I better let it run for longer than that then...

Last BSOD... (no logs uploaded for this one)

Code:

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.218 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\072823-18546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\symsrv*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\symsrv*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 22621 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Kernel base = 0xfffff800`6a400000 PsLoadedModuleList = 0xfffff800`6b013100
Debug session time: Fri Jul 28 12:50:39.958 2023 (UTC + 2:00)
System Uptime: 0 days 13:56:54.178
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
.
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000003d`ceee3018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`6a830c00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8005`385e6310=000000000000003b
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffffc27f9689286, Address of the instruction which caused the BugCheck
Arg3: ffff8005385e6c60, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1968

    Key  : Analysis.Elapsed.mSec
    Value: 13788

    Key  : Analysis.IO.Other.Mb
    Value: 3

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 15

    Key  : Analysis.Init.CPU.mSec
    Value: 218

    Key  : Analysis.Init.Elapsed.mSec
    Value: 12179

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 113

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: 0x3B_C000001D_win32kbase!SURFMEM::_SURFMEM

    Key  : Failure.Hash
    Value: {dfaffe8e-52d0-cf38-2ccb-d60eeb722c8e}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.1928


BUGCHECK_CODE:  3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffffc27f9689286

BUGCHECK_P3: ffff8005385e6c60

BUGCHECK_P4: 0

FILE_IN_CAB:  072823-18546-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


CONTEXT:  ffff8005385e6c60 -- (.cxr 0xffff8005385e6c60)
rax=fffff80081c35a20 rbx=fffff80081c35a20 rcx=ffff8005385e77b0
rdx=0000000000000001 rsi=ffff8005385e77b0 rdi=0000000000000000
rip=fffffc27f9689286 rsp=ffff8005385e7680 rbp=ffff8005385e7709
 r8=0000000000000000  r9=0000000000000000 r10=fffff8006a6d3840
r11=ffff8005385e7740 r12=0000000000000000 r13=0000000000000001
r14=ffff8005385e7950 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
win32kbase!SURFMEM::~SURFMEM+0x56:
fffffc27`f9689286 0f8400030000    je      win32kbase!SURFMEM::~SURFMEM+0x35c (fffffc27`f968958c) [br=0]
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  OUTLOOK.EXE

STACK_TEXT: 
ffff8005`385e7680 fffffc27`f96bf36e     : ffff998a`7083c030 ffff998a`7083c030 ffffaa07`4b111b20 00000031`00000030 : win32kbase!SURFMEM::~SURFMEM+0x56
ffff8005`385e7770 fffffc27`f960e0ca     : ffffaa07`4b111b40 ffff8005`6d657347 00000000`00000000 fffffc27`f968ba5e : win32kbase!hbmCreateDriverSurface+0x5a
ffff8005`385e77d0 fffffc27`f9ac3c56     : 00000000`00000000 00000000`80001fc2 ffff998a`6613f020 00000000`00000000 : win32kbase!EngCreateDeviceBitmap+0x2a
ffff8005`385e7820 fffffc27`fa71c9dd     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffaa07`42308a00 : win32k!EngCreateDeviceBitmap+0x16
ffff8005`385e7850 fffffc27`fa708aca     : 00000031`00000030 ffff998a`7083c030 ffff8005`385e79e0 fffff800`6a87adb3 : cdd!CddBitmap::CreateGDIBitmap+0x13ef5
ffff8005`385e78b0 fffffc27`fa707a9c     : 00000031`00000030 ffffaa07`3ca5a920 ffffaa07`3ca5a920 fffff800`6a65ed44 : cdd!CddBitmapHw::InitBitmap+0x10a
ffff8005`385e78e0 fffffc27`fa5d82be     : 00000000`00000000 00000031`00000030 00000000`00000000 fffffc27`f9658f80 : cdd!DrvCreateDeviceBitmapEx+0x24c
ffff8005`385e7a30 fffffc27`fa3ce902     : ffff998a`661d6890 00000000`00000001 00000000`00000006 00000000`00000002 : win32kfull!MulCreateDeviceBitmapEx+0x31e
ffff8005`385e7ae0 fffffc27`fa5d70bd     : fffff800`84183000 00000000`00000030 00000000`00000031 000045f9`00000000 : win32kfull!CreateCompatibleSurface+0x216
ffff8005`385e7bf0 fffffc27`fa5eac46     : ffffaa07`2b3c8080 fffffc27`f9638d86 0000003d`ced0d3f8 ffff8005`385e7dc8 : win32kfull!GreCreateBitmapFromDxSurface+0x1d5
ffff8005`385e7d10 fffffc27`f9acaea5     : 00000000`00000000 00000000`00010010 ffff998a`8e9eb010 00000000`00000000 : win32kfull!NtGdiCreateBitmapFromDxSurface2+0x26
ffff8005`385e7d60 fffff800`6a8459e5     : ffff8005`385e7ea0 fffffc27`f9637fc9 00000000`00010010 00000000`00000020 : win32k!NtGdiCreateBitmapFromDxSurface2+0x3d
ffff8005`385e7db0 00007fff`835647d4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000003d`ced0d3d8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`835647d4


SYMBOL_NAME:  win32kbase!SURFMEM::~SURFMEM+56

MODULE_NAME: win32kbase

IMAGE_NAME:  win32kbase.sys

IMAGE_VERSION:  10.0.22621.2062

STACK_COMMAND:  .cxr 0xffff8005385e6c60 ; kb

BUCKET_ID_FUNC_OFFSET:  56

FAILURE_BUCKET_ID:  0x3B_C000001D_win32kbase!SURFMEM::_SURFMEM

OS_VERSION:  10.0.22621.1928

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {dfaffe8e-52d0-cf38-2ccb-d60eeb722c8e}

Followup:     MachineOwner
---------

zbook · Jul 28, 2023

Windows had predicted RAM failure and blocked one region (0x62057b).

iorx · Jul 29, 2023

Yes, I saw that. That is good news in my case maybe?

Code:

>bcdedit /enum {badmemory}

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

Should I update my case with Microsoft and point this out?
Is this enough to claim that the machine has problem with it's memory?
It shouldn't matter if this is in my current config or a re-imaged version of Windows, no?

Think/hope your right here that, and that we circled back to the memory.
Checking the dmp-files and the process mentioned in every they've been random. Not sure if this is relevant, what if the processes here was running with allocation over and use of the bad memory spot.
072823-18546-01.dmp PROCESS_NAME: OUTLOOK.EXE
072723-14984-01.dmp PROCESS_NAME: System
072723-15703-01.dmp PROCESS_NAME: TextInputHost.exe
072723-15234-01.dmp PROCESS_NAME: logioptionsplus_agent.exe
072223-16093-01.dmp PROCESS_NAME: explorer.exe

Other, for a test: I put in the original SSD and re-imaged with Microsoft 22H2 (Windows 11). Install went fine. Then update... there was allot of it until it was up to speed with current patches (machine and OS).
Tried working on the machine and installing stuff which I've talked about here. Hyper-V, Edge Dev, RDCMan and more. I worked a couple of hours on it but it didn't BSOD (was rather sure that I wouldn't get one). Was not able to fill up memory and put a similar workload on the machine (note. Re-installing a machine which HardwareID is AzureAD/intune joined got really strange when I later switched back to my current config, SSD. Needed to reestablish and relogon both account and machine into intune/azure again. The new install somehow replaced the current join as it joined "again").

Brgs

zbook · Jul 29, 2023

When possible post a new V2 share link into the newest post.

Update the progress with the RAM testing.

iorx · Jul 29, 2023

Do you have access to the folder link I've inserted here in previous posts?

OneDrive

Sign in to your OneDrive cloud storage and Office Online.

1drv.ms

Here it is again. There is no new V2 in there since I last posted the link.

I'll get to the memory testing part, needed the machine and haven't had the extended time slot to reach 20 passes in MEMtest. Will post when I get there.

Thank you very much this far for answering and engaging in this matter. Very much appreciated.