Zoals de titel al zegt, drama met mijn laptop
Elke keer dat ik de laptop aan zet loopt hij minimaal 2x vast en na 5 minuten wachten krijg ik het BSOD.
Heb veel op internet gelezen dat het veelal een driver probleem is.
Ik heb daarom de gratis versie van " driver easy" op de laptop geinstalleerd en deze gaf aan dat er 17 driver updates waren.
Ik heb ze allemaal geinstalleerd behalve de watchdog timer driver kan ik nergens vinden in apparaatbeheer
Na de driverupdates lijkt het problem alleen maar erger te zijn geworden. Hij loopt nu regelmatig al vast nog voordat windows is opgestart :evil:
Hij komt dan met de melding Driver powerstate failure
Wie kan me verder helpen? :thumb:
Alvast bedankt!
Hier nog wat gegevens van mijn laptop vanuit speccy:
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 3630QM @ 2.40GHz 54 °C
Ivy Bridge 22nm Technology
RAM
8,00GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
ASUSTeK COMPUTER INC. N56VB (SOCKET 0) 57 °C
Graphics
Generic PnP Monitor (1920x1080@60Hz)
Intel HD Graphics 4000 (ASUStek Computer Inc)
2047MB NVIDIA GeForce GT 740M (ASUStek Computer Inc) 44 °C
ForceWare version: 385.69
SLI Disabled
Storage
232GB Samsung SSD 840 EVO 250GB (SSD) 36 °C
Optical Drives
Slimtype DVD A
Audio
Realtek High Definition Audio
En de gegevens van Whocrashed:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 13-10-2017 20:22:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF802E7662348, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Fri 13-10-2017 20:09:24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-16656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFA48FAB5C7060, 0xFFFFB801A65F88F0, 0xFFFFA48FAD46E010)
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 Fri 13-10-2017 18:55:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-9468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8004205F348, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Fri 13-10-2017 18:42:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFB1001A435060, 0xFFFF89010227F8F0, 0xFFFFB1001B236C60)
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 Fri 13-10-2017 18:35:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-6906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFDD843C684060, 0xFFFFA901F75C68F0, 0xFFFFDD843D8F1BD0)
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
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.69 , NVIDIA Corporation)
athw10x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
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.
Elke keer dat ik de laptop aan zet loopt hij minimaal 2x vast en na 5 minuten wachten krijg ik het BSOD.
Heb veel op internet gelezen dat het veelal een driver probleem is.
Ik heb daarom de gratis versie van " driver easy" op de laptop geinstalleerd en deze gaf aan dat er 17 driver updates waren.
Ik heb ze allemaal geinstalleerd behalve de watchdog timer driver kan ik nergens vinden in apparaatbeheer
Na de driverupdates lijkt het problem alleen maar erger te zijn geworden. Hij loopt nu regelmatig al vast nog voordat windows is opgestart :evil:
Hij komt dan met de melding Driver powerstate failure
Wie kan me verder helpen? :thumb:
Alvast bedankt!
Hier nog wat gegevens van mijn laptop vanuit speccy:
Operating System
Windows 10 Home 64-bit
CPU
Intel Core i7 3630QM @ 2.40GHz 54 °C
Ivy Bridge 22nm Technology
RAM
8,00GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard
ASUSTeK COMPUTER INC. N56VB (SOCKET 0) 57 °C
Graphics
Generic PnP Monitor (1920x1080@60Hz)
Intel HD Graphics 4000 (ASUStek Computer Inc)
2047MB NVIDIA GeForce GT 740M (ASUStek Computer Inc) 44 °C
ForceWare version: 385.69
SLI Disabled
Storage
232GB Samsung SSD 840 EVO 250GB (SSD) 36 °C
Optical Drives
Slimtype DVD A
Audio
Realtek High Definition Audio
En de gegevens van Whocrashed:
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Fri 13-10-2017 20:22:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-9250-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF802E7662348, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Fri 13-10-2017 20:09:24 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-16656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFA48FAB5C7060, 0xFFFFB801A65F88F0, 0xFFFFA48FAD46E010)
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 Fri 13-10-2017 18:55:19 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-9468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x133 (0x1, 0x1E00, 0xFFFFF8004205F348, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (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 Fri 13-10-2017 18:42:50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-6843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFB1001A435060, 0xFFFF89010227F8F0, 0xFFFFB1001B236C60)
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 Fri 13-10-2017 18:35:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\101317-6906-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x9F (0x3, 0xFFFFDD843C684060, 0xFFFFA901F75C68F0, 0xFFFFDD843D8F1BD0)
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
--------------------------------------------------------------------------------
51 crash dumps have been found and analyzed. Only 5 are included in this report. 2 third party drivers have 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:
nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 385.69 , NVIDIA Corporation)
athw10x.sys (Qualcomm Atheros Extensible Wireless LAN device driver, Qualcomm Atheros Communications, Inc.)
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.
