阅读1013 返回首页    go 阿里云 go 技术社区[云栖]


电脑不断蓝屏,所有蓝屏的code都是IRQL

使用winDbg分析的结果都一样显示:

Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

并且这个错误每次都会由不同的程序触发

以下是完整的诊断:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092917-6703-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 14393 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.0.amd64fre.rs1_release.160715-1616
Machine Name:
Kernel base = 0xfffff800`6da06000 PsLoadedModuleList = 0xfffff800`6dd0b060
Debug session time: Fri Sep 29 22:57:06.154 2017 (UTC + 8:00)
System Uptime: 0 days 0:20:47.906
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
........
Cannot read PEB32 from WOW64 TEB32 00299000 - Win32 error 0n30
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {3, ff, 0, fffff8006db5951c}

Probably caused by : Unknown_Image ( PAGE_NOT_ZERO )

Followup: MachineOwner
---------

 *** Memory manager detected 34868 instance(s) of page corruption, target is likely to have memory corruption.

6: 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: 0000000000000003, memory referenced
Arg2: 00000000000000ff, 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: fffff8006db5951c, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 0000000000000003 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!KiPageFault+5c
fffff800`6db5951c 41f6420380      test    byte ptr [r10+3],80h

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  ComputerZ_CN.e

BAD_PAGES_DETECTED: 8834

LAST_CONTROL_TRANSFER:  from fffff8006db5b129 to fffff8006db4ff90

STACK_TEXT:  
ffffe400`ef8797a8 fffff800`6db5b129 : 00000000`0000000a 00000000`00000003 00000000`000000ff 00000000`00000000 : nt!KeBugCheckEx
ffffe400`ef8797b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69


STACK_COMMAND:  kb

SYMBOL_NAME:  PAGE_NOT_ZERO

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  PAGE_NOT_ZERO

Followup: MachineOwner
---------

 *** Memory manager detected 34868 instance(s) of page corruption, target is likely to have memory corruption.

怀疑过是否是内存原因,但是换了插槽依旧不行

怀疑过是否是独立显卡原因,拔掉显卡使用集显后依旧会蓝屏

怀疑过是否是散热原因,重新装了下CPU散热器,也重新涂抹了硅脂

目前的待机温度是40℃,内核温度是38℃ (室温30℃)

机箱散热没有问题,散热通道很完善,一共5个机箱风扇。

我现在有点怀疑是否是CPU内核温度过高引起的,因为当我试着开启两个大型单机游戏的时候,电脑直接蓝屏

希望看的懂windbg的人可以帮帮我,我快被整崩溃了,看个网页有时候都能蓝屏,今天一整天已经蓝屏15,6次了
————————————————————————————————————————————————————

更新

————————————————————————————————————————————————————

使用bluescreenview查出来,造成蓝屏的罪魁祸首是 ntoskrnl.exe ,但是ntoskrnl.exe导致蓝屏的原因有很多

我的蓝屏代码段: ntoskrnl.exe+149f90 , 在堆栈内地址:ntoskrnl.exe+155129

这个要怎么修复啊???我看不懂代码段代表的意义



最后更新:2017-09-30 08:03:35

  上一篇:go 笔记本随机蓝屏求助
  下一篇:go 我的电脑一直蓝屏重启