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. 匿名
    2023-01-06T05:03:35+00:00

    https://drive.google.com/file/d/112Q_A5rzc7v41rb1nb_SDZV2TLeoIsT3/view?usp=sharing

    昨天更新完驅動後都沒有遇到問題,今天開機藍屏一次,開機後再次藍屏一次。

    這裡附上DMP檔

    另外,我發現DMP的檔案分析裡面寫到 OS版本是WIN10 可是我的作業系統是WIN11。請問這樣是有問題的嗎?有的話如何處理

    此回答有幫助嗎?

    0 則留言 沒有留言
  2. 匿名
    2023-01-06T05:04:05+00:00

    意思是要更新到最新的版本嗎?

    此回答有幫助嗎?

    0 則留言 沒有留言
  3. 已刪除

    由於違反我們的規範,因此已刪除此答案。 在採取動作之前,會透過自動化偵測手動報告或識別答案。 如需詳細資訊,請參閱我們的管理辦法。


    已關閉註解。 深入了解

  4. Pondsi 353.9K 信譽點數
    2023-01-06T07:28:03+00:00

    感謝回復,

    dmp文件中顯示Windows10沒有問題。

    仍然有看到amd處理器相關的異常。

    確保執行了幹凈啟動,沒有認為非Microsoft的進程。

    根據描述,硬盤和內存沒有問題,更新了bios和所有的驅動。(驅動建議優先到asus下載,不是到英偉達或amd的官網下載)

    可以嘗試重置一下bios。

    然後參考以下鏈接,使用MediaCreationToolW11升級/修復繫統,

    【這不是重裝繫統:通常默認選項將保留個人文件、設置、應用等】

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

    若是有重要文件,建議及時備份,防止意外。

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

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

    此回答有幫助嗎?

    0 則留言 沒有留言
  5. 匿名
    2023-01-06T09:42:23+00:00

    處理器相關的異常是指不確定是軟體或硬體嗎?

    關於bios的重置是指進入bios把設定改為默認嗎?

    此回答有幫助嗎?

    0 則留言 沒有留言