none
蓝屏0x00000109 RRS feed

  • 问题

  • Windows10经常不定时蓝屏,开机以后看电影或者玩游戏20分钟左右就蓝屏了。

    请我分析分析:


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


    Loading Dump File [C:\Users\ThinkPad\Desktop\新建文件夹\010218-29265-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*C:\Symbols*http://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.1914.amd64fre.rs1_release_inmarket.171117-1700
    Machine Name:
    Kernel base = 0xfffff803`db60a000 PsLoadedModuleList = 0xfffff803`db908040
    Debug session time: Tue Jan  2 16:36:30.883 2018 (UTC + 8:00)
    System Uptime: 0 days 18:25:32.813
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................................
    Loading User Symbols
    Loading unloaded module list
    ...............
    Cannot read PEB32 from WOW64 TEB32 0000d0ed - Win32 error 0n30
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 109, {a3a01fdf32faaa7f, b3b72c65857b9d31, ffffe086961ab5e0, 1c}

    Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

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

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

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

    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a01fdf32faaa7f, Reserved
    Arg2: b3b72c65857b9d31, Reserved
    Arg3: ffffe086961ab5e0, Failure type dependent information
    Arg4: 000000000000001c, Type of corrupted region, can be
    0 : A generic data region
    1 : Modification of a function or .pdata
    2 : A processor IDT
    3 : A processor GDT
    4 : Type 1 process list corruption
    5 : Type 2 process list corruption
    6 : Debug routine modification
    7 : Critical MSR modification

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


    BUGCHECK_STR:  0x109

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  2

    BAD_PAGES_DETECTED: d0ed

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff803db7598a0

    STACK_TEXT:  
    ffffa881`f9876038 00000000`00000000 : 00000000`00000109 a3a01fdf`32faaa7f b3b72c65`857b9d31 ffffe086`961ab5e0 : nt!KeBugCheckEx


    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 53485 instance(s) of page corruption, target is likely to have memory corruption.

    请帮我分析分析。

    2018年1月12日 9:30

全部回复