Ecrans bleus... je n'en peux plus ! Fermé

Question

Bonjour à tous,

J'espère que vous passez un bon week-end de trois jours ;-)

De mon côté je me dis que c'est l'occasion de regarder de plus près mon problème de pc.

Cela fait maintenant trop longtemps que je n'arrive plus à avoir un pc stable qui ne plante pas sans arrêt.
J'ai changé les RAM, le ssd, la carte mère, etc.. réinstallé windows de zéro deux ou trois fois.
Le seul truc qui date un peu il me semble ce sont les HDD contenant mes data et backup.

Mon PC me fait des écrans bleus très très régulièrement (sympa en pleine partie de jeu).

L'antimalware ne détecte jamais rien.
J'ai mis à jour presque tous mes drivers.

J'ai installer il y a un mois Whocrashed et voici un rapport d'aujourd'hui:

Windows version: Windows 10, 10.0, version 2009, build: 19042
Windows dir: C:\WINDOWS
Hardware: ASRock, B450M Pro4
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor 8664, level: 23
12 logical processors, active mask: 4095
RAM: 17109413888 bytes (15,9GB)




Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump

On Sun 04/04/2021 18:52:19 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040421-8484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xA (0xF8, 0xFF, 0x0, 0xFFFFF80717471355)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32
toskrnl.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.



On Sun 04/04/2021 18:52:19 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+0x81C9)
Bugcheck code: 0xA (0xF8, 0xFF, 0x0, 0xFFFFF80717471355)
Error: IRQL_NOT_LESS_OR_EQUAL
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.



On Sun 04/04/2021 15:10:39 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040421-20296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xA (0xFFFFAD8166E00070, 0x2, 0x0, 0xFFFFF80580571629)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32
toskrnl.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.



On Sat 03/04/2021 03:59:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040321-34593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xEF (0xFFFFAE87187020C0, 0x0, 0x0, 0x0)
Error: CRITICAL_PROCESS_DIED
file path: C:\WINDOWS\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a critical system process died.
There is a possibility this problem was caused by a virus or other malware.
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 03/04/2021 03:53:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040321-16046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0xA (0x80024, 0x2, 0x0, 0xFFFFF80572C439AC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32
toskrnl.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.



On Wed 31/03/2021 00:29:47 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\033121-11781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5C50)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFC42, 0x0, 0xFFFFF80768863E6B, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\WINDOWS\system32
toskrnl.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.



The following dump files were found but could not be read. These files may be corrupted:
C:\WINDOWS\LiveKernelReports\PdcLockWatchdog-20210330-2207.dmp




Conclusion


7 crash dumps have been found and analyzed. Only 6 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.

Est-ce que vous savez ce que je peux faire ?
Merci d'avance !



Configuration: Windows / Chrome 89.0.4389.114

AgentMulder · Answer

Bonjour,

Il y a quelques diagnostics à faire je pense afin d'isoler le problème.

Déjà, as-tu une carte graphique ? Si oui as-tu mis à jour les drivers récemment ?

Ensuite vérifier l'état des disques durs avec CrystalDiskInfo :
https://crystalmark.info/en/software/crystaldiskinfo/
Si un disque ne ressort par bleu, il y a un souci.

Puis faire un memtest afin de s'assurer que la RAM ou les slots de RAM ne sont pas corrompus ou endommagés :
https://www.commentcamarche.net/informatique/composants/1437-tester-la-memoire-vive-ram-d-un-ordinateur-avec-memtest86/

Seb23_ · Answer

Edit

AgentMulder · Answer

Ce n'est pas normal que ton processeur chauffe aussi vite. Il doit y avoir un souci avec le refroidissement.

Quel système de refroidissement du processeur as-tu ? Le ventilateur livré avec le processeur ? Ou un autre ? Est ce que la pate thermique a ete bien mise ?

jumulka · Answer

Salut,
je dirais de changer la carte mère, je conseil une asus ou msi. je me base sur les bsod et le fais que j'ai eu ce problème sur une asrock ab350m pro4. 

c'est quoi le modèle précis de la ram et quel configuration (4x4go, 2x8go) ? 
si 4x4 essaye en 2x4go sur slot 1 et 3, si 2x8 essaye en mettant une seul barrette sur le slot 1

seb77150 · Answer

Salut, en mettant la température max a 90 degrés, ça donne quoi dans occt si tu relance un test OOCT en large data set pour commencer ?

Seb23_ · Answer

Bonsoir tout le monde,

Alors voici les news.

Depuis la semaine dernière je n'ai eu que deux écrans bleus. (rapport plus bas) 

A savoir que j'ai aussi fait une maj de windows à la main (complément disponible qui ne se lançait pas de façon auto).

J'ai aussi fait un gros dépoussiérage aujourd'hui et refermé le boîtier.
Les températures CPU et GPU sont bien plus basses.

J'ai fait un OCCT small data sur 10 mn. C'est monté jusquà 54°. Pas d'erreurs détectées.


PS : je suis passé chez LDLC hier et le vendeur ne croyaiçs pas que c'était possible que j'ai la RAM susmentionnée car en 3000Hz elle ne devrait pas être compatible.
J'ai vérifié pdt le ménage de ce jour et c'est pourtant bien celle que j'ai.  (et sur Amazon dans le commentaires il est dit que c'est parfaitement compatible). Bref ça reste quand même une piste (cf com de jumulka) si le ménage n'aura pas été suffisant.


J'aurais tendance à attendre un peu pour voir les résultat du dépoussiérage mais vous avez d'autres conseils pour la suite des évènements ? Je dois continuer quelques test OCCT ?



Crash dump directories: 
C:\WINDOWS
C:\WINDOWS\Minidump

On Wed 07/04/2021 21:16:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040721-18296-01.dmp
This was probably caused by the following module: rtwlanu.sys (0xFFFFF8010B72DF62) 
Bugcheck code: 0xD1 (0x300383, 0x2, 0x1, 0xFFFFF8010B72DF62)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\driverstwlanu.sys
product: Realtek WLAN Wireless USB 2.0 Adapter 
company: Realtek Semiconductor Corporation 
description: Realtek WLAN USB NDIS Driver 80816
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtwlanu.sys (Realtek WLAN USB NDIS Driver 80816, Realtek Semiconductor Corporation ). 
Google query: rtwlanu.sys Realtek Semiconductor Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Wed 07/04/2021 21:16:38 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: rtwlanu.sys (0xFFFFF8010B72DF62) 
Bugcheck code: 0xD1 (0x300383, 0x2, 0x1, 0xFFFFF8010B72DF62)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\driverstwlanu.sys
product: Realtek WLAN Wireless USB 2.0 Adapter 
company: Realtek Semiconductor Corporation 
description: Realtek WLAN USB NDIS Driver 80816
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. 
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. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: rtwlanu.sys (Realtek WLAN USB NDIS Driver 80816, Realtek Semiconductor Corporation ). 
Google query: rtwlanu.sys Realtek Semiconductor Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Tue 06/04/2021 21:27:43 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\040621-10921-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F5DB0) 
Bugcheck code: 0x4E (0x8D, 0x1344C5, 0x4100B5, 0xFFFFC78E8CA26DB0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32
toskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the page frame number (PFN) list is corrupted. 
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.

Seb23 · Answer

Bonjour à tous,

Cela fait maintenant une semaine sans écran bleus...c'est top. Espérons que ça continue comme ça et donc un GRAND merci à vous tous !!

Question complémentaire. : je me rend compte que mes boutons pour gérer la vitesse des ventilos en fait ne fonctionnent pas (sans doute pas branchés sur la CM). Est-ce qu'il existe un logiciel simple et efficace pour gérer les vitesses (et éventuellement stipuler un seuil de température ou les ventilo se remette en gestion auto) ?

Ecrans bleus... je n'en peux plus !

7 réponses

Discussions similaires