Suite à un changement de disque dur : écran bleu
Fermé
vivi72098
Messages postés
109
Date d'inscription
samedi 26 février 2011
Statut
Membre
Dernière intervention
4 janvier 2018
-
Modifié le 1 janv. 2018 à 20:21
vivi72098 Messages postés 109 Date d'inscription samedi 26 février 2011 Statut Membre Dernière intervention 4 janvier 2018 - 4 janv. 2018 à 01:42
vivi72098 Messages postés 109 Date d'inscription samedi 26 février 2011 Statut Membre Dernière intervention 4 janvier 2018 - 4 janv. 2018 à 01:42
A voir également:
- Suite à un changement de disque dur : écran bleu
- Cloner disque dur - Guide
- Defragmenter disque dur - Guide
- Chkdsk disque dur externe - Guide
- Remplacer disque dur par ssd - Guide
- Changer lettre disque dur - Guide
4 réponses
Judge_DT
Messages postés
29395
Date d'inscription
vendredi 5 février 2010
Statut
Modérateur
Dernière intervention
23 octobre 2021
9 657
1 janv. 2018 à 20:12
1 janv. 2018 à 20:12
Salut,
Changé de disque dur, ok.
Mais après ? Qu'as-tu fais ?
Parce que changer le disque dur ne fait pas apparaître Windows comme par magie dessus...
Manque des détails dans ton récit.
Changé de disque dur, ok.
Mais après ? Qu'as-tu fais ?
Parce que changer le disque dur ne fait pas apparaître Windows comme par magie dessus...
Manque des détails dans ton récit.
vivi72098
Messages postés
109
Date d'inscription
samedi 26 février 2011
Statut
Membre
Dernière intervention
4 janvier 2018
1
3 janv. 2018 à 00:13
3 janv. 2018 à 00:13
Après avoir fait toutes les mise à jour et plusieurs heures après je n'ai plus d'écran bleu ! Donc le problème est réglé. Merci à vous pour la solution !
vivi72098
Messages postés
109
Date d'inscription
samedi 26 février 2011
Statut
Membre
Dernière intervention
4 janvier 2018
1
3 janv. 2018 à 07:37
3 janv. 2018 à 07:37
Fausse alerte, il l'a refait avec un nouveau code erreur !
Judge_DT
Messages postés
29395
Date d'inscription
vendredi 5 février 2010
Statut
Modérateur
Dernière intervention
23 octobre 2021
9 657
Modifié le 3 janv. 2018 à 09:06
Modifié le 3 janv. 2018 à 09:06
J'attends toujours les rapports WhoCrashed, personnellement...
vivi72098
Messages postés
109
Date d'inscription
samedi 26 février 2011
Statut
Membre
Dernière intervention
4 janvier 2018
1
4 janv. 2018 à 01:42
4 janv. 2018 à 01:42
J'ai tenté de réinstaller windows mais j'ai toujours des erreurs. J'ai aussi une mise à jour de windows qui ne veut pas se faire avec le code : 0x80091007. Et Driverscloud n'arrive pas à installer : Haswell-ULT Integrated Graphics Controller RTL8411B PCI Express Card Reader (pour ce driver je ne trouve que pour windows 8.1 32x alors que mon pc est sous windows 10 64x)
Et enfin voilà le rapport whocrashed
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 04/01/2018 01:04:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010418-28968-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x50 (0xFFFFBB0CB75F7028, 0x2, 0xFFFFF809DF901892, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys PAGE_FAULT_IN_NONPAGED_AREA
On Thu 04/01/2018 01:04:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x50 (0xFFFFBB0CB75F7028, 0x2, 0xFFFFF809DF901892, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 03/01/2018 15:27:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-40890-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x7F (0x8, 0xFFFF9B01CD708A30, 0xFFFFEB8F29807040, 0xFFFFF8004CB7F26C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys UNEXPECTED_KERNEL_MODE_TRAP
On Wed 03/01/2018 14:26:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-18093-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80081908B0A, 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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nt_wrong_symbols.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.
Et enfin voilà le rapport whocrashed
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Thu 04/01/2018 01:04:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010418-28968-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x50 (0xFFFFBB0CB75F7028, 0x2, 0xFFFFF809DF901892, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys PAGE_FAULT_IN_NONPAGED_AREA
On Thu 04/01/2018 01:04:27 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x50 (0xFFFFBB0CB75F7028, 0x2, 0xFFFFF809DF901892, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys PAGE_FAULT_IN_NONPAGED_AREA
On Wed 03/01/2018 15:27:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-40890-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x7F (0x8, 0xFFFF9B01CD708A30, 0xFFFFEB8F29807040, 0xFFFFF8004CB7F26C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.Double Fault, indicates that an exception occurs during a call to the handler for a prior exception. Most often this is caused by a software problem (kernel stack overflow) but this can also be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys UNEXPECTED_KERNEL_MODE_TRAP
On Wed 03/01/2018 14:26:42 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\010318-18093-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80081908B0A, 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 might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
nt_wrong_symbols.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
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.
1 janv. 2018 à 20:14
1 janv. 2018 à 20:20
-> As-tu vérifié si tous tes pilotes sont bien installés et à jour ?
--> Si c'est pas le cas ou si tu as un doute, utilises DriversCloud, effectues une détection et voit ensuite dans l'onglet "Mes pilotes" si il t'en propose.
-> Qu'est-ce que l'ordinateur a eu pour que tu doives changer de disque dur ?
--> Certains de tes BSOD sont issus de problèmes matériels, si l'ordinateur a subit un choc/une chute/un coup violent, il se peut que d'autres composants en plus du disque que tu as déjà du changé soient endommagés et donc, qu'ils provoquent le problème
1 janv. 2018 à 20:23
1 janv. 2018 à 20:26
Certains "problèmes" sont invisibles, l'électronique étant parfois relativement sensible, sans forcément montrer de trace visible à l'oeil en dehors des symptômes lors de l'utilisation (comme ici, avec des BSOD), si le coup était violent, d'autres composants internes ont pu être endommagés... et donc, ça provoque des BSOD, car il y a défectuosité matérielle. Les codes erreurs vont dans ce sens...
1 janv. 2018 à 20:29
Manque peut-être les drivers de la carte mère.