Problemme bad pool caller crash

[dragongwenn]

Bonsoir à tous,
Jais écran bleu indiquant Bad Pool Caller qui fait redémarrer mon pc
Jais vue que sa pouvait venir des drivers .
Sur drivercloud tout et a jour
Donc voilà si quelqu'un peux m'aidé sa serait très gentil. Merci

[Rocca]

Salut,

Utilise donc whocrashed pour savoir ce qu'il t'indique comme motif de crash. Enfin, si c'est enregistré (à tester).

[dragongwenn]

Salut,

Utilise donc whocrashed pour savoir ce qu'il t'indique comme motif de crash. Enfin, si c'est enregistré (à tester).

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sat 08/04/2017 20:32:42 your computer crashed
crash dump file: C:\WINDOWS\Minidump\040817-5281-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFC50B9F8E0488)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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 Sat 08/04/2017 20:32:42 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: e2xw1.sys (e2xw10x64+0x89CD)
Bugcheck code: 0xC2 (0x7, 0x0, 0x0, 0xFFFFC50B9F8E0488)
Error: BAD_POOL_CALLER
Bug check description: This indicates that the current thread is making a bad pool request.
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: e2xw1.sys .
Google query: e2xw1.sys BAD_POOL_CALLER



On Fri 07/04/2017 21:23:36 your computer crashed
crash dump file: C:\WINDOWS\Minidump\040717-14093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E7C0)
Bugcheck code: 0xC2 (0x7, 0x0, 0x2C25B6, 0xFFFF9D8E73FF3848)
Error: BAD_POOL_CALLER
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 current thread is making a bad pool request.
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

---

3 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:

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

Voila les rapports des 3 crash

[Rocca]

On peut avoir la config détaillée / OS... ??

Je ne suis pas spécialiste dans l'analyse des rapports pour être clair. Néanmoins, en regardant le lien proposé "e2xw1.sys" le problème semble cerné

[dragongwenn]

Pour la config je prends celle indiquée dans whocrashed

Computer name: GWENN
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\WINDOWS
Hardware: MS-7978, MSI, Z170A GAMING M3 (MS-7978)
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17104924672 bytes total

[Robix66]

A priori, une solution ici : https://service.msicomputer.com/msi_...px?formid=3054

[dragongwenn]

Ok merci je viens de le faire je vois si sa continue de le faire ou pas