问题:最近电脑总是自动重启,一天好几次,并且电脑里存在流氓软件,我找不到母体在哪,怀疑跟flash有关,删了一些垃圾文件不知道有没有误删的,下面是我找到的日志和最近的dmp文件,请帮我看看是什么原因,应该怎么处理流氓软件系统日志:dmp文件:Microsoft (R) Windows Debugger Version 6.12.0002.633 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\101622-9140-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol 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.exeWindows 7 Kernel Version 19041 MP (8 procs) Free x64Product: WinNt, suite: Terminal<10> SingleUserTS PersonalMachine Name:Kernel base = 0xfffff800`15800000 PsLoadedModuleList = 0xfffff800`1642a270Debug session time: Sun Oct 16 19:42:04.117 2022 (UTC + 8:00)System Uptime: 0 days 2:00:44.932********************************************************************** 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.exeLoading Kernel Symbols........................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list...................********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 3B, {c0000005, fffff80013bdc335, ffffb58653de6940, 0}*** WARNING: Unable to verify timestamp for mssmbios.sys*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sysUnable to load image FLTMGR.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for FLTMGR.SYS*** ERROR: Module load completed but symbols could not be loaded for FLTMGR.SYS***** 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 112689 instance(s) of page corruption, target is likely to have memory corruption.您好,A&K,前来提供帮助。请将dump文件上传到允许匿名下载的网盘里然后将链接分享过来,这边帮您分析一下,谢谢。[Thefollowingisnotpartofthereply以下不是内容]我不是或客服工作人员,可能因为学业及个人事务无法及时,但我会尽快。IamnotaMicrosoftemployee.Imaynotreplyintimeduetoacademic,butwillreplyassoonaspossible.
您好,A&K,前来提供帮助。请将dump文件上传到允许匿名下载的网盘里然后将链接分享过来,这边帮您分析一下,谢谢。[Thefollowingisnotpartofthereply以下不是内容]我不是或客服工作人员,可能因为学业及个人事务无法及时,但我会尽快。IamnotaMicrosoftemployee.Imaynotreplyintimeduetoacademic,butwillreplyassoonaspossible.
您好,A&K,前来提供帮助。请将dump文件上传到允许匿名下载的网盘里然后将链接分享过来,这边帮您分析一下,谢谢。您好,感谢您前来帮助,这是最近几次dump文件的链接https://wormhole.app/YWxmY#jJL5XCz7GO3OkmkwmraR_g

点赞(83) 打赏

评论列表 共有 0 条评论

暂无评论

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部