Bonsoir,  
 
Cet été, j'ai acheté un nouveau pc sur lequel j'ai implémenté windows 10.
 
Depuis ce temps, je subi régulièrement des crash et j'aimerai mettre fin à cette série une bonne fois pour toute.
 
Pour vous aider dans la résolution de mon problème voici quelques éléments:
http://img114.xooimage.com/files/d [...] 823bf9.png
http://img114.xooimage.com/files/0 [...] 823bfc.png
http://img112.xooimage.com/files/b [...] 823c00.png
http://img113.xooimage.com/files/1 [...] 823c0f.png
 

 
Je viens de couper l'hypervisor en suivant ces indications car je me demande si cela n'était pas responsable d'une partie de mes problèmes:

 
Si besoin de plus d'informations pour m'aider dans la résolution de ces crash, aucun soucis.
 
En vous remerciant.

Tes crashes ont été provoqués par VirtualBox et par les drivers AMD.
 
Sont-ils à jour ?

Je pense que mes drivers sont à jour, j'ai vérifié en utilisant driver cloud comme j'en ai l'habitude, j'ai aussi vérifié en regardant mon gestionnaire de périphérique mais aussi via l'application radeon.
 
Quant à virtualbox, j'ai ouvert l'invité de commande et j'ai entré ceci pour le désactiver:
bcdedit /set hypervisorlaunchtype off
 
Mauvaise idée, des choses à faire?
 
http://img111.xooimage.com/files/7 [...] 823ccc.png
http://img112.xooimage.com/files/1 [...] 823cdc.png

Si tu n'as pas besoinn de VirtualBox, il suffit de le désinstaller...
Pas de modifier les options de boot...

Je vais desinstaller puis reinstaller nox pour mettre fin à ce premier problème dont tu parles (virtual box).
 
Néanmoins, cela ne semble pas être l'unique cause de mes multiples crash donc si quelqu'un peut m'aider, ce ne serait pas de refus.
 
Notamment ce truc qui est la première cause de beaucoup de mes crash : ntoskrnl.exe
 
Merci d'avance.

Teste ta mémoire avec Memtest sur plusieurs passes.

Mon bios n'était pas à jour, je viens de le mettre à jour. Possiblement, est-ce que cela pouvait être la cause de mes crash liés aux driver?
 
Pour le test de mémoire, je vais attendre de voir si le pc crash à nouveau maintenant que le bios est à jour.

Oui, un UEFI mis à jour peut potentiellement résoudre tes problèmes.
A suivre.

--------------------------------------------------------------------------------
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  
 
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
 
 
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.  
 
 
 
 

Personne ne peut m'aider, je ne sais plus quoi faire et ça continue de crasher en permanence, je n'ai pas de problème de surchauffe, tous les drivers sont à jours, le bios aussi, windows aussi, j'ai vérifier le matériel.
 
Que faire: sur un autre site, voici ce qu'on m'a indiqué :
- amdkmdag.sys c'est le pilote de ta carte graphique
- ysr0.sys = effectivement c'est VMware
donc à désinstaller ou mettre à jour VMWare.
 
https://forum.malekal.com/viewtopic.php?f=2&t=68294
 
En vous remerciant.

 
Tu indiques : Je vais desinstaller puis reinstaller nox pour mettre fin à ce premier problème dont tu parles (virtual box).
 
This was probably caused by the following module: ysdrv.sys (YSDrv!SUPR0PageFree+0x1FEC)  
Bugcheck code: 0x50 (0xFFFFA08ADD92D480, 0x2, 0xFFFFF802A72099DF, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Program Files (x86)\Bignox\BigNoxVM\RT\YSDrv.sys
product: Nox Limited VM VirtualBox
 
As-tu bien désinstallé Bignox ?
 
Ne le réinstalle pas dans un premier temps  histoire de voir si cela arrange ou pas tes écrans bleus

C'est écrit plusieurs noir sur blanc, mais il s'en fout des réponses en fait. C'est juste du troll.

Je m'en soucis bien au contraire. J'ai effectivement désinstaller nox et je suis passé sur bluestacks car j'ai besoin quotidiennement d'un émulateur android.
 
Malgré tout, les crashs interviennent toujours.
 
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.

Depuis le temps, tu as testé tes barrettes de RAM comme indiqué ou pas ?
Parce que trafiquer avant de tester ce n'est pas la bonne méthode...

Oui j'avais testé aucun soucis.
 
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.

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

Tu as pensé à regarder dans les journaux d'événements de Windows ce qu'il se passer aux heures où ça crashe ?
 
Sinon, si ça a planté sans BSOD (pas de résultat dans Whocrashed), ça peut être le signe d'une faiblesse matérielle (alim, carte mère, ...).

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: oui j'ai aussi regardé mon journal windows sans indication supplémentaire.
 
A mon avis,  mes crash ne dépendaient 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?

https://fr.msi.com/support