Driver_Power_State_Failure ...
FullTribal
Messages postés
165
Statut
Membre
-
FullTribal Messages postés 165 Statut Membre -
FullTribal Messages postés 165 Statut Membre -
Bonjour,
cela fait un bon moment que mon pc portable plante régulièrement à cause de ce message d'erreur (cf titre) ... Cela avait cessé pendant 2 semaines environs, après mon premier passage sur le forum, mais le problème revient ...
Rien qu'à l'instant j'ai eu droit à 3 plantages avant d'arriver enfin au forum (première fois que ça arrive).
Voici le rapport de "who crashed"
"On Sun 24-01-16 12:24:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-24453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0014FD86880, 0xFFFFF8027B295960, 0xFFFFE0014FDE4010)
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 Sun 17-01-16 20:20:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011716-21578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001921D2880, 0xFFFFD001D5B46960, 0xFFFFE00195DC1CA0)
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."
C'est à chaque fois le même message, sauf les codes qui changent mais c'est toujours dû à "ntoskrnl.exe".
Mes drivers sont à jour via le site "DriversCloud" et mes programmes sont à jour via le programme "FileHippo".
Je scanne régulièrement mon pc avec "AviraAntivir" et "Malwarebytes anti-Malware".
Ma config;
OS: Windows 8.1 64 bits
Bios: N751JX.202
Proco: Intel I7-4720HQ 2.60GhZ
RAM: 16GB
CG: Intel HD Graphics 4600
CG 2: NVIDIA GeForce GTX 950M
Je vous remercie d'avance pour l'aide apportée.
cela fait un bon moment que mon pc portable plante régulièrement à cause de ce message d'erreur (cf titre) ... Cela avait cessé pendant 2 semaines environs, après mon premier passage sur le forum, mais le problème revient ...
Rien qu'à l'instant j'ai eu droit à 3 plantages avant d'arriver enfin au forum (première fois que ça arrive).
Voici le rapport de "who crashed"
"On Sun 24-01-16 12:24:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012416-24453-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE0014FD86880, 0xFFFFF8027B295960, 0xFFFFE0014FDE4010)
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 Sun 17-01-16 20:20:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011716-21578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001921D2880, 0xFFFFD001D5B46960, 0xFFFFE00195DC1CA0)
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."
C'est à chaque fois le même message, sauf les codes qui changent mais c'est toujours dû à "ntoskrnl.exe".
Mes drivers sont à jour via le site "DriversCloud" et mes programmes sont à jour via le programme "FileHippo".
Je scanne régulièrement mon pc avec "AviraAntivir" et "Malwarebytes anti-Malware".
Ma config;
OS: Windows 8.1 64 bits
Bios: N751JX.202
Proco: Intel I7-4720HQ 2.60GhZ
RAM: 16GB
CG: Intel HD Graphics 4600
CG 2: NVIDIA GeForce GTX 950M
Je vous remercie d'avance pour l'aide apportée.
A voir également:
- Driver_Power_State_Failure ...
- Msdn bugcheck driver_power_state_failure - Forum Windows 8 / 8.1
- Blue screen DRIVER_POWER_STATE_FAILURE - Forum BIOS
1 réponse
Mon pc à encore planté hoier alors que je regardais simplement un film en streaming ...
"On Tue 26-01-16 21:49:24 GMT your computer crashed"
crash dump file: C:\Windows\Minidump\012716-24015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001DF351360, 0xFFFFD00122946960, 0xFFFFE001E2280CA0)
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 Tue 26-01-16 21:49:24 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, 0xFFFFE001DF351360, 0xFFFFD00122946960, 0xFFFFE001E2280CA0)
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 26-01-16 21:49:24 GMT your computer crashed"
crash dump file: C:\Windows\Minidump\012716-24015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0)
Bugcheck code: 0x9F (0x3, 0xFFFFE001DF351360, 0xFFFFD00122946960, 0xFFFFE001E2280CA0)
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 Tue 26-01-16 21:49:24 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, 0xFFFFE001DF351360, 0xFFFFD00122946960, 0xFFFFE001E2280CA0)
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.