Я купил Lenovo 700-15ISK. Несколько раз я получал BSOD. Я проверил RAM Memtest и все ок. Я установил драйверы от Lenovo (предназначенные для моей модели), за исключением интерфейса Intel Management Engine, Intel Serial I/O, потому что у меня были более новые.
Ниже содержания ДМП с последней аварии.
Кто-нибудь знает, как решить эту проблему?
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\elcol\Desktop\010217-12906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.576.amd64fre.rs1_release_inmarket.161208-2252
Machine Name:
Kernel base = 0xfffff801`77609000 PsLoadedModuleList = 0xfffff801`7790e060
Debug session time: Mon Jan 2 20:39:13.407 2017 (UTC + 1:00)
System Uptime: 0 days 0:08:43.176
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 C4, {f5, 0, ffffa3801ccc4c60, 0}
Probably caused by : win32kbase.sys ( win32kbase!rimOnPnpArrived+254 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
A device driver attempting to corrupt the system has been caught. This is
because the driver was specified in the registry as being suspect (by the
administrator) and the kernel has enabled substantial checking of this driver.
If the driver attempts to corrupt the system, bugchecks 0xC4, 0xC1 and 0xA will
be among the most commonly seen crashes.
Arguments:
Arg1: 00000000000000f5, ObReferenceObjectByHandle is being called with a NULL handle.
Arg2: 0000000000000000, Handle value specified by the caller.
Arg3: ffffa3801ccc4c60, Object type specified by the caller.
Arg4: 0000000000000000
Debugging Details:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.576 (rs1_release_inmarket.161208-2252)
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80RU
SYSTEM_SKU: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
SYSTEM_VERSION: Lenovo ideapad 700-15ISK
BIOS_VENDOR: LENOVO
BIOS_VERSION: E5CN56WW
BIOS_DATE: 09/29/2016
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: Lenovo ideapad 700-15ISK
BASEBOARD_VERSION: NO DPK
DUMP_TYPE: 2
BUGCHECK_P1: f5
BUGCHECK_P2: 0
BUGCHECK_P3: ffffa3801ccc4c60
BUGCHECK_P4: 0
BUGCHECK_STR: 0xc4_f5
CPU_COUNT: 8
CPU_MHZ: a20
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: VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-HKKCHJ7
ANALYSIS_SESSION_TIME: 01-02-2017 21:02:06.0384
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff80177d15360 to fffff801777536f0
STACK_TEXT:
ffffc780`472dc6c8 fffff801`77d15360 : 00000000`000000c4 00000000`000000f5 00000000`00000000 ffffa380`1ccc4c60 : nt!KeBugCheckEx
ffffc780`472dc6d0 fffff801`77d25da9 : 00000000`00000000 ffffc780`472dc7d9 ffffa380`1ccc4c60 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x48
ffffc780`472dc710 fffffb20`3edbabc4 : 00000000`00000000 ffffc780`472dc7d9 ffffa380`23750570 00000000`00000000 : nt!VerifierObReferenceObjectByHandle+0xb9
ffffc780`472dc750 fffffb20`3ee17a34 : 00000000`00000000 ffffc780`472dc9a9 ffffc780`472dc998 ffffa380`232f41f0 : win32kbase!rimOnPnpArrived+0x254
ffffc780`472dc840 fffffb20`3ea21052 : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : win32kbase!RIMAddNonPnpDeviceOfTypeUsingSuppliedFileHandle+0x124
ffffc780`472dc8f0 fffffb20`3ed9cb7c : 00000000`00000001 00000000`00269fb3 ffffa380`00000001 00000000`00000002 : win32kfull!xxxDesktopThread+0x6c2
ffffc780`472dca10 fffffb20`3ea9372f : 00000000`00000001 fffffb20`3eeb09a0 00000000`00000004 00000000`00000000 : win32kbase!xxxCreateSystemThreads+0x6c
ffffc780`472dca50 fffff801`7775e393 : ffffa380`23f11080 00000000`00000004 00000267`99d0a5f8 00000267`99d04f20 : win32kfull!NtUserCallNoParam+0x2f
ffffc780`472dca80 00007ff8`a1f71144 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000fd`61b3f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`a1f71144
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: a3fb7771e6a1795db836fabaa3d2e2570ff88095
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 80c49bbda5d71235d87911337d4f82fb3aa2110c
THREAD_SHA1_HASH_MOD: 0745d0c298af4320efd071415d32a539ba294c1f
FOLLOWUP_IP:
win32kbase!rimOnPnpArrived+254
fffffb20`3edbabc4 448bf0 mov r14d,eax
FAULT_INSTR_CODE: 48f08b44
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32kbase!rimOnPnpArrived+254
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32kbase
IMAGE_NAME: win32kbase.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a777e
IMAGE_VERSION: 10.0.14393.576
BUCKET_ID_FUNC_OFFSET: 254
FAILURE_BUCKET_ID: 0xc4_f5_VRF_win32kbase!rimOnPnpArrived
BUCKET_ID: 0xc4_f5_VRF_win32kbase!rimOnPnpArrived
PRIMARY_PROBLEM_CLASS: 0xc4_f5_VRF_win32kbase!rimOnPnpArrived
TARGET_TIME: 2017-01-02T19:39:13.000Z
OSBUILD: 14393
OSSERVICEPACK: 576
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-12-09 10:23:02
BUILDDATESTAMP_STR: 161208-2252
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.576
ANALYSIS_SESSION_ELAPSED_TIME: 4bf
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xc4_f5_vrf_win32kbase!rimonpnparrived
FAILURE_ID_HASH: {ee1f2564-23a0-fe46-4311-33b049cbda1f}
Followup: MachineOwner
---------