Problème BSOD
Fermé
Val
-
Modifié le 20 août 2019 à 08:00
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 21 août 2019 à 00:16
Malekal_morte- Messages postés 180304 Date d'inscription mercredi 17 mai 2006 Statut Modérateur, Contributeur sécurité Dernière intervention 15 décembre 2020 - 21 août 2019 à 00:16
A voir également:
- Problème BSOD
- Bsod - Guide
- Bsod ntoskrnl.exe - Windows 11
- Bsod memory_management - Forum Windows 10
- Bsod minidump ✓ - Forum Virus
- Bsod cache manager - Forum Windows
5 réponses
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 644
20 août 2019 à 08:02
20 août 2019 à 08:02
Salut,
Tu devrais faire jouer la garantie, ce n'est pas normal.
Il y a des chances que tu aies un problème matériel.
Tu devrais faire jouer la garantie, ce n'est pas normal.
Il y a des chances que tu aies un problème matériel.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 644
20 août 2019 à 14:52
20 août 2019 à 14:52
Faut plutôt utiliser Whocrashed,
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
On peut aussi utiliser WhoCrashed pour obtenir des informations sur ces plantages.
Télécharger et exécute Whocrashed : Telecharger WhoCrashed
=> Tutoriel WhoCrashed
Fais un copier/coller du contenu ici comme indiqué dans le tuto.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 644
20 août 2019 à 22:50
20 août 2019 à 22:50
Ca n'aide pas plus mais ça confirme que c'est bien matériel.
Faut tester le matos un par un.
Les magasins d'informatiques doivent pouvoir t'aider.
Faut tester le matos un par un.
Les magasins d'informatiques doivent pouvoir t'aider.
Malekal_morte-
Messages postés
180304
Date d'inscription
mercredi 17 mai 2006
Statut
Modérateur, Contributeur sécurité
Dernière intervention
15 décembre 2020
24 644
>
Val
21 août 2019 à 00:16
21 août 2019 à 00:16
bon courage à toi :)
voici le rapport de Blue screen view
==================================================
Dump File : 081819-7609-01.dmp
Crash Time : 18/08/2019 19:50:08
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000020
Parameter 2 : 00000000`00000000
Parameter 3 : ffffa180`8f579180
Parameter 4 : 00000000`00000003
Caused By Driver : hal.dll
Caused By Address : hal.dll+1848
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1bfcc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\081819-7609-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 18362
Dump File Size : 507 980
Dump File Time : 18/08/2019 19:50:44
==================================================
==================================================
Dump File : 081819-7609-01.dmp
Crash Time : 18/08/2019 19:50:08
Bug Check String :
Bug Check Code : 0x00000101
Parameter 1 : 00000000`00000020
Parameter 2 : 00000000`00000000
Parameter 3 : ffffa180`8f579180
Parameter 4 : 00000000`00000003
Caused By Driver : hal.dll
Caused By Address : hal.dll+1848
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+1bfcc0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\081819-7609-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 18362
Dump File Size : 507 980
Dump File Time : 18/08/2019 19:50:44
==================================================
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------
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 support visit www.resplendence.com/support
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 support 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: DESKTOP-EMF6LGO
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING EDGE AC (MS-7B17)
CPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 34292129792 bytes (31,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 20/08/2019 08:40:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082019-7984-01.dmp
This was probably caused by the following module: hal.dll (hal+0x491E1)
Bugcheck code: 0x9C (0x0, 0xFFFF86814642CCD0, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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/08/2019 08:40:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1AE1)
Bugcheck code: 0x9C (0x0, 0xFFFF86814642CCD0, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 19/08/2019 19:01:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081919-7640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x7F (0x8, 0xFFFF84011D564010, 0xFFFF94870E068F70, 0xFFFFF8055EDCBE94)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sun 18/08/2019 19:50:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081819-7609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFFA1808F579180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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.
Welcome to WhoCrashed (HOME EDITION) v 6.65
--------------------------------------------------------------------------------
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 support visit www.resplendence.com/support
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 support 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: DESKTOP-EMF6LGO
Windows version: Windows 10 , 10.0, version 1903, build: 18362
Windows dir: C:\WINDOWS
Hardware: MS-7B17, Micro-Star International Co., Ltd., MPG Z390 GAMING EDGE AC (MS-7B17)
CPU: GenuineIntel Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz Intel8664, level: 6
6 logical processors, active mask: 63
RAM: 34292129792 bytes (31,9GB)
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 20/08/2019 08:40:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\082019-7984-01.dmp
This was probably caused by the following module: hal.dll (hal+0x491E1)
Bugcheck code: 0x9C (0x0, 0xFFFF86814642CCD0, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
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/08/2019 08:40:56 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1AE1)
Bugcheck code: 0x9C (0x0, 0xFFFF86814642CCD0, 0x0, 0x0)
Error: MACHINE_CHECK_EXCEPTION
file path: C:\WINDOWS\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal machine check exception has occurred.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 19/08/2019 19:01:25 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081919-7640-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x7F (0x8, 0xFFFF84011D564010, 0xFFFF94870E068F70, 0xFFFFF8055EDCBE94)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also 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 Sun 18/08/2019 19:50:08 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\081819-7609-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1BFCC0)
Bugcheck code: 0x101 (0x20, 0x0, 0xFFFFA1808F579180, 0x3)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. This can be caused by non-responding hardware or by a overheated CPU (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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 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.
20 août 2019 à 08:03
20 août 2019 à 08:05
Faut que ça marche, c'est neuf.
C'est à eux de trouver et remplacer le composant défectueux.
20 août 2019 à 08:09
20 août 2019 à 08:10
Déjà essaye une barrette à la fois.
Après malheureusement à part tester les composants sur un autre PC voir si ça plante.
Par exemple la CG sur un autre PC ..... Mais ça demande des moyens.