系统蓝屏问题常规处理步骤

匿名
2010-02-21T00:25:15+00:00

出现蓝屏了怎么办

蓝屏（Blue Screen）错误可能是Windows系统中比较常见的一种错误。而且对于我们大多数人来说，发生蓝屏之后可能就束手无策了。这里介绍一些发生蓝屏错误时的一些办法。办法很多，但是今天这部分，主要介绍如何用Windows Debugging Tool，或者叫Windbg，结合微软的论坛来处理问题的办法。

首先，要用WinDBG处理蓝屏问题，要确保系统有生成内存转储文件。

确认存在内存转储文件

默认配置的Windows 7，生成的可能是核心转储文件（Kernal Memory Dump）或是小内存转储文件（Minidump）。如果是核心转储文件，默认会存为C:\Windows\Memory.dmp，如果是小内存转储文件，相关文件会保存在C:\Windows\MiniDump目录下面。

所以，出现蓝屏后，请检查系统中有没有C:\Windows\Memory.dmp这个文件，或者是C:\Windows\MiniDump目录下面按照日期命名的文件。比如，Mini010810-01.dmp就是2010年1月8日的第一个小内存转储文件。

如果没有相应的内存转储文件，请参考有关文档。

安装Windows Debugging Tool （WinDBG）

接下来，我们要安装Windbg了。WinDBG可以在微软网站下载，32位的地址是http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx ，64位的地址是http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx 。注意WinDBG只有英文版的。你只要到这两个地方找一个最新的版本下载安装就可以了。如果你不是很懂英语，那就直接到这两个地址下载：32位：http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.11.1.404.msi，64位：

http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.11.1.404.msi

http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.11.1.404.msi。然后一路Next安转就可以了。WinDBG安转文件大小，大概在15-30兆左右。

配置Windows Debugging Tool （WinDBG）

在用WinDBG分析内存转储文件之前，我们要配置一下WinDBG。

首先，选一个临时目录存放Symbol文件。比如，建立一个目录叫C:\Temp

然后，打开WinDBG，在File菜单-〉选择Symbol File Path。在打开的对话框里输入：

SRV*c:\temp*http://msdl.microsoft.com/download/symbols

选择OK确定。WinDBG就配置好了。

用Windows Debugging Tool （WinDBG）分析内存转储文件

在WinDBG里面，在File菜单，选择Open Crash Dump，然后找到前面说的那个核心内存转储文件或者小内存转储文件，选择打开。等待一会儿，如果需要从微软网站下载Symbole文件的话，时间可能会比较长。如果不出现大量Warning，就说明设置是成功的。如果出现Your debugger is not using the correct symbols                之类的信息，说明配置有问题，到上一步再仔细检查一下。

一直等到出现Use !analyze -v to get detailed debugging information.字样和0: kd>提示符。

按照提示，输入!analyze -v命令。等待命令执行完成。

分析Windows Debugging Tool（WinDBG）结果

如果你的英文有一定基础，!analyze -v命令可能就告诉你很多信息了。如果看的不是很明白，就把结果贴出来让热心的网友给你分析一下吧。

http://shower-thunder.spaces.live.com/blog/cns!250DE47BD119587C!131.entry

Windows 家庭版 | 以前的 Windows 版本 | Windows 更新

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。

0 个注释
问题作者接受的答案
匿名
2014-09-12T06:03:21+00:00

您好，

从您提供的蓝屏信息中可以查看到是由于EagleX64.sys、KartRider.exe文件导致的。

错误代码: 0x00000019，表示磁盘驱动器在磁盘找不到持定的扇区或磁道。

Eaglex64.sys 是安博士杀毒软件，可能是游戏自带的安全软件也有可能是您安装的该软件。

KartRider.exe是跑跑卡丁车这款游戏的进程，可能是该软件不兼容当前系统或与电脑上安装的应用软件存在冲突（特别是杀毒软件）。

建议您暂时卸载掉电脑上的安全防护类软件再确认问题（您安装了360和迅雷之类的应用了）。

此答案是否有帮助?

6 个人认为此答案很有帮助。
0 个注释

80 个其他答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. 匿名
    2012-07-19T05:13:59+00:00

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    VIDEO_TDR_FAILURE (116)

    Attempt to reset the display driver and recover from timeout failed.

    Arguments:

    Arg1: fffffa800b6f8010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

    Arg2: fffff88005ce5f14, The pointer into responsible device driver module (e.g. owner tag).

    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.

    Arg4: 0000000000000004, Optional internal context dependent data.

    Debugging Details:

    FAULTING_IP:

    nvkflt+1af14

    fffff880`05ce5f14 4c8bc1          mov     r8,rcx

    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

    CUSTOMER_CRASH_COUNT:  1

    BUGCHECK_STR:  0x116

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT: 

    fffff880056eab48 fffff88005d68000 : 0000000000000116 fffffa800b6f8010 fffff88005ce5f14 ffffffffc000009a : nt!KeBugCheckEx

    fffff880056eab50 fffff88005d3b867 : fffff88005ce5f14 fffffa8008cce000 0000000000000000 ffffffffc000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec

    fffff880056eab90 fffff88005d67e0f : 00000000ffffd84d fffffa8008bbc010 fffffa800b6f8010 000000000000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3

    fffff880056eac40 fffff88005c37eb1 : fffffa8009fd2590 0000000000000080 0000000000000000 fffffa8008bbc010 : dxgkrnl!TdrResetFromTimeout+0x23

    fffff880056eacc0 fffff8000431f6e6 : 000000000200913f fffffa8008ce8210 fffffa8003f5ab30 fffffa8008ce8210 : dxgmms1!VidSchiWorkerThread+0x101

    fffff880056ead00 fffff8000405e566 : fffff880049d4180 fffffa8008ce8210 fffff880049defc0 fffff8800163c534 : nt!PspSystemThreadStartup+0x5a

    fffff880056ead40 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x16

    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:

    nvkflt+1af14

    fffff880`05ce5f14 4c8bc1          mov     r8,rcx

    SYMBOL_NAME:  nvkflt+1af14

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nvkflt

    IMAGE_NAME:  nvkflt.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4eae90a9

    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvkflt.sys

    BUCKET_ID:  X64_0x116_IMAGE_nvkflt.sys

    Followup: MachineOwner

    以上是我的分析结果，版主麻烦帮我看下，我的手提N55，WIN7系统，新买的，现在几天就蓝屏几次了，晕死！麻烦大神帮帮我，小弟在此感谢了！

    此答案是否有帮助?

    0 个注释
  2. 匿名
    2012-06-25T10:57:35+00:00

    WHEA_UNCORRECTABLE_ERROR (124)

    A fatal hardware error has occurred. Parameter 1 identifies the type of error

    source that reported the error. Parameter 2 holds the address of the

    WHEA_ERROR_RECORD structure that describes the error conditon.

    Arguments:

    Arg1: 00000000, Machine Check Exception

    Arg2: 87d7136c, Address of the WHEA_ERROR_RECORD structure.

    Arg3: 00000000, High order 32-bits of the MCi_STATUS value.

    Arg4: 00000000, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:

    BUGCHECK_STR:  0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT:

    90b93cc4 846e5105 87d71350 8477dc28 8477dc20 nt!WheapCreateTriageDumpFromPreviousSession+0x32

    90b93ce4 846e5f2f 8477dc20 87d71350 8477dc50 nt!WheapProcessWorkQueueItem+0x56

    90b93d00 8468406b 8477dc20 00000000 86daa4c0 nt!WheapWorkQueueWorkerRoutine+0x1f

    90b93d50 84824ad1 00000001 a5f6a8ec 00000000 nt!ExpWorkerThread+0x10d

    90b93d90 846d6209 84683f5e 00000001 00000000 nt!PspSystemThreadStartup+0x9e

    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_BUS_PRV

    Followup: MachineOwner

    麻烦楼主帮我看看这是什么情况

    此答案是否有帮助?

    0 个注释
  3. 匿名
    2012-05-11T08:43:39+00:00

    Microsoft (R) Windows Debugger Version 6.12.0002.633 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\MEMORY.DMP]

    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: C:\Program Files\Debugging Tools for Windows (x86)\symproxy;C:\Users\gaoxingliang

    Executable search path is:

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

    THIS DUMP FILE IS PARTIALLY CORRUPT.

    KdDebuggerDataBlock is not present or unreadable.

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

    Unable to read PsLoadedModuleList

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

    THIS DUMP FILE IS PARTIALLY CORRUPT.

    KdDebuggerDataBlock is not present or unreadable.

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

    KdDebuggerData.KernBase < SystemRangeStart

    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Machine Name:

    Kernel base = 0x00000000 PsLoadedModuleList = 0x84548810

    Debug session time: Mon May 10 00:10:58.306 2010 (UTC + 8:00)

    System Uptime: 0 days 0:02:32.711

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

    THIS DUMP FILE IS PARTIALLY CORRUPT.

    KdDebuggerDataBlock is not present or unreadable.

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

    Unable to read PsLoadedModuleList

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

    THIS DUMP FILE IS PARTIALLY CORRUPT.

    KdDebuggerDataBlock is not present or unreadable.

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

    KdDebuggerData.KernBase < SystemRangeStart

    Loading Kernel Symbols

    Unable to read PsLoadedModuleList

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    CS descriptor lookup failed

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get program counter

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {80a7da98, 2, 1, 84469d5e}

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to read selector for PCR for processor 0

    GetContextState failed, 0x80004002

    Unable to read selector for PCR for processor 0

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    Unable to get current machine context, HRESULT 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    Unable to read selector for PCR for processor 0

    GetContextState failed, 0x80004002

    Unable to read selector for PCR for processor 1

    GetContextState failed, 0x80004002

    Unable to read selector for PCR for processor 0

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    GetContextState failed, 0x80004002

    帮下忙分析下 谢谢

    此答案是否有帮助?

    0 个注释
  4. 匿名
    2012-04-09T11:32:51+00:00

    BugCheck 116, {fffffa800405a010, fffff8800fe68ed4, 0, 2}

    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2

    *** WARNING: Unable to verify timestamp for nvlddmkm.sys

    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys

    Probably caused by : nvlddmkm.sys ( nvlddmkm+175ed4 )

    Followup: MachineOwner

    0: kd> !analyze -v

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

    VIDEO_TDR_FAILURE (116)

    Attempt to reset the display driver and recover from timeout failed.

    Arguments:

    Arg1: fffffa800405a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).

    Arg2: fffff8800fe68ed4, The pointer into responsible device driver module (e.g. owner tag).

    Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.

    Arg4: 0000000000000002, Optional internal context dependent data.

    Debugging Details:

    FAULTING_IP:

    nvlddmkm+175ed4

    fffff880`0fe68ed4 4883ec28        sub     rsp,28h

    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

    CUSTOMER_CRASH_COUNT:  1

    BUGCHECK_STR:  0x116

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    STACK_TEXT: 

    fffff880051d85f8 fffff88005d30000 : 0000000000000116 fffffa800405a010 fffff8800fe68ed4 0000000000000000 : nt!KeBugCheckEx

    fffff880051d8600 fffff88005d2fd0a : fffff8800fe68ed4 fffffa800405a010 fffffa8008451160 fffffa80085260a0 : dxgkrnl!TdrBugcheckOnTimeout+0xec

    fffff880051d8640 fffff88005c0ff07 : fffffa800405a010 0000000000000000 fffffa8008451160 fffffa80085260a0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2

    fffff880051d8670 fffff88005c3dd5a : fffffa80ffffffff 0000000000003042 fffff880051d87c0 0000000000000006 : dxgmms1!VidSchiReportHwHang+0x40b

    fffff880051d8750 fffff88005c23bb1 : fffffa8008550000 fffffffffeced300 0000000000000006 fffffa8008550000 : dxgmms1!VidSchWaitForCompletionEvent+0x196

    fffff880051d8790 fffff88005c2104c : 0000000000000001 fffff8a008ba3980 fffffa8008550000 0000000000000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9

    fffff880051d8890 fffff88005c1e803 : 0000000000000000 fffffa800411b000 0000000000000013 fffff8a008ba3980 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc

    fffff880051d88d0 fffff88005c3865d : 0000000000000000 fffff8a0089cdfd0 fffffa8000000000 fffffa80040b6320 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f

    fffff880051d8aa0 fffff88005c38398 : fffff80000b96080 fffff88005c37d00 fffffa8000000000 fffffa8000000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241

    fffff880051d8c90 fffff88005c37e96 : 0000000000000000 fffffa800405f8b0 0000000000000080 fffffa80085260a0 : dxgmms1!VidSchiSubmitQueueCommand+0x50

    fffff880051d8cc0 fffff80004f1df7a : 0000000001c3650a fffffa800854f770 fffffa8003cd5740 fffffa800854f770 : dxgmms1!VidSchiWorkerThread+0xd6

    fffff880051d8d00 fffff80004c749c6 : fffff80004df8e80 fffffa800854f770 fffff80004e06cc0 fffff88001627384 : nt!PspSystemThreadStartup+0x5a

    fffff880051d8d40 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KxStartSystemThread+0x16

    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP:

    nvlddmkm+175ed4

    fffff880`0fe68ed4 4883ec28        sub     rsp,28h

    SYMBOL_NAME:  nvlddmkm+175ed4

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nvlddmkm

    IMAGE_NAME:  nvlddmkm.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ed21614

    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

    Followup: MachineOwner

    求各种解释，求解答，求发到邮箱。衷心感谢

    此答案是否有帮助?

    0 个注释