Bad_pool_header et easeus

Bonjour,

En fait les disques ne sont pas fractionnés. Je pensais qu'on pouvait utiliser le disque "D" pour agrandir le disque "C". J'ai fini par comprendre ... un peu tard, certes ... que je n'étais pas dans un cas de figure permettant l'extension du disque "C". Il n'y a pas d'espace non alloué. J'utilise quand même "Minitool partition Wizard" ?

PS: Je suis sur Windows 8.1.

Si j'ai Windows 8.1 le tuto ne fonctionne pas ?

Voilà je suis sur le logiciel. Comment je fais pour vérifier la bonne santé des partitions ?

En fait c'est au démarrage et lorsque je lance un jeu. Dans ce dernier cas, la tour s'allume s'éteint s'allume etc.

Lorsque j'exécute "Whocrashed" je le fais quand je suis sur le CD ?

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

Crash dumps are enabled on your computer.

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

On Fri 15/02/2019 21:19:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: amifldrv64.sys (amifldrv64+0x1A04)
Bugcheck code: 0x19 (0x22, 0xFFFFD00021E93000, 0x0, 0x0)
Error: BAD_POOL_HEADER
Bug check description: This indicates that a pool header is corrupt.
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. This problem might also be caused because of overheating (thermal issue).
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: amifldrv64.sys .
Google query: amifldrv64.sys BAD_POOL_HEADER



On Thu 14/02/2019 14:20:20 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021419-3750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD001D9707000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Thu 14/02/2019 14:03:26 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021419-4203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD0002273E000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Thu 14/02/2019 14:00:33 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021419-4234-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD00021D20000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Thu 14/02/2019 13:57:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021419-4906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD0003AC49000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Thu 14/02/2019 13:57:13 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021419-5156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD000226C9000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Thu 14/02/2019 13:50:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021419-4875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD00021D7F000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Sun 10/02/2019 20:18:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021019-3703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x19 (0x22, 0xFFFFD00026CBB000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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 Sun 10/02/2019 20:03:57 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\021019-4203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x19 (0x22, 0xFFFFD00023C58000, 0x0, 0x0)
Error: BAD_POOL_HEADER
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 a pool header is corrupt.
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. 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.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\021019-9250-01.dmp




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

On your computer a total of 47 crash dumps have been found. Only 10 have been analyzed. Only 9 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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:

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

J'ai cherché dans mon explorateur de fichiers "amifldrv64.sys". C'était lié à "Super Raid" et "Command Center". J'ai supprimé les deux. Dans mon utilitaire "MSI Smart" il ne reste que "NetworkGenie".

J'ai téléchargé "CoreTemp". Voici ce qui s'affiche :
https://pjjoint.malekal.com/files.php?id=20190216_c6l12p14i6z13


Quand j'ai voulu utiliser "Memtest" voilà ce qui s'est affiché :
https://pjjoint.malekal.com/files.php?id=20190216_o5g10y15l12f11


Pour finir voici les 3 rapports :
https://pjjoint.malekal.com/files.php?id=20190216_h13f11k7i10r14 (Addition)
https://pjjoint.malekal.com/files.php?id=FRST_20190216_h7y158t13w8 (FRST)
https://pjjoint.malekal.com/files.php?id=20190216_o9p12l12m6g6 (Shortcut)

Je pense que ça s'est un peu amélioré. Je n'ai pas galéré au démarrage ce matin. Mais je plante toujours en jeu.

Le logiciel ne fonctionne pas correctement. Durant le premier essai mon écran a figé et était multicolore avec des tas de caractères spéciaux après avoir affiché quelques lignes rouges. Ensuite il fonctionnait, affichait quelques lignes rouges et éteignait mon ordi. La clé branchée, l'ordi se rallumait, s'éteignait, se rallumait etc avant de s'allumer pour de bon. Voici ce que j'ai pu rapidement prendre en photo :

J'ai essayé de le faire fonctionner autrement. Dans le tuto il était marqué qu'il ne fonctionnait qu'à partir du CD; je me suis donc dit que c'était le problème. Mais impossible de télécharger quoique ce soit à partir du CD, le navigateur se fige et finit par fermer. J'ai donc branché les deux clés en même temps et fait démarrer celle du CD puis celle du logiciel. Le logiciel se lance et rebelote même problème.

Je suppose que vous vouliez que j'aille sur "Virustotal" avec "ndisrd.sys" ... Voilà le lien : https://www.virustotal.com/gui/#/file/5e6d01591211df13ed035707125668db91f2e6a2ba5fdc9b03b71413f00ae279/details

Pour finir Je me suis dit que mon problème venait peut-être des mises à jour. Il y a une mise à jour importante à faire mais elle n'aboutit pas. J'ai cette erreur : code 8024200D.