Keyboard not responding, wifi can't configure ip, bsod with driver failure

[marijush]

Hi, I am sorry for complicated title, i have several problems and I think that they somehow can be connected, i'll try to explain what's happening. Basically when I work on PC for a longer time, keyboard at some random moment stops working, it doesn't respond when buttons are pressed. Sometimes it follows with blue screen of death which says that there's some kind of driver failure. But I have updated all drivers, so I'm not sure why it's happening.
The other problem is that sometimes after turning on pc or restarting pc, it is connected to wifi, but wifi icon is with exclamation mark and wifi doesn't work, after troubleshooting it said that ip isn't configured.
I will really appreciate any useful advice, thanks.

 

[Colif]

can you download and run who crashed: http://www.resplendence.com/whocrashed
it looks at bsod and will give us a summary which might show us driver name causing error.

copy/paste results here.

is this a custom PC or brand name? If custom, what motherboard? If brand name, what make/model?

 

[marijush]

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 8/30/2016 3:12:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\083016-26171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14C670)
Bugcheck code: 0x9F (0x3, 0xFFFF8205465CF060, 0xFFFFBD818D45C890, 0xFFFF8205465AFB40)
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 8/30/2016 3:12:48 PM 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, 0xFFFF8205465CF060, 0xFFFFBD818D45C890, 0xFFFF8205465AFB40)
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 Mon 8/29/2016 2:04:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082916-29359-01.dmp
This was probably caused by the following module: wdf01000.sys (Wdf01000+0x14E8)
Bugcheck code: 0x9F (0x3, 0xFFFF9B886A586060, 0xFFFFBE015973F890, 0xFFFF9B886E1A9010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\drivers\wdf01000.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Driver Framework Runtime
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 8/27/2016 1:25:14 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082716-38578-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14C670)
Bugcheck code: 0x9F (0x3, 0xFFFF8A051BDA5060, 0xFFFFCB01C545C890, 0xFFFF8A05211212F0)
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 8/21/2016 10:20:02 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082216-24500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14C670)
Bugcheck code: 0x9F (0x3, 0xFFFF8A02A9BDF060, 0xFFFFC9812853F890, 0xFFFF8A02A9BDCB40)
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 8/16/2016 3:07:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\081616-26218-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14C670)
Bugcheck code: 0x9F (0x3, 0xFFFFC900BB872060, 0xFFFFB88023EBA890, 0xFFFFC900B865F9D0)
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 Mon 8/8/2016 8:31:39 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080816-24531-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14C670)
Bugcheck code: 0x9F (0x3, 0xFFFFA58F9DF8A620, 0xFFFFB581AC376890, 0xFFFFA58F9FCC7C10)
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 Mon 8/8/2016 4:15:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\080816-41265-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14C670)
Bugcheck code: 0x9F (0x3, 0xFFFFA28DD45A8840, 0xFFFFC68156A6A890, 0xFFFFA28DD7D9BB40)
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 Mon 7/25/2016 10:34:22 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072616-21062-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x2C71A1)
Bugcheck code: 0x1E (0xFFFFFFFFC0000094, 0xFFFFF80E1D0C71A1, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED



On Sat 7/23/2016 11:30:21 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\072416-22406-01.dmp
This was probably caused by the following module: igdkmd64.sys (igdkmd64+0x2C71A1)
Bugcheck code: 0x3B (0xC0000094, 0xFFFFF806241471A1, 0xFFFFE680383BBBB0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\igdkmd64.sys
product: Intel HD Graphics Drivers for Windows(R)
company: Intel Corporation
description: Intel Graphics Kernel Mode Driver
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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: igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation).
Google query: Intel Corporation SYSTEM_SERVICE_EXCEPTION





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Only 10 are included in this report. 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:

igdkmd64.sys (Intel Graphics Kernel Mode Driver, Intel Corporation)

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.

 

[marijush]

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

Computer name: DESKTOP-8N6G15Q
Windows version: Windows 10 , 10.0, build: 14385
Windows dir: C:\Windows
Hardware: 80NV, LENOVO, Allsparks 5A
CPU: GenuineIntel Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8409448448 bytes total

 

[marijush]

I tried to reinstall Intel HD Graphics Drivers but it didn't help. Someone has an idea what can be wrong?

 

[Colif]

normally there are a few people around who can read crash dumps and help you fix these things up. I can't read them myself or I wouldn't be about to do this. I would suggest you follow the posting instructions here and ask them as they seem to have more helpers that can fix bsod. http://www.tenforums.com/bsod-crashes-debugging/

who crashed is only useful when it tells us more than the windows service the error is being caused in.

 

[marijush]

normally there are a few people around who can read crash dumps and help you fix these things up. I can't read them myself or I wouldn't be about to do this. I would suggest you follow the posting instructions here and ask them as they seem to have more helpers that can fix bsod. http://www.tenforums.com/bsod-crashes-debugging/

who crashed is only useful when it tells us more than the windows service the error is being caused in.

Ok, thanks Colif.