BSOD while sitting in a discord voice call after long Fortnite session

Page 1 of 7 123 ... LastLast

  1. Posts : 106
    Microsoft Windows 10 Home 64-bit 19042 Multiprocessor Free
       #1

    BSOD while sitting in a discord voice call after long Fortnite session


    After a couple hours of Fortnite with my friends (using Discord voice call to talk), I then closed Fortnite and remained on the Discord call. About 10-20 minutes later, I blue screened. The stop code was ATTEMPTED_WRITE_TO_READONLY_MEMORY.

    This is the 2nd BSOD I've had within 2 months. I couldn't get a picture of the stop code on the first one, so not sure what it said.
    BSOD while sitting in a discord voice call after long Fortnite session Attached Files
      My Computer


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

    Please perform the following steps: (in sequence)


    1) Run Tuneup plus > post a share link into the newest post

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

    Batch files for use in BSOD debugging


    2) Create a new restore point:

    Create System Restore Point in Windows 10



    3) Run Sea Tools for Windows Long Generic test (all drives) > post images or share links into the newest post

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

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



    4) Open administrative command prompt and copy and paste: chkdsk /b /v

    Run these chkdsk switches on all drives using the syntax: chkdsk /b /v c: or chkdsk /b /v d: or chkdsk /b /v e: , etc.

    Make sure that the chkdsk on the windows drive runs overnight while sleeping



    C:\WINDOWS\system32>chkdsk /b /v c:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: y

    Reboot as needed.



    5) After completing chkdsk /b /v on all drives run:

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

    Post a share link into the newest post.


    6) Download and install Samsung Magician: Samsung Magician Software | Samsung Semiconductor USA
    Run the software on the applicable drive(s) post images or share links:

    Drive Details
    Update software /firmware
    Diagnostic Scan > full scan
    Performance Benchmark
    Over Provisioning
    Performance Optimization




    7) The BIOS Version/Date American Megatrends Inc. F31e, 10/29/2020

    Upgrade the BIOS to the most up to date non-beta BIOS



    8) Uninstall Easy anti-cheat > monitor computer performance using Reliability Monitor:

    Easy Anti-Cheat

    View Reliability History in Windows 11 Tutorial | Windows 11 Forum



    9) For any new BSOD or unexpected shutdowns and restarts after completing all of the above steps post a new V2 share link into the newest post





    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 63.4 GB
    Total Space: 476.3 GB
    File System: NTFS
          Model: Samsung SSD 980 PRO 500GB
    
          Drive: D:
     Free Space: 172.8 GB
    Total Space: 476.9 GB
    File System: NTFS
          Model: Samsung SSD 980 PRO 500GB
    
          Drive: E:
     Free Space: 207.2 GB
    Total Space: 953.9 GB
    File System: NTFS
          Model: Samsung SSD 980 PRO 1TB
      My Computer


  3. Posts : 402
    Windows 10 and Windows 11
       #3

    The dump is pretty clear on this one, your problem is EasyAntiChet, and you're far from the first. You can see it called several times in the lead up to the page fault and bugcheck...
    Code:
    21: kd> !dpx
    Start memory scan  : 0xffffb1075a65ee98 ($csp)
    End memory scan    : 0xffffb1075a660000 (Kernel Stack Base)
    
    0xffffb1075a65ef98 : 0xfffff80036024660 : nt!MmAccessFault+0x400
    0xffffb1075a65eff8 : 0xfffff80036051bfe : nt!HalRequestIpiSpecifyVector+0x7e
    0xffffb1075a65f018 : 0xfffff800362058f6 : nt!KiSwapContext+0x76
    0xffffb1075a65f048 : 0xfffff8003604f35a : nt!KiIpiSendRequest+0x3aa
    0xffffb1075a65f100 : 0xfffff802ffc00000 : EasyAntiCheat_EOS
    0xffffb1075a65f110 : 0xfffff80035e00000 : "nt!VrpRegistryString <PERF> (nt+0x0)"
    0xffffb1075a65f138 : 0xfffff8003620d1d8 : nt!KiPageFault+0x358
    0xffffb1075a65f158 : 0xfffff8003608eff5 : nt!KeFlushMultipleRangeTb+0x135
    0xffffb1075a65f228 : 0xfffff800363446d3 : nt!MiUnmapRetpolineStubs+0x2bb
    0xffffb1075a65f2a8 : 0xfffff80036212d30 : nt!memset+0x30
    0xffffb1075a65f2c0 : 0xffffb1075a65f2d8 : 0xfffff800360ebb08 : nt!RtlClearBitsEx+0x98
    0xffffb1075a65f2d8 : 0xfffff800360ebb08 : nt!RtlClearBitsEx+0x98
    0xffffb1075a65f308 : 0xfffff800366d23f7 : nt!MiMarkRetpolineBits+0x63
    0xffffb1075a65f338 : 0xfffff800366d237c : nt!MiMarkKernelImageRetpolineBits+0x34
    0xffffb1075a65f340 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f370 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f378 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f3d8 : 0xfffff802ffc00000 : EasyAntiCheat_EOS
    0xffffb1075a65f500 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f508 : 0xfffff80036570e01 : nt!MmUnloadSystemImage+0x41
    0xffffb1075a65f538 : 0xfffff80036570d2e : nt!IopDeleteDriver+0x4e
    0xffffb1075a65f588 : 0xfffff80036444950 : nt!ObpRemoveObjectRoutine+0x80
    0xffffb1075a65f5a8 : 0xfffff8003647406f : nt!ObpDeleteNameCheck+0x1df
    0xffffb1075a65f5d0 : 0xfffff80036b25400 : nt!KiInitialProcess+0xa00
    0xffffb1075a65f5e8 : 0xfffff80036045c07 : nt!ObfDereferenceObjectWithTag+0xc7
    0xffffb1075a65f628 : 0xfffff80036045b2e : nt!HalPutDmaAdapter+0xe
    0xffffb1075a65f658 : 0xfffff800365689f8 : nt!IopUnloadDriver+0x250
    0xffffb1075a65f6c8 : 0xffff9e8b44ca6770 :  !du "\Driver\EasyAntiCheat_EOSSys"
    0xffffb1075a65f720 : 0xfffff8003657ee00 : nt!IopLoadUnloadDriver
    0xffffb1075a65f788 : 0xfffff8003669ca0b : nt!NtUnloadDriver+0xb
    0xffffb1075a65f7b0 : 0xfffff8003669ca00 : nt!NtUnloadDriver
    0xffffb1075a65f7b8 : 0xfffff80036210ef8 : nt!KiSystemServiceCopyEnd+0x28
    0xffffb1075a65f7d8 : 0xffffb28b1a5e7060 :  !da "*SYSTEM*"
    0xffffb1075a65f7f8 : 0xfffff8003643f569 : nt!PsAssignImpersonationToken+0xb9
    0xffffb1075a65f858 : 0xfffff800367b6074 : nt!ExAllocatePoolWithTag+0x64
    0xffffb1075a65f878 : 0xfffff800364118fd : nt!SePrivilegeCheck+0x2d
    0xffffb1075a65f8a8 : 0xfffff80036015aa0 : nt!ExAllocatePoolWithQuotaTag+0x60
    0xffffb1075a65f8d8 : 0xfffff800364526ec : nt!SeReleaseSubjectContext+0x5c
    0xffffb1075a65f908 : 0xffffb28b2729a1a0 :  !du "\Registry\Machine\System\CurrentControlSet\Services\EasyAntiCheat_EOSSys"
    0xffffb1075a65f928 : 0xfffff800362022a0 : nt!KiServiceLinkage
    0xffffb1075a65f968 : 0xfffff80036429f4d : nt!SeReleaseLuidAndAttributesArray+0x15
    0xffffb1075a65f9b8 : 0xffffb28b2729a1a0 :  !du "\Registry\Machine\System\CurrentControlSet\Services\EasyAntiCheat_EOSSys"
    0xffffb1075a65f9d0 : 0xffffb28b2729a1a0 :  !du "\Registry\Machine\System\CurrentControlSet\Services\EasyAntiCheat_EOSSys"
    0xffffb1075a65f9f8 : 0xffffb28b1a5e7060 :  !da "*SYSTEM*"
    0xffffb1075a65fa48 : 0xfffff80036444efc : nt!NtClose+0xec
    0xffffb1075a65fa88 : 0xfffff8003669ca0b : nt!NtUnloadDriver+0xb
    0xffffb1075a65fab0 : 0xfffff8003669ca00 : nt!NtUnloadDriver
    0xffffb1075a65fab8 : 0xfffff80036210ef8 : nt!KiSystemServiceCopyEnd+0x28
    0xffffb1075a65fac0 : 0xffff9e8b39b9c000 :  Trap @ ffffb1075a65fac0
    0xffffb1075a65fc58 : 0xffffb1075a659000 : 0xfffff80036205fb1 : nt!SwapContext+0x3e1
    The version of EasyAntiCheat_EOS.sys that you have installed looks current...
    Code:
    21: kd> lmvm EasyAntiCheat_EOS
    Browse full module list
    start             end                 module name
    fffff802`ffc00000 fffff803`00d74000   EasyAntiCheat_EOS T (no symbols)           
        Loaded symbol image file: EasyAntiCheat_EOS.sys
        Image path: \??\C:\Program Files (x86)\EasyAntiCheat_EOS\EasyAntiCheat_EOS.sys
        Image name: EasyAntiCheat_EOS.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Nov  9 03:49:06 2023 (654C3A92)
        CheckSum:         0111D7D0
        ImageSize:        01174000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    All you can do is disable/uninstall EastAntiCheat and see whether the system is stable, or contact the vendor.
      My Computer


  4. Posts : 106
    Microsoft Windows 10 Home 64-bit 19042 Multiprocessor Free
    Thread Starter
       #4

    ubuysa said:
    The dump is pretty clear on this one, your problem is EasyAntiChet, and you're far from the first. You can see it called several times in the lead up to the page fault and bugcheck...
    Code:
    21: kd> !dpx
    Start memory scan  : 0xffffb1075a65ee98 ($csp)
    End memory scan    : 0xffffb1075a660000 (Kernel Stack Base)
    
    0xffffb1075a65ef98 : 0xfffff80036024660 : nt!MmAccessFault+0x400
    0xffffb1075a65eff8 : 0xfffff80036051bfe : nt!HalRequestIpiSpecifyVector+0x7e
    0xffffb1075a65f018 : 0xfffff800362058f6 : nt!KiSwapContext+0x76
    0xffffb1075a65f048 : 0xfffff8003604f35a : nt!KiIpiSendRequest+0x3aa
    0xffffb1075a65f100 : 0xfffff802ffc00000 : EasyAntiCheat_EOS
    0xffffb1075a65f110 : 0xfffff80035e00000 : "nt!VrpRegistryString <PERF> (nt+0x0)"
    0xffffb1075a65f138 : 0xfffff8003620d1d8 : nt!KiPageFault+0x358
    0xffffb1075a65f158 : 0xfffff8003608eff5 : nt!KeFlushMultipleRangeTb+0x135
    0xffffb1075a65f228 : 0xfffff800363446d3 : nt!MiUnmapRetpolineStubs+0x2bb
    0xffffb1075a65f2a8 : 0xfffff80036212d30 : nt!memset+0x30
    0xffffb1075a65f2c0 : 0xffffb1075a65f2d8 : 0xfffff800360ebb08 : nt!RtlClearBitsEx+0x98
    0xffffb1075a65f2d8 : 0xfffff800360ebb08 : nt!RtlClearBitsEx+0x98
    0xffffb1075a65f308 : 0xfffff800366d23f7 : nt!MiMarkRetpolineBits+0x63
    0xffffb1075a65f338 : 0xfffff800366d237c : nt!MiMarkKernelImageRetpolineBits+0x34
    0xffffb1075a65f340 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f370 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f378 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f3d8 : 0xfffff802ffc00000 : EasyAntiCheat_EOS
    0xffffb1075a65f500 : 0xffff9e8b30dc36a0 : 0xfffff80036a2a730 : nt!PsLoadedModuleList
    0xffffb1075a65f508 : 0xfffff80036570e01 : nt!MmUnloadSystemImage+0x41
    0xffffb1075a65f538 : 0xfffff80036570d2e : nt!IopDeleteDriver+0x4e
    0xffffb1075a65f588 : 0xfffff80036444950 : nt!ObpRemoveObjectRoutine+0x80
    0xffffb1075a65f5a8 : 0xfffff8003647406f : nt!ObpDeleteNameCheck+0x1df
    0xffffb1075a65f5d0 : 0xfffff80036b25400 : nt!KiInitialProcess+0xa00
    0xffffb1075a65f5e8 : 0xfffff80036045c07 : nt!ObfDereferenceObjectWithTag+0xc7
    0xffffb1075a65f628 : 0xfffff80036045b2e : nt!HalPutDmaAdapter+0xe
    0xffffb1075a65f658 : 0xfffff800365689f8 : nt!IopUnloadDriver+0x250
    0xffffb1075a65f6c8 : 0xffff9e8b44ca6770 :  !du "\Driver\EasyAntiCheat_EOSSys"
    0xffffb1075a65f720 : 0xfffff8003657ee00 : nt!IopLoadUnloadDriver
    0xffffb1075a65f788 : 0xfffff8003669ca0b : nt!NtUnloadDriver+0xb
    0xffffb1075a65f7b0 : 0xfffff8003669ca00 : nt!NtUnloadDriver
    0xffffb1075a65f7b8 : 0xfffff80036210ef8 : nt!KiSystemServiceCopyEnd+0x28
    0xffffb1075a65f7d8 : 0xffffb28b1a5e7060 :  !da "*SYSTEM*"
    0xffffb1075a65f7f8 : 0xfffff8003643f569 : nt!PsAssignImpersonationToken+0xb9
    0xffffb1075a65f858 : 0xfffff800367b6074 : nt!ExAllocatePoolWithTag+0x64
    0xffffb1075a65f878 : 0xfffff800364118fd : nt!SePrivilegeCheck+0x2d
    0xffffb1075a65f8a8 : 0xfffff80036015aa0 : nt!ExAllocatePoolWithQuotaTag+0x60
    0xffffb1075a65f8d8 : 0xfffff800364526ec : nt!SeReleaseSubjectContext+0x5c
    0xffffb1075a65f908 : 0xffffb28b2729a1a0 :  !du "\Registry\Machine\System\CurrentControlSet\Services\EasyAntiCheat_EOSSys"
    0xffffb1075a65f928 : 0xfffff800362022a0 : nt!KiServiceLinkage
    0xffffb1075a65f968 : 0xfffff80036429f4d : nt!SeReleaseLuidAndAttributesArray+0x15
    0xffffb1075a65f9b8 : 0xffffb28b2729a1a0 :  !du "\Registry\Machine\System\CurrentControlSet\Services\EasyAntiCheat_EOSSys"
    0xffffb1075a65f9d0 : 0xffffb28b2729a1a0 :  !du "\Registry\Machine\System\CurrentControlSet\Services\EasyAntiCheat_EOSSys"
    0xffffb1075a65f9f8 : 0xffffb28b1a5e7060 :  !da "*SYSTEM*"
    0xffffb1075a65fa48 : 0xfffff80036444efc : nt!NtClose+0xec
    0xffffb1075a65fa88 : 0xfffff8003669ca0b : nt!NtUnloadDriver+0xb
    0xffffb1075a65fab0 : 0xfffff8003669ca00 : nt!NtUnloadDriver
    0xffffb1075a65fab8 : 0xfffff80036210ef8 : nt!KiSystemServiceCopyEnd+0x28
    0xffffb1075a65fac0 : 0xffff9e8b39b9c000 :  Trap @ ffffb1075a65fac0
    0xffffb1075a65fc58 : 0xffffb1075a659000 : 0xfffff80036205fb1 : nt!SwapContext+0x3e1
    The version of EasyAntiCheat_EOS.sys that you have installed looks current...
    Code:
    21: kd> lmvm EasyAntiCheat_EOS
    Browse full module list
    start             end                 module name
    fffff802`ffc00000 fffff803`00d74000   EasyAntiCheat_EOS T (no symbols)           
        Loaded symbol image file: EasyAntiCheat_EOS.sys
        Image path: \??\C:\Program Files (x86)\EasyAntiCheat_EOS\EasyAntiCheat_EOS.sys
        Image name: EasyAntiCheat_EOS.sys
        Browse all global symbols  functions  data
        Timestamp:        Thu Nov  9 03:49:06 2023 (654C3A92)
        CheckSum:         0111D7D0
        ImageSize:        01174000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    All you can do is disable/uninstall EastAntiCheat and see whether the system is stable, or contact the vendor.
    Ok. I did steps 1-6 of @zbook's list, so I'll still post that stuff.

    - - - Updated - - -

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


    1) Run Tuneup plus > post a share link into the newest post

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

    Batch files for use in BSOD debugging


    2) Create a new restore point:

    Create System Restore Point in Windows 10



    3) Run Sea Tools for Windows Long Generic test (all drives) > post images or share links into the newest post

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

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



    4) Open administrative command prompt and copy and paste: chkdsk /b /v

    Run these chkdsk switches on all drives using the syntax: chkdsk /b /v c: or chkdsk /b /v d: or chkdsk /b /v e: , etc.

    Make sure that the chkdsk on the windows drive runs overnight while sleeping



    C:\WINDOWS\system32>chkdsk /b /v c:
    The type of the file system is NTFS.
    Cannot lock current drive.

    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: y

    Reboot as needed.



    5) After completing chkdsk /b /v on all drives run:

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

    Post a share link into the newest post.


    6) Download and install Samsung Magician: Samsung Magician Software | Samsung Semiconductor USA
    Run the software on the applicable drive(s) post images or share links:

    Drive Details
    Update software /firmware
    Diagnostic Scan > full scan
    Performance Benchmark
    Over Provisioning
    Performance Optimization




    7) The BIOS Version/Date American Megatrends Inc. F31e, 10/29/2020

    Upgrade the BIOS to the most up to date non-beta BIOS



    8) Uninstall Easy anti-cheat > monitor computer performance using Reliability Monitor:

    Easy Anti-Cheat

    View Reliability History in Windows 11 Tutorial | Windows 11 Forum



    9) For any new BSOD or unexpected shutdowns and restarts after completing all of the above steps post a new V2 share link into the newest post





    Code:
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
     Free Space: 63.4 GB
    Total Space: 476.3 GB
    File System: NTFS
          Model: Samsung SSD 980 PRO 500GB
    
          Drive: D:
     Free Space: 172.8 GB
    Total Space: 476.9 GB
    File System: NTFS
          Model: Samsung SSD 980 PRO 500GB
    
          Drive: E:
     Free Space: 207.2 GB
    Total Space: 953.9 GB
    File System: NTFS
          Model: Samsung SSD 980 PRO 1TB
    See attached. I only completed steps 1-6 because @ubuysa said the problem is easy anti-cheat. I'm going to try uninstalling it, but I'm worried that that means I won't be able to play any of the games that use this software...
    Attached Thumbnails Attached Thumbnails BSOD while sitting in a discord voice call after long Fortnite session-seagateresults.png   BSOD while sitting in a discord voice call after long Fortnite session-smdrivedetails_c.png   BSOD while sitting in a discord voice call after long Fortnite session-smdrivedetails_e.png   BSOD while sitting in a discord voice call after long Fortnite session-smdrivedetails_d.png   BSOD while sitting in a discord voice call after long Fortnite session-smdiagnosticscan_c.png  

    BSOD while sitting in a discord voice call after long Fortnite session-smdiagnosticscan_e.png   BSOD while sitting in a discord voice call after long Fortnite session-smdiagnosticscan_d.png  
    BSOD while sitting in a discord voice call after long Fortnite session Attached Files
      My Computer


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

    Nice progress.

    Run: HD Sentinel (trial version) (these tab results are instantaneous)
    Post images or share links displaying results on these tabs:
    a) Overview
    b) Temperature
    c) SMART


    For Easy anti-cheat the link posted had options for repair, uninstall, and uninstall games.
    Indicate which method(s) was/were performed.

    Upgrade the BIOS then monitor the computer for stability / instability.

    In a few days post a new V2 share link.

    If the logs are unremarkable then plan to reinstall.
      My Computer


  6. Posts : 106
    Microsoft Windows 10 Home 64-bit 19042 Multiprocessor Free
    Thread Starter
       #6

    zbook said:
    Nice progress.

    Run: HD Sentinel (trial version) (these tab results are instantaneous)
    Post images or share links displaying results on these tabs:
    a) Overview
    b) Temperature
    c) SMART


    For Easy anti-cheat the link posted had options for repair, uninstall, and uninstall games.
    Indicate which method(s) was/were performed.

    Upgrade the BIOS then monitor the computer for stability / instability.

    In a few days post a new V2 share link.

    If the logs are unremarkable then plan to reinstall.
    I just got a new series of blue screens. This time, the error is WHEA_UNCORRECTABLE_ERROR. I received the error when playing youtube videos while also running ComfyUI in the same browser to generate 1024x1024 AI images. I had about 12 tabs open. I was also in a discord call watching someone's stream.

    Should I make a new thread or can we continue here? If I need to redo some of the steps, I can definitely do so. Please let me know what those steps are.
      My Computer


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

    BSOD WHEA 124 are almost always related to malfunctioning hardware.

    Please post a new V2 share link into the newest post.

    Some steps from the earlier parts of the thread may be repeated.




    Run Tuneup plus > post a share link into the newest post

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

    Batch files for use in BSOD debugging

    Batch files for use in BSOD debugging
      My Computer


  8. Posts : 106
    Microsoft Windows 10 Home 64-bit 19042 Multiprocessor Free
    Thread Starter
       #8

    zbook said:
    BSOD WHEA 124 are almost always related to malfunctioning hardware.

    Please post a new V2 share link into the newest post.

    Some steps from the earlier parts of the thread may be repeated.




    Run Tuneup plus > post a share link into the newest post

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

    Batch files for use in BSOD debugging

    Batch files for use in BSOD debugging
    Tuneup results:

    ###########################################################
    # The following commands will be run in sequence. #
    # The first 5 will take quite a while to run, be patient. #
    ###########################################################

    sfc /scannow
    dism /online /cleanup-image /scanhealth
    dism /online /cleanup-image /restorehealth
    sfc /scannow

    chkdsk /scan

    wmic recoveros get autoreboot
    wmic recoveros set autoreboot = false
    wmic recoveros get autoreboot
    wmic recoveros get DebugInfoType
    wmic recoveros set DebugInfoType = 7
    wmic recoveros get DebugInfoType

    wmic pagefile list /format:list
    wmic Computersystem where name="DESKTOP-UK88SFT" get AutomaticManagedPagefile
    wmic Computersystem where name="DESKTOP-UK88SFT" set AutomaticManagedPagefile=True
    wmic Computersystem where name="DESKTOP-UK88SFT" get AutomaticManagedPagefile

    bcdedit /enum {badmemory}


    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.3636

    Image Version: 10.0.19045.3930

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.19041.3636

    Image Version: 10.0.19045.3930

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\WINDOWS\system32>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\WINDOWS\system32>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    1208576 file records processed.
    File verification completed.
    Phase duration (File record verification): 6.53 seconds.
    17158 large file records processed.
    Phase duration (Orphan file record recovery): 0.00 milliseconds.
    0 bad file records processed.
    Phase duration (Bad file record checking): 0.70 milliseconds.

    Stage 2: Examining file name linkage ...
    1261 reparse records processed.
    1675692 index entries processed.
    Index verification completed.
    Phase duration (Index verification): 14.26 seconds.
    0 unindexed files scanned.
    Phase duration (Orphan reconnection): 2.78 seconds.
    0 unindexed files recovered to lost and found.
    Phase duration (Orphan recovery to lost and found): 1.55 milliseconds.
    1261 reparse records processed.
    Phase duration (Reparse point and Object ID verification): 7.92 milliseconds.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    Phase duration (Security descriptor verification): 13.67 milliseconds.
    233559 data files processed.
    Phase duration (Data attribute verification): 0.39 milliseconds.
    CHKDSK is verifying Usn Journal...
    35190360 USN bytes processed.
    Usn Journal verification completed.
    Phase duration (USN journal verification): 63.14 milliseconds.

    Windows has scanned the file system and found no problems.
    No further action is required.

    487756799 KB total disk space.
    472231832 KB in 743782 files.
    472264 KB in 233560 indexes.
    0 KB in bad sectors.
    1327675 KB in use by the system.
    65536 KB occupied by the log file.
    13725028 KB available on disk.

    4096 bytes in each allocation unit.
    121939199 total allocation units on disk.
    3431257 allocation units available on disk.
    Total duration: 23.69 seconds (23694 ms).

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-UK88SFT\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get autoreboot
    AutoReboot
    FALSE


    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
    Updating property(s) of '\\DESKTOP-UK88SFT\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\WINDOWS|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic recoveros get DebugInfoType
    DebugInfoType
    7


    C:\WINDOWS\system32>wmic pagefile list /format:list


    AllocatedBaseSize=4864
    CurrentUsage=0
    Description=C:\pagefile.sys
    InstallDate=20231202001638.729824-360
    Name=C:\pagefile.sys
    PeakUsage=1
    Status=
    TempPageFile=FALSE




    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-UK88SFT" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-UK88SFT" set AutomaticManagedPagefile=True
    Updating property(s) of '\\DESKTOP-UK88SFT\ROOT\CIMV2:Win32_ComputerSystem.Name="DESKTOP-UK88SFT"'
    Property(s) update successful.

    C:\WINDOWS\system32>wmic Computersystem where name="DESKTOP-UK88SFT" get AutomaticManagedPagefile
    AutomaticManagedPagefile
    TRUE


    C:\WINDOWS\system32>bcdedit /enum {badmemory}

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

    C:\WINDOWS\system32>Echo off
    ###################################################################################
    # How to capture batch file data and post in your thread in the BSOD forum #
    # #
    # Batch files and instructions for use in BSOD debugging[Part Two-Four] #
    # #
    # Press [V] to visit the above web page for detailed instructions. #
    # Press [C] to close this window. #
    ###################################################################################
    BSOD while sitting in a discord voice call after long Fortnite session Attached Files
      My Computer


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

    1) Increase the free space on C: so that there is >30 GB free space


    2) Detach E: drive (Samsung SSD 980 PRO 1TB) > monitor the computer using reliability monitor

    View Reliability History in Windows 11 Tutorial | Windows 11 Forum

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


    Code:
    Event[12546]:
      Log Name: System
      Source: Ntfs
      Date: 2024-01-17T21:31:56.4680000Z
      Event ID: 50
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\System Volume Information\tracking.log. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\System Volume Information\tracking.log. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Mft::$BITMAP. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$BitMap. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Extend\$UsnJrnl:$J. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Extend\$UsnJrnl:$J. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Mft::$BITMAP. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.


    Code:
    Event[11948]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T18:53:04.4220000Z
      Event ID: 129
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    Reset to device, \Device\RaidPort4, was issued.
    
    Event[11949]:
      Log Name: System
      Source: disk
      Date: 2024-01-17T18:53:04.4330000Z
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
    
    Event[11950]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T18:53:04.4330000Z
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    The driver detected a controller error on \Device\RaidPort4.

    Code:
    Event[10221]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T16:58:14.5370000Z
      Event ID: 129
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    Reset to device, \Device\RaidPort2, was issued.
    
    Event[10222]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T16:58:14.5480000Z
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    The driver detected a controller error on \Device\RaidPort2.




    Drive: E:
    Free Space: 207.2 GB
    Total Space: 953.9 GB
    File System: NTFS
    Model: Samsung SSD 980 PRO 1TB
      My Computer


  10. Posts : 106
    Microsoft Windows 10 Home 64-bit 19042 Multiprocessor Free
    Thread Starter
       #10

    zbook said:
    1) Increase the free space on C: so that there is >30 GB free space


    2) Detach E: drive (Samsung SSD 980 PRO 1TB) > monitor the computer using reliability monitor

    View Reliability History in Windows 11 Tutorial | Windows 11 Forum

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


    Code:
    Event[12546]:
      Log Name: System
      Source: Ntfs
      Date: 2024-01-17T21:31:56.4680000Z
      Event ID: 50
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\System Volume Information\tracking.log. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\System Volume Information\tracking.log. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Mft::$BITMAP. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$BitMap. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Extend\$UsnJrnl:$J. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Extend\$UsnJrnl:$J. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
    Code:
    {Delayed Write Failed} Windows was unable to save all the data for the file E:\$Mft::$BITMAP. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.


    Code:
    Event[11948]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T18:53:04.4220000Z
      Event ID: 129
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    Reset to device, \Device\RaidPort4, was issued.
    
    Event[11949]:
      Log Name: System
      Source: disk
      Date: 2024-01-17T18:53:04.4330000Z
      Event ID: 51
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
    
    Event[11950]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T18:53:04.4330000Z
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    The driver detected a controller error on \Device\RaidPort4.

    Code:
    Event[10221]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T16:58:14.5370000Z
      Event ID: 129
      Task: N/A
      Level: Warning
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    Reset to device, \Device\RaidPort2, was issued.
    
    Event[10222]:
      Log Name: System
      Source: stornvme
      Date: 2024-01-17T16:58:14.5480000Z
      Event ID: 11
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-UK88SFT
      Description: 
    The driver detected a controller error on \Device\RaidPort2.




    Drive: E:
    Free Space: 207.2 GB
    Total Space: 953.9 GB
    File System: NTFS
    Model: Samsung SSD 980 PRO 1TB
    Is there a way to detach through Windows or do I need to physically detach? It would be nice if Windows could do it so that later I could reattached quickly, but if that's not possible it's all good
      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 10:35.
Find Us




Windows 10 Forums