Hey salut à tous, alors voilà je me suis taper des blues screen je ne sais pas pourquoi, rien de chelou d'installer je fait attention.
J'ai fait une analyse sur Who Crashed et j'ai eu ça:
Ne m'y connaissant pas je ne sais pas d'où ça vient.... Je ne sais pas comment arranger ça.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 28/10/2020 01:32:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102820-12359-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073261A876, 0xFFFF8F01149D9920, 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 Wed 28/10/2020 01:32:56 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+0x8279)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8073261A876, 0xFFFF8F01149D9920, 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 Mon 26/10/2020 23:47:01 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102620-14406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1 (0x7FFC88F2BE14, 0x0, 0xFFFF, 0xFFFFD283EB7E2B80)
Error: APC_INDEX_MISMATCH
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 there has been a mismatch in the APC state index.
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 Tue 20/10/2020 01:15:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\102020-7484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xA (0xFFFFA6274F1D27A0, 0xFF, 0xFC, 0xFFFFF8066CD2860C)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. 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.
---------------
KAYHLL
peux-tu me dire ?