Écran bleu windows 10

Bonjour,

J'ai un soucis avec mon pc, je pense que c'est une Ram qui bug (j'ai fait tout les tests avec CrystalDiskInfo, Whocrashed, vérification de la mémoire Windows qui à montrer un soucis de mémoire, des disques et mise à jour des pilotes qui doivent être fait à 100%) problème, quand je l'enlève c'est encore pire. J'ai écran bleu avec l'erreur "storport.sys" , donc je me pose la question si j'ai pas fait de fausse manipulation ou autre.

Le bug à lieu que quand je lance un jeu, ou en pleine partit. Si je fait que de la bureautique aucun soucis le pc tourne.

Voici le rapport de Whocrashed

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

Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\WINDOWS
Hardware: MS-7821, MSI, Z87-G45 GAMING (MS-7821)
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17121157120 bytes total

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

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

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

On Thu 26/07/2018 16:16:32 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072618-35500-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF80392602751)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80392602751, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
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 storage driver or controller 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.

On Thu 26/07/2018 16:06:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072618-52625-01.dmp
This was probably caused by the following module: storport.sys (0xFFFFF804808026C9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF804808026C9, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\storport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Microsoft Storage Port Driver
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 storage driver or controller 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.

On Thu 26/07/2018 15:51:29 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072618-27937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803A843A127, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 26/07/2018 13:59:36 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072618-42953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80321834127, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Thu 26/07/2018 00:39:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072618-77296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8036F249127, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Wed 25/07/2018 20:22:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\072518-49078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198430)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF803AFBA1127, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 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 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\MEMORY.DMP

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

7 crash dumps have been found and analyzed. Only 6 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.


Merci d'avance pour vos réponses et votre aides.