Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\100724-10937-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff802`0fc00000 PsLoadedModuleList = 0xfffff802`108134f0 Debug session time: Mon Oct 7 16:42:23.796 2024 (UTC + 8:00) System Uptime: 0 days 19:25:48.564 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ..................................... Loading User Symbols Loading unloaded module list ............................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {7fffffff0000, 2, 0, fffff8020fe81b39} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command 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: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : hardware_ram ( PAGE_NOT_ZERO ) Followup: MachineOwner --------- *** Memory manager detected 113166 instance(s) of page corruption, target is likely to have memory corruption.  

频繁出现蓝屏现象 求大神帮帮忙   14: kd> !analyze -v ******************************************************************************* * * * 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: fffffffffffffff8, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, 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: fffff8004981fded, address which referenced memory Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2468 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2565 Key : Analysis.Init.CPU.mSec Value: 484 Key : Analysis.Init.Elapsed.mSec Value: 51558 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Bugcheck.Code.DumpHeader Value: 0xa Key : Bugcheck.Code.Register Value: 0xa Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 092222-12531-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: a BUGCHECK_P1: fffffffffffffff8 BUGCHECK_P2: 2 BUGCHECK_P3: 0 BUGCHECK_P4: fffff8004981fded READ_ADDRESS: fffff8004a2fb390: 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 fffffffffffffff8 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System TRAP_FRAME: ffffdc853bb25710 -- (.trap 0xffffdc853bb25710)NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=0000000000000082 rbx=0000000000000000 rcx=ffffcc059af76040 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8004981fded rsp=ffffdc853bb258a0 rbp=0000000000000000 r8=0000000000000002 r9=0000000000000000 r10=0000000000000000 r11=ffffffffffffffff r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 ov up ei pl nz na pe cy nt!IopfCompleteRequest+0x9d: fffff800`4981fded c80f8f27 enter 8F0Fh,27h Resetting default scope MISALIGNED_IP: nt!IopfCompleteRequest+9d fffff800`4981fded c80f8f27 enter 8F0Fh,27h STACK_TEXT: ffffdc85`3bb255c8 fffff800`49a0af69 : 00000000`0000000a ffffffff`fffffff8 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffdc85`3bb255d0 fffff800`49a07269 : fffff800`499f5090 fffff800`49922d7a ffffcc05`91b49458 fffff800`4d3c778a : nt!KiBugCheckDispatch+0x69 ffffdc85`3bb25710 fffff800`4981fded : 00000008`6d2a0c92 00000000`00989680 00000008`6d09e544 fffff800`4981a53a : nt!KiPageFault+0x469 ffffdc85`3bb258a0 fffff800`4981fd14 : ffffcc05`00000000 fffff800`00000001 00000000`00000002 fffff800`a2224400 : nt!IopfCompleteRequest+0x9d ffffdc85`3bb25990 fffff800`8a2a430e : ffffcc05`9d4e79a8 ffffffff`fffeab5e 00000000`00000008 ffffdc85`3bb25a90 : nt!KeReleaseMutex+0x14 ffffdc85`3bb259c0 fffff800`8a2d527e : ffff2384`3aa441f8 00000000`00000000 00000000`00000000 ffffcc05`9d4e78b0 : ks!CKsPin::ReleaseProcessSync+0x1e ffffdc85`3bb259f0 fffff800`a22242f9 : ffffcc05`00000001 00000000`00000000 00000000`000154a2 00000000`00000000 : ks!KsPinReleaseProcessingMutex+0x2e ffffdc85`3bb25a20 fffff800`a222368a : ffffcc05`9d4e78b0 ffffcc05`96923dd0 00000000`00000000 fffff800`49852f57 : BthA2dp!CPcmPin::Pump+0x35d ffffdc85`3bb25ad0 fffff800`498995a3 : ffffcc05`9e7cdb20 00000000`00000000 00000000`00000000 fffff800`4d3bc5c0 : BthA2dp!CPcmPin::TimerWorker+0x2a ffffdc85`3bb25b00 fffff800`49852b65 : ffffcc05`9af76040 ffffcc05`9af76040 fffff800`49899510 00000000`00000000 : nt!IopProcessWorkItem+0x93 ffffdc85`3bb25b70 fffff800`49871d25 : ffffcc05`9af76040 00000000`00000080 ffffcc05`8a302080 00000000`00000000 : nt!ExpWorkerThread+0x105 ffffdc85`3bb25c10 fffff800`49a00628 : ffffe481`61f63180 ffffcc05`9af76040 fffff800`49871cd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 ffffdc85`3bb25c60 00000000`00000000 : ffffdc85`3bb26000 ffffdc85`3bb20000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28 SYMBOL_NAME: ks!CKsPin::ReleaseProcessSync+1e IMAGE_VERSION: 10.0.19041.630 STACK_COMMAND: .cxr; .ecxr ; kb MODULE_NAME: AuthenticAMD IMAGE_NAME: AuthenticAMD.sys FAILURE_BUCKET_ID: IP_MISALIGNED_AuthenticAMD.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {716d112a-8330-4bbb-160c-ec98297019d2} Followup: MachineOwner ---------