none
Windows 10 keeps crashing

    Question

  • I'm looking thrugh crash dumps but they seem somewhtat random. What I see most often is the below. I can't find a pattern to what might be causing the crashes. I checked the CPU with the Intel utility and it didn't fine any issues.

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffc1010334c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    ffffd480`d248bbe8 fffff802`08a4c520 : 00000000`00000124 00000000`00000000 ffffc101`0334c028 00000000`be000000 : nt!KeBugCheckEx
    ffffd480`d248bbf0 fffff807`f2ea14ba : ffffc101`0334c028 ffffc101`02908640 ffffc101`02908640 ffffc101`02908640 : hal!HalBugCheckSystem+0xd0
    ffffd480`d248bc30 fffff802`08d57d61 : ffffc101`0334c028 00000000`00000000 ffffc101`02908640 ffffc101`02908640 : PSHED!PshedBugCheckSystem+0xa
    ffffd480`d248bc60 fffff802`08a4dc60 : 00000000`00000728 00000000`00000007 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
    ffffd480`d248bcc0 fffff802`08a4dfc0 : 00000000`00000010 ffffc101`02908690 ffffd480`d248be68 00000000`00000007 : hal!HalpMcaReportError+0x50
    ffffd480`d248be10 fffff802`08a4deae : ffffc101`029080e0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
    ffffd480`d248be60 fffff802`08a4e0f2 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    ffffd480`d248bea0 fffff802`08a4e390 : ffffc101`029080e0 ffffd480`d248c0d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    ffffd480`d248bed0 fffff802`08c50c3b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffffd480`d248bf00 fffff802`08c508ff : 00000000`00000000 fffff802`08c5087e 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd480`d248c040 fffff807`f61313f3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1bf
    fffffc8d`e627d6e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!MWaitIdle+0x23
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    Followup: MachineOwner


    yaro

    Monday, December 3, 2018 5:43 PM

Answers

  • All of the mini dumps when debugged displayed WHEA 0 x 124.

    These are typically due to malfunctioning hardware.

    There are tests/steps below and more tests to follow to systematically check the hardware.

    For all tests /steps please post images / results into the thread using one drive, drop box, or google drive share links.

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) 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

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

    7) Sometimes there are problems in the bios that produce bsod.
    The BIOS: BIOS Version/Date    American Megatrends Inc. F7, 9/18/2015
    8) Please check to see if this is the most up to date non-beta version.

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

    a) Indicate the version for the motherboard:  Z97X-Gaming 3

    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) Backup the computer files to another drive or to the cloud.
    13) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    https://www.macrium.com/reflectfree

    14) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    https://www.howtogeek.com/131623/how-to-clear-your-computers-cmos-to-reset-bios-settings/
    3 Ways to Reset Your BIOS - wikiHow:
    http://www.wikihow.com/Reset-Your-BIOS

    15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread.

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    16) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab > scroll down to system and advanced > post an image into the thread

    17) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.

    18) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    https://www.piriform.com/speccy
    https://www.ccleaner.com/speccy
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    http://www.cpuid.com/softwares/hwmonitor.html
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    http://www.almico.com/speedfan.php

    19) Check the RAM to determine whether it is DDR3 or DDR4.

    If the RAM is DDR3 then run memtest86+ version 5.01 for at least 8 passes.

    http://www.memtest.org/

    If the RAM is DDR4 then run memtest86 version 8.0 for at least 8 passes.

    https://www.memtest86.com/

    The testing is done not by time but by passes.
    The more passes the better the testing conditions.

    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM

    A substantial portion of the testing can be performed overnight.

    Testing must be continuous.

    Just 1 error is a fail and you can abort testing.

    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.

    https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461
    https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

    20) Run HD Tune (free edition) (all drives)

    https://www.hdtune.com/

    Post images for test results on these tabs:

    b) Health (SMART)

    c) Benchmark

    d) Full error scan

    .

    .

    .

    .

    .

    .

    .

    ===============================================================================
    Common Platform Error Record @ ffff998490551028
    -------------------------------------------------------------------------------
    Record Id     : 01d49575bbf4ab6c
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/16/2018 19:30:35 (UTC)
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffff9984905510a8
    Section       @ ffff998490551180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306c3
    Processor ID  : 0x0000000000000000

    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffff9984905510f0
    Section       @ ffff998490551240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id        : c3 06 03 00 00 08 10 00 - bf 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

    Proc. Info 0  @ ffff998490551240

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffff998490551138
    Section       @ ffff9984905512c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal

    Error         : Internal timer (Proc 0 Bank 4)
      Status      : 0xbe00000000800400
      Address     : 0xfffff80136fa2426
      Misc.       : 0xfffff80136fa2426


    Monday, December 17, 2018 4:02 AM

All replies

  • For a moment I thought it might be the CPU overheating as when I installed HWiNFO it was showing the CPU cores going to 99C in red. I run a CPU stress test Which kept the CPU at this temerature for a while and no crash happened. Some time later however there was another one. This time pointing to a diferent driver. Each crash mentiones MODULE_NAME: GenuineIntel though.

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffc70813b4c028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  WmiPrvSE.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    ffffb580`b448bbe8 fffff802`9d258520 : 00000000`00000124 00000000`00000000 ffffc708`13b4c028 00000000`be000000 : nt!KeBugCheckEx
    ffffb580`b448bbf0 fffff802`95ea14ba : ffffc708`13b4c028 ffffc708`13109640 ffffc708`13109640 ffffc708`13109640 : hal!HalBugCheckSystem+0xd0
    ffffb580`b448bc30 fffff802`9d563d61 : ffffc708`13b4c028 00000000`00000000 ffffc708`13109640 ffffc708`13109640 : PSHED!PshedBugCheckSystem+0xa
    ffffb580`b448bc60 fffff802`9d259c60 : 00000000`00000728 00000000`00000007 00000000`00000000 00000000`00000000 : nt!WheaReportHwError+0x261
    ffffb580`b448bcc0 fffff802`9d259fc0 : 00000000`00000010 ffffc708`13109690 ffffb580`b448be68 00000000`00000007 : hal!HalpMcaReportError+0x50
    ffffb580`b448be10 fffff802`9d259eae : ffffc708`131090e0 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerCore+0xe0
    ffffb580`b448be60 fffff802`9d25a0f2 : 00000000`00000008 00000000`00000001 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xda
    ffffb580`b448bea0 fffff802`9d25a390 : ffffc708`131090e0 ffffb580`b448c0d0 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0xce
    ffffb580`b448bed0 fffff802`9d45cc3b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    ffffb580`b448bf00 fffff802`9d45c8ff : 00000000`00000000 fffff802`9d45c817 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffb580`b448c040 fffff802`9d3d2869 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x1bf
    ffff968e`84d39b40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeFlushProcessWriteBuffers+0x9d
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    Followup: MachineOwner


    yaro

    Tuesday, December 11, 2018 8:54 PM
  • The OS just keeps crushing where from the dumps only the PROCESS_Name keeps changing. Anyone anything?

    yaro

    Sunday, December 16, 2018 5:05 PM
  • To evaluate the BSOD please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There are two files for you to find manually:

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

    b) dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

    Please remember to vote and to mark the replies as answers if they help.

    Sunday, December 16, 2018 5:09 PM
  • I uploaded the files into my Dropbox. It seems like my minidumps get overvwitten as my PC crashed like 6 times today and in the Minidump folder I see only 3 most recent.

    yaro

    Sunday, December 16, 2018 7:44 PM
  • All of the mini dumps when debugged displayed WHEA 0 x 124.

    These are typically due to malfunctioning hardware.

    There are tests/steps below and more tests to follow to systematically check the hardware.

    For all tests /steps please post images / results into the thread using one drive, drop box, or google drive share links.

    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) 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

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

    7) Sometimes there are problems in the bios that produce bsod.
    The BIOS: BIOS Version/Date    American Megatrends Inc. F7, 9/18/2015
    8) Please check to see if this is the most up to date non-beta version.

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

    a) Indicate the version for the motherboard:  Z97X-Gaming 3

    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) Backup the computer files to another drive or to the cloud.
    13) Make a backup image using Macrium:
    Macrium Software | Macrium Reflect Free:
    https://www.macrium.com/reflectfree

    14) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    https://www.howtogeek.com/131623/how-to-clear-your-computers-cmos-to-reset-bios-settings/
    3 Ways to Reset Your BIOS - wikiHow:
    http://www.wikihow.com/Reset-Your-BIOS

    15) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread.

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

    16) If the computer has Ccleaner (do not install the software if it is not already installed) > click windows tab > scroll down to system and advanced > post an image into the thread

    17) When testing for WHEA hardware errors we need to systematically check CPU, GPU, RAM and drive.

    18) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    https://www.piriform.com/speccy
    https://www.ccleaner.com/speccy
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    http://www.cpuid.com/softwares/hwmonitor.html
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    http://www.almico.com/speedfan.php

    19) Check the RAM to determine whether it is DDR3 or DDR4.

    If the RAM is DDR3 then run memtest86+ version 5.01 for at least 8 passes.

    http://www.memtest.org/

    If the RAM is DDR4 then run memtest86 version 8.0 for at least 8 passes.

    https://www.memtest86.com/

    The testing is done not by time but by passes.
    The more passes the better the testing conditions.

    There is 16 GB of RAM on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM

    A substantial portion of the testing can be performed overnight.

    Testing must be continuous.

    Just 1 error is a fail and you can abort testing.

    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.
    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.

    https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461
    https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html

    20) Run HD Tune (free edition) (all drives)

    https://www.hdtune.com/

    Post images for test results on these tabs:

    b) Health (SMART)

    c) Benchmark

    d) Full error scan

    .

    .

    .

    .

    .

    .

    .

    ===============================================================================
    Common Platform Error Record @ ffff998490551028
    -------------------------------------------------------------------------------
    Record Id     : 01d49575bbf4ab6c
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 12/16/2018 19:30:35 (UTC)
    Flags         : 0x00000000

    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ ffff9984905510a8
    Section       @ ffff998490551180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal

    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000306c3
    Processor ID  : 0x0000000000000000

    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ ffff9984905510f0
    Section       @ ffff998490551240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal

    Local APIC Id : 0x0000000000000000
    CPU Id        : c3 06 03 00 00 08 10 00 - bf 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

    Proc. Info 0  @ ffff998490551240

    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ ffff998490551138
    Section       @ ffff9984905512c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal

    Error         : Internal timer (Proc 0 Bank 4)
      Status      : 0xbe00000000800400
      Address     : 0xfffff80136fa2426
      Misc.       : 0xfffff80136fa2426


    Monday, December 17, 2018 4:02 AM
  • The PC went so bad I coudn't even reply properly as it now hangs after a couple of minutes. Anyway, all the tests above came clean, no RAM related errors, no disk errors, corrected Recovery options not to overwrite old minidumps, HD Tune all good, Intel CPU diagnostics fine, even burn in test somehow managed to get to the end. After all the testing the hangs started. One thing that was wisible in a few tests, including MemTest was that the CPU was hot all the time as mentioned before. I started looking for max operation temp for this particular CPU and it turns it should be getting over 70C where in my case this is when idle. I ordered some thermal paste to re-apply and we'll see then.

    yaro

    Wednesday, December 19, 2018 9:31 AM
  • For all tests / steps please post images of the results into the thread.
    Wednesday, December 19, 2018 3:10 PM
  • Sorry for the delay. I uploaded more pictures to dropbox link I shared above. I tested RAM chips separatelly each in it's bank while other removed. No errors found. SDD that I keep the system on seems fine. The freezes I mentioned seem to have been related to the Intel graphics card driver. I tried uninstalling it including deleteng the files but it just kept coming back not sure how. I have the option of Device Installation Settings set to No yet for some reason the driver installs itself back after a while, replacing the basic graphics driver. I installed a diferend card and disabled the Intel one in the BIOS. Interestingly the OS recognised the new card and installed it's drivers. Who knows.... Anyway, so far no freezes but too early to say anything regarding the crashes as I just came back home after Christmas holiday. I'll give it a while and update when it crashes again.

    yaro

    Thursday, December 27, 2018 7:15 PM
  • 1) Threads can grow with many posts and time may be spent looking for links instead of troubleshooting the contents of the link.  Please post new information into the newest post so that the link is easily found.

    2) For startup and recovery system failure:

    a) uncheck automatically restart

    b) reboot to maintain settings

    It can be easy to miss BSOD when automatically restart is checked.

    When automatically restart is unchecked and there is a BSOD there should be a BSOD window with bugcheck and : (

    Sometimes you may see a misbehaving driver in the form *.sys

    At the very beginning of a BSOD you may see a % counter.

    If you see the % counter allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.

    3) For the image displaying performance options > in the virtual memory section click on change > in the popup virtual memory window > post an image into the thread

    4) For the ST500 drive run HD Sentinel (free or trial)

    Post images into the thread

    5)Today is 12/27 and the log collector was last ran on 12/16/2018 and no new BSOD were reported.

    When available please post some memory dumps.

    6) For any BSOD run the administrative command prompt and post logs into the newest post

    7) Open file explorer > this PC > C: > in the right upper area search for:  C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a share link into the thread using one drive ,drop box, or google drive

    8) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
    Speccy - Free Download - Piriform: Speccy - System Information - Free
    https://www.piriform.com/speccy
    https://www.ccleaner.com/speccy
    HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
    http://www.cpuid.com/softwares/hwmonitor.html
    SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
    http://www.almico.com/speedfan.php

    9) Run Prime95 - Stress Test Your CPU
    Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
    https://www.tenforums.com/tutorials/16474-prime95-stress-test-your-cpu.html
    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.

    10) Run FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
    FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials:
    https://www.tenforums.com/tutorials/13081-furmark-gpu-stress-test.html
    Please make note of the importance of temperature monitoring and aborting the test in the GPU link.
    a) Record the maximum temperature and post the maximum temperature into the thread.
    b) Record the test duration and post the uninterrupted test duration into the thread.
    c) Aim for testing 1 hour.
    d) Use the Microsoft snipping tool to post images into the thread.

    11) For each of the above tests please record and post maximum temperatures.

    12) For each of the above tests please record and post test duration.

    Thursday, December 27, 2018 9:07 PM
  • After disabling the on-board graphics and switching to a PCIe card no more crashes occured. Many thanks questionsformicrosoftproducts for leading me to the right solution by advising on the troubleshooting process. 

    yaro

    Saturday, January 5, 2019 11:26 AM
  • That's great.

    You are very welcome.

    Glad to see it sorted.

    Saturday, January 5, 2019 4:58 PM