magicbook吧 关注:6,364贴子:58,372
  • 15回复贴,共1

magicbook14 2023款蓝屏的可能解决办法

只看楼主收藏回复

荣耀俱乐部不给发帖,出现蓝屏字样就不给发帖,贴吧写个帖子留给有需要的人。
蓝屏原因很多,不一一列举,现在说说两个容易漏掉的蓝屏原因:
1.此款机器只有一个A口,用集线器可能会导致蓝屏
2.荣耀电脑管家尿性,一直是管家驱动和官网驱动不同步,重装电脑请直接把官网十六七个驱动下载手动安装。
如果出现蓝屏,不是硬件原因,排除掉其他原因后,很可能是上面中的一个。
多说一句荣耀电脑管家,如果不是特别需要,不要安装。省的哪天微软更新,管家服务被禁用,管家和微软更新冲突这个雷从2022年好像就出现过了。本来就bug一堆的win11,加上荣耀OS Turbo调教、再加上微软更新就冲突的荣耀电脑管家,槽点满满。


IP属地:江苏1楼2025-11-12 18:55回复
    我买的机器重装系统后就没有蓝屏过了,同时我把系统更新也关了。以前原装系统的时候有时候充电会莫名其妙发热,重装后都好了


    IP属地:浙江来自Android客户端2楼2025-11-13 13:34
    回复
      2026-03-10 13:26:07
      广告
      不感兴趣
      开通SVIP免广告
      不到半个月又蓝屏了,process name 是msedge,edge浏览器使用时蓝屏。不知道啥原因,网上说的硬件加速已经关掉还是蓝屏,现在Choose ANgle graphics backend 设置为D3D9, 用几天试试。


      IP属地:江苏4楼2025-11-25 19:42
      回复
        ************* Preparing the environment for Debugger Extensions Gallery repositories **************
        ExtensionRepository : Implicit
        UseExperimentalFeatureForNugetShare : true
        AllowNugetExeUpdate : true
        NonInteractiveNuget : true
        AllowNugetMSCredentialProviderInstall : true
        AllowParallelInitializationOfLocalRepositories : true
        EnableRedirectToChakraJsProvider : false
        -- Configuring repositories
        ----> Repository : LocalInstalled, Enabled: true
        ----> Repository : UserExtensions, Enabled: true
        >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
        ************* Waiting for Debugger Extensions Gallery to Initialize **************
        >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds
        ----> Repository : UserExtensions, Enabled: true, Packages count: 0
        ----> Repository : LocalInstalled, Enabled: true, Packages count: 46
        Microsoft (R) Windows Debugger Version 10.0.29457.1000 AMD64
        Copyright (c) Microsoft Corporation. All rights reserved.
        Loading Dump File [C:\Windows\Minidump\112525-6437-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
        Kernel base = 0xfffff804`33800000 PsLoadedModuleList = 0xfffff804`344134f0
        Debug session time: Tue Nov 25 15:53:34.336 2025 (UTC + 8:00)
        System Uptime: 3 days 2:49:34.085
        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
        PEB is paged out (Peb.Ldr = 00000000`002fe018). Type ".hh dbgerr001" for details
        Loading unloaded module list
        .....................................
        For analysis of this file, run !analyze -v
        nt!KeBugCheckEx:
        fffff804`33c16000 48894c2408 mov qword ptr [rsp+8],rcx ss:fffffe80`39b52b50=000000000000000a
        3: kd> !analyze -v
        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
        PEB is paged out (Peb.Ldr = 00000000`002fe018). Type ".hh dbgerr001" for details
        Loading unloaded module list
        .....................................
        *******************************************************************************
        * *
        * Bugcheck Analysis *
        * *
        *******************************************************************************
        IRQL_NOT_LESS_OR_EQUAL (a)
        An attempt was made to access a pageable (or completely invalid) address at an
        interrupt request level (IRQL) that is too high. This is usually
        caused by drivers using improper addresses.
        If a kernel debugger is available get the stack backtrace.
        Arguments:
        Arg1: 0000000000000852, memory referenced
        Arg2: 00000000000000ff, IRQL
        Arg3: 0000000000000058, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
        Arg4: fffff80433c1a082, address which referenced memory
        Debugging Details:
        ------------------
        KEY_VALUES_STRING: 1
        Key : Analysis.CPU.mSec
        Value: 531
        Key : Analysis.Elapsed.mSec
        Value: 5729
        Key : Analysis.IO.Other.Mb
        Value: 0
        Key : Analysis.IO.Read.Mb
        Value: 1
        Key : Analysis.IO.Write.Mb
        Value: 0
        Key : Analysis.Init.CPU.mSec
        Value: 484
        Key : Analysis.Init.Elapsed.mSec
        Value: 83196
        Key : Analysis.Memory.CommitPeak.Mb
        Value: 107
        Key : Analysis.Version.DbgEng
        Value: 10.0.29457.1000
        Key : Analysis.Version.Description
        Value: 10.2506.23.01 amd64fre
        Key : Analysis.Version.Ext
        Value: 1.2506.23.1
        Key : Bugcheck.Code.LegacyAPI
        Value: 0xa
        Key : Bugcheck.Code.TargetModel
        Value: 0xa
        Key : Dump.Attributes.AsUlong
        Value: 0x1008
        Key : Dump.Attributes.DiagDataWrittenToHeader
        Value: 1
        Key : Dump.Attributes.ErrorCode
        Value: 0x0
        Key : Dump.Attributes.KernelGeneratedTriageDump
        Value: 1
        Key : Dump.Attributes.LastLine
        Value: Dump completed successfully.
        Key : Dump.Attributes.ProgressPercentage
        Value: 0
        Key : Failure.Bucket
        Value: AV_nt!KiIsrLinkage
        Key : Failure.Exception.IP.Address
        Value: 0xfffff80433c1a082
        Key : Failure.Exception.IP.Module
        Value: nt
        Key : Failure.Exception.IP.Offset
        Value: 0x41a082
        Key : Failure.Hash
        Value: {588a5d06-357f-6f49-df1f-3968d1b4c987}
        Key : WER.System.BIOSRevision
        Value: 1.12.0.0
        BUGCHECK_CODE: a
        BUGCHECK_P1: 852
        BUGCHECK_P2: ff
        BUGCHECK_P3: 58
        BUGCHECK_P4: fffff80433c1a082
        FILE_IN_CAB: 112525-6437-01.dmp
        DUMP_FILE_ATTRIBUTES: 0x1008
        Kernel Generated Triage Dump
        FAULTING_THREAD: ffffe003c3147080
        READ_ADDRESS: fffff8043451d470: 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
        0000000000000852
        BLACKBOXBSD: 1 (!blackboxbsd)
        BLACKBOXNTFS: 1 (!blackboxntfs)
        BLACKBOXPNP: 1 (!blackboxpnp)
        BLACKBOXWINLOGON: 1 (!blackboxwinlogon)
        CUSTOMER_CRASH_COUNT: 1
        PROCESS_NAME: msedge.exe
        STACK_TEXT:
        fffffe80`39b52b48 fffff804`33c2bf29 : 00000000`0000000a 00000000`00000852 00000000`000000ff 00000000`00000058 : nt!KeBugCheckEx
        fffffe80`39b52b50 fffff804`33c27389 : 00000000`00000000 fffff804`6a5810ed fffffe80`39b52cf0 ffffa30d`0ae117ab : nt!KiBugCheckDispatch+0x69
        fffffe80`39b52c90 fffff804`33c1a082 : ffffe003`c3147080 ffffe003`bab71080 fffffe80`3b8afa38 00000000`00000000 : nt!KiPageFault+0x489
        fffffe80`39b52e20 00007fff`d4597cfa : aaaaaaaa`aaaaaaaa aaaaaaaa`aaaaaaaa 00000000`00000000 00000000`00000000 : nt!KiIsrLinkage+0xe1
        00000000`00bfdca0 aaaaaaaa`aaaaaaaa : aaaaaaaa`aaaaaaaa 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`d4597cfa
        00000000`00bfdca8 aaaaaaaa`aaaaaaaa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xaaaaaaaa`aaaaaaaa
        00000000`00bfdcb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xaaaaaaaa`aaaaaaaa
        SYMBOL_NAME: nt!KiIsrLinkage+e1
        MODULE_NAME: nt
        IMAGE_NAME: ntkrnlmp.exe
        IMAGE_VERSION: 10.0.22621.4169
        STACK_COMMAND: .process /r /p 0xffffe003ba3280c0; .thread 0xffffe003c3147080 ; kb
        BUCKET_ID_FUNC_OFFSET: e1
        FAILURE_BUCKET_ID: AV_nt!KiIsrLinkage
        OSPLATFORM_TYPE: x64
        OSNAME: Windows 10
        FAILURE_ID_HASH: {588a5d06-357f-6f49-df1f-3968d1b4c987}
        Followup: MachineOwner
        ---------


        IP属地:江苏5楼2025-11-26 11:40
        回复
          win11 22H2装后发现拖动图片变白块bug,还未修复


          IP属地:江苏6楼2025-11-28 23:13
          回复
            啥蓝屏代码?有截图吗?


            IP属地:湖南7楼2025-11-29 13:38
            回复
              win11 25H2 , 长时间不关机变卡顿,桌面移动文件都是一卡一卡,复制粘贴经常失灵。


              IP属地:江苏8楼2025-12-25 17:21
              收起回复
                现在装win11 ltsc ,删WD禁止更新,手动安装15个驱动,使用一段时间看看。


                IP属地:江苏9楼2025-12-30 13:53
                收起回复