电脑时不时的会蓝屏报错重启

汉尼拔 — Wed, 07 Feb 2018 16:29:54 GMT

我是一名大学生，17年八月份购买了惠普的暗影精灵2pro并被我带去常州上学，现在寒假回家，当我试图运行一些游戏，例如星际争霸2时出现了蓝屏报错，但当我玩一些类似炉石传说的游戏，看直播视频，浏览论坛时并未发生报错现象，运行检查程序时显示并无任何故障，请求帮助！:smileysad:

回复：电脑时不时的会蓝屏报错重启

坏坏的笑 — Thu, 08 Feb 2018 01:04:15 GMT

如果运行其他程序都正常，有可能是星际争霸2和系统兼容性有问题

考虑优化游戏里面的跟性能相关的设置，降低特效和性能试试

回复：电脑时不时的会蓝屏报错重启

汉尼拔 — Thu, 08 Feb 2018 10:35:24 GMT

好的，解决了，不过这是为什么呢？以前我采用的配置现在却会导致蓝屏故障呢？

回复：电脑时不时的会蓝屏报错重启

坏坏的笑 — Thu, 08 Feb 2018 11:07:14 GMT

我的观点，主要原因是windows的更新导致的

回复：电脑时不时的会蓝屏报错重启

汉尼拔 — Thu, 08 Feb 2018 13:53:02 GMT

那么我能否回溯的之前版本的windows呢？如果可以我该怎么做呢？

回复：电脑时不时的会蓝屏报错重启

汉尼拔 — Thu, 08 Feb 2018 13:57:43 GMT

然后虽然解决一进游戏就卡的问题，但是当我多次进行游戏后，电脑仍然出现了蓝屏的现象

回复：电脑时不时的会蓝屏报错重启

汉尼拔 — Thu, 08 Feb 2018 14:01:46 GMT

发帖时本想上传dump的分析结果，但那些都不见了，这是最近一次dump文件的分析结果，能麻烦您帮我看一下吗？

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


Loading Dump File [C:\Windows\Minidump\020818-8640-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 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`8ee02000 PsLoadedModuleList = 0xfffff803`8f168fd0
Debug session time: Thu Feb  8 21:47:12.671 2018 (UTC + 8:00)
System Uptime: 0 days 0:16:01.555
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 EF, {ffffd587af9e0580, 0, 0, 0}

Probably caused by : bfe.dll

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

nt!KeBugCheckEx:
fffff803`8ef77880 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffeb02`479db840=00000000000000ef

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_PROCESS_DIED (ef)
        A critical system process died
Arguments:
Arg1: ffffd587af9e0580, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10.0.16299.214 (WinBuild.160101.0800)

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  OMEN by HP Laptop

SYSTEM_SKU:  1DE96PA#AB2

SYSTEM_VERSION:  Type1ProductConfigId

BIOS_VENDOR:  Insyde

BIOS_VERSION:  F.35

BIOS_DATE:  01/23/2017

BASEBOARD_MANUFACTURER:  HP

BASEBOARD_PRODUCT:  8259

BASEBOARD_VERSION:  83.45

DUMP_TYPE:  2

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_P1: ffffd587af9e0580

BUGCHECK_P2: 0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME:  svchost.exe

CRITICAL_PROCESS:  svchost.exe

EXCEPTION_CODE: (NTSTATUS) 0xbe148300 - <Unable to get error code text>

ERROR_CODE: (NTSTATUS) 0xbe148300 - <Unable to get error code text>

CRITICAL_PROCESS_REPORTGUID:  {a5f81d48-9cc2-401e-bd9f-c29dc189b1af}

IMAGE_NAME:  bfe.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: bfe

FAULTING_MODULE: 0000000000000000 

CPU_COUNT: 4

CPU_MHZ: 9c0

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: 9

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

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0xEF

CURRENT_IRQL:  0

ANALYSIS_SESSION_HOST:  LAPTOP-ES61CU7F

ANALYSIS_SESSION_TIME:  02-08-2018 21:59:28.0010

ANALYSIS_VERSION: 10.0.17074.1002 amd64fre

LAST_CONTROL_TRANSFER:  from fffff8038f51632f to fffff8038ef77880

STACK_TEXT:  
ffffeb02`479db838 fffff803`8f51632f : 00000000`000000ef ffffd587`af9e0580 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffeb02`479db840 fffff803`8f42604d : 00000000`00000000 fffff803`8eeffc61 ffffd587`af9e0580 00000000`c0000005 : nt!PspCatchCriticalBreak+0xff
ffffeb02`479db8e0 fffff803`8f352fd4 : ffffd587`00000000 ffffd587`af9e0580 ffffd587`af9e0858 ffffd587`af9e0580 : nt!PspTerminateAllThreads+0x14de71
ffffeb02`479db950 fffff803`8f352dbd : ffffffff`ffffffff ffffeb02`479dba80 ffffd587`af9e0580 ffff9adf`3e7e1201 : nt!PspTerminateProcess+0xe0
ffffeb02`479db990 fffff803`8ef8a403 : ffffd587`0000052c ffffd587`be148300 ffffd587`af9e0580 00000052`5c47f5fc : nt!NtTerminateProcess+0xa9
ffffeb02`479dba00 00007ff9`02ad0404 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000052`5c47d568 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`02ad0404


THREAD_SHA1_HASH_MOD_FUNC:  042a2b51772309c39e12d732cc93cacf0af3064e

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  ca38fbbb9b111619b13a10beaa752ffcf21089c6

THREAD_SHA1_HASH_MOD:  ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693

FOLLOWUP_NAME:  MachineOwner

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_be148300_bfe.dll!BfeObjectFindById_IMAGE_bfe.dll

BUCKET_ID:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_be148300_bfe.dll!BfeObjectFindById_IMAGE_bfe.dll

PRIMARY_PROBLEM_CLASS:  0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_be148300_bfe.dll!BfeObjectFindById_IMAGE_bfe.dll

TARGET_TIME:  2018-02-08T13:47:12.000Z

OSBUILD:  16299

OSSERVICEPACK:  214

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:  

USER_LCID:  0

OSBUILD_TIMESTAMP:  2018-01-18 04:38:31

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.214

ANALYSIS_SESSION_ELAPSED_TIME:  78e

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xef_svchost.exe_bugcheck_critical_process_be148300_bfe.dll!bfeobjectfindbyid_image_bfe.dll

FAILURE_ID_HASH:  {a2674355-e3a9-624d-585c-28933b4facd6}

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

Re: 回复：电脑时不时的会蓝屏报错重启

Chen-MF — Sun, 11 Feb 2018 02:28:34 GMT

另，如果要恢复出厂系统，备份数据，点开机按钮启动同时不停点键盘F11 调用疑难解答-recovery manager 就可以恢复。

该主题

电脑时不时的会蓝屏报错重启

回复： 电脑时不时的会蓝屏报错重启

回复： 电脑时不时的会蓝屏报错重启

回复： 电脑时不时的会蓝屏报错重启

回复： 电脑时不时的会蓝屏报错重启

回复： 电脑时不时的会蓝屏报错重启

回复： 电脑时不时的会蓝屏报错重启

Re: 回复： 电脑时不时的会蓝屏报错重启

回复：电脑时不时的会蓝屏报错重启

回复：电脑时不时的会蓝屏报错重启

回复：电脑时不时的会蓝屏报错重启

回复：电脑时不时的会蓝屏报错重启

回复：电脑时不时的会蓝屏报错重启

回复：电脑时不时的会蓝屏报错重启

Re: 回复：电脑时不时的会蓝屏报错重启