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

匿名

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

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

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

0 則留言

34 個回答

Pondsi 353.9K 信譽點數

2023-01-07T10:58:46+00:00

感謝回復，

若是有核顯，嘗試在裝置管理員中，禁用英偉達顯卡，看下是否恢復正常，以便判斷是否和英偉達顯卡有關。

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

註意！請務必遮擋個人信息（電子郵件/電話/姓名等）。（若是沒有，請忽略）
此回答有幫助嗎？

0 則留言沒有留言
匿名

2023-01-07T08:43:49+00:00

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

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

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

0 則留言沒有留言
Pondsi 353.9K 信譽點數

2023-01-06T15:45:20+00:00

感謝回復，

根據描述，之前檢查硬盤沒有問題。（除了壞點，也需要看下健康狀況）

目前已經嘗試了上述所有的步驟，仍然有藍屏。

建議打開繫統的設定，繫統，恢復，重設此電腦。

重設時可以選擇保留個人文件，安裝的應用仍然需要重新安裝。

若是仍然有該錯誤，

建議拔掉目前安裝繫統的硬盤，把繫統安裝到另一個硬盤，看下是否恢復正常。

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

註意！請務必遮擋個人信息（電子郵件/電話/姓名等）。（若是沒有，請忽略）
此回答有幫助嗎？

0 則留言沒有留言
匿名

2023-01-06T15:06:09+00:00

目前用了MediaCreationToolW11後升級成22H2了...

升級完後bios還要再次重置嗎?

另外更新之後正在進入桌面時，遇到藍屏，以下是代碼

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\010623-12031-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 = 0xfffff80756000000 PsLoadedModuleList = 0xfffff80756c12fc0 Debug session time: Fri Jan 6 22:53:00.089 2023 (UTC + 8:00) System Uptime: 0 days 0:02:12.404 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: fffff80756428700 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffa0ca97edc10=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: ffffffffc0000005, The exception code that was not handled Arg2: fffff80756ae416b, The address that the exception occurred at Arg3: 0000000000000001, Parameter 0 of the exception Arg4: 0000000000000038, 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: 2437 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 4801 Key : Analysis.IO.Other.Mb Value: 24 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 31 Key : Analysis.Init.CPU.mSec Value: 171 Key : Analysis.Init.Elapsed.mSec Value: 144658 Key : Analysis.Memory.CommitPeak.Mb Value: 101 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: 010623-12031-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump BUGCHECK_CODE: 1e BUGCHECK_P1: ffffffffc0000005 BUGCHECK_P2: fffff80756ae416b BUGCHECK_P3: 1 BUGCHECK_P4: 38 EXCEPTION_PARAMETER1: 0000000000000001 EXCEPTION_PARAMETER2: 0000000000000038 WRITE_ADDRESS: fffff80756d1c468: Unable to get MiVisibleState Unable to get NonPagedPoolStart Unable to get NonPagedPoolEnd Unable to get PagedPoolStart Unable to get PagedPoolEnd unable to get nt!MmSpecialPagesInUse 0000000000000038 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: Registry TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000) Unable to read trap frame at ffff800000000000 STACK_TEXT: fffffa0ca97edc08 fffff8075621055b : 000000000000001e ffffffffc0000005 fffff80756ae416b 0000000000000001 : nt!KeBugCheckEx fffffa0ca97edc10 fffff8075643defc : 0000000000001000 ffffd6851e3e2040 ffff800000000000 ffffd6851e3e2780 : nt!KiDispatchException+0x7eb fffffa0ca97ee2f0 fffff8075643940e : 00000000ffffffff 0000000000000000 ffffc00c50729640 0000000000000000 : nt!KiExceptionDispatch+0x13c fffffa0ca97ee4d0 fffff80756ae416b : fff80756ae42c1ff 0000000000000000 0000000000000000 0000000000000000 : nt!KiPageFault+0x44e fffffa0ca97ee668 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 ffffffff`00000000 : nt!CmpLockKcbShared+0x3b SYMBOL_NAME: nt!CmpLockKcbShared+3b MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.963 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 3b FAILURE_BUCKET_ID: AV_W_nt!CmpLockKcbShared OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f9b0ec14-acb6-b541-a6eb-81fbd40b8c4c} Followup: MachineOwner ---------
此回答有幫助嗎？

0 則留言沒有留言
Pondsi 353.9K 信譽點數

2023-01-06T11:20:33+00:00

感謝回復，

是的，把bios的設定重置為默認。

沒有看到硬件錯誤，大多是軟件或驅動等問題。

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

註意！請務必遮擋個人信息（電子郵件/電話/姓名等）。（若是沒有，請忽略）
此回答有幫助嗎？

0 則留言沒有留言