BSOD in Ryzen 2200G ''CRITICAL PROCESS DIED''

Page 1 of 4 123 ... LastLast

  1. Posts : 29
    Windows 10
       #1

    BSOD in Ryzen 2200G ''CRITICAL PROCESS DIED''


    Hi, i'm having ''CRITICAL PROCESS DIED'' in a while, i don't know how to solve this, i've done many things, but nothing worked. Checked my HD, cmd commands, nothing.

    Attachment 202009
      My Computer


  2. Posts : 29
    Windows 10
    Thread Starter
       #2

    luizguuus said:
    Hi, i'm having ''CRITICAL PROCESS DIED'' in a while, i don't know how to solve this, i've done many things, but nothing worked. Checked my HD, cmd commands, nothing.

    Attachment 202009
    Attachment 202099
      My Computer

  3. philc43's Avatar
    Posts : 5,039
    64bit Win 10 Pro ver 20H2 Build 19042.985 and W10 Insider Preview Build 21376
       #3




    Diagnostics Test

     HDD TEST


    Run HDTune to
    • check the health,
    • scan for errors, no quick scan but full scan
    • run a benchmark.

    It may take some time, but please take the time you need to perform it properly.
    When above is done please make screenshots of the following
    • the health,
    • the error scan,
    • the benchmark incl. following
      • transfer rate,
      • access time,
      • burst rate,
      • cpu usage.


      My Computers

  4. Ztruker's Avatar
    Posts : 13,526
    Windows 10 Pro X64 20H4 19042.928
       #4

    The log files are in a foreign (non-English) language and some can not be analyzed. Please change the system language to English and post a new log collector zip. Use the Beta log collector shown at the bottom of the Blue Screen of Death (BSOD) Posting Instructions link as it collects more information than the standard collector.

    Add, Remove, and Change Display Language in Windows 10

    You can put the language back to normal once done though you may have to do this multiple times if I need you to run the log collector script again in the future.

    Thanks
      My Computers


  5. Posts : 29
    Windows 10
    Thread Starter
       #5

    I'm finishing the HD tests, when it's done, i'll send with the log file. I just got ''KERNEL DATA IN PAGE ERROR'' and ''CRITICAL PROCESS DIED'', but KERNEL BSOD seems different now, take a look.Attachment 202113Attachment 202114Attachment 202115
      My Computer


  6. Posts : 29
    Windows 10
    Thread Starter
       #6
      My Computer


  7. Posts : 38,559
    windows 10 professional version 1607 build 14393.969 64 bit
       #7

    The logs were in a foreign language and could not be scanned or read.
    1) Please change the default language to English so that the files can be troubleshooted.

    Add, Remove, and Change Display Language in Windows 10 | Windows 10 Tutorials

    2) The license information in the logs in one area displayed: LocalGenuineState : SL_GEN_STATE_INVALID_LICENSE
    It's unclear why it has displayed this result in this section.
    What is the history of the Windows installation?

    3) Please uninstall these software and any drivers installed by these software:

    a) Advanced SystemCare 11
    b) Driver Booster 5

    4) Please list if possible any known drivers modified by these software.
    Sometime a system restore is useful in case the drivers are not know.
    And at times a clean install may be beneficial if there are no restore points.


    5) In startup and recovery system failure change write debugging information from complete memory dump to automatic memory dump.

    6) Uncheck automatically restart.

    7) Then reboot to keep the settings.

    Once the troubleshooting has completed these settings can be modified.

    The current memory dump is 7 GB.
    During the troubleshooting if memory dumps are needed they should be significantly smaller in size and can be uploaded for debugging.
    When automatically restart is checked it can be easy to miss bsod. With it unchecked you should see a bugcheck with : (.
    If you see a %counter please allow it to rise to 100% before rebooting so that there is sufficient time to create the dump file.

    8) The logs had entries reporting GPU, Drive (paging and possible corruption), and virtual memory problems:

    Code:
    Event[1980]:
      Log Name: System
      Source: Display
      Date: 2018-09-02T18:31:51.117
      Event ID: 4115
      Task: N/A
      Level: Aviso
      Opcode: Informaş§es
      Keyword: Clßssico
      User: N/A
      User Name: N/A
      Computer: DESKTOP-MK5IPSP
      Description: 
    Falha ao iniciar driver de vİdeo; usando Driver de Vİdeo Bßsico da Microsoft em vez disso. Verifique no Windows Update se hß um driver de vİdeo mais recente.
    Failed to start video driver; using Microsoft's Basic Video Driver instead. Check with Windows Update if you have a newer video driver.

    Code:
    Event[1204]:
      Log Name: System
      Source: Microsoft-Windows-Resource-Exhaustion-Detector
      Date: 2018-08-31T16:33:49.021
      Event ID: 2004
      Task: Eventos do Diagn¾stico de Esgotamento de Recursos
      Level: Aviso
      Opcode: ContÚm os resultados do diagn¾stico.
      Keyword: Eventos relacionados ao esgotamento de limite confirmado do sistema (mem¾ria virtual).
      User: S-1-5-18
      User Name: AUTORIDADE NT\SISTEMA
      Computer: DESKTOP-MK5IPSP
      Description: 
    O Windows diagnosticou com Ûxito uma condişÒo de mem¾ria virtual insuficiente. Os programas a seguir consumiram a maior parte da mem¾ria virtual: League of Legends.exe (4680) consumiu 1309708288 bytes, LeagueClientUxRender.exe (5172) consumiu 1265389568 bytes e Spotify.exe (6900) consumiu 218734592 bytes.

    Windows has successfully diagnosed an insufficient virtual memory condition. The following programs consumed most of the virtual memory: League of Legends.exe (4680) consumed 1309708288 bytes, LeagueClientUxRender.exe (5172) consumed 1265389568 bytes, and Spotify.exe (6900) consumed 218734592 bytes.
    Code:
    Event[719]:
      Log Name: System
      Source: Microsoft-Windows-Ntfs
      Date: 2018-08-31T13:59:51.353
      Event ID: 140
      Task: N/A
      Level: Aviso
      Opcode: Informaş§es
      Keyword: N/A
      User: S-1-5-18
      User Name: AUTORIDADE NT\SISTEMA
      Computer: DESKTOP-MK5IPSP
      Description: 
    Falha do sistema ao liberar dados para o log de transaş§es. Pode ocorrer corrupşÒo em IDdoVolume: C:, NomeDoDispositivo: \Device\HarddiskVolume5.
    (Foi especificado um dispositivo inexistente.)

    System crash when releasing data to the transaction log. Corruption can occur in VolumeID: C :, DeviceName: \ Device \ HarddiskVolume5.
    Last edited by zbook; 04 Sep 2018 at 00:00.
      My Computer


  8. Posts : 29
    Windows 10
    Thread Starter
       #8

    Here it is the file in English.

    Attachment 202253
      My Computer


  9. Posts : 29
    Windows 10
    Thread Starter
       #9

    ``System crash when releasing data to the transaction log. Corruption can occur in VolumeID: C :, DeviceName: \ Device \ HarddiskVolume5.`` What this means?
      My Computer


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

    The steps in post #7 were numbered (edited).
    Please comment on the windows version and licensing.
    These type of entries are related to the drive or drive file system.
    HD Tune displayed a low transfer rate number but that may just be due to the spike.
    What is the age of the drive?
    There are additional steps that can be performed to check the drive.

    The logs going forward may display more useful information in English.
    The current logs unfortunately do not change form a foreign language to English.
    New error reporting logs appear to be in English.
    So time will be needed to see problems within the logs.
      My Computer


 
Page 1 of 4 123 ... LastLast

  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 20:56.
Find Us




Windows 10 Forums