Crash de windows

Hello

Fais d'abord les mises à jour ensuite on verra

Re,
J'ai fais les mises a jour mais je crash toujours (mais moins)
Je pense avoir trouvé le problème, un détail qui ma échappé: lors du montage le dernier câble a brancher (celui de processeur), sur la carte mère (msi 760GM P34) la prise comportait 4pin, et sur l'alimentation (coolermaster 500W serie B).
Je ne savais pas comment le brancher, et comme sur internet j'ai vu que mon alim gérait très bien les sous-tentions et les surtension, je l'ai branché quand même, avec 4pin de l'alim dans le vide a gauche.
Bon, sa je pense que c'est une connerie car avant d'acheter je n'avait pas vu que l'alimentation était dédié a une carte mère ATX et non micro ATX...
Apres comme l'ordinateur c'est allumé j'ai installé mon windows et mes driver tout en crashant. Je pensais que la cause était les pilotes de ma carte graphique gtx 660 car les pilotes ne voulaient pas s'installer (Je ne pouvais rien a faire).
J'ai vu sur un forum anglais que mon crash pouvait être lié a une surtension ou a une sous-tension, ce qui ma mis sur la piste.

Dois-je remplacer mon alimentation ?
Merci.

Hello

Je ne suis pas trop spécialiste au niveau hardware

Mais on peut vérifier les écrans bleu avec Whocrashed

=> https://www.commentcamarche.net/telecharger/utilitaires/23795-whocrashed-free-home-edition/

Voili Voilu :
System Information (local)
--------------------------------------------------------------------------------

computer name: X-GAMING-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: AuthenticAMD AMD FX(tm)-8350 Eight-Core Processor AMD586, level: 21
8 logical processors, active mask: 255
RAM: 8589074432 total
VM: 2147352576, free: 1974763520

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 01/08/2013 01:03:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-55458-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CFD6F2, 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 Thu 01/08/2013 01:03:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CFD6F2, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 Thu 01/08/2013 00:42:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-96829-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007D90028, 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 Wed 31/07/2013 23:15:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-46691-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002CB86F2, 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 Wed 31/07/2013 22:49:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-48672-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x4A359C)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007C684F8, 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 31/07/2013 22:30:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-38079-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002CB06F2, 0xFFFFF880055E3D10, 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 Wed 31/07/2013 19:43:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-25490-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007DAF028, 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 Wed 31/07/2013 18:47:19 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-35490-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002D00C22, 0xFFFFF88007A577F0, 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 Wed 31/07/2013 18:28:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073113-61277-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12903)
Bugcheck code: 0x124 (0x0, 0xFFFFFA8007FB6028, 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.

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

9 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

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 actually 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.

Hello

Bon ça peut très bien venir de ton alimentation ou alors des barrettes de mémoire

Je vais quand même me renseigner

En attendant regarde ici => https://answers.microsoft.com/en-us/windows/forum/windows_7-system/windows-7-crashed-error-code-0x124/56bad8ea-0c97-43a5-aa9c-47c65343f057

Salut

"Je ne savais pas comment le brancher, et comme sur internet j'ai vu que mon alim gérait très bien les sous-tentions et les surtension, je l'ai branché quand même, avec 4pin de l'alim dans le vide a gauche." <= Gné??

Alors, le connecteur CPU sur la carte-mère à combien de broches 4 ou 8? Et celui de l'alim?

Si c'est un 8 broches il faut brancher les 8 et pas la moitié ^^

"l'alimentation était dédié a une carte mère ATX et non micro ATX..." <= ATX/µATX c'est la même chose mais µATX la carte-mère est plus petite, les branchements d'alimentation sont les mêmes.

Avant de poser une question: 1° Le cerveau ne s'use pas si on s'en sert, n'hésite pas à l'utiliser!
2° Google est ton ami, le moteur de recherche de CCM aussi, fais une recherche!

Memtest86+ ne détecte aucune erreur.
Je passe au test Prime95.

Bonjour,

J'update mon poste suite a tout les tests:

- Je crash toujours, mais depuis que j'ai formater mon pc et que j'ai réussi a installer les pilotes de ma carte graphique, je n'ai plus qu'un seul crash au BCcode 124, j'ai lu très vite que ça avait un rapport avec le CPU, mais mon CPU ne chauffe pas et est neuf.

-Memtest86 + ne détecte aucune erreur et prime95 fait crasher mon ordi comme les jeux que j'exécute.

- Toutes les pistes n'ont aboutit a rien (sauf pour les pilotes graphique mais sa a supprimé un crash sur les deux) et je n'en n'ai plus, si vous avez un conseil, je suis preneur.

up

UP

J'ai du nouveau: quand je retire ma carte graphique je ne crash pas, quand je la remet il crash au bout de 2 partie (de world of tanks mais bref).
Il me parait évident que la carte graphique y est pour quelque chose non?
Vous en pensez quoi ?

(Mes pilotes Nvidia sont a jour.)

le probleme peut venir de la carte mere elle meme et je ne precise rien de plus car dans un ordianteur portable si un composant est mort, toute la carte va a la poubelle, sauf si la défaillance vient de la RAM

Bonjour

Pensez vous que je dois l'emmener chez un réparateur ?
Pourra-t-il corriger le problème ?
Cela prendra du temps ?
Combien prendra t-il ? (bien que je sais que ce n'ai pas facile a dire.

Merci

Re bonjour,
Je pense avoir trouver une piste, voila ce qu'indique l'observateur d'événement après avoir crashé:

Nom du journal :System
Source : Microsoft-Windows-WHEA-Logger
Date : 06/08/2013 17:52:30
ID de l'événement :20
Catégorie de la tâche :Aucun
Niveau : Erreur
Mots clés :
Utilisateur : LOCAL SERVICE
Ordinateur : X-Gaming-PC
Description :
Une erreur matérielle irrécupérable s'est produite.

Composant : AMD Northbridge
Source de l'erreur : Exception de vérification d'ordinateur
Type d'erreur : Erreur d'expiration de la surveillance HyperTransport
ID du processeur : 0

Pour plus d'informations, consultez les détails de cette entrée.
XML de l'événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WHEA-Logger" Guid="{C26C4F3C-3F66-4E99-8F8A-39405CFED220}" />
<EventID>20</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2013-08-07T00:52:30.936936800Z" />
<EventRecordID>13949</EventRecordID>
<Correlation ActivityID="{6D7D7880-29DB-473B-A302-7D55E223E659}" />
<Execution ProcessID="1836" ThreadID="1972" />
<Channel>System</Channel>
<Computer>X-Gaming-PC</Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">3</Data>
<Data Name="ApicId">0</Data>
<Data Name="MCABank">4</Data>
<Data Name="MciStat">0xfe00000000070f0f</Data>
<Data Name="MciAddr">0xfebf8024</Data>
<Data Name="MciMisc">0xc00a0fff01000000</Data>
<Data Name="ErrorType">7</Data>
<Data Name="Length">928</Data>
<Data Name="RawData">435045521002FFFFFFFF03000100000002000000A00300001733000007080D140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131FE6FF5E89C91C54CBA8865ABE14913BB27C8C5360893CE0102000000000000000000000000000000000000000000000058010000C00000000102000001000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000001000000000000000000000000000000000000000000000018020000800000000102000000000000B0A03EDC44A19747B95B53FA242B6E1D0000000000000000000000000000000001000000000000000000000000000000000000000000000098020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E8000000000000000000000000000000000100000000000000000000000000000000000000000000007F010000000000000002040000030000200F60000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007000000000000000000000000000000200F6000000808000B32983EFFFB8B170000000000000000000000000000000000000000000000000000000000000000B3F8F31CB1C5A249AA595EEF92FFA63C03000000000000009E07C0E6070000002480BFFE0000000000000000000000000000000000000000000000000000000001000000020000009D270A3D0893CE010000000000000000000000000000000000000000040000000F0F0700000000FE2480BFFE0000000000000001FF0F0AC00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

Se qui me parle le plus je l'ai mis en gras.

Merci.

Bonjour,
J'ai vu sur le site de Nvidia que la consomation minimal de ma carte graphique était 450W, or je possède une alimentation de 500W, est-ce la cause du crash ? Dois-je remplacer mon alimentation par une alimentation plus puissante ?
Ma config est en haut et la fiche technique de ma carte graphique est ici: https://www.nvidia.com/fr-fr/geforce/#pdpContent=2

Merci

Problème résolu.

--> Alimentation 500W insuffisante, j'ai pris une 600W et je n'ai plus aucun souci.

est-ce un ordinateur portable?