cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Mo7ammad_Helal
Punch Card
Posts: 32
Location: IL
Views: 1,542
Message 1 of 17

The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Hello
I have been playing Counter-Strike 1.6
And the keyboard stopped working fully
But the mouse kept working
This problem was repeated more than once

I turn off the power button and then I turn it to work again
Please help me

Guru
Posts: 3,401
Location: MX
Views: 1,498
Message 2 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Can you please try using an external keyboard and see if the problem replicates itself.

Thank you.

---------------------------------
Current System - Lenovo Y720
Y720 REVIEW - Youtube Link (Opens in New Tab)
If your experience was good today, please feel free to give KUDOS. It Ain't Over, 'til it's over.
t0mc4t
Fanfold Paper
Posts: 7
Location: PL
Views: 1,444
Message 3 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Hi I have exactly the same problem. Yesterday it happened two times while playing hereos of the storm - i must turn off the laptop - press turn off button. Please help us.

Mo7ammad_Helal
Punch Card
Posts: 32
Location: IL
Views: 1,437
Message 4 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

I have used an external keyboard but the problem still
t0mc4t
Fanfold Paper
Posts: 7
Location: PL
Views: 1,392
Message 5 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Hi Rockykoston,

Have You any others ideas with our problem?

Guru
Posts: 3,401
Location: MX
Views: 1,385
Message 6 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

So, if I understand correctly the problem still happens while using an external keyboard (and the external keyboard gets disabled). Well this is odd because this points to something wrong with the game or software.

 

I would suggest performing a system reset and going back to factory settings. I am thinking that this is some program on the laptop that is doing this, I dont think that there is anything wrong with the keyboards (given that both keyboards get disabled).

 

Does this happen in other games too?

While browsing, typing?

---------------------------------
Current System - Lenovo Y720
Y720 REVIEW - Youtube Link (Opens in New Tab)
If your experience was good today, please feel free to give KUDOS. It Ain't Over, 'til it's over.
t0mc4t
Fanfold Paper
Posts: 7
Location: PL
Views: 1,348
Message 7 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

In my case i don't try with external keyboard. This happen only when i play game. Last time i play in windowed mode so i can go back to Windows. The keyboard was stil turned off, after while i get BSOD. Below content from Minidump file:

Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\081716-4468-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols

Executable search path is: 
Windows 8 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.0.amd64fre.rs1_release.160715-1616
Machine Name:
Kernel base = 0xfffff801`47089000 PsLoadedModuleList = 0xfffff801`4738e060
Debug session time: Wed Aug 17 13:48:30.894 2016 (UTC + 2:00)
System Uptime: 0 days 2:31:18.634
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff888bb47e4840, ffffe0018409e8e0, ffff888bb9c23b80}

Probably caused by : pci.sys

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff888bb47e4840, Physical Device Object of the stack
Arg3: ffffe0018409e8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff888bb9c23b80, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57899938

MODULE_NAME: pci

FAULTING_MODULE: fffff80b393b0000 pci

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

DPC_STACK_BASE:  FFFFE001840A6FB0

STACK_TEXT:  
ffffe001`8409e8a8 fffff801`472831ff : 00000000`0000009f 00000000`00000003 ffff888b`b47e4840 ffffe001`8409e8e0 : nt!KeBugCheckEx
ffffe001`8409e8b0 fffff801`47283112 : ffff888b`ba971e88 00000000`00000001 00000000`00000001 ffffe001`84073180 : nt!PopIrpWatchdogBugcheck+0xeb
ffffe001`8409e910 fffff801`470c0260 : ffff888b`ba971ec0 00000000`00225514 00000000`00140001 00000000`00000000 : nt!PopIrpWatchdog+0x22
ffffe001`8409e960 fffff801`471d601a : ffffffff`00000000 ffffe001`84073180 ffffe001`8407fbc0 ffff888b`bbca6080 : nt!KiRetireDpcList+0x440
ffffe001`8409ebe0 00000000`00000000 : ffffe001`8409f000 ffffe001`84098000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.14393.0

FAILURE_BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys

BUCKET_ID:  0x9F_3_ACPI_IMAGE_pci.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_acpi_image_pci.sys

FAILURE_ID_HASH:  {20ddeb92-07eb-ebdc-bd08-44da71ffbd68}

Followup: MachineOwner
---------
t0mc4t
Fanfold Paper
Posts: 7
Location: PL
Views: 1,284
Message 8 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Ok, I think my problem is over. Lenovo service helped me.

I run CMD as an administrator and enter:

dism / online / cleanup-image / restorehealth
ENTER
sfc / scannow
ENTER
chkdsk C: / R
ENTER
and confirm the restart.

I also install new BIOS (17.08 release). Till now the keyboard don't turn off while playing games.
Mo7ammad_Helal
Punch Card
Posts: 32
Location: IL
Views: 1,259
Message 9 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Hello my friend
is your problem solved?
or normally again

t0mc4t
Fanfold Paper
Posts: 7
Location: PL
Views: 1,249
Message 10 of 17

Re: The keyboard stops working (Lenovo IdeaPad Y700 15.6" Gaming)

Hi,

 

The problem still hapend.

 

I reinstall windows 10 and all drivers. And I still have a problem.

 

I get minidump

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\082716-6546-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Temp*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.82.amd64fre.rs1_release.160805-1735
Machine Name:
Kernel base = 0xfffff802`c2079000 PsLoadedModuleList = 0xfffff802`c237e060
Debug session time: Sat Aug 27 22:40:54.542 2016 (UTC + 2:00)
System Uptime: 1 days 13:02:58.373
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
........................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffff8002ddb72060, ffffaf81d5f9c8e0, ffff8002e3affc60}

Implicit thread is now ffff8002`dd2a4040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!DpiFdoHandleDevicePower+1e5 )

Followup:     MachineOwner
---------

Implicit thread is now ffff8002`dd2a4040
2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff8002ddb72060, Physical Device Object of the stack
Arg3: ffffaf81d5f9c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8002e3affc60, The blocked IRP

Debugging Details:
------------------

Implicit thread is now ffff8002`dd2a4040

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.14393.82 (rs1_release.160805-1735)

SYSTEM_MANUFACTURER:  LENOVO

SYSTEM_PRODUCT_NAME:  80NV

SYSTEM_SKU:  LENOVO_MT_80NV_BU_idea_FM_Lenovo ideapad Y700-15ISK

SYSTEM_VERSION:  Lenovo ideapad Y700-15ISK

BIOS_VENDOR:  LENOVO

BIOS_VERSION:  CDCN37WW

BIOS_DATE:  05/25/2016

BASEBOARD_MANUFACTURER:  LENOVO

BASEBOARD_PRODUCT:  Allsparks 5A

BASEBOARD_VERSION:   NO DPK

DUMP_TYPE:  2

BUGCHECK_P1: 3

BUGCHECK_P2: ffff8002ddb72060

BUGCHECK_P3: ffffaf81d5f9c8e0

BUGCHECK_P4: ffff8002e3affc60

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  dd2a4040

CPU_COUNT: 4

CPU_MHZ: 900

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 74'00000000 (cache) 74'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-KNLA23V

ANALYSIS_SESSION_TIME:  08-27-2016 23:06:13.0509

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER:  from fffff802c20b2cdc to fffff802c21c7e76

STACK_TEXT:  
ffffaf81`d5edd4f0 fffff802`c20b2cdc : fffff80d`dcab96c0 fffff802`00000000 ffff8002`dd2ed3f0 fffff80d`dcab96c0 : nt!KiSwapContext+0x76
ffffaf81`d5edd630 fffff802`c20b277f : ffff8002`dd2ed3f0 fffff80d`00000001 00000000`00000000 fffff803`00000008 : nt!KiSwapThread+0x17c
ffffaf81`d5edd6e0 fffff802`c20b4547 : ffff8002`00000000 00000000`00000000 fffff80d`dca9a5f0 00000000`00000000 : nt!KiCommitThreadWait+0x14f
ffffaf81`d5edd780 fffff80d`deb5f7b5 : ffffaf81`d5edd860 00000000`00000000 ffff8002`e3affc00 00000000`00000000 : nt!KeWaitForSingleObject+0x377
ffffaf81`d5edd830 fffff80d`deb5f0fb : ffff8002`e3affc00 ffff8002`e0f96180 ffff8002`e3affc60 00000000`ff030000 : dxgkrnl!DpiFdoHandleDevicePower+0x1e5
ffffaf81`d5edd8c0 fffff80d`e0b59a09 : 00000000`00000001 ffffaf81`d5edda59 00000000`00000001 ffff8002`e0f96030 : dxgkrnl!DpiDispatchPower+0x8b
ffffaf81`d5edd9e0 00000000`00000001 : ffffaf81`d5edda59 00000000`00000001 ffff8002`e0f96030 ffffaf81`d5eddad8 : nvlddmkm+0x159a09
ffffaf81`d5edd9e8 ffffaf81`d5edda59 : 00000000`00000001 ffff8002`e0f96030 ffffaf81`d5eddad8 00000000`00000004 : 0x1
ffffaf81`d5edd9f0 00000000`00000001 : ffff8002`e0f96030 ffffaf81`d5eddad8 00000000`00000004 00000000`00000000 : 0xffffaf81`d5edda59
ffffaf81`d5edd9f8 ffff8002`e0f96030 : ffffaf81`d5eddad8 00000000`00000004 00000000`00000000 00000000`00000001 : 0x1
ffffaf81`d5edda00 ffffaf81`d5eddad8 : 00000000`00000004 00000000`00000000 00000000`00000001 ffff8002`e11dc000 : 0xffff8002`e0f96030
ffffaf81`d5edda08 00000000`00000004 : 00000000`00000000 00000000`00000001 ffff8002`e11dc000 00000000`00000000 : 0xffffaf81`d5eddad8
ffffaf81`d5edda10 00000000`00000000 : 00000000`00000001 ffff8002`e11dc000 00000000`00000000 ffff8002`dd2a4040 : 0x4


STACK_COMMAND:  .thread 0xffff8002dd2a4040 ; kb

THREAD_SHA1_HASH_MOD_FUNC:  2ea4cf1c896de376a694cc11332188cc09a25b0f

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  c7a650ef8f5b45cde02637093055e1a89e46d468

THREAD_SHA1_HASH_MOD:  b9b390840bee87fd6e8db687803b2d74479116dd

FOLLOWUP_IP: 
dxgkrnl!DpiFdoHandleDevicePower+1e5
fffff80d`deb5f7b5 4863f0          movsxd  rsi,eax

FAULT_INSTR_CODE:  85f06348

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  dxgkrnl!DpiFdoHandleDevicePower+1e5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  579168ce

IMAGE_VERSION:  10.0.14393.5

BUCKET_ID_FUNC_OFFSET:  1e5

FAILURE_BUCKET_ID:  0x9F_3_dxgkrnl!DpiFdoHandleDevicePower

BUCKET_ID:  0x9F_3_dxgkrnl!DpiFdoHandleDevicePower

PRIMARY_PROBLEM_CLASS:  0x9F_3_dxgkrnl!DpiFdoHandleDevicePower

TARGET_TIME:  2016-08-27T20:40:54.000Z

OSBUILD:  14393

OSSERVICEPACK:  82

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  272

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2016-08-06 05:25:45

BUILDDATESTAMP_STR:  160805-1735

BUILDLAB_STR:  rs1_release

BUILDOSVER_STR:  10.0.14393.82

ANALYSIS_SESSION_ELAPSED_TIME: 595

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_dxgkrnl!dpifdohandledevicepower

FAILURE_ID_HASH:  {8058ca7c-9d12-86b8-15a2-3340127a0162}

Followup:     MachineOwner

And also in Windows Event log i have 5 the same logs:

- System 

  - Provider 

   [ Name]  ACPI 
 
  - EventID 13 

   [ Qualifiers]  49157 
 
   Level 2 
 
   Task 0 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2016-08-27T20:39:05.508624900Z 
 
   EventRecordID 1472 
 
   Channel System 
 
   Computer DESKTOP-KNLA23V 
 
   Security 
 

- EventData 

    
   0000C00001000000000000000D0005C000000000000000000000000000000000000000000000000011552200150AFFFF75000100150A1E0085001801A509F303150AAF0065001A0035830B00150AFFFF75000000150A1C008500FD00A5096F03150A990065000C0035830600150AFFFF75000000150A1E0085000901A509A303150A9B0065000C0035830500150AFFFF75000000150A1C0085003C01A5090A04150A160165000600130AFFFF000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 


--------------------------------------------------------------------------------

Dane binarne:


W wyrazach

0000: 00C00000 00000001 00000000 C005000D 
0010: 00000000 00000000 00000000 00000000 
0020: 00000000 00000000 00225511 FFFF0A15 
0030: 00010075 001E0A15 01180085 03F309A5 
0040: 00AF0A15 001A0065 000B8335 FFFF0A15 
0050: 00000075 001C0A15 00FD0085 036F09A5 
0060: 00990A15 000C0065 00068335 FFFF0A15 
0070: 00000075 001E0A15 01090085 03A309A5 
0080: 009B0A15 000C0065 00058335 FFFF0A15 
0090: 00000075 001C0A15 013C0085 040A09A5 
00a0: 01160A15 00060065 FFFF0A13 00000000 
00b0: 00000000 00000000 00000000 00000000 
00c0: 00000000 00000000 00000000 00000000 
00d0: 00000000 00000000 00000000 00000000 
00e0: 00000000 00000000   


W bajtach

0000: 00 00 C0 00 01 00 00 00   ..À.....
0008: 00 00 00 00 0D 00 05 C0   .......À
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 11 55 22 00 15 0A FF FF   .U"...ÿÿ
0030: 75 00 01 00 15 0A 1E 00   u.......
0038: 85 00 18 01 A5 09 F3 03   …...¥.ó.
0040: 15 0A AF 00 65 00 1A 00   ..¯.e...
0048: 35 83 0B 00 15 0A FF FF   5ƒ....ÿÿ
0050: 75 00 00 00 15 0A 1C 00   u.......
0058: 85 00 FD 00 A5 09 6F 03   ….ý.¥.o.
0060: 15 0A 99 00 65 00 0C 00   ..™.e...
0068: 35 83 06 00 15 0A FF FF   5ƒ....ÿÿ
0070: 75 00 00 00 15 0A 1E 00   u.......
0078: 85 00 09 01 A5 09 A3 03   …...¥.£.
0080: 15 0A 9B 00 65 00 0C 00   ..›.e...
0088: 35 83 05 00 15 0A FF FF   5ƒ....ÿÿ
0090: 75 00 00 00 15 0A 1C 00   u.......
0098: 85 00 3C 01 A5 09 0A 04   ….<.¥...
00a0: 15 0A 16 01 65 00 06 00   ....e...
00a8: 13 0A FF FF 00 00 00 00   ..ÿÿ....
00b0: 00 00 00 00 00 00 00 00   ........
00b8: 00 00 00 00 00 00 00 00   ........
00c0: 00 00 00 00 00 00 00 00   ........
00c8: 00 00 00 00 00 00 00 00   ........
00d0: 00 00 00 00 00 00 00 00   ........
00d8: 00 00 00 00 00 00 00 00   ........
00e0: 00 00 00 00 00 00 00 00   ........
Top Kudoed Authors