取消
显示结果 
搜索替代 
您的意思是: 
见习生
见习生
16 8 0 0
1个帖子(共 3 条)
4,829 次查看
标记帖子

睡眠唤醒蓝屏

probook 440G4 Z3Y33PA#AB2
Microsoft Windows 10 (64-bit)

 

第三次蓝屏才看出如下问题:


Microsoft (R) Windows Debugger Version 10.0.15063.137 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [E:\蓝屏\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 15063 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 15063.0.amd64fre.rs2_release.170317-1834
Machine Name:
Kernel base = 0xfffff801`12c7d000 PsLoadedModuleList = 0xfffff801`12fc95a0
Debug session time: Sat Apr 29 19:59:06.266 2017 (UTC + 8:00)
System Uptime: 0 days 2:33:12.081
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............
Loading User Symbols

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

Use !analyze -v to get detailed debugging information.

BugCheck A0, {608, ffff83871d949018, ffffffff80000000, 0}

*** ERROR: Module load completed but symbols could not be loaded for RtsPer.sys
Probably caused by : RtsPer.sys ( RtsPer+832a5 )

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

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

INTERNAL_POWER_ERROR (a0)
The power policy manager experienced a fatal error.
Arguments:
Arg1: 0000000000000608, A driver has attempted to transition a component to idle without
 a preceeding active request.
Arg2: ffff83871d949018, POP_FX_COMPONENT component
Arg3: ffffffff80000000, POP_FX_COMPONENT_FLAGS component condition
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  HP ProBook 440 G4

SYSTEM_SKU:  Z3Y33PA#AB2

BIOS_VENDOR:  HP

BIOS_VERSION:  P85 Ver. 01.04

BIOS_DATE:  04/12/2017

BASEBOARD_MANUFACTURER:  HP

BASEBOARD_PRODUCT:  822E

BASEBOARD_VERSION:  KBC Version 42.65

DUMP_TYPE:  1

BUGCHECK_P1: 608

BUGCHECK_P2: ffff83871d949018

BUGCHECK_P3: ffffffff80000000

BUGCHECK_P4: 0

BUGCHECK_STR:  0xa0_608

CPU_COUNT: 4

CPU_MHZ: b58

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 8e

CPU_STEPPING: 9

CPU_MICROCODE: 6,8e,9,0 (F,M,S,R)  SIG: 3C'00000000 (cache) 3C'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-PATE8PS

ANALYSIS_SESSION_TIME:  04-30-2017 21:21:49.0820

ANALYSIS_VERSION: 10.0.15063.137 x86fre

LAST_CONTROL_TRANSFER:  from fffff80112ea3f60 to fffff80112de8fd0

STACK_TEXT: 
ffffae00`9e12f8b8 fffff801`12ea3f60 : 00000000`000000a0 00000000`00000608 ffff8387`1d949018 ffffffff`80000000 : nt!KeBugCheckEx
ffffae00`9e12f8c0 fffff801`12e2a30b : ffff8387`1d949018 00000000`00000000 00000000`00000000 00000000`00000002 : nt!PopFxBugCheck+0x1c
ffffae00`9e12f900 fffff801`12db097c : 00000015`66e8e234 ffff8387`1c61b0f0 00000000`00000001 00000000`00000000 : nt!PopFxIdleComponent+0xfb9df
ffffae00`9e12f950 fffff809`eb4a32a5 : ffff8387`1dc551b0 00000000`00000000 ffff8387`1e602110 00000000`0000002f : nt!PoFxReportDevicePoweredOn+0x10c
ffffae00`9e12f9d0 fffff809`eb4a3378 : 00000000`00000000 00000000`00000000 ffff8387`1dc55060 fffff809`eb4cd2d0 : RtsPer+0x832a5
ffffae00`9e12fa20 fffff809`eb4a4dbc : ffff8387`1dc551b0 00000000`00000000 fffff809`eb4cd630 00000000`00000001 : RtsPer+0x83378
ffffae00`9e12fa50 fffff801`12d29a1b : ffff8387`1ff3f260 fffff801`13075650 fffff801`13075650 ffff8387`194ff040 : RtsPer+0x84dbc
ffffae00`9e12fa90 fffff801`12c9c1c8 : 00000000`00000200 ffff8387`194ff040 fffff801`12d29920 fffff801`0000000c : nt!IopProcessWorkItem+0xfb
ffffae00`9e12fb00 fffff801`12d36a37 : fffff809`e5456170 00000000`00000080 ffff8387`1847a500 ffff8387`194ff040 : nt!ExpWorkerThread+0xd8
ffffae00`9e12fb90 fffff801`12dee456 : ffffae00`980a8180 ffff8387`194ff040 fffff801`12d369f0 fffff809`e54c1d8a : nt!PspSystemThreadStartup+0x47
ffffae00`9e12fbe0 00000000`00000000 : ffffae00`9e130000 ffffae00`9e129000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  d6253787bb4b5ba22484d4d77a32d1c6ce80fece

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  f4f3c0e5f61aab88f27a0eb9d05fcd962372cdae

THREAD_SHA1_HASH_MOD:  133a75268342efb703c50a473401f547cdc0b5e4

FOLLOWUP_IP:
RtsPer+832a5
fffff809`eb4a32a5 488bd6          mov     rdx,rsi

FAULT_INSTR_CODE:  b9d68b48

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  RtsPer+832a5

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RtsPer

IMAGE_NAME:  RtsPer.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  57a306b2

BUCKET_ID_FUNC_OFFSET:  832a5

FAILURE_BUCKET_ID:  0xa0_608_RtsPer!unknown_function

BUCKET_ID:  0xa0_608_RtsPer!unknown_function

PRIMARY_PROBLEM_CLASS:  0xa0_608_RtsPer!unknown_function

TARGET_TIME:  2017-04-29T11:59:06.000Z

OSBUILD:  15063

OSSERVICEPACK:  0

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:  2017-04-19 14:01:43

BUILDDATESTAMP_STR:  170317-1834

BUILDLAB_STR:  rs2_release

BUILDOSVER_STR:  10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME:  13a8

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa0_608_rtsper!unknown_function

FAILURE_ID_HASH:  {d17c2b0a-065c-797b-88e9-a0e0c1514c79}

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

0: kd> lmvm RtsPer
Browse full module list
start             end                 module name
fffff809`eb420000 fffff809`eb4e4000   RtsPer     (no symbols)          
    Loaded symbol image file: RtsPer.sys
    Image path: \SystemRoot\system32\DRIVERS\RtsPer.sys《==到这才发现的读卡器驱动的问题,把读卡器驱动卸载,然后让windows10自动更新,结果两天没有在出现蓝屏,不知以后还会不会????
    Image name: RtsPer.sys
    Browse all global symbols  functions  data
    Timestamp:        Thu Aug  4 17:11:14 2016 (57A306B2)
    CheckSum:         000BFE1A
    ImageSize:        000C4000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

2 条回复2
高级教授 高级教授
高级教授
2,749 1,477 71 250
2个帖子(共 3 条)
标记帖子

睡眠唤醒蓝屏

官网的驱动试过没?

我作为志愿者在社区帮忙,我的回帖只代表我自己。
如果我的答复对您有帮助,欢迎您点击我答复下方的 “大拇指”给我奖励。
如果我的答复解决了您的问题,欢迎您点击我的帖子下方的 “接受为解决方案”。
这条回复对您有帮助吗? 没有
见习生
作者
见习生
16 8 0 0
3个帖子(共 3 条)
标记帖子

睡眠唤醒蓝屏

就是装官网驱动出的问题,卸载后让windows10自动更新才解决问题。

这条回复对您有帮助吗? 没有
† 惠普支持社区是一个客户交流平台,便于客户找到有效的解决方法,快速解决问题,充分利用惠普产品。请在发帖之前,阅读社区的使用条款注册须知。