LenovoY700 BSODs do Windows 10 e teclado desligando

Question

Eu estava procurando ajuda com o LenovoY700 executando o Windows 10. Alguns dias está funcionando bem, mas nos outros dias meu teclado simplesmente para de funcionar (não consigo nem colocar o laptop para dormir), ele está literalmente desligado. A única coisa que posso fazer é pressionar o botão Power por alguns segundos para desligá-lo completamente. Neste sistema de tempo e mouse está funcionando completamente normal e eu posso fazer tudo o que não inclui o uso de teclado para como 5-15 minutos e, em seguida, estou recebendo BSOD. Eu tentei analisar o minidump e atualizei as unidades wifi e os drivers da placa de vídeo integrada da Intel, mas não foi isso: (

Download do arquivo de minidespejo

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


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


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*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.447.amd64fre.rs1_release_inmarket.161102-0100
Machine Name:
Kernel base = 0xfffff800'8028f000 PsLoadedModuleList = 0xfffff800'80594060
Debug session time: Mon Dec 12 01:22:44.612 2016 (UTC + 1:00)
System Uptime: 1 days 10:41:32.400
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...
Loading User Symbols
Loading unloaded module list
................
Cannot read PEB32 from WOW64 TEB32 0000df8f - Win32 error 0n30
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffbe8841188060, ffff800136f9c8e0, ffffbe8841a0a010}

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: ffffbe8841188060, Physical Device Object of the stack
Arg3: ffff800136f9c8e0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffbe8841a0a010, The blocked IRP

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


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  pci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5801a742

MODULE_NAME: pci

FAULTING_MODULE: fffff80379510000 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:  FFFF800136FA4FB0

STACK_TEXT:  
ffff8001'36f9c8a8 fffff800'8048a1cf : 00000000'0000009f 00000000'00000003 ffffbe88'41188060 ffff8001'36f9c8e0 : nt!KeBugCheckEx
ffff8001'36f9c8b0 fffff800'8048a0e2 : ffffbe88'41a0b4c8 00000000'00000002 00000000'00000004 ffffbe88'41a0b540 : nt!PopIrpWatchdogBugcheck+0xeb
ffff8001'36f9c910 fffff800'802f2300 : ffffbe88'00000000 ffffbe88'41a0b500 00000000'00140001 00000000'00000002 : nt!PopIrpWatchdog+0x22
ffff8001'36f9c960 fffff800'803dc59a : 00000000'00000000 ffff8001'36f6d180 ffff8001'36f79bc0 ffffbe88'42df2680 : nt!KiRetireDpcList+0x440
ffff8001'36f9cbe0 00000000'00000000 : ffff8001'36f9d000 ffff8001'36f96000 00000000'00000000 00000000'00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  10.0.14393.351

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

    

Answer 1

Observar o dmp mostra que o dispositivo " VEN_8086&DEV_1901 " ( Intel (R) Xeon (R) E3 - 1200/1500 v5 / 6ª Intel (R) Core (TM) PCIe Controller ) casues o acidente:

2: kd> !podev ffffbe8841188060
Device object is for:
  DriverObject 41a90a70
Current Irp 00000000 RefCount 0 Type 00000022 AttachedDev ffffbe883ce774b0 DevFlags 00001040
Device queue is not busy.
Device Object Extension: ffffbe88411887b0:
PowerFlags: 00000040 =>SystemState=0 DeviceState=4
Dope: 00000000:
2: kd> !devstack ffffbe8841188060
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffbe8841a1cb10  \Driver\pci        ffffbe8841a1cc60  InfoMask field not found for _OBJECT_HEADER at ffffbe8841a1cae0

  ffffbe883ce774b0  \Driver\ACPI       ffffbe883ceeb840  InfoMask field not found for _OBJECT_HEADER at ffffbe883ce77480

> ffffbe8841188060  \Driver\pci        ffffbe88411881b0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffbe8841a34d30 :
  DeviceInst is "PCI\VEN_8086&DEV_1901&SUBSYS_380217AA&REV_07&11583659&0&08"
  ServiceName is "pci"

Então um dispositivo dentro do laptop causou isso. Atualize todos os drivers (nVIDIA GPU, Intel HD, sem fio, LAN, som) e desative as opções de economia de energia das configurações do barramento PCIe na alimentação e veja o que acontece.