BSOD (DRIVER_POWER_STATE_FAILURE) et dérèglement d'horloge

Fermé
ig21 Messages postés 2 Date d'inscription jeudi 10 avril 2014 Statut Membre Dernière intervention 13 novembre 2018 - 13 nov. 2018 à 15:21
bazfile Messages postés 53724 Date d'inscription samedi 29 décembre 2012 Statut Modérateur, Contributeur sécurité Dernière intervention 25 avril 2024 - 13 nov. 2018 à 15:28
Bonjour à tous

J'ai eu il y a quelques semaines, quelques minutes après le démarrage de mon ordi (et alors que je n'avais encore rien lancé) un écran bleu qui a eu une conséquence inattendue après le redémarrage : l'horloge avait avancé d'une heure ! (le fuseau horaire est le bon, ainsi que le fait que ce soit heure d'été ou d'hiver)

J'avais déjà eu un souci similaire il y a quelques années mais je ne me rappelle plus comment je l'avais résolu...

Au bout de quelques jours j'ai manuellement remis l'heure correcte mais dans la journée j'ai à nouveau eu un écran bleu (comme il y a quelques années) et au re-démarrage, à nouveau l'horloge est avancée d'une heure.

Par manque de temps et par curiosité j'ai attendu de voir ce qui allait se passer au changement d'heure : l'horloge a bien reculé d'une heure, donc j'ai toujours 1h d'avance sur mon ordi.

Voici le rapport WhoCrashed :


    System Information (local)
--------------------------------------------------------------------------------

Computer name: ANTIOPE
Windows version: Windows 8.1 , 6.3, build: 9600
Windows dir: C:\Windows
Hardware: Inspiron 5748, Dell Inc., 0JP0G1
CPU: GenuineIntel Intel(R) Core(TM) i5-4210U CPU @ 1.70GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8489086976 bytes total




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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 26/09/2018 06:03:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092618-20468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1402A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001A5570060, 0xFFFFD001EB0B9CB0, 0xFFFFE001A49A7010)
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.



On Wed 26/09/2018 06:03:55 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: 0x9F (0x3, 0xFFFFE001A5570060, 0xFFFFD001EB0B9CB0, 0xFFFFE001A49A7010)
Error: DRIVER_POWER_STATE_FAILURE
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.



On Tue 11/09/2018 06:10:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091118-21875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1401A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE00026FE8880, 0xFFFFD000421BB960, 0xFFFFE0002A931980)
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
--------------------------------------------------------------------------------

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




J'ai bien compris qu'il y a des problèmes avec ntoskrnl.exe et ntkrnlmp.exe, mais je ne sais pas comment les résoudre...

En vous remerciant d'avance pour votre aide :)


A voir également:

1 réponse

bazfile Messages postés 53724 Date d'inscription samedi 29 décembre 2012 Statut Modérateur, Contributeur sécurité Dernière intervention 25 avril 2024 18 480
Modifié le 13 nov. 2018 à 15:31
Bonjour,
Voir cette page.

0