BSOD 3 times a week while idle or active

Page 1 of 2 12 LastLast

  1. Posts : 7
    Windows 11
       #1

    BSOD 3 times a week while idle or active


    Cannot seem to figure out any pattern to this at all; BSODS happens 3-4 times a week. Sometimes I see errors that microsoft edge is taking too much memory, other times i see graphical glitches/artifacts/mostly black screen, other times my steam webhelper just starts creating multiple instances of itself until the system runs out of memory. I got up this morning and BSOD was in the process as I was approaching the PC. Any help would be much appreciated.

    Logs: BIGBOY-(2024-03-19_05-53-58).zip - Google Drive
      My Computer


  2. Posts : 108
    Windows 10
       #2

    The MS Edge or any browser taking too much memory is a classic, it could be for insufficient pagefile.sys size. Unless you've limited it, it could be that the OS partition or disk is nearly full. In such case I wouldn't say that it could not cause the other issues, but browsers tend to do exactly that. Counter-intuitively, they are a case in which more RAM calls for more pagefile, more or less because browsers/pages tend to ask for much more RAM than they actually need and, wisely, the OS either assigns it to the pagefile or evicts it soon to the pagefile for lack of use. The more RAM, the more evictable contents.
      My Computer


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

    Please make sure that share links are available without sign in.
      My Computer


  4. Posts : 7
    Windows 11
    Thread Starter
       #4

    JLArranz said:
    The MS Edge or any browser taking too much memory is a classic, it could be for insufficient pagefile.sys size. Unless you've limited it, it could be that the OS partition or disk is nearly full. In such case I wouldn't say that it could not cause the other issues, but browsers tend to do exactly that. Counter-intuitively, they are a case in which more RAM calls for more pagefile, more or less because browsers/pages tend to ask for much more RAM than they actually need and, wisely, the OS either assigns it to the pagefile or evicts it soon to the pagefile for lack of use. The more RAM, the more evictable contents.
    Thanks for the suggestion. I have 1 drive one partition thats 2TB and its 90% empty. Also 32GB of ram. I monitor edge memory consumption when Im using and it never gets passed a 3 Gbs that I have seen. Hard to believe it just eats through all available memory.

    - - - Updated - - -

    zbook said:
    Please make sure that share links are available without sign in.
    I just double checked in incognito mode. I was able to download without sign in.
      My Computer


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

    Please perform the following steps: (in sequence)


    1) Run Tune up plus > post a share link

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

    Batch files for use in BSOD debugging

    Batch files for use in BSOD debugging



    2) Run HD Tune (free or trial version)
    HD Tune website
    Post images or share links for results on these tabs:
    a) Health
    b) Benchmark
    c) Full errror scan




    3) Run Sea Tools for Windows Long Generic test > post a share link

    https://www.seagate.com/content/dam/...00869623_B.pdf

    https://www.seagate.com/content/dam/...sInstaller.exe



    4) The BIOS Version/Date American Megatrends International, LLC. 1.60, 2023-05-30

    Upgrade the BIOS: 1.60 > 1E

    MAG B650 TOMAHAWK WIFI
      My Computer


  6. Posts : 7
    Windows 11
    Thread Starter
       #6

    zbook said:
    Please perform the following steps: (in sequence)


    1) Run Tune up plus > post a share link

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

    Batch files for use in BSOD debugging

    Batch files for use in BSOD debugging



    2) Run HD Tune (free or trial version)
    HD Tune website
    Post images or share links for results on these tabs:
    a) Health
    b) Benchmark
    c) Full errror scan




    3) Run Sea Tools for Windows Long Generic test > post a share link

    https://www.seagate.com/content/dam/...00869623_B.pdf

    https://www.seagate.com/content/dam/...sInstaller.exe



    4) The BIOS Version/Date American Megatrends International, LLC. 1.60, 2023-05-30

    Upgrade the BIOS: 1.60 > 1E

    MAG B650 TOMAHAWK WIFI

    1. Tune Up results:
    Code:
     
    Microsoft Windows 11 Pro  Version 23H2 (OS Build 22631.3296)
      
    ==================================================================
    
        Started on 2024-03-20 at 18:04:00.87 
    	
            [SFC /ScanNow] 
    	
    Beginning system scan.  This process will take some time.
    
    Results: 
     
    Windows Resource Protection did not find any integrity violations.
     
    ==================================================================
    
        Started on 2024-03-20 at 18:04:46.44 
    
            [DISM /online /cleanup-image /ScanHealth] 
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792
    
    Image Version: 10.0.22631.3296 
     
    No component store corruption detected.
    
    The operation completed successfully. 
     
    ==================================================================
    
        Started on 2024-03-20 at 18:05:43.43 
    
            [DISM /online /cleanup-image /RestoreHealth] 
    
    Deployment Image Servicing and Management tool
    Version: 10.0.22621.2792
    
    Image Version: 10.0.22631.3296 
     
    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 2024-03-20 at 18:06:40.41 
    
            [ChkDsk /Scan]  
     
    The type of the file system is NTFS.
     
    Stage 1: Examining basic file system structure ... 
    486912 file records processed.                                                        
    File verification completed.
    Phase duration (File record verification): 2.86 seconds.
    14191 large file records processed.                                   
    Phase duration (Orphan file record recovery): 5.98 milliseconds.
    0 bad file records processed.                                     
    Phase duration (Bad file record checking): 0.02 milliseconds.
     
    Stage 2: Examining file name linkage ... 
    882 reparse records processed.                                      
    657474 index entries processed.                                                       
    Index verification completed.
    Phase duration (Index verification): 6.28 seconds.
    0 unindexed files scanned.                                        
    Phase duration (Orphan reconnection): 368.09 milliseconds.
    0 unindexed files recovered to lost and found.                    
    Phase duration (Orphan recovery to lost and found): 0.07 milliseconds.
    882 reparse records processed.                                      
    Phase duration (Reparse point and Object ID verification): 2.57 milliseconds.
     
    Stage 3: Examining security descriptors ... 
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 47.05 milliseconds.
    85282 data files processed.                                           
    Phase duration (Data attribute verification): 0.03 milliseconds.
    CHKDSK is verifying Usn Journal...
    41776128 USN bytes processed.                                                           
    Usn Journal verification completed.
    Phase duration (USN journal verification): 70.10 milliseconds.
    
    Windows has scanned the file system and found no problems.
    
    No further action is required.
     
    1952614399 KB total disk space. 
    689589440 KB in 318060 files.
    220636 KB in 85283 indexes.
    0 KB in bad sectors.
    662659 KB in use by the system.
    65536 KB occupied by the log file.
    1262141664 KB available on disk.
     
    4096 bytes in each allocation unit. 
    488153599 total allocation units on disk.
    315535416 allocation units available on disk.
    Total duration: 9.63 seconds (9639 ms).
     
    ==================================================================
     
        Started on 2024-03-20 at 18:06:58.34 
     
    AutoReboot   
     
    FALSE       
     
    ==================================================================
     
            [Set AutoReboot = False] 
     
    Updating property(s) of '\\BIGBOY\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
    Property(s) update successful.
    ==================================================================
     
    AutoReboot   
     
    FALSE       
     
    ==================================================================
     
    DebugInfoType   
     
    7              
     
    ==================================================================
    
            [Set DebugInfoType = 7]
    
    Updating property(s) of '\\BIGBOY\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 11 Pro|C:\\Windows|\\Device\\Harddisk0\\Partition3"'
    Property(s) update successful.
    ==================================================================
     
    DebugInfoType   
     
    7              
     
    ==================================================================
    
            [WMIC PageFile list]
    
    AllocatedBaseSize=98304
    CurrentUsage=122
    Description=C:\pagefile.sys
    InstallDate=20220507003614.583979-240
    Name=C:\pagefile.sys
    PeakUsage=291
    Status=
    TempPageFile=FALSE
     
    ==================================================================
     
    AutomaticManagedPagefile   
     
    TRUE                      
     
    ==================================================================
    
            [Set AutomaticManagedPagefile = True]
    
    Updating property(s) of '\\BIGBOY\ROOT\CIMV2:Win32_ComputerSystem.Name="BIGBOY"'
    Property(s) update successful.
    ==================================================================
     
    AutomaticManagedPagefile   
     
    TRUE                      
     
    ==================================================================
    
            [BcdEdit /enum {badmemory}]
    
    RAM Defects
    -----------
    identifier              {badmemory}
     
    ==================================================================
    
        Finished on 2024-03-20 at 18:06:59.05
        It took 2 minutes and 59 seconds to complete the operations.
    2. HD Tune results:

    BSOD 3 times a week while idle or active-benchmark.pngBSOD 3 times a week while idle or active-error-scan.pngBSOD 3 times a week while idle or active-health.png

    3. Sea Tool results:
    BSOD 3 times a week while idle or active-sea-tool.png

    4. Bios:
    BSOD 3 times a week while idle or active-bios-version.png


    Thanks for taking a look.
    Last edited by Brink; 22 Mar 2024 at 11:31. Reason: code box
      My Computer


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

    Please run HD Sentinel (trial version) > post images or share links for results on these tabs:
    Hard Disk Sentinel - HDD health and temperature monitoring
    a) Overview
    b) Temperature
    c) SMART


    Monitor the computer using reliability monitor > for any BSOD post a new V2 share link into the newest post

    View Reliability History in Windows 11 Tutorial | Windows 11 Forum

    Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using
      My Computer


  8. Posts : 7
    Windows 11
    Thread Starter
       #8

    Reliability and Sentinel Report


    zbook said:
    Please run HD Sentinel (trial version) > post images or share links for results on these tabs:
    Hard Disk Sentinel - HDD health and temperature monitoring
    a) Overview
    b) Temperature
    c) SMART


    Monitor the computer using reliability monitor > for any BSOD post a new V2 share link into the newest post

    View Reliability History in Windows 11 Tutorial | Windows 11 Forum

    Reliability Monitor is the Best Windows Troubleshooting Tool You Aren't Using
    Code:
      -- General Information --
    
        Application Information
       -------------------------
        Installed Version  . . . . . . . . . . . . . . . : Hard Disk Sentinel 6.20 PRO
        Registered To  . . . . . . . . . . . . . . . . . : Unregistered version, please register.
        Current Date And Time  . . . . . . . . . . . . . : 2024-03-22 12:12:44 PM
        Health Calculation Method  . . . . . . . . . . . : Analyse data field (default)
    
        Computer Information
       ----------------------
        Computer Name  . . . . . . . . . . . . . . . . . : BIGBOY
        User Name  . . . . . . . . . . . . . . . . . . . : maslo
        Computer Type  . . . . . . . . . . . . . . . . . : Desktop
        IP Address . . . . . . . . . . . . . . . . . . . : 192.168.0.63
        MAC Address  . . . . . . . . . . . . . . . . . . : 04-7C-16-E8-83-1A
        System Uptime  . . . . . . . . . . . . . . . . . : 1 days, 0 hours, 31 minutes, 39 seconds
        System Idle Time . . . . . . . . . . . . . . . . : 0 days, 0 hours, 0 minutes, 0 seconds
        System Up Since  . . . . . . . . . . . . . . . . : 2024-03-21 11:41:05 AM
        CPU Usage  . . . . . . . . . . . . . . . . . . . : CPU #1: 4 %, CPU #2: 0 %, CPU #3: 1 %, CPU #4: 0 %, CPU #5: 0 %, CPU #6: 1 %, CPU #7: 0 %, CPU #8: 1 %, CPU #9: 0 %, CPU #10: 0 %, CPU #11: 0 %, CPU #12: 0 %, CPU #13: 1 %, CPU #14: 1 %, CPU #15: 0 %, CPU #16: 0 %
        Virtual Memory . . . . . . . . . . . . . . . . . : 130208 MB, Used: 31832 MB (24 %)
    
        System Information
       --------------------
        Windows Version  . . . . . . . . . . . . . . . . : Windows 11 Pro 23H2 
        CPU Type & Speed #1  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #2  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #3  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #4  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #5  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #6  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #7  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #8  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #9  . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #10 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #11 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #12 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #13 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #14 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #15 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        CPU Type & Speed #16 . . . . . . . . . . . . . . : AMD Ryzen 7 7800X3D 8-Core Processor, 4200 MHz
        BIOS Manufacturer  . . . . . . . . . . . . . . . : AMI
        Physical Memory Size . . . . . . . . . . . . . . : 31905 MB, Used: 14654 MB (46 %)
        Display Adapter  . . . . . . . . . . . . . . . . : AMD Radeon(TM) Graphics
        Display Resolution . . . . . . . . . . . . . . . : 3840 x 2160 (32 bit)
        Printer #1 . . . . . . . . . . . . . . . . . . . : Brother MFC-J491DW
        Printer #2 . . . . . . . . . . . . . . . . . . . : Brother MFC-J491DW Printer
        Printer #3 . . . . . . . . . . . . . . . . . . . : Microsoft Print to PDF
        Network Controller #1  . . . . . . . . . . . . . : Realtek Gaming 2.5GbE Family Controller
        Network Controller #2  . . . . . . . . . . . . . : RZ616 Wi-Fi 6E 160MHz
        Optical Drive
    
        PCI Device Information
       ------------------------
        PCI Bus 0; Device 1; Function 1  . . . . . . . . : PCI Express Root Port
        PCI Bus 0; Device 1; Function 2  . . . . . . . . : PCI Express Root Port
        PCI Bus 0; Device 2; Function 1  . . . . . . . . : PCI Express Root Port
        PCI Bus 0; Device 8; Function 1  . . . . . . . . : PCI Express Root Port
        PCI Bus 0; Device 8; Function 3  . . . . . . . . : PCI Express Root Port
        PCI Bus 1; Device 0; Function 0  . . . . . . . . : NVIDIA GeForce RTX 4080 SUPER
        PCI Bus 1; Device 0; Function 1  . . . . . . . . : High Definition Audio Controller
        PCI Bus 2; Device 0; Function 0  . . . . . . . . : Standard NVM Express Controller
        PCI Bus 3; Device 0; Function 0  . . . . . . . . : PCI Express Upstream Switch Port
        PCI Bus 4; Device 0; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 4; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 5; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 6; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 7; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 8; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 9; Function 0  . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 10; Function 0 . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 11; Function 0 . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 12; Function 0 . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 4; Device 13; Function 0 . . . . . . . . : PCI Express Downstream Switch Port
        PCI Bus 10; Device 0; Function 0 . . . . . . . . : Standard SATA AHCI Controller
        PCI Bus 12; Device 0; Function 0 . . . . . . . . : Realtek Gaming 2.5GbE Family Controller
        PCI Bus 13; Device 0; Function 0 . . . . . . . . : RZ616 Wi-Fi 6E 160MHz
        PCI Bus 14; Device 0; Function 0 . . . . . . . . : %1 USB %2 eXtensible Host Controller - %3 (Microsoft);(AMD,3.20,1.10)
        PCI Bus 15; Device 0; Function 0 . . . . . . . . : Standard SATA AHCI Controller
        PCI Bus 16; Device 0; Function 0 . . . . . . . . : AMD Radeon(TM) Graphics
        PCI Bus 16; Device 0; Function 1 . . . . . . . . : High Definition Audio Bus
        PCI Bus 16; Device 0; Function 2 . . . . . . . . : AMD PSP 11.0 Device
        PCI Bus 16; Device 0; Function 3 . . . . . . . . : %1 USB %2 eXtensible Host Controller - %3 (Microsoft);(AMD,3.10,1.20)
        PCI Bus 16; Device 0; Function 4 . . . . . . . . : %1 USB %2 eXtensible Host Controller - %3 (Microsoft);(AMD,3.10,1.20)
        PCI Bus 16; Device 0; Function 6 . . . . . . . . : High Definition Audio Controller
        PCI Bus 17; Device 0; Function 0 . . . . . . . . : %1 USB %2 eXtensible Host Controller - %3 (Microsoft);(AMD,2.0,1.20)
    
    
    
      -- Physical Disk Information - Disk: #0: Samsung SSD 980 PRO 2TB --
    
        Hard Disk Summary
       -------------------
        Hard Disk Number . . . . . . . . . . . . . . . . : 0
        Interface  . . . . . . . . . . . . . . . . . . . : NVMe
        Disk Controller  . . . . . . . . . . . . . . . . : Standard NVM Express Controller (NVMe) [VEN: 144D, DEV: A80A] Version: 10.0.22621.3235, 6-21-2006
        Disk Location  . . . . . . . . . . . . . . . . . : Bus Number 0, Target Id 0, LUN 0
        Hard Disk Model ID . . . . . . . . . . . . . . . : Samsung SSD 980 PRO 2TB
        Firmware Revision  . . . . . . . . . . . . . . . : 5B2QGXA7
        Hard Disk Serial Number  . . . . . . . . . . . . : S6B0NU0WA06102X
        Total Size . . . . . . . . . . . . . . . . . . . : 1907726 MB
        Power State  . . . . . . . . . . . . . . . . . . : Active
        Device Type  . . . . . . . . . . . . . . . . . . : Fixed Disk
        Logical Drive(s) . . . . . . . . . . . . . . . . : C: [] 
        Current Temperature  . . . . . . . . . . . . . . : 35  C
        Power On Time  . . . . . . . . . . . . . . . . . : 57 days, 23 hours
        Estimated Remaining Lifetime . . . . . . . . . . : more than 1000 days
        Lifetime Writes  . . . . . . . . . . . . . . . . : 6.80 TB
        Health . . . . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)
        Performance  . . . . . . . . . . . . . . . . . . : #################### 100 % (Excellent)
    
        The status of the solid state disk is PERFECT. Problematic or weak sectors were not found. 
        The health is determined by SSD specific S.M.A.R.T. attribute(s):  Available Spare (Percent), Percentage Used
        The TRIM feature of the SSD is supported and enabled for optimal performance.
          No actions needed.
    
        Properties
       ------------
        NVMe Standard Version  . . . . . . . . . . . . . : 1.3
        PCI Vendor ID (VID)  . . . . . . . . . . . . . . : 0x144D (Samsung)
        PCI Subsystem Vendor ID (SSVID)  . . . . . . . . : 0x144D (Samsung)
        IEEE OUI Identifier  . . . . . . . . . . . . . . : 38-25-00
        Recommended Arbitration Burst (RAB)  . . . . . . : 2
        Multi-Interface Capabilities . . . . . . . . . . : 0
        Maximum Data Transfer Size . . . . . . . . . . . : 128 (7)
        Abort Command Limit  . . . . . . . . . . . . . . : 8
        Asynchronous Event Request Limit . . . . . . . . : 4
        Number FW Slots Support  . . . . . . . . . . . . : 3
        Maximum Error Log Page Entries . . . . . . . . . : 64
        Total Number Of Power States . . . . . . . . . . : 5
        Admin Vendor Specific CMD Format . . . . . . . . : 1
        Submission Queue Entry Size  . . . . . . . . . . : Max: 64, Min: 64
        Completion Queue Entry Size  . . . . . . . . . . : Max: 16, Min: 16
        Number Of Namespaces . . . . . . . . . . . . . . : 1
        Stripe Size  . . . . . . . . . . . . . . . . . . : 0
        Highest Possible Transfer Rate . . . . . . . . . : PCIe 4.0 x4
        Negotiated Transfer Rate . . . . . . . . . . . . : PCIe 4.0 x4
        Maximum Power (mW) . . . . . . . . . . . . . . . : 8490
    
        NVMe Features
       ---------------
        Doorbell Buffer Config . . . . . . . . . . . . . : Not supported
        Virtualization Management  . . . . . . . . . . . : Not supported
        NVMe MI Send/Receive . . . . . . . . . . . . . . : Not supported
        Directives . . . . . . . . . . . . . . . . . . . : Not supported
        Device Self-test . . . . . . . . . . . . . . . . : Supported
        Extended Self-test Estimated Time  . . . . . . . : 35 minutes
        Only One Device Self-test  . . . . . . . . . . . : No
        Namespace Management . . . . . . . . . . . . . . : Not supported
        Firmware Activate Download . . . . . . . . . . . : Supported
        Format NVM . . . . . . . . . . . . . . . . . . . : Supported
        Security Send Receive  . . . . . . . . . . . . . : Supported
        Firmware Activation Without Reset  . . . . . . . : Supported
        First Firmware Slot Read Only  . . . . . . . . . : No
        Command Effects Log Page . . . . . . . . . . . . : Supported
        SMART Information Per Namespace  . . . . . . . . : Supported
        Reservations . . . . . . . . . . . . . . . . . . : Not supported
        Save / Select Fields . . . . . . . . . . . . . . : Supported
        Write Zeroes . . . . . . . . . . . . . . . . . . : Not supported
        Dataset Management Command . . . . . . . . . . . : Supported
        Write Uncorrectable Command  . . . . . . . . . . : Supported
        Compare Command  . . . . . . . . . . . . . . . . : Supported
        Compare And Write Fused Operation  . . . . . . . : Not supported
        Cryptographic Erase  . . . . . . . . . . . . . . : Supported
        Secure Erase All Namespaces  . . . . . . . . . . : Not supported
        Format All Namespaces  . . . . . . . . . . . . . : Supported
        Volatile Write Cache Present . . . . . . . . . . : Supported
        Autonomous Power State Transitions . . . . . . . : Supported
        Atomic Compare And Write Unit  . . . . . . . . . : Not supported
        Scatter Gather List (SGL)  . . . . . . . . . . . : Not supported
        Host Controlled Thermal Management . . . . . . . : Supported
        Thermal Management Temperature 1 . . . . . . . . : 355  K (82  C)
        Thermal Management Temperature 2 . . . . . . . . : 356  K (83  C)
        Warning Composite Temperature Threshold  . . . . : 355  K (82  C)
        Critical Composite Temperature Threshold . . . . : 358  K (85  C)
        Sanitize Overwrite . . . . . . . . . . . . . . . : Not supported
        Sanitize Block Erase . . . . . . . . . . . . . . : Supported
        Sanitize Crypto Erase  . . . . . . . . . . . . . : Supported
        Sanitize Status  . . . . . . . . . . . . . . . . : Never sanitized [0]
    
        NVMe Namespace Information
       ----------------------------
        NS 1 Total Sectors . . . . . . . . . . . . . . . : 3907029168
        NS 1 Bytes Per Sector  . . . . . . . . . . . . . : 512
        NS 1 Active LBA Format Index . . . . . . . . . . : 0
        NS 1 LBA Formats Supported . . . . . . . . . . . : 1
        NS 1 LBA Format List (Disk Performance)  . . . . : 512 (Best)
    
        Disk Information
       ------------------
        Disk Information
        Form Factor  . . . . . . . . . . . . . . . . . . : M.2 2280
        Capacity . . . . . . . . . . . . . . . . . . . . : 2000 GB (2000 x 1,000,000,000 bytes)
        SSD Controller . . . . . . . . . . . . . . . . . : Samsung Elpis S4LV003
        Disk Interface . . . . . . . . . . . . . . . . . : PCI-Express x4 (4.0)
        Device Type  . . . . . . . . . . . . . . . . . . : Samsung 128-layer 3D TLC V-NAND
        Width  . . . . . . . . . . . . . . . . . . . . . : 22.0 mm (0.9 inch)
        Depth  . . . . . . . . . . . . . . . . . . . . . : 80.0 mm (3.1 inch)
        Height . . . . . . . . . . . . . . . . . . . . . : 2.4 mm (0.1 inch)
        Weight . . . . . . . . . . . . . . . . . . . . . : 9 grams (0.0 pounds)
    
        S.M.A.R.T.
       ------------
    Attribute                                                            Threshold                       Value
    Critical Warning                                                                                         0
    Composite Temperature (Kelvin)                                                                         308
    Available Spare (Percent)                                                                              100
    Available Spare Threshold                                                                               10
    Percentage Used                                                                                          0
    Data Units Read (512000 Bytes)                                                                  25,496,714
    Data Units Written (512000 Bytes)                                                               14,613,605
    Host Read Commands                                                                             153,056,053
    Host Write Commands                                                                            189,576,844
    Controller Busy Time (minutes)                                                                       3,062
    Power Cycles                                                                                            93
    Power On Hours                                                                                       1,391
    Unsafe Shutdowns                                                                                        25
    Media and Data Integrity Errors                                                                          0
    Number of Error Information Log Entries                                                                  0
    Warning Composite Temperature Time (minutes)                                                             0
    Critical Composite Temperature Time (minutes)                                                            0
    Temperature Sensor 1                                                                                   308
    Temperature Sensor 2                                                                                   312
    
        Transfer Rate Information
       ---------------------------
        Total Data Read  . . . . . . . . . . . . . . . . : 105 MB,  105 MB since installation  (2024-03-22)
        Total Data Write . . . . . . . . . . . . . . . . : 197 MB,  197 MB since installation
        Average Reads Per Day  . . . . . . . . . . . . . : 105.00 MB
        Average Writes Per Day . . . . . . . . . . . . . : 197.00 MB
        Current Transfer Rate  . . . . . . . . . . . . . : 1161 KB/s
        Maximum Transfer Rate  . . . . . . . . . . . . . : 35091 KB/s
        Current Read Rate  . . . . . . . . . . . . . . . : 55 KB/s
        Current Write Rate . . . . . . . . . . . . . . . : 1105 KB/s
        Current Disk Activity  . . . . . . . . . . . . . : 3 %
    
    
    
      -- Partition Information --
    
    Logical Drive                           Total Space         Free Space          Free Space               Used Space
    C: (Disk: #0)                           1862.2 GB           1204.0 GB            65 %                    #######-------------
    
    
    
      -- System Management Information --
    
    
        Motherboard Information
       -------------------------
        Manufacturer . . . . . . . . : Micro-Star International Co., Ltd.
        Product  . . . . . . . . . . : MAG B650 TOMAHAWK WIFI (MS-7D75)   1.0
        Serial Number  . . . . . . . : 07D7511_N71E619791
        Asset Tag  . . . . . . . . . : To be filled by O.E.M.   To be filled by O.E.M.
        BIOS . . . . . . . . . . . . : American Megatrends International, LLC. ver. 1.60 [05/30/2023]
        Memory Module 1  . . . . . . : -
        Memory Module 2  . . . . . . : 16384 MB [4800 MHz] P0 CHANNEL A
        Memory Module 3  . . . . . . : -
        Memory Module 4  . . . . . . : 16384 MB [4800 MHz] P0 CHANNEL B
    
        System Information
       --------------------
        Manufacturer . . . . . . . . : Micro-Star International Co., Ltd.
        Product  . . . . . . . . . . : MS-7D75   1.0
        Serial Number  . . . . . . . : To be filled by O.E.M.
        UUID . . . . . . . . . . . . : E8147308-C8C9-1E52-AB9A-047C16E8831A
        Chassis  . . . . . . . . . . : Micro-Star International Co., Ltd. ver. 1.0
        Chassis Serial Number  . . . : To be filled by O.E.M.
        Chassis Asset Tag  . . . . . : To be filled by O.E.M.
    BSOD 3 times a week while idle or active-screenshot-2024-03-22-121432.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121440.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121449.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121611.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121706.png

    BSOD 3 times a week while idle or active-screenshot-2024-03-22-121754.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121804.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121813.png
    BSOD 3 times a week while idle or active-screenshot-2024-03-22-121822.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121831.png

    BSOD 3 times a week while idle or active-screenshot-2024-03-22-121845.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121853.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-121935.png
    BSOD 3 times a week while idle or active-screenshot-2024-03-22-121955.pngBSOD 3 times a week while idle or active-screenshot-2024-03-22-122008.png
    Last edited by Brink; 22 Mar 2024 at 11:33. Reason: code box
      My Computer


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

    For any unexpected shutdown and restart with or without BSOD comment into this thread.
      My Computer


  10. Posts : 7
    Windows 11
    Thread Starter
       #10

    New BSOD Today March 26th


    BSOD 3 times a week while idle or active-screenshot-2024-03-26-200637.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200705.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200720.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200735.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200752.png
    BSOD 3 times a week while idle or active-screenshot-2024-03-26-200540.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200550.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200602.pngBSOD 3 times a week while idle or active-screenshot-2024-03-26-200612.png

    Memory Dump:


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

    EnableRedirectToV8JsProvider : false

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

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

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

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

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


    Loading Dump File [C:\Users\maslo\OneDrive\Documents\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

    Primary dump contents written successfully

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 22621 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
    Kernel base = 0xfffff802`58c00000 PsLoadedModuleList = 0xfffff802`59813530
    Debug session time: Tue Mar 26 15:32:40.054 2024 (UTC - 4:00)
    System Uptime: 5 days 3:51:39.906
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .................................
    Loading User Symbols
    ..................
    Loading unloaded module list
    ..................................................
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff802`590177f0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff885`432f72a0=00000000000000ef
    4: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    CRITICAL_PROCESS_DIED (ef)
    A critical system process died
    Arguments:
    Arg1: ffff9a0b04af40c0, Process object or thread object
    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
    Arg3: ffff9a0b04af40c0, The process object that initiated the termination.
    Arg4: 0000000000000000

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


    KEY_VALUES_STRING: 1

    Key : Analysis.CPU.mSec
    Value: 1952

    Key : Analysis.Elapsed.mSec
    Value: 4004

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

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

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

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

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

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

    Key : Bugcheck.Code.KiBugCheckData
    Value: 0xef

    Key : Bugcheck.Code.LegacyAPI
    Value: 0xef

    Key : Bugcheck.Code.TargetModel
    Value: 0xef

    Key : CriticalProcessDied.ExceptionCode
    Value: 8a5d0c0

    Key : CriticalProcessDied.Process
    Value: svchost.exe

    Key : Dump.Attributes.AsUlong
    Value: 1800

    Key : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key : Dump.Attributes.ErrorCode
    Value: 0

    Key : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key : Dump.Attributes.ProgressPercentage
    Value: 100

    Key : Failure.Bucket
    Value: 0xEF_svchost.exe_LocalServiceNoNetwork_BUGCHECK_CRITICAL_PROCESS_8a5d0c0_ntdll!NtTerminateProcess

    Key : Failure.Hash
    Value: {6e9e595a-c065-4f9d-4d4e-e5b37838da3f}

    Key : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key : Hypervisor.Flags.CpuManager
    Value: 1

    Key : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    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: 4853999

    Key : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    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 : SecureKernel.HalpHvciEnabled
    Value: 1

    Key : WER.OS.Branch
    Value: ni_release

    Key : WER.OS.Version
    Value: 10.0.22621.1


    BUGCHECK_CODE: ef

    BUGCHECK_P1: ffff9a0b04af40c0

    BUGCHECK_P2: 0

    BUGCHECK_P3: ffff9a0b04af40c0

    BUGCHECK_P4: 0

    FILE_IN_CAB: MEMORY.DMP

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


    DUMP_FILE_ATTRIBUTES: 0x1800

    PROCESS_NAME: svchost.exe

    CRITICAL_PROCESS: svchost.exe

    ERROR_CODE: (NTSTATUS) 0x8a5d0c0 - <Unable to get error code text>

    BLACKBOXBSD: 1 (!blackboxbsd)


    BLACKBOXNTFS: 1 (!blackboxntfs)


    BLACKBOXPNP: 1 (!blackboxpnp)


    BLACKBOXWINLOGON: 1

    STACK_TEXT:
    fffff885`432f7298 fffff802`595b2d2b : 00000000`000000ef ffff9a0b`04af40c0 00000000`00000000 ffff9a0b`04af40c0 : nt!KeBugCheckEx
    fffff885`432f72a0 fffff802`594ba64d : ffff9a0b`04af40c0 fffff802`58ebba25 00000000`00000000 fffff802`58ebb5f7 : nt!PspCatchCriticalBreak+0x11b
    fffff885`432f7330 fffff802`592f66cb : ffff9a0b`04af40c0 00000000`c00001ad ffff9a0b`04af40c0 00000000`00000000 : nt!PspTerminateAllThreads+0x1c3f15
    fffff885`432f73a0 fffff802`592f64a1 : ffffffff`ffffffff ffff9a0b`04af40c0 ffff9a0b`08a5d0c0 ffff9a0b`04af40c0 : nt!PspTerminateProcess+0xe7
    fffff885`432f73e0 fffff802`5902c9e8 : ffff9a0b`00000964 ffff9a0b`08a5d0c0 ffff9a0b`04af40c0 ffffffff`f70f2e80 : nt!NtTerminateProcess+0xb1
    fffff885`432f7460 00007ffb`5feaf8f4 : 00007ffb`5d4790b0 0000008d`15e7e600 00000000`00000000 ffffffff`ffffffff : nt!KiSystemServiceCopyEnd+0x28
    0000008d`15e7e618 00007ffb`5d4790b0 : 0000008d`15e7e600 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : ntdll!NtTerminateProcess+0x14
    0000008d`15e7e620 00007ffb`5d54ca66 : 0000008d`15e7ecb0 00000000`00000250 ffffffff`f70f2e80 0000008d`15e7e730 : KERNELBASE!TerminateProcess+0x30
    0000008d`15e7e650 00007ffb`5d54ccf5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : KERNELBASE!RaiseFailFastException+0x196
    0000008d`15e7ec30 00007ffb`59e817f1 : 00000000`00000034 00000000`00000034 0000008d`15e7ef88 00007ffb`5d3f0000 : KERNELBASE!TerminateProcessOnMemoryExhaustion+0x175
    0000008d`15e7eec0 00007ffb`59e2decb : 00000000`0000000a 00000000`00000034 00000000`00000004 0000025b`91f2bc80 : coremessaging!Cn::Process::NotifyOutOfMemory+0x71
    0000008d`15e7eef0 00007ffb`59e2b8a8 : 0000008d`15e7efe0 00000000`00000000 0000008d`15e7efb0 00000000`00000004 : coremessaging!CFlat::Array$2<char16_t,1>::CreateUninitialized<int & __ptr64>+0x8f
    0000008d`15e7ef20 00007ffb`59e494b7 : 0000025b`91fa40a0 0000025b`0000000a 0000025b`91f2bc80 00000000`00000001 : coremessaging!System::UInt32::ToString+0x30
    0000008d`15e7ef70 00007ffb`59e180c6 : 0000025b`91f143d0 00000000`00000000 0000025b`92950e50 00000000`00000000 : coremessaging!Microsoft::CoreUI::Registrar::RegisteredConversation::ReleasePeerID+0xff
    0000008d`15e7efe0 00007ffb`59e1804b : 0000025b`91f30140 0000025b`91f2bc80 00000000`00000000 00007ffb`59dfa289 : coremessaging!Microsoft::CoreUI::Registrar::RegisteredConversationPeer::Dispose+0x52
    0000008d`15e7f020 00007ffb`59ebda72 : 0000025b`91f30140 00000000`00000000 0000025b`91f30140 00007ffb`59e3619f : coremessaging!Microsoft::CoreUI::Registrar::ConversationClientConnectionInfo::Dispose+0x4b
    0000008d`15e7f060 00007ffb`59e6cd01 : 00000000`00000000 0000008d`15e7f120 0000025b`91f30140 0000025b`91f2bc80 : coremessaging!Microsoft::CoreUI::Registrar::RegisteredConversation::ReleaseListOfClientConnections+0xa2
    0000008d`15e7f0c0 00007ffb`59e71326 : 0000025b`9290ae70 0000025b`91f2bc80 0000025b`928b16e0 00000000`00000000 : coremessaging!Microsoft::CoreUI::Registrar::RegisteredConversation::DisconnectServer+0x93
    0000008d`15e7f120 00007ffb`59e0e1e8 : 0000025b`91fa7520 00000000`00000000 0000025b`928b16e0 00000000`00000000 : coremessaging!Microsoft::CoreUI::Registrar::ServerConversationOperations::CleanupForDepartedThread+0x63a86
    0000008d`15e7f1a0 00007ffb`59e0dbb2 : 0000025b`9162e0e0 0000025b`9162d600 0000025b`9162d830 0000025b`9162d0b0 : coremessaging!Microsoft::CoreUI::Registrar::RemoteRegistrarServer::CleanUpForDepartedThread+0x284
    0000008d`15e7f300 00007ffb`59e0db43 : 0000025b`9162e0e0 0000025b`91640670 0000025b`916b13d0 fffffda4`6e9cc0f0 : coremessaging!Microsoft::CoreUI::Registrar::AlpcServerHost::Microsoft_CoreUI_Registrar_IAlpcServerHost_OnClientDisconnected$+0x62
    0000008d`15e7f370 00007ffb`59dfe2bd : 00000000`000089e0 0000025b`91fa7930 00000000`0000003e 00000000`00000000 : coremessaging!Microsoft::CoreUI::Registrar::AlpcServerThunk::OnClientDisconnected+0x43
    0000008d`15e7f3a0 00007ffb`59e21de5 : 00000000`00000000 0000008d`15e7f519 0000025b`91633f10 00000000`00000000 : coremessaging!AlpcServerConnection::OnClientDisconnected+0x8d
    0000008d`15e7f3f0 00007ffb`59e218dd : 00007f7e`ffa171e9 00000000`00000000 0000008d`15e7f519 00000000`40000402 : coremessaging!AlpcConnection::Callback_HandleReceivedBuffer+0x355
    0000008d`15e7f4a0 00007ffb`59df6cb5 : 00000000`40000401 0000008d`15e7f5a0 0000008d`15e7f5d8 00000000`ffffff00 : coremessaging!AlpcConnection::Callback_ProcessIncoming+0x26d
    0000008d`15e7f580 00007ffb`59df3022 : 00000000`00000000 0000025b`00000001 0000025b`00000000 00007ffb`59e14700 : coremessaging!`CFlat::DelegateImpl<Microsoft::CoreUI::Dispatch::WaitCallback,0,void __cdecl(enum Microsoft::CoreUI::Dispatch::WaitStatus,Microsoft::CoreUI::Support::Win32Handle),long __cdecl(void * __ptr64,unsigned long,void * __ptr64),0>::Bind<CFlat::SmartPtr<Microsoft::CoreUI::Registrar::AlpcServerAdapter>,&Microsoft::CoreUI::Registrar::AlpcServerAdapter::Callback_ProcessIncoming>'::`2'::Thunk::Invoke+0x75
    0000008d`15e7f5d0 00007ffb`59e3d788 : 0000025b`9162dad0 0000008d`15e7f700 0000025b`9162d170 0000008d`15e7f799 : coremessaging!Microsoft::CoreUI::Dispatch::RegisteredWait::DoCallback+0x42
    0000008d`15e7f600 00007ffb`59e398fc : 0000025b`916326c0 0000025b`91634170 7fffffff`ffffffff 0000025b`916326c0 : coremessaging!`CFlat::DelegateImpl<Microsoft::CoreUI::Dispatch::WakeRecordHandler,0,bool __cdecl(CFlat::Ref<Microsoft::CoreUI::Dispatch::WakeRecord>),void,0>::Bind<CFlat::SmartPtr<Microsoft::CoreUI::Dispatch::WaitCollection>,&Microsoft::CoreUI::Dispatch::WaitCollection::Callback_DeliverCompletion>'::`2'::Thunk::Invoke+0xc8
    0000008d`15e7f640 00007ffb`59e3b415 : 0000025b`916323b0 0000008d`00000000 00000000`00000000 00007ffb`59e36915 : coremessaging!Microsoft::CoreUI::Dispatch::WaitCollection::Callback_DoGeneralWait+0x2ac
    0000008d`15e7f710 00007ffb`59e38bff : 0000025b`91632740 0000025b`9162d170 0000025b`9162d410 0000025b`91632740 : coremessaging!Microsoft::CoreUI::Dispatch::WaitController::Callback_OnDispatch+0x2e5
    0000008d`15e7f800 00007ffb`59e37a3b : 0000025b`91616d20 0000025b`916323b0 00000000`00000001 00000000`00000000 : coremessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0x36f
    0000008d`15e7f910 00007ffb`59df2bd1 : 0000025b`916323b0 0000025b`00000001 0000008d`91632300 00000000`00000000 : coremessaging!Microsoft::CoreUI::Dispatch::Win32EventLoopBridge::Callback_Run+0x5ab
    0000008d`15e7f9e0 00007ffb`59e5c821 : 0000025b`916323b0 0000025b`916323b0 0000025b`916326c0 00000000`0000019c : coremessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_Run+0xa1
    0000008d`15e7fa30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : coremessaging!Microsoft::CoreUI::Registrar::CuiRegistrar::Run+0x111


    SYMBOL_NAME: ntdll!NtTerminateProcess+14

    MODULE_NAME: ntdll

    IMAGE_NAME: ntdll.dll

    STACK_COMMAND: .cxr; .ecxr ; kb

    BUCKET_ID_FUNC_OFFSET: 14

    FAILURE_BUCKET_ID: 0xEF_svchost.exe_LocalServiceNoNetwork_BUGCHECK_CRITICAL_PROCESS_8a5d0c0_ntdll!NtTerminateProcess

    OS_VERSION: 10.0.22621.1

    BUILDLAB_STR: ni_release

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    FAILURE_ID_HASH: {6e9e595a-c065-4f9d-4d4e-e5b37838da3f}

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


      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 06:47.
Find Us




Windows 10 Forums