半个小时蓝屏5次     Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.     Loading Dump File [C:\Windows\Minidump\062424-11953-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 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff800`7ba00000 PsLoadedModuleList = 0xfffff800`7c62a360 Debug session time: Mon Jun 24 17:33:06.850 2024 (UTC + 8:00) System Uptime: 0 days 0:29:10.690 ********************************************************************* * 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 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** 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 50, {fffffc007bfe0373, 10, fffffc007bfe0373, 2}   ***** 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 141623 instance(s) of page corruption, target is likely to have memory corruption.   7: kd> !analyze -v ******************************************************************************* *                                                                             * *                        Bugcheck Analysis                                    * *                                                                             * *******************************************************************************   PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced.  This cannot be protected by try-except, it must be protected by a Probe.  Typically the address is just plain bad or it is pointing at freed memory. Arguments: Arg1: fffffc007bfe0373, memory referenced. Arg2: 0000000000000010, value 0 = read operation, 1 = write operation. Arg3: fffffc007bfe0373, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved)   Debugging Details: ------------------   ***** 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                                     *** ***                                                                   *** *************************************************************************   ADDITIONAL_DEBUG_TEXT:   Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.   FAULTING_MODULE: fffff8007ba00000 nt   DEBUG_FLR_IMAGE_TIMESTAMP:  0   WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd  fffffc007bfe0373    FAULTING_IP:  +3532336432616362 fffffc00`7bfe0373 ??              ???   MM_INTERNAL_CODE:  2   CUSTOMER_CRASH_COUNT:  1   DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT   BUGCHECK_STR:  0x50   CURRENT_IRQL:  0   BAD_PAGES_DETECTED: 22937   LAST_CONTROL_TRANSFER:  from fffff8007be397ed to fffff8007bdfdb50   STACK_TEXT:   ffffe08f`02e6f068 fffff800`7be397ed : 00000000`00000050 fffffc00`7bfe0373 00000000`00000010 ffffe08f`02e6f310 : nt+0x3fdb50 ffffe08f`02e6f070 00000000`00000050 : fffffc00`7bfe0373 00000000`00000010 ffffe08f`02e6f310 00000000`00000002 : nt+0x4397ed ffffe08f`02e6f078 fffffc00`7bfe0373 : 00000000`00000010 ffffe08f`02e6f310 00000000`00000002 00000000`00000001 : 0x50 ffffe08f`02e6f080 00000000`00000010 : ffffe08f`02e6f310 00000000`00000002 00000000`00000001 00000000`00000000 : 0xfffffc00`7bfe0373 ffffe08f`02e6f088 ffffe08f`02e6f310 : 00000000`00000002 00000000`00000001 00000000`00000000 00000000`00000000 : 0x10 ffffe08f`02e6f090 00000000`00000002 : 00000000`00000001 00000000`00000000 00000000`00000000 00000003`00000000 : 0xffffe08f`02e6f310 ffffe08f`02e6f098 00000000`00000001 : 00000000`00000000 00000000`00000000 00000003`00000000 00000000`00000000 : 0x2 ffffe08f`02e6f0a0 00000000`00000000 : 00000000`00000000 00000003`00000000 00000000`00000000 00000000`00000000 : 0x1     STACK_COMMAND:  kb   SYMBOL_NAME:  PAGE_NOT_ZERO   FOLLOWUP_NAME:  MachineOwner   MODULE_NAME: hardware   IMAGE_NAME:  hardware_ram   BUCKET_ID:  WRONG_SYMBOLS   Followup: MachineOwner ---------    *** Memory manager detected 141623 instance(s) of page corruption, target is likely to have memory corruption.