查看: 1686|回复: 6
收起左侧

[已解决] 问题已解决

[复制链接]
扬帆起航
发表于 2014-7-21 12:31:39 | 显示全部楼层 |阅读模式
本帖最后由 扬帆起航 于 2016-2-18 08:37 编辑




问题已解决
Flameocean
发表于 2014-7-21 12:49:09 | 显示全部楼层
你都是问题解决专家,还呼叫
Robin1991
发表于 2014-7-21 14:49:41 | 显示全部楼层
快去看看我的蓝屏贴,官人还没给个回信,都求救半天了。
扬帆起航
 楼主| 发表于 2014-7-21 17:48:23 | 显示全部楼层
Flameocean 发表于 2014-7-21 12:49
你都是问题解决专家,还呼叫

初步分析是显卡驱动不稳定造成的,换了几个驱动都不行,谁帮我呼叫下MJ大神
扬帆起航
 楼主| 发表于 2014-7-21 17:57:20 | 显示全部楼层
本帖最后由 扬帆起航 于 2014-7-22 18:49 编辑

以下是从蓝屏检测软件复制来的:



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


Loading Dump File [D:\360安全浏览器下载\Mini072114-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
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 XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055c340
Debug session time: Mon Jul 21 11:34:22.375 2014 (GMT+8)
System Uptime: 0 days 0:06:47.937
Loading Kernel Symbols
...........................................................................................................................................
Loading User Symbols
Loading unloaded module list
.............
Unable to load image igxpdx32.DLL, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpdx32.DLL
*** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bec03acd, a8aeaba0, 0}

Probably caused by : igxpdx32.DLL ( igxpdx32+59acd )

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

kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bec03acd, The address that the exception occurred at
Arg3: a8aeaba0, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

FAULTING_IP:
igxpdx32+59acd
bec03acd 8b510c          mov     edx,dword ptr [ecx+0Ch]

TRAP_FRAME:  a8aeaba0 -- (.trap 0xffffffffa8aeaba0)
ErrCode = 00000000
eax=e31ea018 ebx=e1319488 ecx=00000000 edx=e1318030 esi=e1318000 edi=00000000
eip=bec03acd esp=a8aeac14 ebp=e1319434 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
igxpdx32+0x59acd:
bec03acd 8b510c          mov     edx,dword ptr [ecx+0Ch] ds:0023:0000000c=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  360se.exe

LAST_CONTROL_TRANSFER:  from bf96749e to bec03acd

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
a8aeac60 bf96749e 855d6000 00000000 e2580cb8 igxpdx32+0x59acd
a8aeaca4 be800cb2 a8aeacfc a8aead64 062cfba8 win32k!WatchdogDdContextCreate+0x59
a8aead4c 804df7f8 04200001 01400003 00000000 dxg!DxD3dContextCreate+0x1a2
a8aead4c 7713e514 04200001 01400003 00000000 nt!KiSystemServicePostCall
062cfbb4 00000000 00000000 00000000 00000000 0x7713e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
igxpdx32+59acd
bec03acd 8b510c          mov     edx,dword ptr [ecx+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  igxpdx32+59acd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igxpdx32

IMAGE_NAME:  igxpdx32.DLL

DEBUG_FLR_IMAGE_TIMESTAMP:  4db20205

FAILURE_BUCKET_ID:  0x8E_igxpdx32+59acd

BUCKET_ID:  0x8E_igxpdx32+59acd

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

kd> lmvm igxpdx32
start    end        module name
bebaa000 befaa000   igxpdx32 T (no symbols)           
    Loaded symbol image file: igxpdx32.DLL
    Image path: igxpdx32.DLL
    Image name: igxpdx32.DLL
    Timestamp:        Sat Apr 23 06:32:37 2011 (4DB20205)
    CheckSum:         003F8B76
    ImageSize:        00400000
    Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0
尘梦幽然
发表于 2014-7-22 11:12:50 | 显示全部楼层
有时候显卡驱动出问题不一定是显卡驱动自身的问题,还有可能是别的驱动和显卡驱动冲突了。一般推荐换个杀毒软件之类的尝试
至尊潮流
发表于 2014-7-22 15:14:48 | 显示全部楼层
好久都没看到MJ了
您需要登录后才可以回帖 登录 | 快速注册

本版积分规则

手机版|杀毒软件|软件论坛| 卡饭论坛

Copyright © KaFan  KaFan.cn All Rights Reserved.

Powered by Discuz! X3.4( 沪ICP备2020031077号-2 ) GMT+8, 2024-12-26 15:45 , Processed in 0.123546 second(s), 16 queries .

卡饭网所发布的一切软件、样本、工具、文章等仅限用于学习和研究,不得将上述内容用于商业或者其他非法用途,否则产生的一切后果自负,本站信息来自网络,版权争议问题与本站无关,您必须在下载后的24小时之内从您的电脑中彻底删除上述信息,如有问题请通过邮件与我们联系。

快速回复 客服 返回顶部 返回列表