64位 regsrv win10_win10 专业版 64位系统频繁蓝屏，MEMORY_MANAGEMENT - Microsoft Community...

最新推荐文章于 2022-08-02 16:58:50 发布

理论编码带师

最新推荐文章于 2022-08-02 16:58:50 发布

阅读量3.2k

点赞数 1

文章标签： 64位 regsrv win10

本文链接：https://blog.csdn.net/weixin_32321921/article/details/112995101

版权

最近不管是网游戏看视频还是普通的用qq软件聊天，总是会突然蓝屏然后重启。收集了dump文件。

http://pan.baidu.com/s/1geU4Uhd

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

最后一次crash后的dump

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

Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64

Loading Dump File [C:\Windows\Minidump\121016-8406-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.447.amd64fre.rs1_release_inmarket.161102-0100

Machine Name:

Kernel base = 0xfffff803`6c290000 PsLoadedModuleList = 0xfffff803`6c595060

Debug session time: Sat Dec 10 01:09:29.360 2016 (UTC + 8:00)

System Uptime: 3 days 2:25:56.078

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 1A, {41792, ffffbb3ffd41eb08, 80000000000000, 0}

Probably caused by : memory_corruption ( ONE_BIT )

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of

the PTE. Parameters 3/4 contain the low/high parts of the PTE.

Arg2: ffffbb3ffd41eb08

Arg3: 0080000000000000

Arg4: 0000000000000000

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 14393.447.amd64fre.rs1_release_inmarket.161102-0100

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1902

BIOS_DATE: 06/24/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z170-AR

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffbb3ffd41eb08

BUGCHECK_P3: 80000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BUGCHECK_STR: 0x1a_41792

CPU_COUNT: 8

CPU_MHZ: fa8

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

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: LEADERBEAR-PC

ANALYSIS_SESSION_TIME: 12-10-2016 01:18:17.0071

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT:

ffffa600`914a5128 fffff803`6c427ae3 : 00000000`0000001a 00000000`00041792 ffffbb3f`fd41eb08 00800000`00000000 : nt!KeBugCheckEx

ffffa600`914a5130 fffff803`6c329e73 : 00000000`00000000 ffffa600`914a5409 00000000`00000000 ffff9189`7d3f8080 : nt! ?? ::FNODOBFM::`string'+0x3e143

ffffa600`914a5340 fffff803`6c6f5323 : ffff9189`812f8610 ffff9189`812f8610 ffff9189`81e10840 ffff9189`81e10340 : nt!MiDeleteVad+0x1f3

ffffa600`914a5470 fffff803`6c6f5107 : 00000000`00040000 ffff9189`7d3f8080 00000000`00000001 ffff9189`81e10340 : nt!MmCleanProcessAddressSpace+0xf7

ffffa600`914a54e0 fffff803`6c74c590 : ffff9189`81e10340 ffffbd8f`419dd9d0 ffffa600`914a55c0 00000000`00000000 : nt!PspRundownSingleProcess+0x117

ffffa600`914a5560 fffff803`6c6cac3e : 00000000`c0000005 ffff9189`7d3f8080 ffffa600`914a5a80 ffff9189`7d3f8128 : nt!PspExitThread+0x508

ffffa600`914a56a0 fffff803`6c31fc02 : 00000000`00000011 00000000`00000000 00000000`000004d0 ffffbb3f`00000010 : nt!KiSchedulerApcTerminate+0x2e

ffffa600`914a56d0 fffff803`6c3ddb90 : 00000000`00000001 ffffa600`914a4da8 ffffa600`914a5010 ffffa600`00000000 : nt!KiDeliverApc+0x2f2

ffffa600`914a5760 fffff803`6c3e5789 : ffffa600`914a5a00 00000000`00000001 ffffa600`914a5a00 ffff9189`812f8610 : nt!KiInitiateUserApc+0x70

ffffa600`914a58a0 fffff803`6c3e3be1 : ffff9189`7d3f8080 00000072`00000008 ffff9189`7d3f8080 00000000`00000194 : nt!KiExceptionDispatch+0x149

ffffa600`914a5a80 00007ffa`afe984a9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x221

00000072`07e01200 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`afe984a9

STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: aebc71f874f7bdcfc4a74c5a3f974bf63d4782cd

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: c1f9e21f049178587c6e787f4b37a34f0f1af8b6

THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c

SYMBOL_NAME: ONE_BIT

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BIT

TARGET_TIME: 2016-12-09T17:09:29.000Z

OSBUILD: 14393

OSSERVICEPACK: 447

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-11-02 18:17:03

BUILDDATESTAMP_STR: 161102-0100

BUILDLAB_STR: rs1_release_inmarket

BUILDOSVER_STR: 10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100

ANALYSIS_SESSION_ELAPSED_TIME: 339

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:memory_corruption_one_bit

FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup: MachineOwner

---------

3: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

# Any other values for parameter 1 must be individually examined.

Arguments:

Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of

the PTE. Parameters 3/4 contain the low/high parts of the PTE.

Arg2: ffffbb3ffd41eb08

Arg3: 0080000000000000

Arg4: 0000000000000000

Debugging Details:

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

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.447 (rs1_release_inmarket.161102-0100)

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: SKU

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 1902

BIOS_DATE: 06/24/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: Z170-AR

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

DUMP_FILE_ATTRIBUTES: 0x8

Kernel Generated Triage Dump

BUGCHECK_P1: 41792

BUGCHECK_P2: ffffbb3ffd41eb08

BUGCHECK_P3: 80000000000000

BUGCHECK_P4: 0

MEMORY_CORRUPTOR: ONE_BIT

BUGCHECK_STR: 0x1a_41792

CPU_COUNT: 8

CPU_MHZ: fa8

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

PROCESS_NAME: svchost.exe

CURRENT_IRQL: 2

ANALYSIS_SESSION_HOST: LEADERBEAR-PC

ANALYSIS_SESSION_TIME: 12-10-2016 01:18:17.0899