448      windows

新組裝的電腦總是藍屏，主要是memory

• windows係統日誌裏麵查看的很多：

計算機已經從檢測錯誤後重新啟動。檢測錯誤: 0x0000001a (0x0000000000005012, 0xfffff08010804310, 0x000000000000a518, 0x000000000000a52e)。已將轉儲的數據保存在: C:\Windows\Minidump\121617-4750-01.dmp。報告 ID: feddc5c5-0c02-4e4d-9a35-01c7c5e53040

應用程序-特定 權限設置並未向在應用程序容器 不可用 SID (不可用)中運行的地址 LocalHost (使用 LRPC) 中的用戶 NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19)授予針對 CLSID 為 
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
、APPID 為 
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
 的 COM 服務器應用程序的 本地 激活 權限。此安全權限可以使用組件服務管理工具進行修改

• 藍屏日誌裏麵

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


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

Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1944.amd64fre.rs1_release.171129-2100
Machine Name:
Kernel base = 0xfffff801`3528d000 PsLoadedModuleList = 0xfffff801`3558b040
Debug session time: Sat Dec 16 15:16:34.621 2017 (UTC + 8:00)
System Uptime: 0 days 2:24:40.388
Loading Kernel Symbols
...............................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.......
Cannot read PEB32 from WOW64 TEB32 00008484 - Win32 error 0n30
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {5012, fffff08010804310, a518, a52e}

Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

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

 *** Memory manager detected 33924 instance(s) of page corruption, target is likely to have memory corruption.

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000005012, The subtype of the bugcheck.
Arg2: fffff08010804310
Arg3: 000000000000a518
Arg4: 000000000000a52e

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


BUGCHECK_STR:  0x1a_5012

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  2

BAD_PAGES_DETECTED: 8484

LAST_CONTROL_TRANSFER:  from fffff801352cbefb to fffff801353dc8a0

STACK_TEXT:  
ffffc900`4233c558 fffff801`352cbefb : 00000000`0000001a 00000000`00005012 fffff080`10804310 00000000`0000a518 : nt!KeBugCheckEx
ffffc900`4233c560 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveWorkingSetPages+0x69b


STACK_COMMAND:  kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

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

 *** Memory manager detected 33924 instance(s) of page corruption, target is likely to have memory corruption.

求助！

最後更新：2017-12-16 16:05:07

  上一篇： Windows10 出現DPC WATCHDOG VIOLATION 藍屏

  下一篇： 家長控製已經取消。係統還是顯示鎖屏。不能進入。