CONNEXION
  • RetourJeux
    • Sorties
    • Hit Parade
    • Les + populaires
    • Les + attendus
    • Soluces
    • Tous les Jeux
    • Gaming
  • RetourActu Gaming
    • News
    • Astuces
    • Tests
    • Previews
    • Toute l'actu gaming
  • RetourBons plans
    • Bons plans
    • Bons plans Smartphone
    • Bons plans Hardware
    • Bons plans Image et Son
    • Bons plans Amazon
    • Bons plans Cdiscount
    • Bons plans Decathlon
    • Bons plans Fnac
    • Tous les Bons plans
  • RetourJVTech
    • Actus High-Tech
    • Intelligence Artificielle
    • Smartphones
    • Mobilité urbaine
    • Hardware
    • Image et son
    • Tutoriels
    • Tests produits High-Tech
    • Guides d'achat High-Tech
    • JVTech
  • RetourCulture
    • Actus Culture
    • Culture
  • RetourVidéos
    • A la une
    • Gaming Live
    • Vidéos Tests
    • Vidéos Previews
    • Gameplay
    • Trailers
    • Chroniques
    • Replay Web TV
    • Toutes les vidéos
  • RetourForums
    • Hardware PC
    • PS5
    • Switch 2
    • Xbox Series
    • Switch
    • Pokemon pocket
    • FC 25 Ultimate Team
    • League of Legends
    • Tous les Forums
  • PC
  • PS5
  • Xbox Series
  • Switch 2
  • PS4
  • One
  • Switch
  • iOS
  • Android
  • MMO
  • RPG
  • FPS
En ce moment Genshin Impact Valhalla Breath of the wild Animal Crossing GTA 5 Red dead 2
Liste des sujets

BSOD windows 8.1

zimard
zimard
Niveau 3
01 septembre 2015 à 19:06:47

Bonjour , alors voila je crée un sujet car depuis quelque temps le pc de mon frère ne fait que bluescreen sur bluescreen , tout d'abord sa config :

CM : gigabyte p55 ud3l
CPU : i5 760 non oc
CG : hd 7950
alim : corsair vs 550
ram : PC G.SKILL VALUE DDR3 2 X 4 GO 1333 MHZ NS
Windows 8.1

Donc deja voila , a savoir que tous les pilotes sont a jour , les températures sont plus que correct , par exemple le proc est a 35-38 degrés sur le bureau et en jeux max 65 degrés . La carte graphique , proc et ram sont fonctionnelles , tester sur un autre pc. je vous laisse aussi le rapport de who crashed :

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Tue 01/09/2015 16:34:31 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090115-16046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x124 (0x0, 0xFFFFE0002DF4A028, 0xF2000000, 0x20008F)
Error: WHEA_UNCORRECTABLE_ERROR
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Tue 01/09/2015 08:06:24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\090115-30828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x124 (0x0, 0xFFFFE000B9AC7028, 0xF2000000, 0x20008F)
Error: WHEA_UNCORRECTABLE_ERROR
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 23/08/2015 21:22:39 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082315-22953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0x124 (0x0, 0xFFFFE00020226028, 0xB2000000, 0x10005)
Error: WHEA_UNCORRECTABLE_ERROR
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Sun 23/08/2015 21:06:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082315-28000-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xA (0xFFFFF6D00075E200, 0x2, 0x0, 0xFFFFF8039E2B6ABE)
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 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 Sun 23/08/2015 20:06:55 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\082315-13390-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F9A0)
Bugcheck code: 0xA (0xFFFFF6D800027600, 0x2, 0x1, 0xFFFFF8001203013F)
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 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
--------------------------------------------------------------------------------

5 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

désolée de vous laisser un pavé comme sa mais au moins vous avez tout , merci d'avance pour votre aide :)

Message édité le 01 septembre 2015 à 19:11:18 par zimard
zimard
zimard
Niveau 3
01 septembre 2015 à 19:43:59

up

zimard
zimard
Niveau 3
02 septembre 2015 à 10:22:36

Up

KlugermanV
KlugermanV
Niveau 9
02 septembre 2015 à 10:24:25

Passe a windows10

KlugermanV
KlugermanV
Niveau 9
02 septembre 2015 à 10:25:44

C est le pilote de ta cg qui crash met a jour ton pc avec tous les drivers ainsi que le bios de ta carte mère

zimard
zimard
Niveau 3
02 septembre 2015 à 10:35:48

Changer d'os ne changera rien , cela le faisais même quand il y avais windows 7 et les pilotes de la carte graphique j'essaie mais j'y croit moyen car avant il avait une hd 5830 et sa faisais les bluescreen quand même ...

romaindu01
romaindu01
Niveau 1
02 septembre 2015 à 11:19:56

bonjour, tu as des erreurs WHEA qui sont des erreurs de processeur, vas faire un tour dans le bios il y a très souvent des paramètres d'overclocking automatique qui génèrent ce genre de problème, une recherche Google et on voit que se problème a été résolu de nombreuse fois comme ça sur le forum de driverscloud.

zimard
zimard
Niveau 3
02 septembre 2015 à 19:54:01

J'ai regarder et le bios est complètement par défaut depuis un moment donc je doute fortement que ce soit sa ...
Je pencherai pour le disque dur ou éventuellement l'alim ...
Le disque dur à chaque test sa me trouve aucune erreur

Sous forums
  • Aide à l'achat Mac
  • Création de Jeux
  • Linux
  • Création de sites web
  • Programmation
  • Internet
  • Steam Deck
  • Macintosh
  • Hardware
La vidéo du moment