Constant BSOD crashes

Page 4 of 11 FirstFirst ... 23456 ... LastLast

  1. Posts : 47
    Windos 10 x64
    Thread Starter
       #31

    By disk system you mean the SSD?
    If its the RAM - i have checked it and it came out clean :/
    If its the SSD, i'll perform the check today using the provided links...
      My Computer


  2. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #32

    DarthLordZuko said:
    By disk system you mean the SSD?
    If its the RAM - i have checked it and it came out clean :/
    If its the SSD, i'll perform the check today using the provided links...
    Yes, I did mean the SSD or any drive that you use for virtual RAM. Sometimes people plug in a USB drive to do this.
      My Computers


  3. Posts : 47
    Windos 10 x64
    Thread Starter
       #33

    Will check the SSD, I did use the ADATA toolbox (since it's an ADATA ssd) but that wasn't really thorough... so I'll use what was recommended in post 3 or 4
      My Computer


  4. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #34

    DarthLordZuko said:
    Will check the SSD, I did use the ADATA toolbox (since it's an ADATA ssd) but that wasn't really thorough... so I'll use what was recommended in post 3 or 4
    Post #6 had the details for drive testing.
      My Computers


  5. Posts : 47
    Windos 10 x64
    Thread Starter
       #35

    Attached is the error scan from HD Tune, No errors found.

    Attachment 303957

    What is interesting to me is that I saw another thread on the forum with an X570 Prime motherboard who is having similar problems as mine..
    Which leads me to believe... that if all the hardware is turning out okay in these tests...

    Can it be the motherboard that is the culprit to all these BSODS?

    I did update the bios to the recent bios version (from a few days ago)
    but heck! even that's not stopping it...

    Just a quick edit -
    I don't know why there are so many partitions to the ssd itself,
    I'm guessing one of them is a backup of windows before I formatted it...
    in order to get rid of all of these partitions I'll have to format the computer anyway, correct?
      My Computer


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

    1) Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
    Disk Management - How to Post a Screenshot of

    2) Download and install Minitool Partition Wizard > click launch > post an image of the results into this thread
    MiniTool Partition Wizard Free Edition - Free download and software reviews - CNET Download
    MiniTool Portable Partition Magic Brings Easier Disk Management

    3) DiskParInfo.bat - Click here to go to the BSOD batch repository to download and run this batch file.

    4) Upload a new V2:
    BSOD - Posting Instructions
      My Computer


  7. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #37

    Just a quick edit -
    I don't know why there are so many partitions to the ssd itself,
    I'm guessing one of them is a backup of windows before I formatted it...
    in order to get rid of all of these partitions I'll have to format the computer anyway, correct?
    I would not delete any of those partitions at the moment. Basically there is a recovery partition as the first partition (this might be the original one set by the manufacturer or from an earlier version of Windows), then two system partitions (100MB and 16MB) required by Windows; then your C: drive and finally the windows recovery partition which is now always added to the end so that it can grow as needed.

    This tutorial will give you some explanation of what you have:
    How to Delete Recovery Partition in Windows 10
      My Computers


  8. Posts : 47
    Windos 10 x64
    Thread Starter
       #38

    Thanks for sticking with me guys -
    So another crash this morning, and again the dump is useless... (There was a windows update and it didn't fix the dump situation...)

    Ran all of the things you required, and attaching them to the drive folder of all the logs...
    There are 2 logs, one after another, one after the BSOD and one after running that .bat file...

    Link to the folder:
    Link

    Attaching the disk management screenshot:
    Attachment 304078

    And the DiskParInfo log (which is also in the folder):
    Code:
        Disk 0 is an SSD. It has 5 partition(s). Model: XPG SPECTRIX S40G  
    
        This computer has the above 1 fixed storage device(s) in total.
    =======================================================================
    
    Microsoft DiskPart version 10.0.19041.610
    
    Copyright (C) Microsoft Corporation.
    On computer: DESKTOP-761T659
    
      Disk ###  Status         Size     Free     Dyn  Gpt
      --------  -------------  -------  -------  ---  ---
      Disk 0    Online          953 GB  1024 KB        *
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0         ???????      NTFS   Partition    529 MB  Healthy            
      Volume 1     C                NTFS   Partition    952 GB  Healthy    Boot    
      Volume 2                      NTFS   Partition    527 MB  Healthy            
      Volume 3                      FAT32  Partition    100 MB  Healthy    System  
    
    Disk 0 is now the selected disk.
    
    XPG SPECTRIX S40G
    Disk ID: {706B6BD8-B978-4730-8228-461454B7F5A6}
    Type   : NVMe
    Status : Online
    Path   : 0
    Target : 0
    LUN ID : 0
    Location Path : PCIROOT(0)#PCI(0101)#PCI(0000)#NVME(P00T00L00)
    Current Read-only State : No
    Read-only  : No
    Boot Disk  : Yes
    Pagefile Disk  : Yes
    Hibernation File Disk  : No
    Crashdump Disk  : Yes
    Clustered Disk  : No
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0         ???????      NTFS   Partition    529 MB  Healthy            
      Volume 1     C                NTFS   Partition    952 GB  Healthy    Boot    
      Volume 2                      NTFS   Partition    527 MB  Healthy            
      Volume 3                      FAT32  Partition    100 MB  Healthy    System  
    
      Partition ###  Type              Size     Offset
      -------------  ----------------  -------  -------
      Partition 1    Recovery           529 MB  1024 KB
      Partition 2    System             100 MB   530 MB
      Partition 3    Reserved            16 MB   630 MB
      Partition 4    Primary            952 GB   646 MB
      Partition 5    Recovery           527 MB   953 GB
    
    Partition 1 is now the selected partition.
    
    Partition 1
    Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
    Hidden  : Yes
    Required: Yes
    Attrib  : 0X8000000000000001
    Offset in Bytes: 1048576
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 4         ???????      NTFS   Partition    529 MB  Healthy    Hidden  
    
    Partition 2 is now the selected partition.
    
    Partition 2
    Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
    Hidden  : Yes
    Required: No
    Attrib  : 0X8000000000000000
    Offset in Bytes: 555745280
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 3                      FAT32  Partition    100 MB  Healthy    System  
    
    Partition 3 is now the selected partition.
    
    Partition 3
    Type    : e3c9e316-0b5c-4db8-817d-f92df00215ae
    Hidden  : Yes
    Required: No
    Attrib  : 0X8000000000000000
    Offset in Bytes: 660602880
    
    There is no volume associated with this partition.
    
    Partition 4 is now the selected partition.
    
    Partition 4
    Type    : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
    Hidden  : No
    Required: No
    Attrib  : 0000000000000000
    Offset in Bytes: 677380096
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 1     C                NTFS   Partition    952 GB  Healthy    Boot    
    
    Partition 5 is now the selected partition.
    
    Partition 5
    Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac
    Hidden  : Yes
    Required: Yes
    Attrib  : 0X8000000000000001
    Offset in Bytes: 1023655542784
    
      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
    * Volume 5                      NTFS   Partition    527 MB  Healthy    Hidden  
    
    ===============================================================================
    
    Windows Recovery Environment (Windows RE) and system reset configuration
    Information:
    
        Windows RE status:         Enabled
        Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
        Boot Configuration Data (BCD) identifier: 2384c0ad-e1d6-11ea-a8e4-c644cc2cfbef
        Recovery image location:   
        Recovery image index:      0
        Custom image location:     
        Custom image index:        0
    
    REAGENTC.EXE: Operation Successful.
        
    ===============================================================================
    
    Firmware Boot Manager
    ---------------------
    identifier              {fwbootmgr}
    displayorder            {bootmgr}
                            {2ae8b5ef-168e-11eb-8e30-806e6f6e6963}
                            {2ae8b5f0-168e-11eb-8e30-806e6f6e6963}
                            {2ae8b5f1-168e-11eb-8e30-806e6f6e6963}
                            {5d75f3b0-181f-11eb-8e33-806e6f6e6963}
                            {5d75f3b1-181f-11eb-8e33-806e6f6e6963}
    timeout                 1
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    flightsigning           Yes
    default                 {current}
    resumeobject            {2384c0ab-e1d6-11ea-a8e4-c644cc2cfbef}
    displayorder            {current}
    toolsdisplayorder       {memdiag}
    timeout                 0
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {2ae8b5ef-168e-11eb-8e30-806e6f6e6963}
    device                  unknown
    description             UEFI: SanDisk, Partition 1
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {2ae8b5f0-168e-11eb-8e30-806e6f6e6963}
    device                  unknown
    description             UEFI: SanDisk, Partition 2
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {2ae8b5f1-168e-11eb-8e30-806e6f6e6963}
    description             UEFI:CD/DVD Drive
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {5d75f3b0-181f-11eb-8e33-806e6f6e6963}
    description             UEFI:Removable Device
    
    Firmware Application (101fffff)
    -------------------------------
    identifier              {5d75f3b1-181f-11eb-8e33-806e6f6e6963}
    description             UEFI:Network Device
    
    Windows Boot Loader
    -------------------
    identifier              {current}
    device                  partition=C:
    path                    \Windows\system32\winload.efi
    description             Windows 10
    locale                  en-US
    inherit                 {bootloadersettings}
    recoverysequence        {2384c0ad-e1d6-11ea-a8e4-c644cc2cfbef}
    displaymessageoverride  Recovery
    recoveryenabled         Yes
    isolatedcontext         Yes
    flightsigning           Yes
    allowedinmemorysettings 0x15000075
    osdevice                partition=C:
    systemroot              \Windows
    resumeobject            {2384c0ab-e1d6-11ea-a8e4-c644cc2cfbef}
    nx                      OptIn
    bootmenupolicy          Standard
    hypervisorlaunchtype    Auto
    useplatformclock        No
    
    Windows Boot Loader
    -------------------
    identifier              {2384c0ad-e1d6-11ea-a8e4-c644cc2cfbef}
    device                  ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{2384c0ae-e1d6-11ea-a8e4-c644cc2cfbef}
    path                    \windows\system32\winload.efi
    description             Windows Recovery Environment
    locale                  en-us
    inherit                 {bootloadersettings}
    displaymessage          Recovery
    osdevice                ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{2384c0ae-e1d6-11ea-a8e4-c644cc2cfbef}
    systemroot              \windows
    nx                      OptIn
    bootmenupolicy          Standard
    winpe                   Yes
    
    Resume from Hibernate
    ---------------------
    identifier              {2384c0ab-e1d6-11ea-a8e4-c644cc2cfbef}
    device                  partition=C:
    path                    \Windows\system32\winresume.efi
    description             Windows Resume Application
    locale                  en-US
    inherit                 {resumeloadersettings}
    recoverysequence        {2384c0ad-e1d6-11ea-a8e4-c644cc2cfbef}
    recoveryenabled         Yes
    isolatedcontext         Yes
    allowedinmemorysettings 0x15000075
    filedevice              partition=C:
    filepath                \hiberfil.sys
    bootmenupolicy          Standard
    debugoptionenabled      No
    
    Windows Memory Tester
    ---------------------
    identifier              {memdiag}
    device                  partition=\Device\HarddiskVolume2
    path                    \EFI\Microsoft\Boot\memtest.efi
    description             Windows Memory Diagnostic
    locale                  en-US
    inherit                 {globalsettings}
    badmemoryaccess         Yes
    
    EMS Settings
    ------------
    identifier              {emssettings}
    bootems                 No
    
    Debugger Settings
    -----------------
    identifier              {dbgsettings}
    debugtype               Local
    
    RAM Defects
    -----------
    identifier              {badmemory}
    
    Global Settings
    ---------------
    identifier              {globalsettings}
    inherit                 {dbgsettings}
                            {emssettings}
                            {badmemory}
    
    Boot Loader Settings
    --------------------
    identifier              {bootloadersettings}
    inherit                 {globalsettings}
                            {hypervisorsettings}
    
    Hypervisor Settings
    -------------------
    identifier              {hypervisorsettings}
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200
    
    Resume Loader Settings
    ----------------------
    identifier              {resumeloadersettings}
    inherit                 {globalsettings}
    
    Device options
    --------------
    identifier              {2384c0ae-e1d6-11ea-a8e4-c644cc2cfbef}
    description             Windows Recovery
    ramdisksdidevice        partition=C:
    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    I did not run the required software Minitool Partition Wizard since after downloading the .exe Windows Defender went all "nah uh" on me and said there was malware in the file...


    Last thoughts:
    About the eiffiy dump files, I did run the -
    Please run: Tuneup.bat - Click here to go to the BSOD batch repository to download and run this batch file.
    3-4 days ago, can that maybe point to the problems with the dump files?


    Currently running OCCT for an hour, I'll update this post if no one replies with the results :)

    - - - Updated - - -

    OCCT results: no errors detected... ran for 1 hour.

    Attachment 304081

    Another crash... updated the drive folder with the new log...
    Dump is still a mess
    Last edited by DarthLordZuko; 30 Oct 2020 at 07:42.
      My Computer


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

    Run: LOGS.bat - Click here to go to the BSOD batch repository to download and run this batch file.


    The extra partition is < 1 GB.
    There is no significant benefit in modifying it.
      My Computer


  10. Posts : 47
    Windos 10 x64
    Thread Starter
       #40

    Ran Logs.bat - uploaded it to the google-drive folder,
    Link to Log.zip
    Link to Folder
      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 08:13.
Find Us




Windows 10 Forums