Altconsult
-
Modifié par Altconsult le 6/12/2016 à 16:25
Altconsult -
10 déc. 2016 à 12:15
Bonjour,
Suite à un écran bleu mon ordi a redémarré. Suite à ce redémarrage j'ai fais une restauration système où après la page du bios j'ai eu un nouvel écran bleu.
Mon système est instable depuis et beaucoup d'applications ne fonctionne plus normalement.
J'ai fais un scan AdwCleaner et vérifie ce qui tourne. Je vous post les rapports car j'ai besoin de votre aide et j'aimerais éviter d'endommager mon pc de manière irréversible.
# AdwCleaner v6.040 - Rapport créé le 06/12/2016 à 15:51:59
# Mis à jour le 02/12/2016 par Malwarebytes
# Base de données : 2016-12-05.1 [Serveur]
# Système d'exploitation : Windows 7 Professional Service Pack 1 (X64)
# Nom d'utilisateur : ALTCONSULT - ALT-HOME-PC
# Exécuté depuis : C:\Users\ALTCONSULT\Desktop\adwcleaner_6.040.exe
# Mode: Nettoyage
# Support : https://www.malwarebytes.com/support
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: ALT-HOME-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., Z170 PRO GAMING
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 34273361920 bytes total
On Tue 06/12/2016 16:55:48 your computer crashed
crash dump file: C:\Windows\Minidump\120616-6910-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA801F213A00, 0xFFFFF80000B9A3D8, 0xFFFFFA8073DE7B80)
Error: DRIVER_POWER_STATE_FAILURE
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 the driver is in an inconsistent or invalid power state.
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.
One crash dump has 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.
Malekal_morte-
Messages postés180304Date d'inscriptionmercredi 17 mai 2006StatutModérateur, Contributeur sécuritéDernière intervention15 décembre 202024 627
>
Altconsult
7 déc. 2016 à 08:30
6 déc. 2016 à 21:19
Voici le rapport.
Merci.
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: ALT-HOME-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK COMPUTER INC., Z170 PRO GAMING
CPU: GenuineIntel Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 34273361920 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are disabled for your computer.
On Tue 06/12/2016 16:55:48 your computer crashed
crash dump file: C:\Windows\Minidump\120616-6910-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x9F (0x3, 0xFFFFFA801F213A00, 0xFFFFF80000B9A3D8, 0xFFFFFA8073DE7B80)
Error: DRIVER_POWER_STATE_FAILURE
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 the driver is in an inconsistent or invalid power state.
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
--------------------------------------------------------------------------------
One crash dump has 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.
7 déc. 2016 à 08:30
Vois ce que cela donne ensuite.
7 déc. 2016 à 11:26
Je vois ce que ça donne et je vous tiens au courant.
Merci.
7 déc. 2016 à 20:43
8 déc. 2016 à 17:29