电脑经常蓝屏重启，请问如何解决？

      dmp文件如下： Microsoft (R) Windows Debugger Version 6.10.0003.233 X86 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Windows\Minidump\060821-7937-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff801`2b200000 PsLoadedModuleList = 0xfffff801`2be2a1b0 Debug session time: Tue Jun  8 16:06:18.227 2021 (GMT+8) System Uptime: 0 days 0:05:10.960 ********************************************************************* * 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 1000007F, {8, ffffda81d074de70, fffff003d24a1fe0, fffff8012b4c42cb}  ***** 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                                     *** ***                                                                   *** ************************************************************************* ********************************************************************* * 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+                                    * ********************************************************************* ********************************************************************* * 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+                                    * ********************************************************************* Probably caused by : hardware_ram ( PAGE_NOT_ZERO_VISTA )  Followup: MachineOwner ---------   *** Memory manager detected 73255 instance(s) of page corruption, target is likely to have memory corruption.      尊敬的Microsoft产品和服务客户，下午好！LingGao，很荣幸有机会为您提供帮助。关于“电脑蓝屏”的问题，当您遇到蓝屏问题时，需要上传扩展名为.dmp的蓝屏日志文件以供进行分析，您可以通过以下方式收集日志文件。启动开始菜单，输入“控制面板”，回车。将查看方式调整为“大图标”，选择“系统”>“高级系统设置”>“高级”>“启动和故障恢复”>“设置”>“写入调试信息”>选择“小内存转储(256KB)”，路径选择默认，确定并重启设备。再次蓝屏重启后，请您前往C:\Windows\Minidump提取扩展名为.dmp的日志文件，将日志文件上传至百度网盘或者其他的国内网盘，然后通过分享生成链接，将链接至此问题以供分析。
        您好，我在问题下面已经传输了dmp文件，请你抽空帮忙看看，
        您好，并没有看到您上传的日至文件，您复制的日至文件，无法为您具体分析的，需要麻烦您再分享一次日至文件MicrosoftAnswers本站欢迎您！此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        您好，这是我的百度云链接，里面包含了最近几次的dmp文件，感谢您的帮助链接：https://pan.baidu.com/s/1slSV20HFlQ8a6zf2iM6dbw提取码：7of6此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。