Crash PC systématique
Jerome_33
Messages postés
5
Date d'inscription
Statut
Membre
Dernière intervention
-
jumulka Messages postés 12157 Date d'inscription Statut Membre Dernière intervention -
jumulka Messages postés 12157 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
Me voilà avec un soucis dont je ne comprends pas l'origine, depuis maintenant 2 semaines, mon PC crash a l'utilisation de jeu au bout d'une 15aine de minutes ( en l'occurrence, Fortnite ( sur SSD ), Warzone et Vanguard
( Sur Disque Dur )). Pour tout autre utilisation ( Chrome, Youtube, TV, Twitch, Netflix ) aucun soucis
Pourtant avant cela il n'y avait absolument aucun soucis, je faisais tournais les 3 jeux en ultra sans aucun bug, perte de fps ou crash.
Lorsque le crash se produit, soit le jeu se fige puis se ferme et un message d'erreur apparaît, soit la même chose et il fait en meme temps crash les autres applications ouvertes ( comme chrome ), soit dernière option, il provoque un blue screen avec ce message d'erreur "page fault in nonpaged area" et le PC redémarre.
J'ai déjà essayé l'option de désinstaller le pilote de ma carte graphique et le réinstaller avec installation personnalisée ( chose que j'avais trouvé sur un autre sujet ) sans succès, je bien nettoyé et vérifier que les RAM et carte graphique étaient bien fixées, pareil ça n'a rien changé. J'ai vérifié qu'aucun virus n'était présent.
J'ai ouvert Core Temp pendant le jeu pour voir s'il y avait une surchauffe, pas de soucis ça dépasse pas les 70°, j'ai vérifié la consommation du processeur, carte graphique et RAM pendant le jeu, c'est au max a 60-65% donc rien à signaler.
Si vous avez une idée de la cause du problème et de sa résolution je vous en serez reconnaissant.
Merci beaucoup.
Ma config :
- Processeur ► I7-8700K ( 3.7 GHz )
- Carte graphique ► Gigabyte GeForce GTX 1080 WindForce OC, 8GO
- Carte Mère ► MSI Z370
- RAM ► DDR4 Ballistix Sport LT, Rouge, 2 x 8 Go, 2400 MHz, CAS 16
- Alimentation ► Cooler Master G750M, 750W
- SSD ► Kingston SSDNow UV400, 240 Go, SATA III
- Disque dur ► Seagate BarraCuda, 2 To
- Ventirad ► Be Quiet! Dark Rock Pro 4
Me voilà avec un soucis dont je ne comprends pas l'origine, depuis maintenant 2 semaines, mon PC crash a l'utilisation de jeu au bout d'une 15aine de minutes ( en l'occurrence, Fortnite ( sur SSD ), Warzone et Vanguard
( Sur Disque Dur )). Pour tout autre utilisation ( Chrome, Youtube, TV, Twitch, Netflix ) aucun soucis
Pourtant avant cela il n'y avait absolument aucun soucis, je faisais tournais les 3 jeux en ultra sans aucun bug, perte de fps ou crash.
Lorsque le crash se produit, soit le jeu se fige puis se ferme et un message d'erreur apparaît, soit la même chose et il fait en meme temps crash les autres applications ouvertes ( comme chrome ), soit dernière option, il provoque un blue screen avec ce message d'erreur "page fault in nonpaged area" et le PC redémarre.
J'ai déjà essayé l'option de désinstaller le pilote de ma carte graphique et le réinstaller avec installation personnalisée ( chose que j'avais trouvé sur un autre sujet ) sans succès, je bien nettoyé et vérifier que les RAM et carte graphique étaient bien fixées, pareil ça n'a rien changé. J'ai vérifié qu'aucun virus n'était présent.
J'ai ouvert Core Temp pendant le jeu pour voir s'il y avait une surchauffe, pas de soucis ça dépasse pas les 70°, j'ai vérifié la consommation du processeur, carte graphique et RAM pendant le jeu, c'est au max a 60-65% donc rien à signaler.
Si vous avez une idée de la cause du problème et de sa résolution je vous en serez reconnaissant.
Merci beaucoup.
Ma config :
- Processeur ► I7-8700K ( 3.7 GHz )
- Carte graphique ► Gigabyte GeForce GTX 1080 WindForce OC, 8GO
- Carte Mère ► MSI Z370
- RAM ► DDR4 Ballistix Sport LT, Rouge, 2 x 8 Go, 2400 MHz, CAS 16
- Alimentation ► Cooler Master G750M, 750W
- SSD ► Kingston SSDNow UV400, 240 Go, SATA III
- Disque dur ► Seagate BarraCuda, 2 To
- Ventirad ► Be Quiet! Dark Rock Pro 4
A voir également:
- Crash PC systématique
- Reinitialiser pc - Guide
- Test performance pc - Guide
- Pc lent - Guide
- Downloader for pc - Télécharger - Téléchargement & Transfert
- Forcer demarrage pc - Guide
2 réponses
Bonjour,
tu peux faire un rapport whocrashed voir ce que donne les bsod
le message d'erreur quand le jeu crash ça dit quoi ?
tu peux faire un rapport whocrashed voir ce que donne les bsod
le message d'erreur quand le jeu crash ça dit quoi ?
--------------------------------------------------------------------------------
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: CONFIG-O-MATIC
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: MS-7B49, Micro-Star International Co., Ltd., Z370 PC PRO (MS-7B49)
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 8664, level: 6
12 logical processors, active mask: 4095
RAM: 17132482560 bytes (16,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 15/12/2021 19:28:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121521-6687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB61, 0x1F923845A20, 0xFFFFC80128AD8000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 15/12/2021 19:28:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!SeConvertSidToStringSid+0x4002)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB61, 0x1F923845A20, 0xFFFFC80128AD8000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
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 14/12/2021 04:06:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121421-5531-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFCA9C0AE13B3A)
Bugcheck code: 0x50 (0xFFFFCAB9C466E7D8, 0x0, 0xFFFFCA9C0AE13B3A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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.
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 Sun 12/12/2021 17:07:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121221-18640-01.dmp
This was probably caused by the following module: bedaisy.sys (0xFFFFF802B260D37E)
Bugcheck code: 0x7F (0x8, 0xFFFFAF81A2359E50, 0xCFEF7A4F, 0xFFFFF802B260D37E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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: bedaisy.sys .
Google query: bedaisy.sys UNEXPECTED_KERNEL_MODE_TRAP
On Wed 01/12/2021 21:35:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120121-6609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x3D4, 0x2134C113520, 0xFFFFD681468C0000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 01/12/2021 18:49:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120121-5640-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80143E22167)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80143E22167, 0xFFFFDA8E94B26CB8, 0xFFFFDA8E94B264F0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has 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:
bedaisy.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.
Message d'erreur :
Les message d'erreur c'est des messages d'erreur des jeux en questions assez basique qui disent d'essayer de cliquer sur "analyser et réparer" pour réparer le soucis et de contacter le support si ça ne marche pas, ( chose que j'ai fait sans succès )
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: CONFIG-O-MATIC
Windows version: Windows 10, 10.0, version 2009, build: 19043
Windows dir: C:\WINDOWS
Hardware: MS-7B49, Micro-Star International Co., Ltd., Z370 PC PRO (MS-7B49)
CPU: GenuineIntel Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz 8664, level: 6
12 logical processors, active mask: 4095
RAM: 17132482560 bytes (16,0GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Wed 15/12/2021 19:28:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121521-6687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB61, 0x1F923845A20, 0xFFFFC80128AD8000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 15/12/2021 19:28:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!SeConvertSidToStringSid+0x4002)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB61, 0x1F923845A20, 0xFFFFC80128AD8000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
Bug check description: This bug check indicates that a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
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 14/12/2021 04:06:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121421-5531-01.dmp
This was probably caused by the following module: win32kfull.sys (0xFFFFCA9C0AE13B3A)
Bugcheck code: 0x50 (0xFFFFCAB9C466E7D8, 0x0, 0xFFFFCA9C0AE13B3A, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32\win32kfull.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Full/Desktop Win32k Kernel Driver
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.
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 Sun 12/12/2021 17:07:28 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\121221-18640-01.dmp
This was probably caused by the following module: bedaisy.sys (0xFFFFF802B260D37E)
Bugcheck code: 0x7F (0x8, 0xFFFFAF81A2359E50, 0xCFEF7A4F, 0xFFFFF802B260D37E)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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: bedaisy.sys .
Google query: bedaisy.sys UNEXPECTED_KERNEL_MODE_TRAP
On Wed 01/12/2021 21:35:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120121-6609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0x3D4, 0x2134C113520, 0xFFFFD681468C0000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Wed 01/12/2021 18:49:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\120121-5640-01.dmp
This was probably caused by the following module: ntfs.sys (0xFFFFF80143E22167)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80143E22167, 0xFFFFDA8E94B26CB8, 0xFFFFDA8E94B264F0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has 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:
bedaisy.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.
Message d'erreur :
Les message d'erreur c'est des messages d'erreur des jeux en questions assez basique qui disent d'essayer de cliquer sur "analyser et réparer" pour réparer le soucis et de contacter le support si ça ne marche pas, ( chose que j'ai fait sans succès )
Sinon les messages d'erreur quand le jeu crash c'est juste de smessages basiques qui disent de cliquer sur vérifier et réparer, et de contacter le support si ça ne marche pas ( chose qui ne m'a pas avancé )
crash dump file: C:\WINDOWS\Minidump\121521-6687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F72A0)
Bugcheck code: 0x12B (0xFFFFFFFFC00002C4, 0xB61, 0x1F923845A20, 0xFFFFC80128AD8000)
Error: FAULTY_HARDWARE_CORRUPTED_PAGE
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 a single-bit error was found in this page. This is a hardware memory error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Ah j'ai réussi a en poster une partie
sfc /scannow
une fois finis :
chkdsk /F
(il te dira que ce n'est pas possible de suite et de le faire au démarrage, tape o et valide puis redémarre)
réouvre et tape :
DISM /Online /Cleanup-image /Restorehealth
si tu as toujours des problèmes, au vu de l'erreur essaye de changer les barrettes de slot si tu as la place sinon de les inversé. si toujours pareil essaye de brancher une seul barrette regarde si tu en a une qui te fait les erreurs