Jump to content

Search the Community

Showing results for tags 'hal.dll'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Vie du site
    • Charte et mode d'emploi du forum
    • Actualités
    • Achats/Ventes informatiques
    • Point de détente
    • Bugs et améliorations du site
  • Software
    • Recherche pilote
    • BSOD / Plantages / Freeze
    • Systèmes d'exploitation
    • Logiciels et jeux (pour Windows)
    • Réseau
    • Sécurité
  • Hardware
    • Bien choisir son matériel
    • Composants
    • Périphériques
    • Overclocking
    • Refroidissement

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Lieu


Intérêts

Found 2 results

  1. Bonjour, mon ordinateur crash à des moment surprise, je suis victime de bsod intempestif ! Mes Core 1 et core 2 sont monté à 100 degré ce matin sur speed fan, je me suis rendu compte que mon cpu était overclocked... ( l'ordo n'a pas crash ) Après une mise à defaut du bios cpu seulement, win 10 à cessé de fonctionné et Bsod à chaque lancement, impossibilité d'aller sur ma session. J'ai donc formaté mon C et réinstallé mon système d'exploitation win10. Surprise Bsod après la moitié des installations des mises à jour ... Je remet par défaut mon bios entièrement en reconfigurant seulement mes DD en ahci. voila la story, c'est chiant, ça crash et ça abime mon casse coui*** ! Pouvez vous m'aidez à résoudre mon problème ? Merci d'avance, cordialement. https://www.driverscloud.com/fr/configuration/50488938-1/resume Je précise que mon cpu n'est pas overclocké. Mes ram sont des 1600mhz mais tourne à ~1300mhz car je ne peu pas activer le mod ( je sais plus le nom ) sans que cela overclock mon cpu :/ Bizarerie drivercloud me dit que mes rams sont des 667mhz ! Je n'arrive pas à faire de lien bsod, voici le detail : Informations générales Bug Check Code 0x00000124 Bug Check String WHEA_UNCORRECTABLE_ERROR Paramètre 1 0x0000000000000000 Paramètre 2 0xFFFF8202D3028028 Paramètre 3 0x00000000B2000000 Paramètre 4 0x0000000000010005 Date du crash 14/01/2018 00:03 Architecture x64 Version majeure 15 Version mineure 16299 Nombre de processeurs 4 Taille du fichier dump 316.21 Ko Hardware errors (WHEA) - severity:fatal error, notify type:Machine Check Exception (MCE) WHEA processeur fatal error, Microarchitecture error WHEA MCA fatal error, MCI_STATUS: 0xB200000000010005 (Internal Parity Error) Source du crash Source du crash pshed.dll+148A Chemin C:\WINDOWS\system32\pshed.dll Description Pilote d’erreurs matérielles spécifiques à une plateforme Version 10.0.16299.15 Compagnie Microsoft Corporation Taille 64.90 Ko Pile d'appels Adresse de la pile hal.dll+3C460 Adresse de la pile ntoskrnl.exe+280B92 Adresse de la pile ntoskrnl.exe+280E11 Adresse de la pile pshed.dll+148A Adresse de la pile ntoskrnl.exe+37D220 Adresse de la pile hal.dll+3BF1F Si besoin Zhpdiag.
  2. Salut a tous ! Ayant eu m'a config (commandé sur topachat) il y a moins d'1 mois et monté de mes propre main et qui fonctionné parfaitement jusqu'a quelques jours .... Je décide d'aller chez l'imformaticien afin de réparer mon ventilo ( Casser au cours du montage) et il me la rendu le jours même car plus de stock de ventillo dans un délai de 10 jours. Le soir je la monte et en ne faisant pas attention je l'a branche sur un second port graphique.Je lance le PC et commance a joué a un jeu et BOUM ! Mon first BSOD .... Me disant que c'était pas grave et je relance un autre jeu et second BSOD .... Puis un 3ème en relancant un autre jeu ..... Mes BSOD peuvent arriver a tous moment , aussi bien au début qu'en plein séance de jeu . Alors je panique .... J'ai peur .... Voici ma config : -Carte graphique VTX3D Radeon HD 7870 OC X-Edition, 2 Go -Processeur AMD FX-8350 Black Edition (4.0 GHz) -Carte mère ASRock 970 Extreme3 -Ventirad Coolermaster Hyper 212 EVO -Kit dual Channel DDR3 Corsair Vengeance, 2 x 4 Go, PC3-12800, CAS 9 -DD 2000go -Boitier PC Zalman Z11 Plus -Alimentation Antec High Current Gamer Series, 620 W J'ai fais WHOCRASHED : On Sat 02/02/2013 18:03:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\020213-34663-01.dmp This was probably caused by the following module: hal.dll (hal+0x12A3B) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008DCC028, 0xB0800000, 0x40151) Error: WHEA_UNCORRECTABLE_ERROR 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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 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 02/02/2013 18:03:51 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0x1E3) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008DCC028, 0xB0800000, 0x40151) Error: WHEA_UNCORRECTABLE_ERROR 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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 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 02/02/2013 16:55:09 GMT your computer crashed crash dump file: C:\Windows\Minidump\020213-25038-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90) 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 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 Sat 02/02/2013 16:30:17 GMT your computer crashed crash dump file: C:\Windows\Minidump\020213-29811-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EF90) 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 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 Sat 02/02/2013 15:36:42 GMT your computer crashed crash dump file: C:\Windows\Minidump\020213-27830-01.dmp This was probably caused by the following module: dxgmms1.sys (dxgmms1+0xC2B4) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800031009B2, 0xFFFFF88008F17768, 0xFFFFF88008F16FC0) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M 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 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 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 Mon 28/01/2013 18:37:34 GMT your computer crashed crash dump file: C:\Windows\Minidump\012813-29686-01.dmp This was probably caused by the following module: hal.dll (hal+0x12A3B) Bugcheck code: 0x124 (0x0, 0xFFFFFA8008DFA028, 0xB0800000, 0x40151) Error: WHEA_UNCORRECTABLE_ERROR 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 hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue. 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 26/01/2013 21:40:06 GMT your computer crashed crash dump file: C:\Windows\Minidump\012613-22900-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4) 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 Sat 26/01/2013 10:05:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\012613-25521-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030E61E6, 0xFFFFF8800BD61DE0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION 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 exception happened while executing a routine that transitions from non-privileged code to privileged code. 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 Fri 25/01/2013 21:31:52 GMT your computer crashed crash dump file: C:\Windows\Minidump\012513-25443-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800031179B2, 0x0, 0xFFFFFFFFFFFFFFFF) 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 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 Fri 25/01/2013 21:27:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\012513-24460-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880030FB180, 0x6) 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 appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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. Merci d'avance pour vos réponse ! merci ! H_azky
×
×
  • Create New...