☰

启动我的内核驱动程序 (StartService) 导致出现 0x124 蓝屏，原因是由于处理器 0 上的 L2 缓存组 6 错误导致机器检查异常

tag-icon • tag-icon windows drivers bsod kernel bluescreenview
启动我的内核驱动程序 (StartService) 导致出现 0x124 蓝屏，原因是由于处理器 0 上的 L2 缓存组 6 错误导致机器检查异常

当我使用 或其他方式手动启动我的驱动程序时StartService，或者当设置为 auto_start 时系统自动加载它时，在DriverEntry达到之前会导致蓝屏。

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


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


************* Path validation summary **************
Response                         Time (ms)     Location
OK                                             c:\symbols

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: c:\symbols
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.23864.amd64fre.win7sp1_ldr.170707-0600
Machine Name:
Kernel base = 0xfffff800`0364a000 PsLoadedModuleList = 0xfffff800`0388c750
Debug session time: Wed Apr 14 10:45:37.450 2021 (UTC + 1:00)
System Uptime: 0 days 0:00:03.199
Loading Kernel Symbols
......................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000000, Machine Check Exception
Arg2: fffffa801a70b8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 1

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on QWERTYUIOP

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 1

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 74

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  124

BUGCHECK_P1: 0

BUGCHECK_P2: fffffa801a70b8f8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff880`03fa25b0 fffff800`03909cd9 : fffffa80`1a70b8d0 fffffa80`19aa2660 fffff8a0`00413b10 00000000`00000000 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`03fa2ad0 fffff800`037e96d7 : fffffa80`1a70b8d0 fffff800`038632f8 fffffa80`19aa2660 00000000`00000202 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`03fa2b00 fffff800`03750fd5 : fffff800`038c5bc0 00000000`00000001 fffff8a0`00413a88 fffffa80`19aa2660 : nt!WheapProcessWorkQueueItem+0x57
fffff880`03fa2b40 fffff800`036c3c85 : fffff800`03ae6200 fffff800`03750fb0 fffffa80`19aa2600 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`03fa2b70 fffff800`03955152 : 00000000`00000000 fffffa80`19aa2660 00000000`00000080 fffffa80`19a8db10 : nt!ExpWorkerThread+0x111
fffff880`03fa2c00 fffff800`036ab926 : fffff880`03d89180 fffffa80`19aa2660 fffff880`03d940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03fa2c40 00000000`00000000 : fffff880`03fa3000 fffff880`03f9d000 fffff880`04782720 00000000`00000000 : nt!KiStartSystemThread+0x16


MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel.sys

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

OS_VERSION:  7.1.7601.23864

BUILDLAB_STR:  win7sp1_ldr

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

FAILURE_ID_HASH:  {270f58cb-a20a-a72d-6d81-eb8c82f01f7a}

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

4: kd> !errrec fffffa801a70b8f8
===============================================================================
Common Platform Error Record @ fffffa801a70b8f8
-------------------------------------------------------------------------------
Record Id     : 01d73112eb4e0c21
Severity      : Fatal (1)
Length        : 928
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Creator       : Microsoft
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Notify Type   : Machine Check Exception
Timestamp     : 4/14/2021 9:45:37 (UTC)
Flags         : 0x00000002 PreviousError

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa801a70b978
Section       @ fffffa801a70ba50
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Proc. Type    : x86/x64
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Instr. Set    : x64
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Error Type    : Cache error
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Operation     : Generic
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Flags         : 0x00
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Level         : 2
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
CPU Version   : 0x00000000000906e9
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Processor ID  : 0x0000000000000000

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa801a70b9c0
Section       @ fffffa801a70bb10
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Local APIC Id : 0x0000000000000000
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
CPU Id        : e9 06 09 00 00 08 10 00 - bf fb fa 7f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa801a70bb10
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa801a70ba08
Section       @ fffffa801a70bb90
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock

fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
Error         : GCACHEL2_ERR_ERR (Proc 0 Bank 6)
  Status      : 0xee2000000040110a
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
  Address     : 0x00000000fef1ffc0
fffff800038370e8: Unable to get Flags value from nt!KdVersionBlock
  Misc.       : 0x0000007880010086

驱动程序已使用SetupOpenInfFile和正确安装SetupInstallFileW：

λ sc qc MyDriver
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: MyDriver
TYPE : 1 KERNEL_DRIVER
START_TYPE : 3 DEMAND_START
ERROR_CONTROL : 1 NORMAL
BINARY_PATH_NAME : \??\C:\Windows\system32\drivers\MyDriver.sys
LOAD_ORDER_GROUP :
TAG : 0
DISPLAY_NAME : MyDriver
DEPENDENCIES :
SERVICE_START_NAME :

我正在使用 kmspico 激活的 Windows 7 版本。我打开了调试模式，关闭了测试签名并关闭了驱动程序签名强制，MyDriver.sys 是使用 Visual Studio 2017 编译的基本 WDM Driver.c。

我只是无法想象为什么会出现这个蓝屏，出于某种原因，在我的 Windows 7 版本中，这是我 4 年内 30 个蓝屏转储中唯一遇到的蓝屏，所有都是 0x124，但都需要特定的软件触发器，因为所有其他驱动程序都可以正确启动。此外，自 2018 年以来，我遇到的每一个蓝屏都显示：

Error         : GCACHEL2_ERR_ERR (Proc 0 Bank 6)
  Status      : 0xee2000000040110a
  Address     : 0x00000000fef1ffc0
  Misc.       : 0x0000007880010086

但是再一次，我的电脑现在可以运行 150 天，而且只有当我启动这个特定的驱动程序时才会发生这种情况。

这类似，但没有帮助。

在 MiniDump 上，它说异常发生在ntosknl.exe+4acfac哪个位置nt!WheapCreateLiveTriageDump+0x6c，即指令mov [rsp+518h+Size], rdi，但这似乎是在发生 0x124 时为 WHEA 实时转储创建的线程，并且不会KeBugCheckEx像普通蓝屏那样在堆栈顶部显示导致异常的调用堆栈；因此，我实际上看不到蓝屏，因为KeBugCheckEx显示蓝屏的是，而在这种情况下它没有被调用。每个 0x124 蓝屏nt!WheapCreateLiveTriageDump+0x6c在堆栈顶部都有，并且由于某种原因将其显示为导致异常的地址——我认为这是因为它是之后的指令RtlCaptureContext，它是堆栈上显示的返回地址，所以这是捕获的上下文。通常，当您出现蓝屏时KeBugCheckEx，显示的故障 IP 是首先导致异常的 IP，并且位于调用堆栈的某个位置，并且由于它不是这个调用堆栈的一部分，它只使用帧的返回地址RtlCaptureContext。它以某种方式知道故障模块是GenunineIntel.sys，除非它总是显示 0x124——显然我不认为这是导致 MCA 的模块。

不要回答说我的硬件有问题——我没有。好吧，这是我的 CPU，我的 BIOS 与所述不同，但我已更新到 2019版本 1.9.0并且它仍然出现蓝屏并显示相同的 MCI 状态，但这不应该相关，因为这是由软件创建的条件，并且仅当我加载该特定驱动程序时才会发生，因此应该可以在不更改硬件或固件的情况下解决它。

事实上有趣的是，我甚至得到了一个 7E 错误检查，这是蓝屏第一次显示蓝屏，但小型转储显示 0x124...

答案1

我刚刚在虚拟机中运行了它，windbg 内核调试器通过命名管道连接到虚拟 COM1 端口，它进入了调试器，你猜对了MyDriver!__security_init_cookie+0x2d，我们确实在图像中的失败分支后看到了一堆 cc 断点。就像我说的，它没有到达，DriverEntry所以我预计错误会出现在GsDriverEntry。我会告诉你是什么导致这个函数失败。但至于这个错误，它是由未连接调试器时的断点异常引起的——更重要的是不是硬件问题

这是原始代码：

在此处输入图片描述

当你凝视它时，很明显它会失败

解决方法是将.vxproj文件更改为 Windows7，而原来显示的是 Windows10

现在我有这个__security_init_cookie：

在此处输入图片描述

相关内容