Hello =)
Voila, en ayant fait récemment l'acquisition d'une nouvelle carte graphique,d'un nouveau processeur et d'une nouvelle alimentation, je remarque que de temps en temps l'ordi s’éteint (Bsod/écran noir ou écran avec soucis de ré affichage de bureau/redémarrage) tout seul.
Je n'ai en ce moment aucun overclockage, autant en cg qu'en proco. J'ai l'impression qu'il manque quelque chose que je n'ai pas fait ou une incompatibilité avec ma carte mère ou je sais pas trop quoi.. (j'ai mis a jour le bios après tout ces problèmes mais ça n'a pas changé) toute ma config est dans Mon matériel, à vos claviers =)
Merci beaucoup par avance pour vos réponses.
Il y a actuellement 169 visiteurs
Jeudi 18 Avril 2024
       |
Ordi qui s’éteint tout seul
7 messages
• Page 1 sur 1
Re: Ordi qui s’éteint tout seul
le 28 Nov 2014 21:59
Bonjour ,
Avais tu désinstaller les pilotes de l'ancienne carte graphique ?
Peux tu analyser ton appareil avec whocrashed > ICI < c'est un lien direct pour savoir d'où viennent tes Bsod ?
Bonne continuation .
Avais tu désinstaller les pilotes de l'ancienne carte graphique ?
Peux tu analyser ton appareil avec whocrashed > ICI < c'est un lien direct pour savoir d'où viennent tes Bsod ?
Bonne continuation .
-
routman54 - PC-Infopraticien
- Messages: 16619
- Inscription: 06 Mar 2010 22:03
- Localisation: Là ou se trouve mon PC
Re: Ordi qui s’éteint tout seul
le 30 Nov 2014 14:56
salut routman !
Bon j'avais auparavant désinstallé mes anciens pilotes graphiques avec DriverSweeper et ensuite j'ai dl comme tu m'as dit whycrashed et voici le listing qui me sort:
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASRock, 985GM-GS3 FX
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8572362752 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 30/11/2014 11:31:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113014-9703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800720E8F8, 0x0, 0x0)
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 Sat 29/11/2014 21:49:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112914-9812-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960000B552C)
Bugcheck code: 0x50 (0xFFFFF962A0D0C088, 0x0, 0xFFFFF960000B552C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Thu 27/11/2014 09:55:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112714-9562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073C8038, 0x0, 0x0)
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 Wed 26/11/2014 19:13:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112614-9422-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073B6038, 0x0, 0x0)
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 25/11/2014 17:00:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112514-9874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073A4038, 0x0, 0x0)
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.
--------------------------------------------------------------------------------
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.
C'est ce que tu voulais voir? au passage j'ai une alim 4 broches pour le cpu, tu ne penses pas qu'il faudrait que je passe en sur une nouvelle cm donc? merci =)
Bon j'avais auparavant désinstallé mes anciens pilotes graphiques avec DriverSweeper et ensuite j'ai dl comme tu m'as dit whycrashed et voici le listing qui me sort:
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASRock, 985GM-GS3 FX
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8572362752 total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Sun 30/11/2014 11:31:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\113014-9703-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800720E8F8, 0x0, 0x0)
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 Sat 29/11/2014 21:49:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112914-9812-01.dmp
This was probably caused by the following module: win32k.sys (0xFFFFF960000B552C)
Bugcheck code: 0x50 (0xFFFFF962A0D0C088, 0x0, 0xFFFFF960000B552C, 0x5)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 Thu 27/11/2014 09:55:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112714-9562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073C8038, 0x0, 0x0)
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 Wed 26/11/2014 19:13:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112614-9422-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073B6038, 0x0, 0x0)
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 25/11/2014 17:00:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\112514-9874-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A587C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80073A4038, 0x0, 0x0)
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.
--------------------------------------------------------------------------------
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.
C'est ce que tu voulais voir? au passage j'ai une alim 4 broches pour le cpu, tu ne penses pas qu'il faudrait que je passe en sur une nouvelle cm donc? merci =)
- jf3252
- Apprenti(e) Expert(e)
- Messages: 105
- Inscription: 20 Nov 2012 17:45
- Localisation: Tarn
Re: Ordi qui s’éteint tout seul
le 30 Nov 2014 16:24
Bonjour ,
Tes rapports parlent plus de mise à jour des pilotes , essaies avec TLD > ICI < .
On voit que ta CM est dotée de port Pcie 2.0 alors que ta carte graphique demande des Pcie 3.0 mais je ne pense pas que cela vienne de ça , on peut être ralenti mais pas de bsod .
Bonne continuation .
Tes rapports parlent plus de mise à jour des pilotes , essaies avec TLD > ICI < .
On voit que ta CM est dotée de port Pcie 2.0 alors que ta carte graphique demande des Pcie 3.0 mais je ne pense pas que cela vienne de ça , on peut être ralenti mais pas de bsod .
Bonne continuation .
-
routman54 - PC-Infopraticien
- Messages: 16619
- Inscription: 06 Mar 2010 22:03
- Localisation: Là ou se trouve mon PC
Re: Ordi qui s’éteint tout seul
le 01 Déc 2014 19:33
Bonsoir Routman
Bon j'ai fait comme tu m'as dit j'ai tout mis a jour, on verra bien.
Ensuite, penses-tu que ça puisse venir de l'alimentation du cpu en 4 broches? elle ne nécessiterait pas une 8 broches? merci
Bon a nouveau même problème au bout d'un moment ca crash ecran bleu ou ordi qui redémarre tout seul...
On Mon 01/12/2014 19:48:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120114-36285-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC455B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600014455B, 0xFFFFF8800630B070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 01/12/2014 19:48:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x86B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600014455B, 0xFFFFF8800630B070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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.
Sachant que tout est a jour =)
Bon j'ai fait comme tu m'as dit j'ai tout mis a jour, on verra bien.
Ensuite, penses-tu que ça puisse venir de l'alimentation du cpu en 4 broches? elle ne nécessiterait pas une 8 broches? merci
Bon a nouveau même problème au bout d'un moment ca crash ecran bleu ou ordi qui redémarre tout seul...
On Mon 01/12/2014 19:48:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120114-36285-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xC455B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600014455B, 0xFFFFF8800630B070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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 01/12/2014 19:48:00 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!memset+0x86B)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600014455B, 0xFFFFF8800630B070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Système d’exploitation Microsoft® Windows®
company: Microsoft Corporation
description: Pilote Win32 multi-utilisateurs
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 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.
Sachant que tout est a jour =)
- jf3252
- Apprenti(e) Expert(e)
- Messages: 105
- Inscription: 20 Nov 2012 17:45
- Localisation: Tarn
Re: Ordi qui s’éteint tout seul
le 02 Déc 2014 17:57
Bonsoir ,
As tu le CD de l'installation de Seven , si oui tu le mets dans ton appareil il va charger le système puis te demander si tu veux faire une nouvelle installation ou Réparer celle existante , tu choisis Réparer .
Apparemment ce n'est plus du Hardware mais du système que vient le problème .
Bonne continuation .
As tu le CD de l'installation de Seven , si oui tu le mets dans ton appareil il va charger le système puis te demander si tu veux faire une nouvelle installation ou Réparer celle existante , tu choisis Réparer .
Apparemment ce n'est plus du Hardware mais du système que vient le problème .
Bonne continuation .
-
routman54 - PC-Infopraticien
- Messages: 16619
- Inscription: 06 Mar 2010 22:03
- Localisation: Là ou se trouve mon PC
Re: Ordi qui s’éteint tout seul
le 03 Déc 2014 11:09
Salut routman !
Oui j'ai seven sur usb, j'ai changer la CM avec le 8 coeurs ma micro atx de chez Asrock ne passait pas.
Et maintenant plus de redémarrage intempestif.
Merci bien
Oui j'ai seven sur usb, j'ai changer la CM avec le 8 coeurs ma micro atx de chez Asrock ne passait pas.
Et maintenant plus de redémarrage intempestif.
Merci bien
- jf3252
- Apprenti(e) Expert(e)
- Messages: 105
- Inscription: 20 Nov 2012 17:45
- Localisation: Tarn
7 messages
• Page 1 sur 1
Sujets similaires
[résolu] (tout seul) traducteur google intrusifBonjour Dès que je navigue sur un site étranger, j'ai la traduction de google, je n'en veux pas, il y a moyen de s'en débarrasser ? Merciici :J'éditeOui déjà Je n'avais pas assez cherché, normalement, j'ai réussi :Comment désactiver le traducteur ?Activer ou désactiver la traductionSur votre ordin ...
Réponses: 5
PC s'éteint lorsqu'on le débrancheBonjour,j'ai un PC portable ASUS notebook X411U qui s'éteint si on le débranche du secteur. J'ai cherché la panne donc je l'ai démonté et recherché sur le circuit une trace d'une panne et j'ai vu ça (voir photo) ça a l'air d'être sur la ligne des composants qu'on appelle des fusibles, juste au dessu ...
Réponses: 1
Configuration ordi travailBonjour à tous,En 2009 j'ai monté ça : - Boîtier : Antec NSK4480B-II avec alimentation Earthwatt 380W - Carte mère : ASUS P5QL-E (C2D + DDR2 + PCI-E) - Processeur : INTEL Core2 Duo E8400 (3.0 DualCore LGA775) - Ventirad CPU : Cooler Master Hyper TX3 S775/1156 - Mémoire : 2x2 Go DDR2-800 PC6400 Corsa ...
Réponses: 19
[Réglé] (tout seul) WinX DVD Authorbonjour hier j'ai utiliser le log WinX DVD Author( free) pour faire un dvd ,aujourd?hui quand il fait l'operation fabrication du fichier pour après graver.il s'arrete et s'efface du bureau, j'ai essayer plusieurs fois c'est pareil..hier j'ai réussi un faire un dvd mais le son était faible...mercije ...
Réponses: 0
Redmi 8 vers ordi portableBonjour,J'ai un téléphone REDMI 8, et je souhaite utiliser l'internet de celui-ci sur mon ordi portable (win10), et profiter d'un écran plus confortable.Mais ça ne fonctionne pas.Est-il possible d'utiliser un transmetteur "CHROMECAST" pour solutionner le problème ?Merci pour vos lumières. ...
Réponses: 1
[Réglé] Demande conseil ordi à la carte avec tour existanteMon projet :acheter un ordi de bureau d'occasion et changer si besoin des composants pour l'améliorer.Carte (Gigabyte ?) ATOMX2 18 200 500 GOProcess AMD A4-4000 APU avec Radeon HD graphicRAM 4 Go installéAnnée 2011Des questions générales :L'écran a une connexion VGA, si je mets une Carte Mère récent ...
Réponses: 12
HTC cosmos elite casque seul : fonctionnel ?Bonjour,voilà, j'ai profité d'une énorme promo à la FNAC pour acquérir le casque VR HTC Cosmos Elite, en version "casque seul".Mon objectif est de l'utiliser sur des simulateurs de vol, donc avec mon joystick et éventuellement clavier-souris. Pas besoin de manette (contrôleur) VR me dis-je ...
Réponses: 0
Qui est en ligne
Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 11 invités
|
.: Nous contacter :: Flux RSS :: Données personnelles :. |