The computer has rebooted from a bugcheck SOS

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 111
    Windows 10 PRO
    Thread Starter
       #21

    zbook said:
    Please post links without sign in or permissions.
    Sorry! My mistake:

    WIN-P8G5GE6M6SI-Tue_09_17_2019__02512_28.zip - Google Drive

    or check the attach file:
    Last edited by Thanos92; 17 Sep 2019 at 03:05.
      My Computer


  2. Posts : 39,995
    windows 10 professional version 1607 build 14393.969 64 bit
       #22

    The logs displayed one WHEA corrected hardware error.
    It then displayed many uncorrected hardware errors or WHEA 0x124 bugchecks.
    The newest bugcheck was the exception and was bugcheck 133 with parameter 1.

    The first WHEA 0x124 bugcheck was on 07/28/19.

    There were 7 mini dump bugchecks dispaying WHEA 0x124.
    These were internal parity.

    The bugchecks are consistent with malfunctioning hardware.

    There are software tests to check hardware.

    Sometimes the software may not be able to find malfunctioning hardware.

    The best testing is/are swaps.

    If you are comfortable inside the computer then you can perform the swaps with the hardware.
    If you are not comfortable inside the computer then check warranty status and /or options at a local computer store.


    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan

    7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    8) Make sure that there is no over clocking while troubleshooting.

    9) Sometimes there are problems in the bios that produce BSOD.

    The BIOS: Version/Date American Megatrends Inc. F4 HZ, 4/30/2019

    10) Please check to see if this is the most up to date version.

    11) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    12) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    13) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.
    Some of the testing may require significant continuous downtime.
    For some testing a substantial portion can be performed overnight.
    There is no software test for the motherboard.

    14) Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    Prime95 - Stress Test Your CPU
    a) Record the maximum temperature and post the maximum temperature into the thread
    b) Record test duration and post the uninterrupted test duration into the thread
    c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10

    15) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    16) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    17) Run Memtest86 version 8.2 (or newer version if available) for four passes.
    Repeat the test so that eight passes are performed.

    The computer has 64 GB RAM.
    Two RAM modules can be removed to test 32 GB at a time.

    MemTest86 - Official Site of the x86 Memory Testing Tool
    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)
    Memtest86 has a feature to produce a text report.
    Please post this in addition to the images.

    For each of the above tests please record maximum temperatures.

    18) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10


    Code:
    ===============================================================================
    Common Platform Error Record @ ffffe58cea701028
    -------------------------------------------------------------------------------
    Record Id     : 01d552cd2f149127
    Severity      : Fatal (1)
    Length        : 864
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Creator       : Microsoft
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Notify Type   : Machine Check Exception
    Timestamp     : 8/27/2019 10:03:45 (UTC)
    Flags         : 0x00000000
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe58cea7010a8
    Section       @ ffffe58cea701180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Proc. Type    : x86/x64
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Instr. Set    : x64
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Error Type    : Micro-Architectural Error
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Flags         : 0x00
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Version   : 0x00000000000906ec
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Processor ID  : 0x0000000000000002
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe58cea7010f0
    Section       @ ffffe58cea701240
    Offset        : 536
    Length        : 64
    Flags         : 0x00000000
    Severity      : Fatal
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Local APIC Id : 0x0000000000000002
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Id        : ec 06 09 00 00 08 10 02 - ff fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe58cea701138
    Section       @ ffffe58cea701280
    Offset        : 600
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Error         : Internal parity (Proc 2 Bank 0)
      Status      : 0xb200000000030005
    Code:
    Event[3682]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2019-07-16T12:46:56.538
      Event ID: 19
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: WIN-P8G5GE6M6SI
      Description: 
    A corrected hardware error has occurred.
    
    Reported by component: Processor Core
    Error Source: Corrected Machine Check
    Error Type: Cache Hierarchy Error
    Processor APIC ID: 11
    
    The details view of this entry contains further information.

    Code:
    ===============================================================================
    Common Platform Error Record @ ffffde8254cd1028
    -------------------------------------------------------------------------------
    Record Id     : 01d55d3ad83ba452
    Severity      : Fatal (1)
    Length        : 864
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Creator       : Microsoft
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Notify Type   : Machine Check Exception
    Timestamp     : 8/28/2019 18:45:03 (UTC)
    Flags         : 0x00000000
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde8254cd10a8
    Section       @ ffffde8254cd1180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Proc. Type    : x86/x64
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Instr. Set    : x64
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Error Type    : Micro-Architectural Error
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Flags         : 0x00
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Version   : 0x00000000000906ec
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Processor ID  : 0x0000000000000003
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde8254cd10f0
    Section       @ ffffde8254cd1240
    Offset        : 536
    Length        : 64
    Flags         : 0x00000000
    Severity      : Fatal
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Local APIC Id : 0x0000000000000003
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Id        : ec 06 09 00 00 08 10 03 - ff fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde8254cd1138
    Section       @ ffffde8254cd1280
    Offset        : 600
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Error         : Internal parity (Proc 3 Bank 0)
      Status      : 0xb200000000030005
      My Computer


  3. Posts : 111
    Windows 10 PRO
    Thread Starter
       #23

    Before start posting the results here tell me something! They said change me server and put the old drivers how can be have the same problem ? They change me server before 3 days!

    - - - Updated - - -

    zbook said:
    The logs displayed one WHEA corrected hardware error.
    It then displayed many uncorrected hardware errors or WHEA 0x124 bugchecks.
    The newest bugcheck was the exception and was bugcheck 133 with parameter 1.

    The first WHEA 0x124 bugcheck was on 07/28/19.

    There were 7 mini dump bugchecks dispaying WHEA 0x124.
    These were internal parity.

    The bugchecks are consistent with malfunctioning hardware.

    There are software tests to check hardware.

    Sometimes the software may not be able to find malfunctioning hardware.

    The best testing is/are swaps.

    If you are comfortable inside the computer then you can perform the swaps with the hardware.
    If you are not comfortable inside the computer then check warranty status and /or options at a local computer store.


    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan

    7) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    8) Make sure that there is no over clocking while troubleshooting.

    9) Sometimes there are problems in the bios that produce BSOD.

    The BIOS: Version/Date American Megatrends Inc. F4 HZ, 4/30/2019

    10) Please check to see if this is the most up to date version.

    11) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    12) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    Download Speccy | Find your computer specs, free!
    Download Speccy | Find your computer specs, free!
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    HWMONITOR | Softwares | CPUID
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    SpeedFan - Access temperature sensor in your computer

    13) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.
    Some of the testing may require significant continuous downtime.
    For some testing a substantial portion can be performed overnight.
    There is no software test for the motherboard.

    14) Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    Prime95 - Stress Test Your CPU
    a) Record the maximum temperature and post the maximum temperature into the thread
    b) Record test duration and post the uninterrupted test duration into the thread
    c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
    d) Use the Microsoft snipping tool to post images into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10

    15) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    16) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |
    Seagate

    How to use SeaTools for Windows | Seagate Support US

    17) Run Memtest86 version 8.2 (or newer version if available) for four passes.
    Repeat the test so that eight passes are performed.

    The computer has 64 GB RAM.
    Two RAM modules can be removed to test 32 GB at a time.

    MemTest86 - Official Site of the x86 Memory Testing Tool
    Use a camera or smart phone camera to take pictures and post images into the thread.
    In case there are any problems uploading images use share links (one drive, drop box, or google drive)
    Memtest86 has a feature to produce a text report.
    Please post this in addition to the images.

    For each of the above tests please record maximum temperatures.

    18) And please make sure that you use the Microsoft snipping tool to post images of each into the thread.
    Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
    Take Screenshot in Windows 10


    Code:
    ===============================================================================
    Common Platform Error Record @ ffffe58cea701028
    -------------------------------------------------------------------------------
    Record Id     : 01d552cd2f149127
    Severity      : Fatal (1)
    Length        : 864
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Creator       : Microsoft
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Notify Type   : Machine Check Exception
    Timestamp     : 8/27/2019 10:03:45 (UTC)
    Flags         : 0x00000000
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe58cea7010a8
    Section       @ ffffe58cea701180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Proc. Type    : x86/x64
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Instr. Set    : x64
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Error Type    : Micro-Architectural Error
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Flags         : 0x00
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Version   : 0x00000000000906ec
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Processor ID  : 0x0000000000000002
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe58cea7010f0
    Section       @ ffffe58cea701240
    Offset        : 536
    Length        : 64
    Flags         : 0x00000000
    Severity      : Fatal
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Local APIC Id : 0x0000000000000002
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Id        : ec 06 09 00 00 08 10 02 - ff fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffe58cea701138
    Section       @ ffffe58cea701280
    Offset        : 600
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    fffff80353787e08: Unable to get Flags value from nt!KdVersionBlock
    Error         : Internal parity (Proc 2 Bank 0)
      Status      : 0xb200000000030005
    Code:
    Event[3682]:
      Log Name: System
      Source: Microsoft-Windows-WHEA-Logger
      Date: 2019-07-16T12:46:56.538
      Event ID: 19
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-19
      User Name: NT AUTHORITY\LOCAL SERVICE
      Computer: WIN-P8G5GE6M6SI
      Description: 
    A corrected hardware error has occurred.
    
    Reported by component: Processor Core
    Error Source: Corrected Machine Check
    Error Type: Cache Hierarchy Error
    Processor APIC ID: 11
    
    The details view of this entry contains further information.

    Code:
    ===============================================================================
    Common Platform Error Record @ ffffde8254cd1028
    -------------------------------------------------------------------------------
    Record Id     : 01d55d3ad83ba452
    Severity      : Fatal (1)
    Length        : 864
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Creator       : Microsoft
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Notify Type   : Machine Check Exception
    Timestamp     : 8/28/2019 18:45:03 (UTC)
    Flags         : 0x00000000
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde8254cd10a8
    Section       @ ffffde8254cd1180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Proc. Type    : x86/x64
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Instr. Set    : x64
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Error Type    : Micro-Architectural Error
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Flags         : 0x00
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Version   : 0x00000000000906ec
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Processor ID  : 0x0000000000000003
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde8254cd10f0
    Section       @ ffffde8254cd1240
    Offset        : 536
    Length        : 64
    Flags         : 0x00000000
    Severity      : Fatal
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Local APIC Id : 0x0000000000000003
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Id        : ec 06 09 00 00 08 10 03 - ff fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffde8254cd1138
    Section       @ ffffde8254cd1280
    Offset        : 600
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803662f8e08: Unable to get Flags value from nt!KdVersionBlock
    Error         : Internal parity (Proc 3 Bank 0)
      Status      : 0xb200000000030005



      My Computer


  4. Posts : 39,995
    windows 10 professional version 1607 build 14393.969 64 bit
       #24

    Thanos92 said:
    Before start posting the results here tell me something! They said change me server and put the old drivers how can be have the same problem ? They change me server before 3 days!

    - - - Updated - - -






    The BSOD have been happening for 2 months.
    There were no misbehaving drivers seen in the debugging.

    If there are no important files you can perform a "vanilla" clean install and check for stability / instability.
      My Computer


  5. Posts : 111
    Windows 10 PRO
    Thread Starter
       #25

    zbook said:
    The BSOD have been happening for 2 months.
    There were no misbehaving drivers seen in the debugging.

    If there are no important files you can perform a "vanilla" clean install and check for stability / instability.
    For now i can post this results:

    Code:
    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /scanhealth
    4) dism /online /cleanup-image /restorehealth
    5) sfc /scannow
    6) chkdsk /scan
    
    
    Results:
    
    
    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    
    
    C:\Users\Administrator> sfc /scannow
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    
    
    C:\Users\Administrator>dism /online /cleanup-image /scanhealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085
    
    
    Image Version: 10.0.14393.3085
    
    
    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.
    
    
    C:\Users\Administrator>dism /online /cleanup-image /restorehealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085
    
    
    Image Version: 10.0.14393.3085
    
    
    [==========================100.0%==========================]
    Error: 0x800f081f
    
    
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    
    C:\Users\Administrator>sfc /scannow
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    
    
    C:\Users\Administrator>chkdsk /scan
    The type of the file system is NTFS.
    
    
    Stage 1: Examining basic file system structure ...
      525824 file records processed.
    File verification completed.
      19401 large file records processed.
      0 bad file records processed.
    
    
    Stage 2: Examining file name linkage ...
      725486 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
    
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      99832 data files processed.
    CHKDSK is verifying Usn Journal...
      41517848 USN bytes processed.
    Usn Journal verification completed.
    
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
    
     999623679 KB total disk space.
     281794352 KB in 325855 files.
        238428 KB in 99833 indexes.
             0 KB in bad sectors.
        663855 KB in use by the system.
         65536 KB occupied by the log file.
     716927044 KB available on disk.
    
    
          4096 bytes in each allocation unit.
     249905919 total allocation units on disk.
     179231761 allocation units available on disk.
    
    
    C:\Users\Administrator>
    Attachment 247743Attachment 247744Attachment 247745
      My Computer


  6. Posts : 39,995
    windows 10 professional version 1607 build 14393.969 64 bit
       #26

    Code:
    Windows Resource Protection found corrupt files but was unable to fix some
    of them.
    Code:
    The source files could not be found.
    1) See if you can clean install the server operating system:

    Windows Server Catalog

    2) Download and install Samsung Magician > post images for the results

    Samsung Magician Software | Samsung V-NAND SSD | Samsung Semiconductor Global Website

    3) Open task manager (ctrl +alt + del) > post an image into the thread

    4) During HD Tune CPU was 100%.
    If possible perform the testing in safe mode.

    5) Run HD Sentinel: (free or trial edition)
    Hard Disk Sentinel - HDD health and temperature monitoring
    Hard Disk Sentinel - HDD health and temperature monitoring
    Post images of each of these tabs into the thread:
    Overview tab
    Temperature
    SMART
    Disk performance

    6) Run Crystal Disk (standard edition)
    CrystalDiskInfo – Crystal Dew World
    Post images into the thread.
      My Computer


  7. Posts : 111
    Windows 10 PRO
    Thread Starter
       #27
      My Computer


  8. Posts : 39,995
    windows 10 professional version 1607 build 14393.969 64 bit
       #28

    Open administrative powershell and copy and paste:
    Get-Disk
    Get-PhysicalDisk
    Get-Partition

    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    The bugcheck was
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred.


    When available update the progress with the steps in post #25



    Code:
    2: kd> !errrec ffffc406b04d8028
    ===============================================================================
    Common Platform Error Record @ ffffc406b04d8028
    -------------------------------------------------------------------------------
    Record Id     : 01d56ce8c730989e
    Severity      : Fatal (1)
    Length        : 864
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Creator       : Microsoft
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Notify Type   : Machine Check Exception
    Timestamp     : 9/18/2019 0:26:01 (UTC)
    Flags         : 0x00000000
    
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc406b04d80a8
    Section       @ ffffc406b04d8180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Proc. Type    : x86/x64
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Instr. Set    : x64
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Error Type    : Micro-Architectural Error
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Flags         : 0x00
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Version   : 0x00000000000906ed
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Processor ID  : 0x0000000000000002
    
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc406b04d80f0
    Section       @ ffffc406b04d8240
    Offset        : 536
    Length        : 64
    Flags         : 0x00000000
    Severity      : Fatal
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Local APIC Id : 0x0000000000000002
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    CPU Id        : ed 06 09 00 00 08 10 02 - ff fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffffc406b04d8138
    Section       @ ffffc406b04d8280
    Offset        : 600
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    fffff803aa2f9e08: Unable to get Flags value from nt!KdVersionBlock
    Error         : Internal parity (Proc 2 Bank 0)
      Status      : 0xb200000000030005
      My Computer


  9. Posts : 111
    Windows 10 PRO
    Thread Starter
       #29

    Done:

    Code:
    Windows PowerShell
    Copyright (C) 2016 Microsoft Corporation. All rights reserved.
    
    
    PS C:\Users\Administrator> Get-Disk
    >> Get-PhysicalDisk
    >> Get-Partition
    
    
    FriendlyName               SerialNumber         CanPool OperationalStatus HealthStatus Usage            Size
    ------------               ------------         ------- ----------------- ------------ -----            ----
    SAMSUNG MZVLB1T0HALR-00000 0025_3885_91BA_857B. False   OK                Healthy      Auto-Select 953.87 GB
    SAMSUNG MZVLB1T0HALR-00000 0025_3885_91BA_856E. False   OK                Healthy      Auto-Select 953.87 GB
    
    
    
    
    PS C:\Users\Administrator>
    Code:
    Microsoft Windows [Version 10.0.14393]
    (c) 2016 Microsoft Corporation. All rights reserved.
    
    
    C:\Users\Administrator>sfc /scannow
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    
    
    C:\Users\Administrator>dism /online /cleanup-image /scanhealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085
    
    
    Image Version: 10.0.14393.3085
    
    
    [==========================100.0%==========================] The component store is repairable.
    The operation completed successfully.
    
    
    C:\Users\Administrator>dism /online /cleanup-image /restorehealth
    
    
    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085
    
    
    Image Version: 10.0.14393.3085
    
    
    [==========================100.0%==========================]
    Error: 0x800f081f
    
    
    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
    
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    
    C:\Users\Administrator>sfc /scannow
    
    
    Beginning system scan.  This process will take some time.
    
    
    Beginning verification phase of system scan.
    Verification 100% complete.
    
    
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    
    
    C:\Users\Administrator>chkdsk /scan
    The type of the file system is NTFS.
    
    
    Stage 1: Examining basic file system structure ...
      525824 file records processed.
    File verification completed.
      19530 large file records processed.
      0 bad file records processed.
    
    
    Stage 2: Examining file name linkage ...
      725294 index entries processed.
    Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
    
    
    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
      99736 data files processed.
    CHKDSK is verifying Usn Journal...
      37418264 USN bytes processed.
    Usn Journal verification completed.
    
    
    Windows has scanned the file system and found no problems.
    No further action is required.
    
    
     999623679 KB total disk space.
     297834016 KB in 337189 files.
        244412 KB in 99737 indexes.
             0 KB in bad sectors.
        659771 KB in use by the system.
         65536 KB occupied by the log file.
     700885480 KB available on disk.
    
    
          4096 bytes in each allocation unit.
     249905919 total allocation units on disk.
     175221370 allocation units available on disk.
    
    
    C:\Users\Administrator>
    Last edited by Thanos92; 18 Sep 2019 at 01:03.
      My Computer


  10. Posts : 39,995
    windows 10 professional version 1607 build 14393.969 64 bit
       #30

    When available please update the steps in post #26.
      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:18.
Find Us




Windows 10 Forums