Ecran bleu KERNEL MODE HEAP CORRUPT
Richter001 Messages postés 4 Statut Membre -
Bonjour,
J'ai acheté un lecteur SSD 1 To depuis quelques jours pour l'ajouter comme stockage supplémentaire pour quelques jeux.
Lors des deux premiers jours après mon ajout, pas de soucis, les jeux se lancent sans difficultés.
Lors du troisième jour d'utilisation, lors du lancement de l'application, un écran bleu apparait avec un descriptif d'erreur de type "KERNEL MODE HEAP CORRUPT"
Pas moyens de lancer le jeu sur ce SSD. Je suis obligé de le déplacer sur un HDD que j'ai également sur mon PC mais avec une vitesse de lecture moindre. Mon SSD n'est donc pas utilisable sauf si je le formate.
Auriez-vous une solution afin que l'utilisation de mon SSD soit viable svp ?
Merci par avance pour votre aide.
- Kernel mode heap corruption
- Mode avion - Guide
- Mode sécurisé samsung - Guide
- God mode - Guide
- Mode d'emploi - Guide
- Mode suivi des modifications - Guide
4 réponses
Bonjour
Ce tuto permet de faire des recherches dans l'appareil:
https://www.malekal.com/kernel-mode-heap-corruption-bsod-crash-ecran-bleu/
Bonjour,
Voici le rapport whocrashed :
Welcome to WhoCrashed (HOME EDITION) v 7.01
WhoCrashed is a comprehensible crash dump analyzer. It analyzes the system crashes of your computer or a remote computer on the network.
If your computer has displayed a blue (or black) screen of death or rebooted suddenly then your system may have crashed because of a malfunctioning device driver or because of a hardware failure. WhoCrashed will go to great lengths to help you find the root cause of the problem and a solution if available. It will analyze the crash dump files on your system or a system on the network with the single click of a button. In case the problem is caused by a malfunctioning driver, it will tell you what drivers are likely to be responsible for crashing your computer. In case of a hardware failure, it will tell you the most likely root cause and how to fix the problem.
When the analysis process is complete, WhoCrashed will write a report that offers suggestions on how to proceed in any situation, including internet links which will help you further troubleshoot any detected problems.
WhoCrashed will do great efforts to find out why your system crashed and what can be done to remedy the problem.
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-5P85KB3Windows version: Windows 10, 10.0, version 2009, build: 19045 (x64)Windows dir: C:\WindowsHardware: MS-7C02, Micro-Star International Co., Ltd, B450 TOMAHAWK MAX (MS-7C02)CPU: AuthenticAMD AMD Ryzen 5 3600X 6-Core Processor 8664, level: 23Processor count:12 logical processors, active mask: 4095RAM: 16309,6MB
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 06/02/2025 22:19:36 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\020625-8078-01.dmp (Minidump) Bugcheck code: 0x13A(0x12, 0xFFFFB10FD9010100, 0xFFFFB10FE7E59000, 0x0)Bugcheck name:KERNEL_MODE_HEAP_CORRUPTIONBug check description:This indicates that the kernel mode heap manager has detected corruption in a heap.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.
On Thu 06/02/2025 22:19:36 your computer crashed or a problem was reported
Crash dump file: C:\Windows\MEMORY.DMP (Kernel memory dump) Bugcheck code: 0x13A(0x12, 0xFFFFB10FD9010100, 0xFFFFB10FE7E59000, 0x0)Bugcheck name:KERNEL_MODE_HEAP_CORRUPTIONBug check description:This indicates that the kernel mode heap manager has detected corruption in a heap.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.
On Thu 06/02/2025 22:05:19 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\020625-7687-01.dmp (Minidump) Bugcheck code: 0x13A(0x12, 0xFFFFC88627010100, 0xFFFFC886373AA000, 0x0)Bugcheck name:KERNEL_MODE_HEAP_CORRUPTIONBug check description:This indicates that the kernel mode heap manager has detected corruption in a heap.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.
On Thu 06/02/2025 21:38:55 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\020625-8187-01.dmp (Minidump) Bugcheck code: 0xC2(0xD, 0xFFFFA88AB93D2210, 0xFFFFA88A, 0x295D51DC6CE8C82)Bugcheck name:BAD_POOL_CALLERBug check description:This indicates that the current thread is making a bad pool request.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.
On Mon 03/02/2025 21:42:53 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\020325-7750-01.dmp (Minidump) Bugcheck code: 0xC2(0xD, 0xFFFFAC0DE8D54940, 0xFFFFAC0D, 0x63A893D9116086FC)Bugcheck name:BAD_POOL_CALLERBug check description:This indicates that the current thread is making a bad pool request.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.
On Mon 03/02/2025 21:03:54 your computer crashed or a problem was reported
Crash dump file: C:\Windows\Minidump\020325-7593-01.dmp (Minidump) Bugcheck code: 0xC2(0xD, 0xFFFFB181D8B55560, 0xFFFFB181, 0x253CC6BEFBDB98C9)Bugcheck name:BAD_POOL_CALLERBug check description:This indicates that the current thread is making a bad pool request.Analysis:This is a typical software problem. Most likely this is caused by a bug in a driver.
Conclusion
6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider 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 suggestions displayed in the bugcheck analysis above.
The analysis process took 0:00:10 (h:mm:ss).
Je ne vois pas si un driver est manquant.
Merci pour votre retour.