A l'aide erreur STOP : 0X00000050
Fermé
chdu57
Messages postés
590
Date d'inscription
samedi 26 décembre 2009
Statut
Membre
Dernière intervention
5 juillet 2023
-
20 févr. 2015 à 12:58
chdu57 Messages postés 590 Date d'inscription samedi 26 décembre 2009 Statut Membre Dernière intervention 5 juillet 2023 - 24 févr. 2015 à 17:24
chdu57 Messages postés 590 Date d'inscription samedi 26 décembre 2009 Statut Membre Dernière intervention 5 juillet 2023 - 24 févr. 2015 à 17:24
A voir également:
- A l'aide erreur STOP : 0X00000050
- Erreur 0x80070643 - Guide
- 36200 stop - Guide
- Stop pub gratuit - Télécharger - Divers Utilitaires
- Windows stop code - Guide
- Erreur 0x80070643 Windows 10 : comment résoudre le problème de la mise à jour KB5001716 - Guide
7 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 651
21 févr. 2015 à 12:04
21 févr. 2015 à 12:04
Salut,
Voir explication sur les BSOD : https://forum.malekal.com/viewtopic.php?t=47660&start=
En général, prob matériel, bug de drivers ou éventuellement un malware.
Faudrait donner un rapport whocrashed pour voir.
Voir explication sur les BSOD : https://forum.malekal.com/viewtopic.php?t=47660&start=
En général, prob matériel, bug de drivers ou éventuellement un malware.
Faudrait donner un rapport whocrashed pour voir.
chdu57
Messages postés
590
Date d'inscription
samedi 26 décembre 2009
Statut
Membre
Dernière intervention
5 juillet 2023
9
22 févr. 2015 à 00:52
22 févr. 2015 à 00:52
Bonjour comment puis je faire le rapport
chdu57
Messages postés
590
Date d'inscription
samedi 26 décembre 2009
Statut
Membre
Dernière intervention
5 juillet 2023
9
22 févr. 2015 à 01:25
22 févr. 2015 à 01:25
voila le rapport
--------------------------------------------------------------------------------
Welcome to WhoCrashed (HOME EDITION) v 5.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue 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.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: BUREAU-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: hp workstation xw6200, Hewlett-Packard, 08B8h
CPU: GenuineIntel Intel(R) Xeon(TM) CPU 3.40GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 8589488128 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 21/02/2015 09:56:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022115-22671-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F2AF0, 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 a standard 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 21/02/2015 09:56:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalInitializeBios+0x1500)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F2AF0, 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 a standard 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 Fri 20/02/2015 11:47:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022015-30687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x50 (0xFFFFE28006EC11A0, 0x0, 0xFFFFF80002B85D2C, 0x7)
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.
On Wed 18/02/2015 02:17:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021815-66484-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880078740F8, 0xFFFFF88007873950, 0xFFFFF80002AE56C0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard 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.
--------------------------------------------------------------------------------
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 5.03
--------------------------------------------------------------------------------
This program checks for drivers which have been crashing your computer. If your computer has displayed a blue screen of death, suddenly rebooted or shut down then this program will help you find the root cause and possibly a solution.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue 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.
Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
computer name: BUREAU-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: hp workstation xw6200, Hewlett-Packard, 08B8h
CPU: GenuineIntel Intel(R) Xeon(TM) CPU 3.40GHz Intel586, level: 15
2 logical processors, active mask: 3
RAM: 8589488128 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sat 21/02/2015 09:56:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022115-22671-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12818)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F2AF0, 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 a standard 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 21/02/2015 09:56:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalInitializeBios+0x1500)
Bugcheck code: 0x9C (0x0, 0xFFFFF880009F2AF0, 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 a standard 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 Fri 20/02/2015 11:47:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022015-30687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74EC0)
Bugcheck code: 0x50 (0xFFFFE28006EC11A0, 0x0, 0xFFFFF80002B85D2C, 0x7)
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.
On Wed 18/02/2015 02:17:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021815-66484-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4211)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880078740F8, 0xFFFFF88007873950, 0xFFFFF80002AE56C0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Système d'exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote du système de fichiers NT
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard 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.
--------------------------------------------------------------------------------
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.
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 651
22 févr. 2015 à 11:05
22 févr. 2015 à 11:05
Ca doit être un problème matériel.
Tu n'as pas touché les branchements disque dur etc?
Tu n'as pas touché les branchements disque dur etc?
Vous n’avez pas trouvé la réponse que vous recherchez ?
Posez votre question
chdu57
Messages postés
590
Date d'inscription
samedi 26 décembre 2009
Statut
Membre
Dernière intervention
5 juillet 2023
9
22 févr. 2015 à 11:27
22 févr. 2015 à 11:27
non rien je viens d'ailleur de le formater en voulant régler ce problème
lors de chaque démarrage , au bout de 3 mn j'ai cette page puis je force un redemarrage et la plus de problème pendant des heures
lors de chaque démarrage , au bout de 3 mn j'ai cette page puis je force un redemarrage et la plus de problème pendant des heures
chdu57
Messages postés
590
Date d'inscription
samedi 26 décembre 2009
Statut
Membre
Dernière intervention
5 juillet 2023
9
22 févr. 2015 à 18:00
22 févr. 2015 à 18:00
je venais de le formatter pour ce problem et après formatage, a nouveau le probleme
chdu57
Messages postés
590
Date d'inscription
samedi 26 décembre 2009
Statut
Membre
Dernière intervention
5 juillet 2023
9
24 févr. 2015 à 17:24
24 févr. 2015 à 17:24
que puis je faire maintenant stp
