BSOD Critical Process Died - Recurring after a couple seconds after in


  1. Posts : 10
    Windows 10 Pro
       #1

    BSOD Critical Process Died - Recurring after a couple seconds after in


    Starting to lose my mind with how my PC has been behaving for the past while. As mentioned in the title, I'm getting blue screens after every login. What I have done so far:

    - sfc scan
    - malwarebytes + windows defender scan
    - updated all drivers
    - DISM Restore Health
    - memtest
    - clean boot
    - reinstalled windows

    I can't seem to figure out anything from system reliability or event viewer. When it BSODs, it reboots into an EFI Shell, which really doesn't let me do much. Only way around it at the moment is to shut it down, turn off the power supply, leave it for 5 mins, and when it boots up, it'll allow me to use it for a little longer before crashing again.

    Any help is greatly appreciated. From my guesses, I suspect it could be that the system board is failing or something hardware oriented.

    Thanks

    Attachment 217167
      My Computer


  2. Posts : 38,333
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Hi CallMeDepravity

    Welcome to Ten Forums BSOD forum.

    There were no dump files collected to perform debugging.
    The logs displayed:

    Code:
    The System log file was cleared.
    The Application log file was cleared.
    The Setup log file was cleared.
    Dump file creation failed due to error during dump creation.



    1) Update the specs in the "My Computer" section:

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


    2) There are two log collectors: DM and BETA
    Please run the BETA log collector and post a zip into the thread.
    BSOD - Posting Instructions - Windows 10 Forums
    https://www.tenforums.com/attachment...-v2-beta15.zip
    (extract all > open)

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

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

    5) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10 | Tutorials

    6) The older log files displayed problems with the Nvidia GPU.
    This problem may reappear once there are BSOD mini and memory dump files for debugging.


    Code:
    17/11/2018 20:11	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 79245143-c632-4fb0-878f-726ac4718ad1
    
    Problem signature:
    P1: 117
    P2: ffffa5051a1864a0
    P3: fffff80796f1c1cc
    P4: 0
    P5: 2860
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20181117-2011.dmp
    \\?\C:\Windows\TEMP\WER-200821250-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER57FC.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER580C.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER580B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER581C.tmp.txt
    \\?\C:\Windows\Temp\WERA949.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_8463799be1a210f284e6bbe374129162398e6_00000000_cab_1ca4ad30
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: dd9694c0-b8cc-4ba0-b15c-39f18cd51b10
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    17/11/2018 20:14	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:0_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: f536e577-c725-46bf-8add-901f585cf79d
    
    Problem signature:
    P1: 117
    P2: ffffa50517820220
    P3: fffff80796f1c1cc
    P4: 0
    P5: 1440
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20181117-2012.dmp
    \\?\C:\Windows\TEMP\WER-200920281-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD526.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD527.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD52A.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD53A.tmp.txt
    \\?\C:\Windows\Temp\WER9B27.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_fbad1457f79e88a6fd5858f8625d4ea7e4bb19d_00000000_cab_09d0d09e
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 40dc94a5-cde8-4aa0-84e1-40468e918828
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
    17/11/2018 19:37	Windows Error Reporting	Fault bucket LKD_0x117_Tdr:3_TdrBug:575504_TdrVTR:12_IMAGE_nvlddmkm.sys_Pascal, type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 12379e0b-d068-4290-8043-4f64f0175d78
    
    Problem signature:
    P1: 117
    P2: ffffa505110a14a0
    P3: fffff80796f1c1cc
    P4: 0
    P5: 2d90
    P6: 10_0_17134
    P7: 0_0
    P8: 256_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20181117-1936.dmp
    \\?\C:\Windows\TEMP\WER-198765781-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFEF5.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF06.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF05.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF16.tmp.txt
    \\?\C:\Windows\Temp\WER44C9.tmp.WERDataCollectionStatus.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_117_bdb8c6b838f75df77cb86f71783653e4b58a5e_00000000_cab_006148ef
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: 2734fc0c-dd79-476c-8152-37ce730aa77d
    Report Status: 268435456
    Hashed bucket: 
    Cab Guid: 0
      My Computer


  3. Posts : 1,104
    win 10 pro x64 os build 20H2
       #3

    check system ram by pulling one out and see if that works, if not pull other one out and see if it works with that one, make sure CPU is not overheating, in any way heat-sink should be cool to the touch, clean it out good, go get some canned air and spray it good, fan and all, sometimes its worth taking it off, reapplying heat sink past , and putting it back on. also make sure video card is seated properly, push on it not to hard, it may be worth wild to pull it out and clean it, that is if you have one and not on-board. you allready did the OS reinstall good starting point there. short of all that if that does not work, then yes a main board may be the case. I'm no PC tech just 30 years of building my own for friends and family most cases its the simplest things that can throw a OS in a bsod.
      My Computer


  4. Posts : 10
    Windows 10 Pro
    Thread Starter
       #4

    @zbook

    Specs have been updated. All files should be attached.

    Attachment 217194Attachment 217195Attachment 217196Attachment 217197
      My Computer


  5. Posts : 10
    Windows 10 Pro
    Thread Starter
       #5

    @Tonyb

    Made sure to clean out all the heatsink. My AIO is using the stock goop, so I'd doubt there'd be much issues there. I'll pull out the compressed air and give it a clean regardless.
      My Computer


  6. Posts : 38,333
    windows 10 professional version 1607 build 14393.969 64 bit
       #6

    1) For startup and recovery system failure:
    a) uncheck automatically restart
    b) reboot to maintain settings

    When automatically restart is checked it can be easy to miss BSOD.
    When automatically restart is unchecked it should display a BSOD window with bugcheck and : (
    Sometimes it may display 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.

    2) For Ccleaner uncheck:
    a) Memory Dumps
    b) Windows log files

    3) For any BSOD:
    a) Run the BETA log collector and post an new zip into the thread
    b) Open file explorer > this PC > C: > in the right upper corner 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

    4) Open administrative command prompt and type or copy and paste:
    5) sfc /scannow
    6) dism /online /cleanup-image /restorehealth
    7) chkdsk /scan
    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
      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 17:48.
Find Us




Windows 10 Forums