ASUS A15 FA506IC 玩遊戲時不定時黑屏當機與藍屏當機

匿名
2023-01-04T19:31:43+00:00

如題,重設過電腦,更新過驅動程式,但不確定問題是甚麼?\

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

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

Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff807`7fc00000 PsLoadedModuleList = 0xfffff807`80829a80
Debug session time: Thu Jan  5 02:41:46.394 2023 (UTC + 8:00)
System Uptime: 0 days 3:28:45.241
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`8001afd0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff382`384de760=00000000000000f7
14: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_OVERRAN_STACK_BUFFER (f7)
A driver has overrun a stack-based buffer.  This overrun could potentially
allow a malicious user to gain control of this machine.
DESCRIPTION
A driver overran a stack-based buffer (or local variable) in a way that would
have overwritten the function's return address and jumped back to an arbitrary
address when the function returned.  This is the classic "buffer overrun"
hacking attack and the system has been brought down to prevent a malicious user
from gaining complete control of it.
Do a kb to get a stack backtrace -- the last routine on the stack before the
buffer overrun handlers and BugCheck call is the one that overran its local
variable(s).
Arguments:
Arg1: fffff382384dfc40, Actual security check cookie from the stack
Arg2: 000039b5cf5497c2, Expected security check cookie
Arg3: ffffc64a30ab683d, Complement of the expected security check cookie
Arg4: 0000000000000000, zero

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1905

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 14453

    Key  : Analysis.IO.Other.Mb
    Value: 23

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 30

    Key  : Analysis.Init.CPU.mSec
    Value: 812

    Key  : Analysis.Init.Elapsed.mSec
    Value: 243808

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0xf7

    Key  : Bugcheck.Code.Register
    Value: 0xf7

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

FILE_IN_CAB:  010523-11203-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

BUGCHECK_CODE:  f7

BUGCHECK_P1: fffff382384dfc40

BUGCHECK_P2: 39b5cf5497c2

BUGCHECK_P3: ffffc64a30ab683d

BUGCHECK_P4: 0

SECURITY_COOKIE:  Expected 000039b5cf5497c2 found fffff382384dfc40

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000

STACK_TEXT:  
fffff382`384de758 fffff807`80101325     : 00000000`000000f7 fffff382`384dfc40 000039b5`cf5497c2 ffffc64a`30ab683d : nt!KeBugCheckEx
fffff382`384de760 fffff807`7ffe2c32     : fffff382`384df9e0 fffff382`384de8a0 fffff807`7fe2fdd4 fffff807`7fc53f7c : nt!_report_gsfailure+0x25
fffff382`384de7a0 fffff807`7ffe2bc7     : fffff382`384dede0 fffff382`384dedb0 fffff382`384dedd0 fffff382`384de800 : nt!_GSHandlerCheckCommon+0x5a
fffff382`384de7d0 fffff807`80026242     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff382`384de8a0 : nt!_GSHandlerCheck+0x13
fffff382`384de800 fffff807`7fef7957     : fffff382`384deda0 fffff807`7fe2fdd4 fffff382`384df9e0 fffff382`384de8a0 : nt!RtlpExecuteHandlerForException+0x12
fffff382`384de830 fffff807`7fefb8a1     : ffffffff`ffffffff fffff382`384df850 fffff382`384df850 fffff382`384defc0 : nt!RtlDispatchException+0x2d7
fffff382`384def90 fffff807`8003048e     : 00000000`00001000 fffff382`384df850 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x1b1
fffff382`384df670 fffff807`8002bb26     : 00000000`00000000 00000000`00000000 0000001d`29c2b7f9 00000000`00000000 : nt!KiExceptionDispatch+0x10e
fffff382`384df850 fffff807`7fe325e8     : fffff780`00000008 fffff780`00000350 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x426
fffff382`384df9e0 fffff807`7fe2fdd4     : 00000000`00000000 ffffa780`1a580440 ffff9701`9b9ae080 00000000`00000488 : nt!PpmIdlePrepare+0x158
fffff382`384dfc40 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PoIdle+0x414

SYMBOL_NAME:  nt!_report_gsfailure+25

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.1335

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  25

FAILURE_BUCKET_ID:  0xF7_MISSING_GSFRAME_nt!_report_gsfailure

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {82d2c1b5-b0cb-60a5-9a5d-78c8c4284f84}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | 效能與系統故障

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

0 則留言 沒有留言

34 個回答

排序依據: 最新
  1. 温弘隆 13,220 信譽點數 志願仲裁者
    2023-01-09T10:15:04+00:00

    感謝回復,

    該文件顯示可能和硬盤有關。
    根據描述,目前已經嘗試了上述所有回復中的方法。仍然沒有找到問題。
    仍然顯示多種錯誤。

    建議備份一下重要文件,然後全新安裝繫統。 完成後不安裝任何程序,手動更新bios和所有的驅動。 完成後只使用內置的Edge等應用。 1-2天內,看下是否還會藍屏。 全新安裝的繫統,通常在繫統上是完好的。也沒有安裝其他應用導致異常。驅動也更新過。 若是仍然會藍屏,建議考慮硬件/驅動等問題。

    關於全新安裝繫統,
    1、制作U盤安裝介質:
    https://answers.microsoft.com/zh-hans/windows/f...
    2、使用U盤全新安裝繫統,
    https://answers.microsoft.com/zh-hans/windows/f...

    若是48小時內沒有新的回復,我將無法再收到回復提醒。
    註意!請務必遮擋個人信息(電子郵件/電話/姓名等)。(若是沒有,請忽略)

    先試試!

    cmd<系統管理員身分執行

    chkdsk /f/r

    無法執行 Chkdsk,因為磁碟區正由其他處理程序使用中。

    是否要將此磁碟區排程在下次系統重新啟動時

    進行檢查? (Y/N) Y

    此回答有幫助嗎?

    0 則留言 沒有留言
  2. Pondsi 353.9K 信譽點數
    2023-01-09T07:30:51+00:00

    感謝回復,

    該文件顯示可能和硬盤有關。

    根據描述,目前已經嘗試了上述所有回復中的方法。仍然沒有找到問題。

    仍然顯示多種錯誤。

    建議備份一下重要文件,然後全新安裝繫統。

    完成後不安裝任何程序,手動更新bios和所有的驅動。

    完成後只使用內置的Edge等應用。

    1-2天內,看下是否還會藍屏。

    全新安裝的繫統,通常在繫統上是完好的。也沒有安裝其他應用導致異常。驅動也更新過。

    若是仍然會藍屏,建議考慮硬件/驅動等問題。


    關於全新安裝繫統,

    1、制作U盤安裝介質:

    https://answers.microsoft.com/zh-hans/windows/f...

    2、使用U盤全新安裝繫統,

    https://answers.microsoft.com/zh-hans/windows/f...

    若是48小時內沒有新的回復,我將無法再收到回復提醒。

    註意!請務必遮擋個人信息(電子郵件/電話/姓名等)。(若是沒有,請忽略)

    此回答有幫助嗎?

    0 則留言 沒有留言
  3. 匿名
    2023-01-09T07:19:37+00:00

    顯卡驅動已看到您說的,更新到最新但仍會有藍屏狀況出現

    開機時經常會遇到藍屏

    以下為近期DMP檔案,發生時間截點不同,若有不同問題請告訴我,希望可以知道如何解決.... https://drive.google.com/file/d/1avrPyWrmwlNiCstCIDOSdpZL-jIPUnA8/view?usp=sharing

    此回答有幫助嗎?

    0 則留言 沒有留言
  4. 温弘隆 13,220 信譽點數 志願仲裁者
    2023-01-09T06:35:05+00:00

    因為之前嘗試過重設電腦了,所以暫時不考慮繼續重設。

    另外硬碟健康度之前下載軟體來檢測,顯示是98%

    還有,在控制台以及NV控制面板看到的顯卡驅動版本不同,想請問是需要DDU重新安裝嗎?或者這是正常現象?分別是527.56和512.78

    影像

    影像

    顯卡驅動新的沒有試過嗎?

    NVIDIA Studio Driver - WHQL

    驅動程式版本: 528.02 - 發佈日期: 2023-1-5

    GeForce Game Ready Driver - WHQL 驅動程式版本: 528.02 - 發佈日期: 2023-1-5

    此回答有幫助嗎?

    0 則留言 沒有留言
  5. 匿名
    2023-01-09T04:11:47+00:00

    目前已讓win11跳過更新AMD驅動,但您給的連結無法使用

    以下為最後遇到的代碼

    Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    Loading Dump File [C:\Windows\Minidump\010923-11000-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*
    Symbol search path is: srv*
    Executable search path is: 
    Windows 10 Kernel Version 22621 MP (16 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0xfffff802`60200000 PsLoadedModuleList = 0xfffff802`60e12fc0
    Debug session time: Mon Jan  9 12:01:34.332 2023 (UTC + 8:00)
    System Uptime: 0 days 0:00:29.155
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    ......
    For analysis of this file, run !analyze -v
    nt!KeBugCheckEx:
    fffff802`60628700 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa887`fd6a6520=000000000000001e
    14: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common BugCheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff80262eea391, The address that the exception occurred at
    Arg3: ffffc082f36d26a0, Parameter 0 of the exception
    Arg4: fffff802604e1df0, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: ExceptionRecord                               ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: ContextRecord                                 ***
    ***                                                                   ***
    *************************************************************************
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 3421
    
        Key  : Analysis.DebugAnalysisManager
        Value: Create
    
        Key  : Analysis.Elapsed.mSec
        Value: 11067
    
        Key  : Analysis.IO.Other.Mb
        Value: 4
    
        Key  : Analysis.IO.Read.Mb
        Value: 0
    
        Key  : Analysis.IO.Write.Mb
        Value: 7
    
        Key  : Analysis.Init.CPU.mSec
        Value: 249
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 37679
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 106
    
        Key  : Bugcheck.Code.DumpHeader
        Value: 0x1e
    
        Key  : Bugcheck.Code.Register
        Value: 0x1e
    
        Key  : Dump.Attributes.AsUlong
        Value: 1008
    
        Key  : Dump.Attributes.DiagDataWrittenToHeader
        Value: 1
    
        Key  : Dump.Attributes.ErrorCode
        Value: 0
    
        Key  : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
    
        Key  : Dump.Attributes.LastLine
        Value: Dump completed successfully.
    
        Key  : Dump.Attributes.ProgressPercentage
        Value: 0
    
    FILE_IN_CAB:  010923-11000-01.dmp
    
    DUMP_FILE_ATTRIBUTES: 0x1008
      Kernel Generated Triage Dump
    
    BUGCHECK_CODE:  1e
    
    BUGCHECK_P1: ffffffffc000001d
    
    BUGCHECK_P2: fffff80262eea391
    
    BUGCHECK_P3: ffffc082f36d26a0
    
    BUGCHECK_P4: fffff802604e1df0
    
    EXCEPTION_PARAMETER1:  ffffc082f36d26a0
    
    EXCEPTION_PARAMETER2:  fffff802604e1df0
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    BLACKBOXWINLOGON: 1
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  SearchIndexer.
    
    TRAP_FRAME:  ffffa887fd6a73d9 -- (.trap 0xffffa887fd6a73d9)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=0000000000000000 rsp=f0ffffa887fd6a74 rbp=a0ffff80050e4da1
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz na pe nc
    00000000`00000000 ??              ???
    Resetting default scope
    
    IP_IN_FREE_BLOCK: 0
    
    FAILED_INSTRUCTION_ADDRESS: 
    Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb+31
    fffff802`62eea391 f0a807          lock test al,7
    
    STACK_TEXT:  
    ffffa887`fd6a6518 fffff802`6041055b     : 00000000`0000001e ffffffff`c000001d fffff802`62eea391 ffffc082`f36d26a0 : nt!KeBugCheckEx
    ffffa887`fd6a6520 fffff802`6063defc     : ffff8005`00000000 00000000`00000002 ffffa887`fd6a73d9 00000000`00000000 : nt!KiDispatchException+0x7eb
    ffffa887`fd6a6c00 fffff802`6063742d     : fffff802`60200000 ffff8005`1a5d09b0 ffff8005`06402140 00000000`00000000 : nt!KiExceptionDispatch+0x13c
    ffffa887`fd6a6de0 fffff802`62eea391     : ffff8005`1b6c45a0 00000000`00000000 ffff8005`00000000 fffff802`62eea2dd : nt!KiInvalidOpcodeFault+0x32d
    ffffa887`fd6a6f70 ffff8005`1b6c45a0     : 00000000`00000000 ffff8005`00000000 fffff802`62eea2dd ffffa887`fd6a74d0 : Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb+0x31
    ffffa887`fd6a6f78 00000000`00000000     : ffff8005`00000000 fffff802`62eea2dd ffffa887`fd6a74d0 00300033`00490024 : 0xffff8005`1b6c45a0
    
    SYMBOL_NAME:  Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb+31
    
    MODULE_NAME: Ntfs
    
    IMAGE_NAME:  Ntfs.sys
    
    IMAGE_VERSION:  10.0.22621.1028
    
    STACK_COMMAND:  .cxr; .ecxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  31
    
    FAILURE_BUCKET_ID:  0x1E_C000001D_BAD_IP_Ntfs!NtfsUpdateFileTimestampsFromNonpagedFcb
    
    OSPLATFORM_TYPE:  x64
    
    OSNAME:  Windows 10
    
    FAILURE_ID_HASH:  {d80fde7b-0aa2-9cb4-fcd7-8888b5bec444}
    
    Followup:     MachineOwner
    ---------
    

    此回答有幫助嗎?

    0 則留言 沒有留言