BSOD et crash PC : ysr0.sys et amdkmdag.sys

Tous les problèmes de Windows : message d'erreur, BSOD et écran bleu, erreur Windows Update ou d'installation, etc

Modérateur : Mods Windows

Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Bonsoir,

Cet été, j'ai acheté un nouveau pc sur lequel j'ai implémenté windows 10.

Depuis ce temps, je subis régulièrement des crash et j'aimerai mettre fin à cette série une bonne fois pour toute.

Mes drivers sont à jour, j'utilise régulièrement driver cloud pour se faire.
Mon bios a été mis à jour également.
Je viens d'utiliser le logiciel msi fourni lors de l'achat du pc pour voir si j'avais des driver non à jour voir image, j'ai installé l'intégralité de ces manques:
MSI-Driver-Software-Setup.jpg
MSI-Driver-Software-Setup-dv5.jpg
Le problème se manifestait régulièrement lorsque j'utilisais l'application nox player qui utilise visiblement virtualbox. Je l'ai totalement désinstallé et à la place je suis passé sur bluestacks 5 un autre émulateur android mais même problème. C'est pourquoi je me demande si tous mes problèmes ne proviennent pas de cette accélération virtuel?

Voici le rapport de whocrashed:

Code : Tout sélectionner

--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-2IOVFH3
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: MS-7C52, Micro-Star International Co., Ltd., A320M-A PRO MAX (MS-7C52)
CPU: AuthenticAMD AMD Ryzen 5 3400G with Radeon Vega Graphics 8664, level: 23
8 logical processors, active mask: 255
RAM: 14978199552 bytes (13,9GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump

On Thu 25/02/2021 07:04:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022521-5562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) 
Bugcheck code: 0x13A (0x9, 0xFFFF9780CE800000, 0xFFFF9780E3127960, 0x0)
Error: KERNEL_MODE_HEAP_CORRUPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the kernel mode heap manager has detected corruption in a heap. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 23/02/2021 22:42:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022321-5671-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF8047F2054C9) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8047F2054C9, 0xFFFFF306545CBE40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Tue 23/02/2021 22:33:04 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022321-5656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) 
Bugcheck code: 0x3D (0xFFFFF80462C7A718, 0xFFFFF80462C79F50, 0x0, 0x0)
Error: INTERRUPT_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check appears very infrequently. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Tue 23/02/2021 18:26:07 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022321-5125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) 
Bugcheck code: 0x9F (0x3, 0xFFFFC48D39749520, 0xFFFFF8040AC6C850, 0xFFFFC48D3E2232B0)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state. A device object has been blocking an IRP for too long a time. 
This is likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Sun 21/02/2021 12:50:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ysr0.sys (0xFFFFF802A72099DF) 
Bugcheck code: 0x50 (0xFFFFA08ADD92D480, 0x2, 0xFFFFF802A72099DF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: ysr0.sys . 
Google query: ysr0.sys PAGE_FAULT_IN_NONPAGED_AREA



On Fri 19/02/2021 18:46:46 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\021921-11062-01.dmp
This was probably caused by the following module: amdkmdag.sys (0xFFFFF807958DF174) 
Bugcheck code: 0xD1 (0x48000019E0, 0x9, 0x0, 0xFFFFF807958DF174)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\c0361901.inf_amd64_e0351ea22e7ad253\B361909\amdkmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.). 
Google query: amdkmdag.sys Advanced Micro Devices, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 

amdkmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)
ysr0.sys 
with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 


En vous remerciant.
Vous ne pouvez pas consulter les pièces jointes insérées à ce message.
Malekal_morte
Messages : 107213
Inscription : 10 sept. 2005 13:57

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Malekal_morte »

Salut,

- amdkmdag.sys c'est le pilote de ta carte graphique
- ysr0.sys = effectivement c'est VMware
donc à désinstaller ou mettre à jour VMWare.

Télécharge et installe HWInfo.
Vas dans les sensors et surveille les températures CPU, GPU et HDD durant l'utilisation de l'ordinateur, quand tu fais rien, lance des vidéos ou joue.
Vois à combien elles montent.
Pour tout cela, voir : Le tutoriel HwInfo
Fais aussi la vérification du paragraphe "Vérifier la fréquence du processeur avec HWinfo" à savoir que la fréquence augmente bien et ne reste pas tout en bas
https://www.malekal.com/wp-content/uplo ... sseur.webp
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Je ne sais plus quoi faire sincèrement, j'ai beau tout vérifier, mes crash continuent, je n'ai pas de problème matériel à priori, pas de surchauffe non plus, ma carte graphique est à jour, mes drivers le sont aussi, le bios également, que faire de plus pour solutionner ce vrai problème.

http://img115.xooimage.com/files/7/f/f/ ... 826113.png
http://img115.xooimage.com/files/3/2/f/ ... 826118.png
http://img115.xooimage.com/files/c/f/0/ ... 82611a.png
http://img115.xooimage.com/files/2/1/1/ ... 82611c.png

Tu me demande de desinstaller ou mettre à jour Virtualbox, je veux bien mais peux-tu m'indiquer une démarche ou un lien pour le faire?

ps: mon dernier who crash

Code : Tout sélectionner

--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-2IOVFH3
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\Windows
Hardware: MS-7C52, Micro-Star International Co., Ltd., A320M-A PRO MAX (MS-7C52)
CPU: AuthenticAMD AMD Ryzen 5 3400G with Radeon Vega Graphics 8664, level: 23
8 logical processors, active mask: 255
RAM: 14978199552 bytes (13,9GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps. 

Crash dump directories: 
C:\Windows
C:\Windows\Minidump

On Fri 26/02/2021 16:40:41 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-5906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) 
Bugcheck code: 0xA (0xFFFFD488288B0590, 0x2, 0x0, 0xFFFFF80127215525)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 26/02/2021 16:36:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-5718-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8026438A3BE) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8026438A3BE, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch. 
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. 
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 26/02/2021 16:01:30 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-5750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8057CC4EE84, 0xFFFFAA0C93AE5800, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 



On Fri 26/02/2021 13:50:44 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-5671-01.dmp
This was probably caused by the following module: amdppm.sys (0xFFFFF806289B10F0) 
Bugcheck code: 0xD1 (0xFFFFF806289B10F0, 0xFF, 0x7F, 0xFFFFF806157FBC90)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out. 
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Fri 26/02/2021 13:48:00 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\022621-5640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5A80) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80461A041C8, 0xFFFFA389CE891850, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you. 


Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 




Bien cordialement.
Malekal_morte
Messages : 107213
Inscription : 10 sept. 2005 13:57

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Malekal_morte »

Ca peut venir de plein de choses comme une fonctions d'AMD Radeon Software qui fait planter le PC...
ou un paramètres de virtualisation du BIOS.

Tu as regardé sur les forums de ces émulateurs si d'autres avec ces crashs etBSOD ?

Faudrait voir aussi en testant des paramètres d'AMD Radeon Software pour ces émulateurs... en désactivant tout.
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Non pas de soucis via ces emulateurs pour les autres.

Je suis convaincu que l'un des soucis vient de la virtualisation du bios en effet mais comment régler ce problème, là est ma question.

S'il le faut je suis prêt à réinitialiser windows10 si j'ai l'assurance que cela mettra fin à ces problèmes?
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Pour information, j'ai désactivé dans le bios à nouveau svm mode de ma carte msi pour voir si je subis toujours des crash ou non. Je vais voir pendant 24h.
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Depuis que j'ai désactivé le mode SVM dans le bios, plus aucun crash. Il semblerait bel et bien que mon pc ne soit pas assez puissant pour supporter la virtualisation.

Je te remercie pour tes explications et ta patience.
Malekal_morte
Messages : 107213
Inscription : 10 sept. 2005 13:57

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Malekal_morte »

Ok,
Par curiosité, c'est quelle config ?
Notamment processeur et mémoire ?
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

config-materielle.png
Vous ne pouvez pas consulter les pièces jointes insérées à ce message.
Malekal_morte
Messages : 107213
Inscription : 10 sept. 2005 13:57

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Malekal_morte »

Ouaip tu as un bon PC quand même, bizarre que ça fasse cela.
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Après réinstallation intégrale de windows sans conservation des fichiers pour vraiment repartir proprement, 2 heures plus tard nouveau crash.

Je ne sais vraiment pas quoi faire, c'est infernal.

Et who crash ne publie rien qui plus est.

Code : Tout sélectionner

--------------------------------------------------------------------------------
Welcome to WhoCrashed (Home Edition) v 6.70
--------------------------------------------------------------------------------

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution. 

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice. 

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems. 

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available. 

Just click the Analyze button for a comprehensible report ...



--------------------------------------------------------------------------------
Home Edition Notice
--------------------------------------------------------------------------------

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network. 

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-8Q44N6A
Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: MS-7C52, Micro-Star International Co., Ltd., A320M-A PRO MAX (MS-7C52)
CPU: AuthenticAMD AMD Ryzen 5 3400G with Radeon Vega Graphics 8664, level: 23
8 logical processors, active mask: 255
RAM: 14978183168 bytes (13,9GB)




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. 

Crash dump directories: 
C:\WINDOWS
C:\WINDOWS\Minidump

No valid crash dumps have been found on your computer


--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

Crash dumps are enabled but no valid crash dumps have been found. In case you are experiencing system crashes, it may be that crash dumps are prevented from being written out. Check out the following article for possible causes: If crash dumps are not written out.



Read the topic general suggestions for troubleshooting system crashes for more information. 

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Malekal_morte
Messages : 107213
Inscription : 10 sept. 2005 13:57

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Malekal_morte »

Si c'est encore avec les émulateurs, faut contacter l'éditeur.
Peut-être qu'ils utilisent une vieille version de Virtualbox qui bug avec ton matériel.
Première règle élémentaire de sécurité : on réfléchit puis on clic et pas l'inverse - Les fichiers/programmes c'est comme les bonbons, quand ça vient d'un inconnu, on n'accepte pas !
Comment protéger son PC des virus

Comment demander de l'aide sur le forum
Partagez malekal.com : n'hésitez pas à partager les articles qui vous plaisent sur la page Facebook du site.
Usdax26
Messages : 8
Inscription : 25 févr. 2021 13:34

Re: BSOD et crash PC : ysr0.sys et amdkmdag.sys

par Usdax26 »

Je me pose en effet la question car dès que je reconfigure mon pc sans utilisation de la SVM, aucun crash et dès que je réactive la SVM dans le bios, je crash, c'est vraiment surprenant.

En tout cas, je suis désormais convaincu d'avoir mis le doigt sur mon problème, je fais sans la SVM et tant pis pour la virtualisation, je fais sans mais au moins mon pc ne crash jamais.

ps: donc non mes crash ne dépendait pas que des émulateurs puisque je joue aujourd'hui dessus sans crash le moindre mais sans avoir activé la SVM dans mon bios en sachant que j'avais des crash auparavant aussi bien sur émulateurs que sur le bureau tout simplement mais à chaque fois avec le SVM activé.
Je me demande aussi si ma carte mère n'est pas défectueuse, ce n'est pas normal de ne pas pouvoir utiliser la SVM selon moi.

Comment contacter MSI pour évoquer le soucis?
  • Sujets similaires
    Réponses
    Vues
    Dernier message

Revenir à « Windows : Résoudre les problèmes »