PB blue screen...(drivers?) Analyse WhoCrashed (HOME EDITION) v 6.01

Bonjour, alors voila depuis 2Jours jai un problème décran bleu
, jai fait la manip avec linvit de commande:

C:\>bcdedit /set {default} bootmenupolicy legacy
The operation completed succesfully.

C:\>exit

Continue
> Exit and continue to windows

ça marche mais le blue screen reviens.

au niveau de windows update il me semble que je suis à jour...


Ensuite jai analysé avec WhoCrashed (HOME EDITION) v 6.01

que dois-je fais j'y connait rien en drivers...

System Information (local)
--------------------------------------------------------------------------------

Computer name: DESKTOP-B7F6CRS
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: MS-7A71, MSI, Z270-A PRO (MS-7A71)
CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17141297152 bytes total




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

Crash dumps are enabled on your computer.

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

On Sun 10/28/2018 1:43:22 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102818-7046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802EDC031D2, 0xFFFFCA006A0BF680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/28/2018 1:43:22 PM 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!setjmpex+0x7499)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802EDC031D2, 0xFFFFCA006A0BF680, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 10/28/2018 11:33:16 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102818-6515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1A9490)
Bugcheck code: 0xC2 (0x7, 0x74696157, 0xD0005, 0xFFFFDD88420172C0)
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.



The following dump files were found but could not be read. These files may be corrupt:
C:\WINDOWS\Minidump\102818-6000-01.dmp
C:\WINDOWS\Minidump\102818-6484-01.dmp
C:\WINDOWS\Minidump\102818-6718-01.dmp




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

6 crash dumps have been found and analyzed. Only 3 are included in this report. No offending third party drivers have been found. Connsider 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 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.