Bonjour à tous,
(je ne sais pas si je suis dans la bonne catégorie)
J'ai depuis quelques mois de gros soucis de BSOD, divers et variés. Une fois sur deux la tour semble lancée mais aucun périphérique ne fonctionne (ecran noir, pas de detection de la souris et du clavier etc...), je l’éteins et par magie j'arrive à aller sur le bureau. Parfois entres les deux j'ai une succession de BSOD (irql_not_less_or_equal, Kernel Security Check Failure, system service exception, driver not less or equal, kmode exception not handled, ...), parfois les erreurs 0xc0000001 0xc0000428 et 0xc0000221 m’empêchaient même de mettre le mode sans echec...
Pour informations, lors des premiers BSOD, j'ai totalement réinstallé win10, j'ai fait une MAJ du BIOS, des drivers, j'ai reinstallé mes drivers CG via le logiciel GEFORCE EXPERIENCE que je maintient à jour.
J'ai effectué un un teste mémoire windows qui n'a rien donné (il est resté figé à 2% pendant 5h). Par contre j'ai également effectué un MEMtest86 qui à complètement craqué au test6 (il m'a trouvé 36667 erreurs ^^). j'ai retiré l'une des deux barrettes et le test c'est très bien passé, j'ai mis lautres, pareil. Par contre j'ai remis les deux sur les mêmes slot et il s'est bien passé aussi... Incompréhensible pour mes piètres connaissances informatique ^^.
J’écris ce message depuis l’ordinateur en question qui ne plante bizarrement pas pour le moment, parfois les BSOD sont à la chaine dès l'allumage, parfois il interviennt quand je suis sur un jeu genre WOW, c'est totalement random.
J'ai installé le logiciel de chez Crucial pour voir l'était de mon SSD et celui-ci me dit qu'il n'y a rien mais je ne sais pas ce que valent ses infos... >>> https://www.zupimages.net/up/20/14/it20.png
Les températures semblent corrects: (screen ici)>>>>> https://www.zupimages.net/up/20/14/e372.png
Commande utilisés egalement pour remettre un peu d'ordre: sfc /scannow et chkdsk /f
Rapport WhoCrashed:
__________________________________________________________________________________________
ystem Information (local)
Computer name: PC_MATERIEL_NET
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: MS-7998, MSI, Z170A SLI PLUS (MS-7998)
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel8664, level: 6
8 logical processors, active mask: 255
RAM: 17138491392 bytes (16,0GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Sat 04/04/2020 15:32:42 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040420-14734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x1 (0x7FFA2CDBCB64, 0x0, 0xFFFF0000, 0xFFFF8982B0507A80)
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 Sat 04/04/2020 15:32:42 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+0x8219)
Bugcheck code: 0x1 (0x7FFA2CDBCB64, 0x0, 0xFFFF0000, 0xFFFF8982B0507A80)
Error: APC_INDEX_MISMATCH
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 Sat 04/04/2020 15:30:54 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040420-14375-01.dmp
This was probably caused by the following module: wof.sys (Wof+0x7223)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8056E7C9437, 0xFFFFF8824856F6A8, 0xFFFFF8824856EEF0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\wof.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Filtre de superposition Windows
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
On Thu 02/04/2020 19:36:24 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040220-13671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x139 (0x4, 0xFFFFAF812EC45FF0, 0xFFFFAF812EC45F48, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
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 02/04/2020 18:17:01 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040220-14156-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1C1510)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8030F6446BC, 0xFFFF8C8057F1D9E0, 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.
The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\Minidump\040420-14281-01.dmp
C:\WINDOWS\Minidump\040220-13640-01.dmp
C:\WINDOWS\Minidump\040220-13875-01.dmp
C:\WINDOWS\Minidump\033020-14953-01.dmp
Conclusion
9 crash dumps have been found and analyzed. Only 5 are included in this report. If dump files are found and they could not be analuzed, it means they are corrupted. Because crash dumps are an emergency measure it is not uncommon for this to happen, however often it points to a problem in the storage stack. It is suggested that you run CHKDSK on your system drive to check your drive for errors.
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 aides, je vais poster le message avant le prochain BSOD ^^.
EDIT: impossible d'avoir le detail de certain blue screen après 16h, il y avait notamment : "driver not less or equal, kmode exception not handled, erreur 0xc0000001 et erreur 0xc0000428" à la suite. Peut-être que le rapport n'a aps le temps d'être créé...
Message édité par jhuntao666 le 05-04-2020 à 14:11:10
