电脑蓝屏的代码,有无大神帮忙看看

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.016 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 29

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


Loading Dump File [C:\Windows\Minidump\090424-11406-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 19041 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`35600000 PsLoadedModuleList = 0xfffff805`3622a830
Debug session time: Wed Sep  4 22:52:22.993 2024 (UTC + 8:00)
System Uptime: 2 days 23:34:21.659
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...........
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000e1`c507b018).  Type ".hh dbgerr001" for details
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
1: kd> !analyze -v
06 ffffee06`264fe7b0 ffffffff`b8797400     0xffff800f`88417eb8
rax=0000000080040031 rbx=fffff8053a097000 rcx=0000000000000028
rdx=ffffb8814ccca180 rsi=ffffee06264ff610 rdi=b3b6cbee6c8b7237
rip=ffff800f88417eb8 rsp=ffffee06264fe7b0 rbp=ffffee06264fe8b0
 r8=0000000000000002  r9=ffff800f88402047 r10=ffff800f8840210f
r11=0000000000000000 r12=0000000080050031 r13=000000000000001e
r14=a39fbf681a08d52f r15=ffff800f8b038640
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00040246
ffff800f`88417eb8 0f22c0          mov     cr0,rax
*******************************************************************************
*                                                                             *
*                        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: ffffffffc0000096, The exception code that was not handled
Arg2: ffff800f88417eb8, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, 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: 2202

    Key  : Analysis.Elapsed.mSec
    Value: 3209

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x1E_C0000096_nt!KiDispatchException

    Key  : Failure.Hash
    Value: {505cfaff-0bdc-8a96-0650-5a81952f0ba1}


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000096

BUGCHECK_P2: ffff800f88417eb8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

FILE_IN_CAB:  090424-11406-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  csrss.exe

STACK_TEXT:  
ffffb881`4cd238e8 fffff805`35a6e7d5     : 00000000`0000001e ffffffff`c0000096 ffff800f`88417eb8 00000000`00000000 : nt!KeBugCheckEx
ffffb881`4cd238f0 fffff805`359ff402     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x164d05
ffffb881`4cd23fb0 fffff805`359ff3d0     : fffff805`35a12be5 00000000`0000000c ffff800f`5f533a28 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffee06`264fe438 fffff805`35a12be5     : 00000000`0000000c ffff800f`5f533a28 00000000`00000000 fffff805`39e95000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffee06`264fe440 fffff805`35a0dfef     : ffff800f`00000000 00000000`0000000e ffffee06`264fe730 ffffee06`00000000 : nt!KiExceptionDispatch+0x125
ffffee06`264fe620 ffff800f`88417eb8     : ffffffff`b8797400 00000000`00000001 ffff800f`88402047 ffffffff`b8797400 : nt!KiGeneralProtectionFault+0x32f
ffffee06`264fe7b0 ffffffff`b8797400     : 00000000`00000001 ffff800f`88402047 ffffffff`b8797400 ffffee06`00000002 : 0xffff800f`88417eb8
ffffee06`264fe7b8 00000000`00000001     : ffff800f`88402047 ffffffff`b8797400 ffffee06`00000002 fffff781`dee6e68b : 0xffffffff`b8797400
ffffee06`264fe7c0 ffff800f`88402047     : ffffffff`b8797400 ffffee06`00000002 fffff781`dee6e68b 00000000`00000000 : 0x1
ffffee06`264fe7c8 ffffffff`b8797400     : ffffee06`00000002 fffff781`dee6e68b 00000000`00000000 ffff800f`66325d40 : 0xffff800f`88402047
ffffee06`264fe7d0 ffffee06`00000002     : fffff781`dee6e68b 00000000`00000000 ffff800f`66325d40 00007ff0`00000000 : 0xffffffff`b8797400
ffffee06`264fe7d8 fffff781`dee6e68b     : 00000000`00000000 ffff800f`66325d40 00007ff0`00000000 ffffca07`bf361c68 : 0xffffee06`00000002
ffffee06`264fe7e0 00000000`00000000     : ffff800f`66325d40 00007ff0`00000000 ffffca07`bf361c68 ffff800f`88463e22 : 0xfffff781`dee6e68b


SYMBOL_NAME:  nt!KiDispatchException+164d05

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4780

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  164d05

FAILURE_BUCKET_ID:  0x1E_C0000096_nt!KiDispatchException

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {505cfaff-0bdc-8a96-0650-5a81952f0ba1}

Followup:     MachineOwner
---------

评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值