藍屏問題,附上分析資料

匿名
2019-12-30T08:27:46+00:00

BugCheck 109, {a39ff3e85f78dbed, b3b7006eb1f7249e, fffff803812fffc4, 1}

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

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

Probably caused by : ntkrnlmp.exe ( nt!SepMaximumAccessCheck+464 )

Followup:     MachineOwner


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

  1. 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.

  1. A hardware corruption occurred, e.g. failing RAM holding kernel code or data.

Arguments:

Arg1: a39ff3e85f78dbed, Reserved

Arg2: b3b7006eb1f7249e, Reserved

Arg3: fffff803812fffc4, Failure type dependent information

Arg4: 0000000000000001, 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

    8   : Object type

    9   : A processor IVT

    a   : Modification of a system service function

    b   : A generic session data region

    c   : Modification of a session function or .pdata

    d   : Modification of an import table

    e   : Modification of a session import table

    f   : Ps Win32 callout modification

    10  : Debug switch routine modification

    11  : IRP allocator modification

    12  : Driver call dispatcher modification

    13  : IRP completion dispatcher modification

    14  : IRP deallocator modification

    15  : A processor control register

    16  : Critical floating point control register modification

    17  : Local APIC modification

    18  : Kernel notification callout modification

    19  : Loaded module list modification

    1a  : Type 3 process list corruption

    1b  : Type 4 process list corruption

    1c  : Driver object corruption

    1d  : Executive callback object modification

    1e  : Modification of module padding

    1f  : Modification of a protected process

    20  : A generic data region

    21  : A page hash mismatch

    22  : A session page hash mismatch

    23  : Load config directory modification

    24  : Inverted function table modification

    25  : Session configuration modification

    26  : An extended processor control register

    27  : Type 1 pool corruption

    28  : Type 2 pool corruption

    29  : Type 3 pool corruption

    101 : General pool corruption

    102 : Modification of win32k.sys

Debugging Details:


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER:  System manufacturer

SYSTEM_PRODUCT_NAME:  System Product Name

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  System Version

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  0604

BIOS_DATE:  07/02/2019

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  PRIME X570-PRO

BASEBOARD_VERSION:  Rev X.0x

DUMP_TYPE:  2

BUGCHECK_P1: a39ff3e85f78dbed

BUGCHECK_P2: b3b7006eb1f7249e

BUGCHECK_P3: fffff803812fffc4

BUGCHECK_P4: 1

PG_MISMATCH:  654E676

FAULTING_IP:

nt!SepMaximumAccessCheck+464

fffff803`812fffc4 3c05            cmp     al,5

CPU_COUNT: 10

CPU_MHZ: e09

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 71

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x109

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  2

ANALYSIS_SESSION_HOST:  DESKTOP-T3NEMRA

ANALYSIS_SESSION_TIME:  12-30-2019 15:49:47.0182

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

STACK_TEXT: 

ffff90089fcb4e98 0000000000000000 : 0000000000000109 a39ff3e85f78dbed b3b7006eb1f7249e fffff803812fffc4 : nt!KeBugCheckEx

STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kbase

    ffffdac200a43f99-ffffdac200a43f9e  6 bytes - win32kbase!DirectComposition::CAnimationMarshaler::SetReferenceProperty+49

    [ ff 15 11 28 1a 00:e8 02 13 21 00 90 ]

    ffffdac200a44009-ffffdac200a4400a  2 bytes - win32kbase!SfmSignalTokenEvent+19 (+0x70)

    [ 48 ff:4c 8b ]

    ffffdac200a44010-ffffdac200a44013  4 bytes - win32kbase!SfmSignalTokenEvent+20 (+0x07)

    [ 0f 1f 44 00:e8 0b 14 21 ]

    ffffdac200a45195-ffffdac200a45196  2 bytes - win32kbase!GreSfmDwmShutdown+35 (+0x1185)

    [ 48 ff:4c 8b ]

    ffffdac200a4519c-ffffdac200a4519f  4 bytes - win32kbase!GreSfmDwmShutdown+3c (+0x07)

    [ 0f 1f 44 00:e8 7f 02 21 ]

    ffffdac200a451a5-ffffdac200a451a6  2 bytes - win32kbase!GreSfmDwmShutdown+45 (+0x09)

    [ 48 ff:4c 8b ]

    ffffdac200a451ac-ffffdac200a451af  4 bytes - win32kbase!GreSfmDwmShutdown+4c (+0x07)

    [ 0f 1f 44 00:e8 6f 02 21 ]

24 errors : !win32kbase (ffffdac200a43f99-ffffdac200a451af)

THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

FOLLOWUP_IP:

nt!SepMaximumAccessCheck+464

fffff803`812fffc4 3c05            cmp     al,5

FAULT_INSTR_CODE:  840f053c

SYMBOL_NAME:  nt!SepMaximumAccessCheck+464

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  12dcb470

IMAGE_VERSION:  10.0.18362.535

BUCKET_ID_FUNC_OFFSET:  464

FAILURE_BUCKET_ID:  OLD_IMAGE_ntkrnlmp.exe

BUCKET_ID:  OLD_IMAGE_ntkrnlmp.exe

PRIMARY_PROBLEM_CLASS:  OLD_IMAGE_ntkrnlmp.exe

TARGET_TIME:  2019-12-30T06:24:19.000Z

OSBUILD:  18362

OSSERVICEPACK:  535

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  784

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE: 

USER_LCID:  0

OSBUILD_TIMESTAMP:  1980-01-11 23:53:20

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 1c7a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:old_image_ntkrnlmp.exe

FAILURE_ID_HASH:  {9c0c4046-5b69-0146-b800-16bdd4721e0b}

Followup:     MachineOwner


Windows for home | Windows 10 | 裝置和驅動程式

鎖定的問題。 此問題已從 Microsoft 支援服務社群移轉。 您可以對其是否有幫助進行投票,但無法對問題新增註解或回覆,或進行追蹤。

0 則留言 沒有留言

12 個回答

排序依據: 最實用
  1. 匿名
    2020-02-18T04:30:18+00:00

    因上一次已更新過驅動版本,但依然有藍屏情況

    那我再試試吧,謝謝

    此回答有幫助嗎?

    0 則留言 沒有留言
  2. TaoLi 120.6K 信譽點數 獨立顧問
    2020-02-15T03:34:34+00:00

    您好,

    根據您提供的藍屏檔案,這邊定位到您的問題可能是由於AtihdWT6.sys運行錯誤導致的。

    AtihdWT6.sys(AMD HD Audio Driver)是屬於AMD品牌設備下的驅動程序檔案,建議您更新或者更換相關設備的驅動版本查看效果。

    請您卸載設備中的協力廠商安全軟件

    希望上述信息能解决您的问题!

    此回答有幫助嗎?

    0 則留言 沒有留言
  3. 匿名
    2020-02-14T11:53:51+00:00

    您好,

    由于您提供的蓝屏信息较少,我无法定位到蓝屏所在位置

    麻烦您将蓝屏文件上传至https://send.firefox.com/

    以便我们找到您的问题所在。

    不管您的问题是否解决,看到此条后请及时回复此条,万分感谢!

    https://send.firefox.com/download/470b0ac45fa76e31/#7ac5GakG61DAMLKJUUYX9w

    已上傳,感謝

    此回答有幫助嗎?

    0 則留言 沒有留言
  4. TaoLi 120.6K 信譽點數 獨立顧問
    2020-02-13T12:22:33+00:00

    您好,

    由于您提供的蓝屏信息较少,我无法定位到蓝屏所在位置

    麻烦您将蓝屏文件上传至https://send.firefox.com/

    以便我们找到您的问题所在。

    不管您的问题是否解决,看到此条后请及时回复此条,万分感谢!

    此回答有幫助嗎?

    0 則留言 沒有留言
  5. 匿名
    2020-02-13T11:21:38+00:00

    您好!

    如果是這樣的話,您可以重新收集最新的dump檔案發送過來,

    以便於我們進行分析,協助您解決這個問題。

    不好意思,請問是否有收到我傳送的檔案呢?

    此回答有幫助嗎?

    0 則留言 沒有留言