Blue Screen différent à chaque démarrage
Fardemus
Messages postés
2
Date d'inscription
Statut
Membre
Dernière intervention
-
Fardemus Messages postés 2 Date d'inscription Statut Membre Dernière intervention -
Fardemus Messages postés 2 Date d'inscription Statut Membre Dernière intervention -
Bonjour,
Je reçois récemment des bsod à chaque fois que je démarre mon ordinateur et à chaque fois le message d'erreur est différent. J'ai fait une analyse avec le logiciel "WhoCrashed" dont je vais coller ici une copie du résultat. Je tiens à préciser que malgré les multiples écrans bleus qui ne se produisent uniquement au démarrage, mon ordinateur tourne comme si tout allait bien après avoir redémarré, du moins c'est mon ressentit:
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-AOPNVFQ
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: Z390 AORUS PRO WIFI, Gigabyte Technology Co., Ltd., Z390 AORUS PRO WIFI-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 17109938176 bytes (15,9GB)
--------------------------------------------------------------------------------
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 Tue 20/10/2020 11:58:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102020-5984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xA (0xFFFFFFF8, 0x2, 0x0, 0xFFFFF806256C8230)
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 Tue 20/10/2020 11:58:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltIsCallbackDataDirty+0x1267)
Bugcheck code: 0xA (0xFFFFFFF8, 0x2, 0x0, 0xFFFFF806256C8230)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 a file system 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 Mon 19/10/2020 10:14:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101920-10515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1A (0x31, 0xFFFFAD01ACF496E0, 0xFFFFC38060BE1000, 0xFFFF9C03BC5E2000)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The image relocation fix-up table or code stream has been corrupted. This is probably a hardware error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
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 18/10/2020 11:16:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-5703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1A (0x41790, 0xFFFFF98007F7F220, 0x53, 0x5B)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. A page table page has been corrupted.
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. This problem might also be caused because of overheating (thermal issue).
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 18/10/2020 11:04:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-5234-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF98000019ED0, 0x100000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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. This problem might also be caused because of overheating (thermal issue).
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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Sun 18/10/2020 11:00:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-5765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3571FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803599571FD, 0xFFFFF5073968F0F8, 0xFFFFF5073968E930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has 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:
hardware.sys
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 users 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.
Je reçois récemment des bsod à chaque fois que je démarre mon ordinateur et à chaque fois le message d'erreur est différent. J'ai fait une analyse avec le logiciel "WhoCrashed" dont je vais coller ici une copie du résultat. Je tiens à préciser que malgré les multiples écrans bleus qui ne se produisent uniquement au démarrage, mon ordinateur tourne comme si tout allait bien après avoir redémarré, du moins c'est mon ressentit:
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-AOPNVFQ
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\WINDOWS
Hardware: Z390 AORUS PRO WIFI, Gigabyte Technology Co., Ltd., Z390 AORUS PRO WIFI-CF
CPU: GenuineIntel Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 17109938176 bytes (15,9GB)
--------------------------------------------------------------------------------
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 Tue 20/10/2020 11:58:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\102020-5984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0xA (0xFFFFFFF8, 0x2, 0x0, 0xFFFFF806256C8230)
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 Tue 20/10/2020 11:58:31 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltIsCallbackDataDirty+0x1267)
Bugcheck code: 0xA (0xFFFFFFF8, 0x2, 0x0, 0xFFFFF806256C8230)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\fltmgr.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Gestionnaire de filtres de système de fichiers Microsoft
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 a file system 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 Mon 19/10/2020 10:14:35 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101920-10515-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F45A0)
Bugcheck code: 0x1A (0x31, 0xFFFFAD01ACF496E0, 0xFFFFC38060BE1000, 0xFFFF9C03BC5E2000)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. The image relocation fix-up table or code stream has been corrupted. This is probably a hardware error.
This is likely to be caused by a hardware problem. This error suggests a case of memory corruption because of a hardware problem. It is suggested you do a test on your RAM modules (memory test) and make sure your system is not getting overheated. This problem might also be caused because of overheating (thermal issue).
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 18/10/2020 11:16:37 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-5703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3F3EA0)
Bugcheck code: 0x1A (0x41790, 0xFFFFF98007F7F220, 0x53, 0x5B)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred. A page table page has been corrupted.
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. This problem might also be caused because of overheating (thermal issue).
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 18/10/2020 11:04:22 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-5234-01.dmp
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFFF98000019ED0, 0x100000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
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. This problem might also be caused because of overheating (thermal issue).
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: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
On Sun 18/10/2020 11:00:15 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\101820-5765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3571FD)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803599571FD, 0xFFFFF5073968F0F8, 0xFFFFF5073968E930)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
6 crash dumps have been found and analyzed. A third party driver has 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:
hardware.sys
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 users 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.
A voir également:
- Blue screen au démarrage
- Ordinateur lent au démarrage - Guide
- Blue screen windows 10 - Guide
- Reinitialiser pc au demarrage - Guide
- Forcer demarrage pc - Guide
- Qu'est ce qui se lance au démarrage de l'ordinateur - Guide
3 réponses
Bonjour, le crash du 20/10/2020 à 11:58:31 a pour effet un problème de disque dur.
Appuyer sur les touches Windows et X et cliquer sur powershell (admin) et copier la commande :
CHKDSK /F /X
Répondre "o" et redémarrer le PC.
Reviens nous dire si la situation s'est améliorée.
Appuyer sur les touches Windows et X et cliquer sur powershell (admin) et copier la commande :
CHKDSK /F /X
Répondre "o" et redémarrer le PC.
Reviens nous dire si la situation s'est améliorée.
Fardemus
Messages postés
2
Date d'inscription
Statut
Membre
Dernière intervention
Ok, je viens de redémarrer mon pc, je l'ai également éteint puis simplement rallumé et il pas de blue screen à l'horizon. Merci pour l'instant je vous tiens au courant si je n'en reçoit plus ou si au contraire un nouveau apparaît.
Bonjour,
Regardes ici , quelques solutions pour C:\WINDOWS\system32\drivers\fltmgr.sys
https://www.malekal.com/bsod-plantages-fltmgr-sys/
Regardes ici , quelques solutions pour C:\WINDOWS\system32\drivers\fltmgr.sys
https://www.malekal.com/bsod-plantages-fltmgr-sys/
