Écrans bleu ou crashs

Bonjour et merci pour votre réponse ! :D


Je viens a peine de le faire te voici ce que ça me donne :

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

Computer name: ROGER
Windows version: Windows 10 , 10.0, build: 16299
Windows dir: C:\WINDOWS
Hardware: GL553VD, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 12760391680 bytes total




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

Crash dumps are enabled on your computer.

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

On Fri 27/04/2018 11:26:02 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\042718-25031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x175930)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFF928, 0x0, 0xFFFFF8025C4DAA6B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Fri 27/04/2018 11:26:02 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!memset+0x21BD1)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFF928, 0x0, 0xFFFFF8025C4DAA6B, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Bug check description: This indicates that invalid system memory has been referenced.
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\042518-29968-01.dmp

Re : un petit oublie de ma part :

La ( conclusion )

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

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