comme ecrit dans ma presentation, je me suis inscrit ici car j'ai un soucis d'ecran bleu sur mon PC
ma config est dans ma signature
l'ecran bleu se presente quand je sort le PC de sa veille, et uniquement dans ce cas là
jamais de soucis en fonctionnement, il ne rame pas, que ce soit en bureautique ou en jeu, et les temperature sont OK, CPU à 30° au repos et 40/45° en jeu, GPU à 47° au repos, 70/80° en jeux (vive AMD
)le premier BSOD s'est manifesté le 27 fevrier, puis le 3 mars, le 6 et enfin aujourd'hui le 8 (je n'ai pas fais de photo de ce dernier)
et voila le rapport de whocrashed de ce soir concernant les 3 dernier BSOD (apres celui du 27 j'ai passé un coup de Ccleaner donc pas de rapport)
Code : Tout sélectionner
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 08/03/2015 21:41:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-6302-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF800034CC8EC)
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 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 06/03/2015 16:06:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030615-8361-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF8000348B8EC)
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 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 03/03/2015 17:37:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030315-8361-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x1 (0x773D168A, 0x0, 0xFFFF0000, 0xFFFFF8800ED0FB60)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
3 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.
j'ai effectué un Memtest, qui est OK
j'ai tester mes disque via crystaldiskmark, pas de soucis
hier j'ai trouvé une maj du firmware de mon SSD, concernant un possible bug en sortie de veille du PC justement
http://www.nextinpact.com/news/78856-le ... crucia.htm
donc je l'ai fais, mais ce soir l'ecran bleu est revenu donc je suppose que ce n'etait pas ca
et là, j'arrive à la limite de mes competence, donc j'espere trouver de l'aide ici
sachant que je n'ai pas de materiel de rechange pour "tester" quoi que ce soit (pas d'ancienne CG ni d'autre barrette de ram)
