电脑无故蓝屏了

显示全部楼层 · 发表于 2014-4-17 23:39:12

上传了dump..求看的懂的帮忙分析一下谢谢

显示全部楼层 · 发表于 2014-4-17 23:48:18

你的WinDbug没设symbol File Path那个分析结果无法作为参考，打开winDbug，点File-symbol File Path在symbol Path对话框中输入SRV*c:\symbols*http://msdl.microsoft.com/download/symbols单击OK
设置好后再分析.dmp文件把结果贴上来。

显示全部楼层 · 发表于 2014-4-17 23:57:01

本帖最后由 via_affect 于 2014-4-18 00:08 编辑

棒棒小星星发表于 2014-4-17 23:48
你的WinDbug没设symbol File Path那个分析结果无法作为参考，打开winDbug，点File-symbol File Path在symbo ...

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

Loading Dump File [E:\041714-19890-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`03e14000 PsLoadedModuleList = 0xfffff800`040576d0
Debug session time: Thu Apr 17 22:32:21.196 2014 (UTC + 8:00)
System Uptime: 0 days 0:00:24.663
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                            *
*                      Bugcheck Analysis                                  *
*                                                                            *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffffffffffc, 0, fffff8800562ff39, 0}

Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys

Could not read faulting driver name
Probably caused by : aswSP.sys ( aswSP+2ff39 )

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

0: 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: fffffffffffffffc, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800562ff39, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800040c1100
fffffffffffffffc

FAULTING_IP:
aswSP+2ff39
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880087975f0 -- (.trap 0xfffff880087975f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800040c1010 rbx=0000000000000000 rcx=f8800565b0800000
rdx=fffff8800879775a rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800562ff39 rsp=fffff88008797780 rbp=fffffa8008ff85c0
r8=fffffffffffffffc  r9=fffffa8007b1356a r10=0000000000000074
r11=fffffa8007b1356a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0       nv up ei ng nz ac pe nc
aswSP+0x2ff39:
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8] ds:002a:ffffffff`fffffffc=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003f07bf0 to fffff80003e89bc0

STACK_TEXT:
fffff880`08797488 fffff800`03f07bf0 : 00000000`00000050 ffffffff`fffffffc 00000000`00000000 fffff880`087975f0 : nt!KeBugCheckEx
fffff880`08797490 fffff800`03e87cee : 00000000`00000000 ffffffff`fffffffc fffffa80`08642800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`087975f0 fffff880`0562ff39 : fffffa80`08e99200 00000000`00000000 00000000`00000000 fffff800`041629c5 : nt!KiPageFault+0x16e
fffff880`08797780 fffffa80`08e99200 : 00000000`00000000 00000000`00000000 fffff800`041629c5 fffff880`08797b00 : aswSP+0x2ff39
fffff880`08797788 00000000`00000000 : 00000000`00000000 fffff800`041629c5 fffff880`08797b00 fffffa80`00100001 : 0xfffffa80`08e99200

STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSP+2ff39
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  aswSP+2ff39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5328af5b

FAILURE_BUCKET_ID:  X64_0x50_aswSP+2ff39

BUCKET_ID:  X64_0x50_aswSP+2ff39

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

0: 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: fffffffffffffffc, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800562ff39, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name

READ_ADDRESS:  fffffffffffffffc

FAULTING_IP:
aswSP+2ff39
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880087975f0 -- (.trap 0xfffff880087975f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800040c1010 rbx=0000000000000000 rcx=f8800565b0800000
rdx=fffff8800879775a rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800562ff39 rsp=fffff88008797780 rbp=fffffa8008ff85c0
r8=fffffffffffffffc  r9=fffffa8007b1356a r10=0000000000000074
r11=fffffa8007b1356a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0       nv up ei ng nz ac pe nc
aswSP+0x2ff39:
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8] ds:002a:ffffffff`fffffffc=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003f07bf0 to fffff80003e89bc0

STACK_TEXT:
fffff880`08797488 fffff800`03f07bf0 : 00000000`00000050 ffffffff`fffffffc 00000000`00000000 fffff880`087975f0 : nt!KeBugCheckEx
fffff880`08797490 fffff800`03e87cee : 00000000`00000000 ffffffff`fffffffc fffffa80`08642800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`087975f0 fffff880`0562ff39 : fffffa80`08e99200 00000000`00000000 00000000`00000000 fffff800`041629c5 : nt!KiPageFault+0x16e
fffff880`08797780 fffffa80`08e99200 : 00000000`00000000 00000000`00000000 fffff800`041629c5 fffff880`08797b00 : aswSP+0x2ff39
fffff880`08797788 00000000`00000000 : 00000000`00000000 fffff800`041629c5 fffff880`08797b00 fffffa80`00100001 : 0xfffffa80`08e99200

STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSP+2ff39
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  aswSP+2ff39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5328af5b

FAILURE_BUCKET_ID:  X64_0x50_aswSP+2ff39

BUCKET_ID:  X64_0x50_aswSP+2ff39

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

0: 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: fffffffffffffffc, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8800562ff39, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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

Could not read faulting driver name

READ_ADDRESS:  fffffffffffffffc

FAULTING_IP:
aswSP+2ff39
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880087975f0 -- (.trap 0xfffff880087975f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff800040c1010 rbx=0000000000000000 rcx=f8800565b0800000
rdx=fffff8800879775a rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800562ff39 rsp=fffff88008797780 rbp=fffffa8008ff85c0
r8=fffffffffffffffc  r9=fffffa8007b1356a r10=0000000000000074
r11=fffffa8007b1356a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0       nv up ei ng nz ac pe nc
aswSP+0x2ff39:
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8] ds:002a:ffffffff`fffffffc=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003f07bf0 to fffff80003e89bc0

STACK_TEXT:
fffff880`08797488 fffff800`03f07bf0 : 00000000`00000050 ffffffff`fffffffc 00000000`00000000 fffff880`087975f0 : nt!KeBugCheckEx
fffff880`08797490 fffff800`03e87cee : 00000000`00000000 ffffffff`fffffffc fffffa80`08642800 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`087975f0 fffff880`0562ff39 : fffffa80`08e99200 00000000`00000000 00000000`00000000 fffff800`041629c5 : nt!KiPageFault+0x16e
fffff880`08797780 fffffa80`08e99200 : 00000000`00000000 00000000`00000000 fffff800`041629c5 fffff880`08797b00 : aswSP+0x2ff39
fffff880`08797788 00000000`00000000 : 00000000`00000000 fffff800`041629c5 fffff880`08797b00 fffffa80`00100001 : 0xfffffa80`08e99200

STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSP+2ff39
fffff880`0562ff39 410fb700       movzx eax,word ptr [r8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  aswSP+2ff39

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5328af5b

FAILURE_BUCKET_ID:  X64_0x50_aswSP+2ff39

BUCKET_ID:  X64_0x50_aswSP+2ff39

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

显示全部楼层 · 发表于 2014-4-18 00:09:16

最近有安装avast吗？

显示全部楼层 · 发表于 2014-4-18 00:12:12

本帖最后由 via_affect 于 2014-4-18 00:22 编辑

棒棒小星星发表于 2014-4-18 00:09
最近有安装avast吗？

有的，用了好几年了。一直用的免费版

显示全部楼层 · 发表于 2014-4-18 09:56:14

本帖最后由 100lj 于 2014-4-18 09:59 编辑

Probably caused by : aswSP.sys
AVAST与什么软件冲突了，可能驱动被拦截了。
楼主还装了什么杀软和安全辅助工具了？关闭或卸载它们试试。

显示全部楼层 · 发表于 2014-4-18 12:27:53

解决办法是啥

显示全部楼层 · 发表于 2014-4-18 12:46:17

蓝屏之前有安装什么软件吗，或者先卸载avast看是否会继续蓝屏
或者重新安装avast试试

显示全部楼层 · 发表于 2014-4-18 15:39:58

100lj 发表于 2014-4-18 09:56
Probably caused by : aswSP.sys
AVAST与什么软件冲突了，可能驱动被拦截了。
楼主还装了什么杀软和安全 ...

单奔的，上次是退出游戏的时候。这次是重启的时候蓝屏了.

显示全部楼层 · 发表于 2014-4-18 15:40:27

棒棒小星星发表于 2014-4-18 12:46
蓝屏之前有安装什么软件吗，或者先卸载avast看是否会继续蓝屏
或者重新安装avast试试

单奔的，上次是退出游戏的时候。这次是重启的时候蓝屏了.

[系统] 电脑无故蓝屏了

本帖子中包含更多资源

评分

评分