【打脸】电脑蓝屏，请大神门帮忙看一下代码分析分析-万达拆迁队

今天突然频繁蓝屏，多发在开机系统加载完毕后，有时能坚持一会，我自行判断是新买的光威内存问题，目前发帖拔掉一根暂时没有死机，请大神们给分析分析是不是内存的问题，如果是内存的问题，我是换两条还是单独换一条就行了

---------------------------
ps.刚下载蛊王360扫描修复了一圈再插上目前暂时不蓝屏了

Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\xxx\Desktop\082722-6640-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff802`04800000 PsLoadedModuleList = 0xfffff802`0542a250
Debug session time: Sat Aug 27 16:53:38.787 2022 (GMT+8)
System Uptime: 0 days 7:36:01.598
*********************************************************************
* 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
..............
Cannot read PEB32 from WOW64 TEB32 0000d7ab - Win32 error 0n30
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff80204a86660, ffff8a86983318b8, ffff8a86983310f0}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
Unable to load image afd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 55211 instance(s) of page corruption, target is likely to have memory corruption.

热议
2楼 心上人 昨天20:26

最后一行：Memory manager detected 55211 instance(s) of page corruption, target is likely to have memory corruption.

3楼 三不 昨天20:26

说来真巧，我前几天也是买了光威8G的，己经蓝屏两次了，之前从未蓝屏过。本着支持国产买的。。

/**
* 和平视窗计划只是个美丽的童话，竞赛代替不了战争，就像葡萄酒代替不了鲜血 ------MJJ友情价出t66y<1024>邀请码

4楼 DaoChen 昨天20:31

用的玖合的单条16G，还行

应该是你内存的问题了，内存最好是两根同品牌同频率

6楼 万达拆迁队 昨天20:54

说来真巧，我前几天也是买了光威8G的，己经蓝屏两次了，之前从未蓝屏过。本着支持国产买的。。

我之前用着都没事，刚才突然就蓝屏了，重启五次蓝屏4次，拆了一条刚下载蛊王360扫了扫修复了修复目前暂时正常了

7楼 万达拆迁队 昨天20:55

应该是你内存的问题了，内存最好是两根同品牌同频率

就是两根同品牌的，一起买的光威单条8G 1600的

8楼 colla 昨天21:05

就是两根同品牌的，一起买的光威单条8G 1600的

那就换货吧

9楼 wangjy 昨天21:14

可以发一下dump看看

10楼 万达拆迁队 昨天23:10

可以发一下dump看看

文中贴的就是dump，目前用360修修补补装上内存暂时好了，不知道还会不会蓝

12楼 Senly 9小时前

不用看，一般蓝屏和内存有关

13楼 jiajieit 1分钟前

蛊王360 形容得很贴切

申明：本文内容由网友收集分享，仅供学习参考使用。如文中内容侵犯到您的利益，请在文章下方留言，本站会第一时间进行处理。