W11 BSOD - various events, how to debug?


  1. Posts : 17
    w10
       #1

    W11 BSOD - various events, how to debug?


    Recently my W11 (23H2) (-Pro) machine had a few times with BSOD crashes with no apparent reason, saying: “Unexpected Kernel mode trap”,
    And “System Thread Exception not handled”, and then on reboot – “… did not start properly”.
    In addition, it is very slow sometimes – sluggish program starts, gaps in response, etc.
    Also a few: "Video Scheduler internal error" crashes.
    Debugging minidump’s only one showed a possible (user program) cause, and rest are system events & exceptions.

    But now I also started getting unexpected shutdowns, with an automatic restart that fails.
    Thus I come back to my maching the next day, and it shows a BSOD with the message –
    “your machine did not start properly…”
    But I can choose “try again” and it works fine.

    I seem to get these every few days.
    Again looking at minidump(s) and events, I don’t see any apparent cause (Event code = 0000….).
    I have turned on Windows Driver Verifier.
    Both Dell and MSoft updates all installed.

    Minidumps (& WinDbg) seem to generally just show it is in the kernel, although one recent one pointed to firefox.

    Code:
    BLACKBOXWINLOGON: 1
    CUSTOMER_CRASH_COUNT:  1
    PROCESS_NAME:  SearchProtocolHost.exe
    --------- 
    BLACKBOXWINLOGON: 1
    CUSTOMER_CRASH_COUNT:  1
    PROCESS_NAME:  firefox.exe
    --------- 
    BLACKBOXWINLOGON: 1
    CUSTOMER_CRASH_COUNT:  1
    PROCESS_NAME:  System
    …
    MODULE_NAME: stornvme
    IMAGE_NAME:  stornvme.sys
    ------- 
    BLACKBOXWINLOGON: 1
    CUSTOMER_CRASH_COUNT:  1
    PROCESS_NAME:  System
    …
    IMAGE_NAME:  ntkrnlmp.exe
    --------- 
    …
    SYMBOL_NAME:  nt!KiDoubleFaultAbort+340
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    ---------
    Etc. …

    And I just got these two:
    VIDEO_SCHEDULER_INTERNAL_ERROR (119)

    Driver IRQL not less or equal
    Kfecollx64.exe

    I ran sfc, it reported some files fixed (I did not see which ones).

    What would be a good next step in debugging this?

    Log files here: https://www.dropbox.com/t/dNn62kqMkEA0jbEP

    I ran Microsoft Malware removal (Microsoft Safety scanner), it ran for 80+ hours (!) and checked 78m items, found nothing.
    I run Malwarebytes scans daily.

    W11 BSOD - various events, how to debug?-picture1.png

    Code:
    Sample Minidump:
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: ffff8089a2e40ff8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
      bit 0 : value 0 = read operation, 1 = write operation
      bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80265872227, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 1828
    
        Key  : Analysis.Elapsed.mSec
        Value: 8603
    
        Key  : Analysis.IO.Other.Mb
        Value: 0
    
        Key  : Analysis.IO.Read.Mb
        Value: 0
    
        Key  : Analysis.IO.Write.Mb
        Value: 1
    
        Key  : Analysis.Init.CPU.mSec
        Value: 375
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 4797
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 94
    
        Key  : Bugcheck.Code.LegacyAPI
        Value: 0xa
    
        Key  : Bugcheck.Code.TargetModel
        Value: 0xa
    
        Key  : Failure.Bucket
        Value: AV_VRF_KfeCo11X64!unknown_function
    
        Key  : Failure.Hash
        Value: {a8dd5be4-b28a-4e52-c33f-ed40455b8b0f}
    
        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
    
        Key  : WER.OS.Version
        Value: 10.0.22621.1
    
    
    BUGCHECK_CODE:  a
    
    BUGCHECK_P1: ffff8089a2e40ff8
    
    BUGCHECK_P2: 2
    
    BUGCHECK_P3: 1
    
    BUGCHECK_P4: fffff80265872227
    
    FILE_IN_CAB:  041524-31375-01.dmp
    
    TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b
    
    
    WRITE_ADDRESS: fffff802661344a8: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    unable to get nt!MmSpecialPagesInUse
    ffff8089a2e40ff8 
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXPNP: 1 (!blackboxpnp)
    
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  ffffa38a491bf5b0 -- (.trap 0xffffa38a491bf5b0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffa38a491bf778 rbx=0000000000000000 rcx=ffffa38a491bf900
    rdx=ffffa38a491bf900 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80265872227 rsp=ffffa38a491bf740 rbp=0000000000000000
    r8=ffff8089a2e40ff8  r9=0000000000000000 r10=0000000000000018
    r11=ffffa38a491befe0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    nt!KiAcquireQueuedSpinLockInstrumented+0x59:
    fffff802`65872227 488716          xchg    rdx,qword ptr [rsi] ds:00000000`00000000=????????????????
    Resetting default scope
    
    STACK_TEXT:  
    ffffa38a`491bf468 fffff802`65846269     : 00000000`0000000a ffff8089`a2e40ff8 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    ffffa38a`491bf470 fffff802`65841705     : ffffa38a`491b9000 ffffa38a`491c0000 00000000`00000000 ffffa38a`491bf540 : nt!KiBugCheckDispatch+0x69
    ffffa38a`491bf5b0 fffff802`65872227     : ffff8089`a2e40ff8 fffff802`65704902 00000000`00000004 ffffa38a`491bf7b0 : nt!KiPageFault+0x485
    ffffa38a`491bf740 fffff802`658625d5     : ffff8088`fa6bd710 ffffa38a`491bf900 ffff8088`fa6bd710 ffff8088`fa6bd6f0 : nt!KiAcquireQueuedSpinLockInstrumented+0x59
    ffffa38a`491bf780 fffff802`659f8c77     : fffff802`65ed6271 ffff8088`fa6aec70 00000000`00000000 fffff802`65eebdfb : nt!KeAcquireInStackQueuedSpinLock+0x152465
    ffffa38a`491bf7b0 fffff802`65eeb247     : ffff8088`fa6aec70 ffffa38a`491bf919 ffff8089`a2e40ff8 ffffa38a`491bf900 : nt!DifKeAcquireInStackQueuedSpinLockWrapper+0xc7
    ffffa38a`491bf800 fffff802`65ed6271     : 00000000`00000000 ffff8089`a2e40f80 fffff802`bb8c2345 ffffa38a`491bf8d0 : nt!VerifierKeAcquireInStackQueuedSpinLockCommon+0x67
    ffffa38a`491bf830 fffff802`bb8c2385     : 00000000`00000000 ffffa38a`491bf919 ffff8089`a2e40f80 00000000`0a1dee56 : nt!VerifierKeAcquireInStackQueuedSpinLock+0x11
    ffffa38a`491bf860 00000000`00000000     : ffffa38a`491bf919 ffff8089`a2e40f80 00000000`0a1dee56 00000000`00000000 : KfeCo11X64+0x2385
    
    
    SYMBOL_NAME:  KfeCo11X64+2385
    
    MODULE_NAME: KfeCo11X64
    
    IMAGE_NAME:  KfeCo11X64.sys
    
    STACK_COMMAND:  .cxr; .ecxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  2385
    
    FAILURE_BUCKET_ID:  AV_VRF_KfeCo11X64!unknown_function
    
    OS_VERSION:  10.0.22621.1
    
    BUILDLAB_STR:  ni_release
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {a8dd5be4-b28a-4e52-c33f-ed40455b8b0f}
    
    Followup:     MachineOwner
      My Computer


  2. Posts : 41,499
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Which link was used for Windows Driver Verifier test settings?

    When was the second RAM module installed?

    What were the reasons for opening the thread in TF instead of EF?




    1) Run Tuneup plus > post a share link

    https://www.tenforums.com/attachment...p_plus_log.bat

    Batch files for use in BSOD debugging

    Batch files for use in BSOD debugging



    2) Turn off WDV:

    Enable and Disable Driver Verifier in Windows 10



    3) Uninstall Bitdefender and Malwarebytes using the applicable uninstall tools:

    Using the Uninstall Tool to remove Bitdefender Endpoint Security Tools

    [KB146] Uninstallers (removal tools) for common Windows antivirus software



    4) Make sure that Microsoft defender is on



    5) Perform Windows and Microsoft defender updates



    6) Uninstall or uninstall and reinstall Acronis software



    7) Uninstall or uninstall and reinstall:

    kfecosvc KfeCoSvc c:\windows\system32\drivers\rivetnetworks\killer\kfeco11x64.sys



    8) Uninstall and reinstall the Nvidia GPU drivers nvlddmkm.sys using DDU / Dell website

    Display Driver Uninstaller: How to use | Tutorials

    Display Driver Uninstaller (DDU) download latest version 18.0.7.6 | Wagnardsoft

    https://www.dell.com/support/home/en...esktop/drivers



    9) Create a new restore point:

    Create System Restore Point in Windows 11 Tutorial | Windows 11 Forum



    10) Run HD Sentinel (trial version) (all drives)
    https://www.hdsentinel.com/
    Post images for results on these tabs:
    a) Overview
    b) Temperature
    c) SMART



    11) Restart WDV with these customized tests:


    Code:
        
    
        [ ] 0x00000010 I/O verification.
        [ ] 0x00000200 Force pending I/O requests.
        [ ] 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.



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

    verifier /querysettings

    Post a share link.

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






    Code:
    Name	NVIDIA GeForce GTX 1650 SUPER
    PNP Device ID	PCI\VEN_10DE&DEV_2187&SUBSYS_13651028&REV_A1\4&209E2803&0&0008
    Adapter Type	NVIDIA GeForce GTX 1650 SUPER, NVIDIA compatible
    Adapter Description	NVIDIA GeForce GTX 1650 SUPER
    Adapter RAM	(1,048,576) bytes
    Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nvdd.inf_amd64_f0470300ded10cee\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdd.inf_amd64_f0470300ded10cee\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdd.inf_amd64_f0470300ded10cee\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nvdd.inf_amd64_f0470300ded10cee\nvldumdx.dll
    Driver Version	31.0.15.5168
    INF File	oem94.inf (Section047 section)
    Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NVDD.INF_AMD64_F0470300DED10CEE\NVLDDMKM.SYS (31.0.15.5168, 57.19 MB (59,965,552 bytes), 3/5/2024 4:41 PM)



    KfeCo11X64.sys Wed Jul 12 00:15:08 2023 (64AE36DC)

    nvlddmkm.sys Tue Feb 27 00:10:07 2024 (65DD7CBF)

    fltsrv.sys Wed Jan 25 01:51:52 2023 (63D0DF98)
    Last edited by zbook; 1 Week Ago at 23:54.
      My Computer


  3. Posts : 17
    w10
    Thread Starter
       #3

    Thanks for the reply and note.
    Lots of items, will do.

    ** Which link was used for Windows Driver Verifier test settings?
    Search verifier, open app "Windows Verifier Manager"
    Choose custom,
    enable everything except {Randomized low resources simulation , DDI Compliance Checking)
    as per: "https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983"
    (So I have already run Verifier as you suggest, except for DDI...)

    ** When was the second RAM module installed?
    About two months ago, Mother-board replacement by Dell, system would not boot.

    ** What were the reasons for opening the thread in TF instead of EF?
    What is EF? I was just familiar with TF.

    ** what is the code block and listing at the end of your post, something else to check?
    ... KfeCo11X64.sys , nvlddmkm.sys, fltsrv.sys
      My Computer


  4. Posts : 41,499
    windows 10 professional version 1607 build 14393.969 64 bit
       #4

    guthrie said:
    Thanks for the reply and note.
    Lots of items, will do.

    ** Which link was used for Windows Driver Verifier test settings?
    Search verifier, open app "Windows Verifier Manager"
    Choose custom,
    enable everything except {Randomized low resources simulation , DDI Compliance Checking)
    as per: "https://answers.microsoft.com/en-us/windows/forum/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983"
    (So I have already run Verifier as you suggest, except for DDI...)

    ** When was the second RAM module installed?
    About two months ago, Mother-board replacement by Dell, system would not boot.

    ** What were the reasons for opening the thread in TF instead of EF?
    What is EF? I was just familiar with TF.

    ** what is the code block and listing at the end of your post, something else to check?
    ... KfeCo11X64.sys , nvlddmkm.sys, fltsrv.sys


    Did Dell select the new RAM?

    If not, how was compatibility checked?


    TF = Ten Forums

    EF = Eleven Forum Windows 11 Forum


    The code block and listing allow me to keep track of computer problems, drivers, etc.
      My Computer


  5. Posts : 17
    w10
    Thread Starter
       #5

    Tuneup_plus - hangs


    I downloaded teh tuneup_plus_log.bat file, and ran it - it hangs on the DISM operation, 62.3% - so I killed it and restarted, same thing.
    W11 BSOD - various events, how to debug?-p1.png

    - - - Updated - - -

    Yes, the entire repair/replacement was Dell under warranty.

    Is EF a better place to post this type of thing?
    Since the log script is failing, what would be the right way to run DISM manually (What parameters?).

    - - - Updated - - -

    Crashed again today - since the tuneup_plus_log failed, I tried running DISM myself - it hangs, just as it did in the script.
    ??

    W11 BSOD - various events, how to debug?-p1.png

    - - - Updated - - -

    The log file: Windows/loga/dism/dism.txt:
    Code:
    2024-04-27 17:21:44, Info                  DISM   PID=15804 TID=11384 Scratch directory set to 'C:\Users\guthr\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir
    2024-04-27 17:21:44, Info                  DISM   PID=15804 TID=11384 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct
    2024-04-27 17:21:44, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2024-04-27 17:21:44, Info                  DISM   PID=15804 TID=11384 Successfully loaded the ImageSession at "C:\Windows\system32\Dism" - CDISMManager::LoadLocalImageSession
    2024-04-27 17:21:44, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2024-04-27 17:21:44, Info                  DISM   DISM Provider Store: PID=15804 TID=11384 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2024-04-27 17:21:44, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2024-04-27 17:21:44, Info                  DISM   DISM Manager: PID=15804 TID=11384 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2024-04-27 17:21:44, Info                  DISM   DISM.EXE: 
    2024-04-27 17:21:44, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2024-04-27 17:21:44, Info                  DISM   DISM.EXE: 
    2024-04-27 17:21:44, Info                  DISM   DISM.EXE: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=20
    2024-04-27 17:21:44, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.22621.2792
    2024-04-27 17:21:44, Info                  DISM   DISM.EXE: Executing command line: "C:\Windows\system32\Dism.exe" /Online /Cleanup-Image /RestoreHealth
    2024-04-27 17:21:44, Info                  DISM   DISM Manager: PID=15804 TID=11384 physical location path: C:\ - CDISMManager::CreateImageSession
    2024-04-27 17:21:44, Info                  DISM   DISM Manager: PID=15804 TID=11384 Event name for current DISM session is Global\{DC09A148-6F9D-4632-8B28-B16AB3F317E1} - CDISMManager::CheckSessionAndLock
    2024-04-27 17:21:44, Info                  DISM   DISM Manager: PID=15804 TID=11384 Create session event 0x260 for current DISM session and event name is Global\{DC09A148-6F9D-4632-8B28-B16AB3F317E1}  - CDISMManager::CheckSessionAndLock
    2024-04-27 17:21:44, Info                  DISM   DISM Manager: PID=15804 TID=11384 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2024-04-27 17:21:44, Info                  DISM   DISM Manager: PID=15804 TID=11384 No Sandbox was created, DISM running in-place. - CDISMManager::CreateImageSessionFromLocation
    2024-04-27 17:21:45, Info                  DISM   DISM Manager: PID=15804 TID=11384 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadRemoteImageSession
    2024-04-27 17:21:45, Info                  DISM   DISM Image Session: PID=19120 TID=3044 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2024-04-27 17:21:45, Info                  DISM   DISM OS Provider: PID=19120 TID=3044 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect
    2024-04-27 17:21:45, Info                  DISM   DISM OS Provider: PID=19120 TID=3044 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect
    2024-04-27 17:21:45, Info                  DISM   DISM Provider Store: PID=19120 TID=3044 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2024-04-27 17:21:45, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2024-04-27 17:21:45, Info                  DISM   DISM Provider Store: PID=19120 TID=3044 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2024-04-27 17:21:45, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2024-04-27 17:21:45, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2024-04-27 17:21:45, Info                  DISM   DISM Manager: PID=15804 TID=11384 Image session successfully loaded from location: C:\Windows\System32\Dism - CDISMManager::CreateImageSession
    2024-04-27 17:21:45, Info                  DISM   DISM.EXE: Target image information: OS Version=10.0.22631.3527, Image architecture=amd64
    2024-04-27 17:21:45, Info                  DISM   DISM.EXE: Image session version: 10.0.22621.1
    2024-04-27 17:21:45, Info                  DISM   DISM Transmog Provider: PID=19120 TID=3044 Current image session is [ONLINE] - CTransmogManager::GetMode
    2024-04-27 17:21:45, Info                  DISM   DISM Transmog Provider: PID=19120 TID=3044 Audit Mode: [No] - CTransmogManager::Initialize
    2024-04-27 17:21:45, Info                  DISM   DISM Transmog Provider: PID=19120 TID=3044 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType
    2024-04-27 17:21:45, Info                  DISM   DISM Transmog Provider: PID=19120 TID=3044 Product Type: [WinNT] - CTransmogManager::Initialize
    2024-04-27 17:21:45, Info                  DISM   DISM Transmog Provider: PID=19120 TID=3044 Product Type ServerNT : [No] - CTransmogManager::Initialize
    2024-04-27 17:21:45, Info                  CSI    00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.3522_none_e93c247a42e7cbb6\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2024-04-27 17:21:45, Info                  CSI    00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.3522_none_e93c247a42e7cbb6\wcp.dll' : got STATUS_SUCCESS
    2024-04-27 17:21:45, Info                  DISM   DISM Driver Manager: PID=19120 TID=3044 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2024-04-27 17:21:45, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2024-04-27 17:21:45, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\CBS\CBS.log - CDISMPackageManager::Initialize
    2024-04-27 17:21:46, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 Loaded servicing stack for online use. - CDISMPackageManager::CreateCbsSession
    2024-04-27 17:21:46, Info                  CSI    00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.3522_none_e93c247a42e7cbb6\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
    2024-04-27 17:21:46, Info                  CSI    00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.3522_none_e93c247a42e7cbb6\wcp.dll' : got STATUS_SUCCESS
    2024-04-27 17:21:46, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2024-04-27 17:21:46, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2024-04-27 17:21:46, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2024-04-27 17:21:46, Info                  DISM   DISM Package Manager: PID=19120 TID=3044 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
    -- Hangs here...
      My Computer


  6. Posts : 41,499
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    Please allow Tuneup plus to run overnight while sleeping.

    If there are any problems then the following evening boot into safe mode with wifi or networking to run Tuneup plus.


    Boot to Safe Mode in Windows 11 Tutorial | Windows 11 Forum


    For any BSOD post a new V2 share link.


    When available update the progress with each step in post #2.
      My Computer


  7. Posts : 17
    w10
    Thread Starter
       #7

    DISM repair for BSOD fails


    I'll have to research this a bit...

    W11 BSOD - various events, how to debug?-p1.png
      My Computer


  8. Posts : 41,499
    windows 10 professional version 1607 build 14393.969 64 bit
       #8

    Perform steps 1 - 10.

    Then find a flash drive that you can format (> or = 8 GB).

    Create a bootable Windows 11 Media Creation Tool (MCT) (Windows 11 iso).

    Download Official Windows 11 ISO file from Microsoft Tutorial | Windows 11 Forum

    https://www.microsoft.com/software-download/windows11



    Run Tuneup plus as per post #6.
      My Computer


  9. Posts : 17
    w10
    Thread Starter
       #9

    BSOD repair


    I did download a windows image, and then did re-run the tune_up_plus log program, (below).
    ( I did not re-run in safe mode.)

    But think I could try the MSoft solution to the reported DISM "source files not found" problem as I now have the downloaded image to use with it.

    Yes?

    --------------------------------------------------------------
    Microsoft Windows 11 Pro Version 23H2 (OS Build 22631.3527)

    ==================================================================

    Started on Mon 04/29/2024 at 8:31:09.21

    [SFC /ScanNow]

    Beginning system scan. This process will take some time.

    Results:

    Windows Resource Protection did not find any integrity violations.

    ==================================================================

    Started on Mon 04/29/2024 at 8:39:49.05

    [DISM /online /cleanup-image /ScanHealth]

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22631.3527

    The component store is repairable.

    The operation completed successfully.

    ==================================================================

    Started on Mon 04/29/2024 at 8:49:13.40

    [DISM /online /cleanup-image /RestoreHealth]

    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792

    Image Version: 10.0.22631.3527

    Error: 0x800f081f

    The source files could not be found.

    Use the "Source" option to specify the location of the files that are required to restore the feature.
    For more information on specifying a source location, see https://go.microsoft.com/fwlink/?LinkId=243077.
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    ==================================================================

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

    Windows Resource Protection did not find any integrity violations.

    ==================================================================

    Started on Mon 04/29/2024 at 11:13:27.03

    [ChkDsk /Scan]

    The type of the file system is NTFS.
    Volume label is System.

    Stage 1: Examining basic file system structure ...
    1595392 file records processed.
    File verification completed.
    Phase duration (File record verification): 22.02 seconds.
    24912 large file records processed.
    Phase duration (Orphan file record recovery): 8.50 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 0.68 milliseconds.

    Stage 2: Examining file name linkage ...
    602520 reparse records processed.
    2076356 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 50.35 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 18.24 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 1.92 milliseconds.
    602520 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 773.22 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 42.97 milliseconds.
    240483 data files processed.
    Phase duration (Data attribute verification): 0.87 milliseconds.
    CHKDSK is verifying Usn Journal...
    36814184 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 369.61 milliseconds.

    Windows has scanned the file system and found no problems.

    No further action is required.

    981260287 KB total disk space.
    338539948 KB in 1111280 files.
    924052 KB in 240484 indexes.
    0 KB in bad sectors.
    1745411 KB in use by the system.
    65536 KB occupied by the log file.
    640050876 KB available on disk.

    4096 bytes in each allocation unit.
    245315071 total allocation units on disk.
    160012719 allocation units available on disk.
    Total duration: 1.53 minutes (91828 ms).

    ==================================================================

    Started on Mon 04/29/2024 at 11:15:52.29

    AutoReboot

    TRUE

    ==================================================================

    [Set AutoReboot = False]

    Updating property(s) of '\\PCGRG\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition3"'
    Property(s) update successful.
    ==================================================================

    AutoReboot

    FALSE

    ==================================================================

    DebugInfoType

    7

    ==================================================================

    [Set DebugInfoType = 7]

    Updating property(s) of '\\PCGRG\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk2\\Partition3"'
    Property(s) update successful.
    ==================================================================

    DebugInfoType

    7

    ==================================================================

    [WMIC PageFile list]

    AllocatedBaseSize=32768
    CurrentUsage=585
    Description=C:\pagefile.sys
    InstallDate=20240428112250.111135-300
    Name=C:\pagefile.sys
    PeakUsage=1660
    Status=
    TempPageFile=FALSE

    ==================================================================

    AutomaticManagedPagefile

    TRUE

    ==================================================================

    [Set AutomaticManagedPagefile = True]

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

    AutomaticManagedPagefile

    TRUE

    ==================================================================

    [BcdEdit /enum {badmemory}]

    RAM Defects
    -----------
    identifier {badmemory}

    ==================================================================

    Finished on Mon 04/29/2024 at 11:16:23.06
    It took 165 minutes and 13 seconds to complete the operations.
      My Computer


  10. Posts : 41,499
    windows 10 professional version 1607 build 14393.969 64 bit
       #10

    When available, update the progress with each step in post #2.

    Plan to restart WDV.


    When WDV testing has completed plan to troubleshoot 0x800f081f
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:59.
Find Us




Windows 10 Forums