BSOD after 15 Mins of normal use (STOP Critical_Process_Died)

Page 1 of 2 12 LastLast

  1. Tbk
    Posts : 8
    Windows 10
       New #1

    BSOD after 15 Mins of normal use (STOP Critical_Process_Died)


    Upgraded from an intel mobo / cpu to and AMD Vega CPU and Mobo.Subsequently changed from W7 to W10 and completely wiped both my SSD and HDD when installing. First time it loaded up I started to install drivers and start to use the PC as normal.However after about 10-20 minutes programs will stop responding for example spotify will remain intractable (I can press play and pause) it just wont do anything and the song will stop. Google chrome will stop loading web pages, it remains like this for around a minute or so before most programs crash and eventually the PC will BSOD with the error message STOP Critical_Process_DiedI have tried a fresh install of W10, using SFC /scannow as well as using CCleaner to fix any registry errors, this hasn't changed anything, the PC still continues to run for around 10-20 minutes before going to a BSOD. I have turned off Overclocking in the Bios as well.When the PC Blue screens it stays at 0% before just restarting, for some reason there are no logs created regardless of what option the log is set to.
      My Computer
    Quote Quote

  3. Caledon Ken
    Posts : 30,193
    Windows 11 Pro x64 Version 23H2
       New #2

    Hi Tbk. Welcome to the TenForums @Tbk


    Have you checked CPU temperature? Could use something like CPUID HWMonitor

    https://www.cpuid.com/softwares/hwmonitor.html

    Have you proven memory?

    MemTest86+ - Test RAM

    I would also have a look at Chkdsk on your boot storage just to be sure.

    Have you checked BIOS level compared to what is available on vendor site?


    Ken
      My Computer
    Quote Quote

  4. Tbk
    Posts : 8
    Windows 10
    Thread Starter
       New #3

    Caledon Ken said:
    Hi Tbk. Welcome to the TenForums @Tbk


    Have you checked CPU temperature? Could use something like CPUID HWMonitor

    https://www.cpuid.com/softwares/hwmonitor.html

    Have you proven memory?

    MemTest86+ - Test RAM

    I would also have a look at Chkdsk on your boot storage just to be sure.

    Have you checked BIOS level compared to what is available on vendor site?


    Ken
    Memtest returned 0 errors

    CPU Temp is at 38C Idle

    Chkdsk returns this
    Attachment 218938

    I will have a look at the BIOS now

    Thanks for your reply
      My Computer
    Quote Quote

  6. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #4

    Please see posting instructions:
    BSOD - Posting Instructions - Windows 10 Forums

    Post both DM and BETA log collectors into this thread.
      My Computer
    Quote Quote

  7. Tbk
    Posts : 8
    Windows 10
    Thread Starter
       New #5

    Attachment 218940Attachment 218941

    done
      My Computer
    Quote Quote

  8. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #6

    The specs in the "My Computer" section displays Windows 7 with different hardware.

    Please update the specs:

    System Specs - Fill in at Ten Forums | Tutorials
    In the left corner below in your post you find 'My System Specs'.
    After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
    System Info - See Your System Specs - Windows 7 Help Forums

    Include PSU. cooler, case, peripherals and anything attached to the computer by wired or wireless (mouse, keyboard, headset, printer, xbox, USB wireless network card, etc.)

    There were multiple BSOD in the logs.
    The computer had a fresh install and there were no dump files.
    There were no Windows error reporting events yet in the logs.



    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) verifier /querysettings
    6) wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
    7) bcdedit /enum all
    8) 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

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

    10) 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

    11) Run the BETA log collector after any BSOD and post a new zip into the thread

    12) The BIOS: Version/Date American Megatrends Inc. P4.60, 19/04/2018
    Upgrade the BIOS to the most up to date non-beta version

    ASRock > Fatal1ty AB350 Gaming-ITX/ac
      My Computer
    Quote Quote

  9. Tbk
    Posts : 8
    Windows 10
    Thread Starter
       New #7

    Microsoft Windows [Version 10.0.17763.107]
    (c) 2018 Microsoft Corporation. All rights reserved.


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


    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1


    Image Version: 10.0.17763.107


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


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


    Stage 1: Examining basic file system structure ...
    104960 file records processed.
    File verification completed.
    3994 large file records processed.
    0 bad file records processed.


    Stage 2: Examining file name linkage ...
    2280 reparse records processed.
    153506 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    2280 reparse records processed.


    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    24274 data files processed.
    CHKDSK is verifying Usn Journal...
    39396864 USN bytes processed.
    Usn Journal verification completed.


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


    116129791 KB total disk space.
    29618016 KB in 76463 files.
    60448 KB in 24275 indexes.
    0 KB in bad sectors.
    216303 KB in use by the system.
    65536 KB occupied by the log file.
    86235024 KB available on disk.


    4096 bytes in each allocation unit.
    29032447 total allocation units on disk.
    21558756 allocation units available on disk.


    C:\Windows\system32>verifier /querysettings


    Verifier Flags: 0x00000000


    Standard Flags:


    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.


    Additional Flags:


    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.


    [X] Indicates flag is enabled.


    Boot Mode:


    Persistent


    Rules:


    All rules are using default settings


    Verified Drivers:


    None


    C:\Windows\system32>wmic memorychip get manufacturer, capacity, partnumber, speed, memorytype, devicelocator, formfactor
    Capacity DeviceLocator FormFactor Manufacturer MemoryType PartNumber Speed
    8589934592 DIMM 0 8 Unknown 0 CMK16GX4M2D3000C16 2134
    8589934592 DIMM 0 8 Unknown 0 CMK16GX4M2D3000C16 2134




    C:\Windows\system32>bcdedit /enum all


    Firmware Boot Manager
    ---------------------
    identifier {fwbootmgr}
    displayorder {bootmgr}
    {ef0669d5-f569-11e8-a400-bf372fa6a9f2}
    {8e314cfa-0af6-11e9-8167-94b86d736602}
    {ef0669d6-f569-11e8-a400-bf372fa6a9f2}
    {8e314cfb-0af6-11e9-8167-94b86d736602}
    {8e314cfd-0af6-11e9-8167-94b86d736602}
    {ef0669d4-f569-11e8-a400-bf372fa6a9f2}
    timeout 1


    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=\Device\HarddiskVolume1
    path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
    description Windows Boot Manager
    locale en-GB
    inherit {globalsettings}
    default {current}
    resumeobject {90c0b323-f599-11e8-99f7-eb67cebef7a2}
    displayorder {current}
    toolsdisplayorder {memdiag}
    timeout 30


    Firmware Application (101fffff)
    -------------------------------
    identifier {8e314cfa-0af6-11e9-8167-94b86d736602}
    description USB


    Firmware Application (101fffff)
    -------------------------------
    identifier {8e314cfb-0af6-11e9-8167-94b86d736602}
    device partition=D:
    description UEFI: SanDisk, Partition 1


    Firmware Application (101fffff)
    -------------------------------
    identifier {8e314cfd-0af6-11e9-8167-94b86d736602}
    device partition=\Device\HarddiskVolume6
    description UEFI: SanDisk, Partition 2


    Firmware Application (101fffff)
    -------------------------------
    identifier {ef0669d4-f569-11e8-a400-bf372fa6a9f2}
    description UEFI: Built-in EFI Shell


    Firmware Application (101fffff)
    -------------------------------
    identifier {ef0669d5-f569-11e8-a400-bf372fa6a9f2}
    description Hard Drive


    Firmware Application (101fffff)
    -------------------------------
    identifier {ef0669d6-f569-11e8-a400-bf372fa6a9f2}
    description Network Card


    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.efi
    description Windows 10
    locale en-GB
    inherit {bootloadersettings}
    recoverysequence {90c0b325-f599-11e8-99f7-eb67cebef7a2}
    displaymessageoverride Recovery
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    osdevice partition=C:
    systemroot \Windows
    resumeobject {90c0b323-f599-11e8-99f7-eb67cebef7a2}
    nx OptIn
    bootmenupolicy Standard


    Windows Boot Loader
    -------------------
    identifier {90c0b325-f599-11e8-99f7-eb67cebef7a2}
    device ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{90c0b326-f599-11e8-99f7-eb67cebef7a2}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    locale en-gb
    inherit {bootloadersettings}
    displaymessage Recovery
    osdevice ramdisk=[C:]\Recovery\WindowsRE\Winre.wim,{90c0b326-f599-11e8-99f7-eb67cebef7a2}
    systemroot \windows
    nx OptIn
    bootmenupolicy Standard
    winpe Yes


    Windows Boot Loader
    -------------------
    identifier {ef0669db-f569-11e8-a400-bf372fa6a9f2}
    device ramdisk=[unknown]\Recovery\ef0669db-f569-11e8-a400-bf372fa6a9f2\Winre.wim,{ef0669dc-f569-11e8-a400-bf372fa6a9f2}
    path \windows\system32\winload.efi
    description Windows Recovery Environment
    inherit {bootloadersettings}
    osdevice ramdisk=[unknown]\Recovery\ef0669db-f569-11e8-a400-bf372fa6a9f2\Winre.wim,{ef0669dc-f569-11e8-a400-bf372fa6a9f2}
    systemroot \windows
    nx OptIn
    winpe Yes


    Resume from Hibernate
    ---------------------
    identifier {90c0b323-f599-11e8-99f7-eb67cebef7a2}
    device partition=C:
    path \Windows\system32\winresume.efi
    description Windows Resume Application
    locale en-GB
    inherit {resumeloadersettings}
    recoverysequence {90c0b325-f599-11e8-99f7-eb67cebef7a2}
    recoveryenabled Yes
    isolatedcontext Yes
    allowedinmemorysettings 0x15000075
    filedevice partition=C:
    filepath \hiberfil.sys
    bootmenupolicy Standard
    debugoptionenabled No


    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=\Device\HarddiskVolume1
    path \EFI\Microsoft\Boot\memtest.efi
    description Windows Memory Diagnostic
    locale en-GB
    inherit {globalsettings}
    badmemoryaccess Yes


    EMS Settings
    ------------
    identifier {emssettings}
    bootems No


    Debugger Settings
    -----------------
    identifier {dbgsettings}
    debugtype Serial
    debugport 1
    baudrate 115200


    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 {90c0b326-f599-11e8-99f7-eb67cebef7a2}
    description Windows Recovery
    ramdisksdidevice partition=C:
    ramdisksdipath \Recovery\WindowsRE\boot.sdi


    C:\Windows\system32>



    Attachment 218946Attachment 218947


    sfc /scannow couldn't finish before I Blue screened, next blue screen I'll post a new zip - going to update bios now

    thanks
    Last edited by Tbk; 28 Dec 2018 at 21:21.
      My Computer
    Quote Quote

  10. Tbk
    Posts : 8
    Windows 10
    Thread Starter
       New #8

    SFC scannow posted this

    Microsoft Windows [Version 10.0.17763.107](c) 2018 Microsoft Corporation. All rights reserved.C:\Windows\system32>sfc /scannowBeginning 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>


    updated to newest bios, will post new bsod log when it happens
      My Computer
    Quote Quote

  12. zbook
    Posts : 41,476
    windows 10 professional version 1607 build 14393.969 64 bit
       New #9

    For the above text from notepad:
    If you post it then edit it, it should fix the layout so that it can be read.

    For example: click edit > post it the second time into the thread


    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.
    With a BSOD with automatically restart unchecked you should see 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.
      My Computer
    Quote Quote

  13. Tbk
    Posts : 8
    Windows 10
    Thread Starter
       New #10

    Updated the format

    As of updating the BIOS the system hasn't crashed - however chrome is acting up and crashing when I attempt to sign into a user profile and sync settings.

    I will change the settings though and try to catch a dump for the BSOD
      My Computer
    Quote Quote

 

  Related Discussions
Frequent BSOD (~15 mins)
in BSOD Crashes and Debugging

Hi there, Typing quick, frequent crashes! Logs attached. Suspecting PSU/CPU failure, but trying to isolate before buying new one. Symptoms are a screen freeze before Windows crash screen. Happening more frequently, under little/no load....
BSOD about every 5 mins
in BSOD Crashes and Debugging

Getting bsod about every 5 mins and have to reboot to use for about 5 more mins. Pretty sure that it is MB related and hoping your tool will help diag the problem. The bsod happens with both my win 10 OSs after about the same time frame.
BSOD loop, stop code: critical_process_died
in BSOD Crashes and Debugging

Computer Model: Lenova Yoga 720 Sorry I can't provide much information because I am locked out of my computer. A few days back, I attempted to do a clean installation of Windows 10 on my laptop through a system reset. The system reset failed and...
have tried everything under the sun to get my computer to stop going to sleep mode where i have to enter my password after 5 minutes to no avail. Please anyone who could help with this?
The last week or so I've been getting a BSOD every 5 or 10 mins. Lots of different ones. (Driver IRQ not less or equal) (system thread exception not handled)(system service exception)(apc index mismatch) to name a few.I have updated all of my...
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 15:13.
Find Us




Windows 10 Forums