Bugs intempestifs ordi

Bonjour,

Si ton PC indique un écran bleu (BSOD), il devrait y avoir un message d'erreur écrit sur l'écran. Précise-nous lequel ?...

Une copie d'écran serait la bienvenue pour comprendre.

Windows 7 n'est plus mis à jour depuis le 14 janvier 2020.

Hélas je n'ai pas fait fait de copie d'écran, j'ai juste ça:

Fichiers aidant à décrire le problème :

  C:\WINDOWS\Minidump\052124-13182-01.dmp

  C:\s\Francis\AppData\Local\Temp\WER-30778-0.sysdata.xml

Lire notre déclaration de confidentialité en ligne :

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x040c

Si la déclaration de confidentialité en ligne n’est pas disponible, lisez la version hors connexion :

  C:\Windows\system32\fr-FR\erofflps.txt

Voici l écran bleu que j'ai eu

salut

si le pc démarre, télécharge et exécute WhoCrashed ==> clique ici

poste le rapport via 1 copier/coller après le scan

@+

Welcome to WhoCrashed (Home Edition) v 6.70

This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical visit www.resplendence.com/

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...

 

Home Edition Notice

This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

PLEASE NOTE THAT THIS VERSION OF WHOCRASHED IS NOT LICENSED FOR USE BY PROFESSIONAL ENGINEERS.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
 

System Information (local)

Computer name: FRANCIS-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: XPS 8300 , Dell Inc., 0Y2MRG
U: GenuineIntel Intel(R) Core(TM) i7-2600 U @ 3.40GHz 8664, level: 6
8 logical processors, active mask: 255
RAM: 6424043520 bytes (6,0GB)


 

Crash Dump Analysis

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 24/05/2024 09:06:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052424-9578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFD22, 0x2, 0x0, 0xFFFFF8000329D530)
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 Fri 24/05/2024 09:06:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: aswarpot.sys (aswArPot+0x161DB)
Bugcheck code: 0xA (0xFFFFFFFFFFFFFD22, 0x2, 0x0, 0xFFFFF8000329D530)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\aswarpot.sys
product: Antivirus
company: Gen Digital Inc.
description: Gen Anti Rootkit
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.
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: aswarpot.sys (Gen Anti Rootkit, Gen Digital Inc.).
Google query: aswarpot.sys Gen Digital Inc. IRQL_NOT_LESS_OR_EQUAL



On Fri 24/05/2024 08:43:38 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052424-10888-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0)
Bugcheck code: 0x4E (0x7, 0xC28CF, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
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 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.



On Fri 24/05/2024 07:48:31 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052424-10093-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0)
Bugcheck code: 0xA (0x20, 0x2, 0x0, 0xFFFFF8000329DCAD)
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 Thu 23/05/2024 09:02:10 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052324-10452-01.dmp
This was probably caused by the following module: iastor.sys (0xFFFFF880010D1C46)
Bugcheck code: 0x50 (0xFFFFF3001EEF7878, 0x1, 0xFFFFF880010D1C46, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\iastor.sys
product: Intel Rapid Storage Technology driver
company: Intel Corporation
description: Intel Rapid Storage Technology driver - x64
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 a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Tue 21/05/2024 08:46:50 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052124-13182-01.dmp
This was probably caused by the following module: atikmdag.sys (atikmdag+0x2A161)
Bugcheck code: 0xA (0xFFFFF8800B242280, 0xC, 0x1, 0xFFFFF8000329066A)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: Advanced Micro Devices, Inc.
description: ATI Radeon Kernel Mode Driver
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.
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: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).
Google query: atikmdag.sys Advanced Micro Devices, Inc. IRQL_NOT_LESS_OR_EQUAL



On Mon 20/05/2024 09:38:23 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\052024-6786-01.dmp
This was probably caused by the following module: aswarpot.sys (aswArPot+0xC794)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8000323FCC9, 0x1, 0x1DAB6B3D)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\aswarpot.sys
product: Antivirus
company: Gen Digital Inc.
description: Gen Anti Rootkit
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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: aswarpot.sys (Gen Anti Rootkit, Gen Digital Inc.).
Google query: aswarpot.sys Gen Digital Inc. KMODE_EXCEPTION_NOT_HANDLED



On Sun 19/05/2024 09:30:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\051924-17316-01.dmp
This was probably caused by the following module: dxgmms1.sys (0xFFFFF88004F734D1)
Bugcheck code: 0xD1 (0x100FABD, 0x2, 0x1, 0xFFFFF88004F734D1)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
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.
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 Sat 16/03/2024 11:44:05 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\031624-15147-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93E70)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
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/02/2024 18:43:55 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\020424-10904-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x93EA0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80003234BB0, 0x1, 0x1030)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



 

Conclusion

On your computer a total of 12 crash dumps have been found. Only 10 have been analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

aswarpot.sys (Gen Anti Rootkit, Gen Digital Inc.)
atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by s who have been experiencing similar problems.


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.



 

re

tu as plusieurs pilotes non à jour sur le pc

tu as Avast qui n'est pas à jour

regarde dans le gestionnaire de périphériques si tu as des alertes (? ou /!\) jaune

poste 1 capture d'écran de ton gestionnaire de périphériques clique ici

@+

apparemment pas de problème sur le gestionnaire. Comment puis je installer les pilotes non à jour?

re

teste ton HDD avec CrystalDiskInfo clique ici

donne l'état de santé et la T° (poste 1 capture d'écran)

@+

re

tu as le N-O-Q:\ qui est en "Prudence"

il va "lâcher", mais on ne sais pas quand...

peux-tu enlever le disque et regarder si le plante encore par la suite?

@+

je vais le faire. J'ai mis à jour mes drivers obsolètes. Pour DD il n'y a pas moyen de réparer les secteurs défectueux?

re

ok pour les drivers

pour le DD, tu parles de celui qui est en prudence?

@+

oui

re

ok, tu as enlevé/débranché le DD qui est en prudence?

PS: éteint le pc et débranche le du secteur avant d'exécuter la manipulation

@+

et ensuite?

re

si tu as débranché le DD en prudence, redémarre le pc et regarde si tu as encore des crahs (BDSO) écran bleu

@+

j'ai déjà fait ça et pour l'instant pas de crash. tu ne pas dis si je peux réparer le DD en prudence

re

j'ai déjà fait ça et pour l'instant pas de crash

ok

tu ne pas dis si je peux réparer le DD en prudence

si le DD est encore accessible, sauvegarde tes données sur 1 DD externe (par exemple) avant de faire 1 manipulation sur le DD en prudence

dis-moi quand c'est fait

@+

le DD en prudence c'est déjà un dd externe, donc je sauvegarde les données sur un autre DD