BOSD je n'en peux plus ! Help svp !

  • Auteur de la discussion itunes user
  • Date de début

itunes user

Habitué
#1
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\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.



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\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.



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\ntoskrnl.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\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.



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\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.



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 !
 
Dernière édition par un modérateur:

vince1053

Modérateur
Staff
#2
Bonjour
Pour commencer, tu n'est pas à jour de Windows
la dernière version est la 20H2 de juillet 2020
va donc dans "Windows Up Date" et fais les mises à jours de ton OS, et refais les mises à jour des drivers (même si tu les à déjà fait)
Si tu as un antivirus tel que "AVAST" supprime le avec l'outil de désinstallation adéquat et réactive Windows Defender tout aussi efficace et surtout moins lourd puisque intégré.

D'autre part :
Cela peut venir du HDD défaillant
Donc fais un CHKDSK
pour cela clic droit sur le logo Windows
choisir power shell en admin
quand la fenêtre est ouverte tape CHKDSK et laisse faire, il va te vérifier et réparer s'il peut
Dans tous les cas, sauvegarde tes données et pense à changer ton HDD si trop de PB
 

itunes user

Habitué
#3
Bonjour et merci Vince pour ton aide !
Alors Windows me disait que j'étais à jour mais me donnait quand même la possibilité d'installer un pack optionnel..ce que j'ai fait

Je n'ai pas (à ma connaissance) d'autre antivirus que Bitdefender qui est actif.

J'ai fait le CHDSK pas de problème trouvé apparemment.
 

vince1053

Modérateur
Staff
#4
Plus haut je t'ai dit que Windows défender suffisait, mais tu fais ce que tu veux, c'est juste un conseil.

- Fait un petit nettoyage de la poussière
cela peut aussi venir de l'alim qui flanche, si tu peux tester avec une autre
 

itunes user

Habitué
#5
Je me suis trompé. C'est bien Windows defender qui est actif et lui seul.
L'alim est très récente.
En revanche pour la poussière c'est tout à fait possible car un pan de mon boitier est à nu.
Gros dépoussiérage prévu ce week-end du coup !
 
Vous devez vous inscrire ou vous connecter pour répondre ici.
Membres en ligne
  • yvesl
Derniers messages publiés
Statistiques globales
Discussions
861 993
Messages
7 744 285
Membres
1 582 326
Dernier membre
togna
Partager cette page
Haut