Имя пользователя:
Пароль:  
Помощь | Регистрация | Забыли пароль?  

Показать сообщение отдельно


Moderator


Сообщения: 53585
Благодарности: 15543

Профиль | Отправить PM | Цитировать


argo39, результат анализа дампа ядра:
Код: Выделить весь код
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: srv*E:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: srv*E:\Symbols*http://msdl.microsoft.com/download/symbols
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
Debug session time: Wed Feb  2 21:24:05.343 2011 (GMT+3)
System Uptime: 0 days 0:02:52.924
Loading Kernel Symbols
..........................................................................................................
Loading User Symbols

Loading unloaded module list
.........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, e99990d8, f893e774, f893e470}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for nv4_disp.dll
*** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
Probably caused by : nv4_disp.dll ( nv4_disp+3d561 )

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

kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: e99990d8, The address that the exception occurred at
Arg3: f893e774, Exception Record Address
Arg4: f893e470, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>

FAULTING_IP: 
+ffffffffe99990d8
e99990d8 0a70f1          or      dh,byte ptr [eax-0Fh]

EXCEPTION_RECORD:  f893e774 -- (.exr 0xfffffffff893e774)
ExceptionAddress: 92b455d1
   ExceptionCode: bb9e4c00
  ExceptionFlags: 07da4ba7
NumberParameters: 499
   Parameter[0]: 0a200a40
   Parameter[1]: 00d1214a
   Parameter[2]: 651d0007
   Parameter[3]: 614e04f5
   Parameter[4]: 00400002
   Parameter[5]: 6c7e3c71
   Parameter[6]: 0007ef2c
   Parameter[7]: 7d700700
   Parameter[8]: 26946cac
   Parameter[9]: 40000002
   Parameter[10]: 5065b635
   Parameter[11]: 0700d180
   Parameter[12]: 78662500
   Parameter[13]: 00000676
   Parameter[14]: 14542907

CONTEXT:  f893e470 -- (.cxr 0xfffffffff893e470)
Unable to get program counter
eax=000007b0 ebx=0300febb ecx=88673698 edx=98070000 esi=9f645d00 edi=400019c0
eip=00d1216e esp=00400004 ebp=af45a740 iopl=0 vip vif nv dn di ng zr ac pe cy
cs=0007  ss=5f17  ds=4761  es=0700  fs=31e9  gs=4000             efl=e3b904f5
0007:216e ??              ???
Resetting default scope

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xbb9e4c00 - <Unable to get error code text>

LAST_CONTROL_TRANSFER:  from 07000004 to 80533826

SYMBOL_ON_RAW_STACK:  1

STACK_ADDR_RAW_STACK_SYMBOL: fffffffff893e3d4

STACK_COMMAND:  dds F893E3D4-0x20 ; kb

STACK_TEXT:  
f893e3b4  00131d5e
f893e3b8  07000003
f893e3bc  12213312
f893e3c0  0007b02c
f893e3c4  2e7e4000
f893e3c8  d1211427
f893e3cc  f2000700
f893e3d0  bf04f561 nv4_disp+0x3d561
f893e3d4  400004ed
f893e3d8  6d667900
f893e3dc  07f2105f
f893e3e0  08070000
f893e3e4  06087f4e
f893e3e8  00000773
f893e3ec  e261b540
f893e3f0  00d121b5
f893e3f4  61f20007
f893e3f8  855f0247
f893e3fc  00400007
f893e400  53011d36
f893e404  00030013
f893e408  a4b50700
f893e40c  b0d6c561
f893e410  40000007
f893e414  eef30ec6
f893e418  0700d121
f893e41c  f561f200
f893e420  01173504
f893e424  7d004000
f893e428  de7d5911
f893e42c  000007ec
f893e430  548b2d07


FOLLOWUP_IP: 
nv4_disp+3d561
bf04f561 ??              ???

SYMBOL_NAME:  nv4_disp+3d561

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nv4_disp

IMAGE_NAME:  nv4_disp.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  47567aa4

FAILURE_BUCKET_ID:  0x7E_nv4_disp+3d561

BUCKET_ID:  0x7E_nv4_disp+3d561
Сбой на nv4_disp.dll - драйвер видеокарты (обновите или наоборот, поставьте другую версию).
Если не поможет, не исключено, что проблема аппаратная (перегрев, неисправность видеокарты или блока питания).
Это сообщение посчитали полезным следующие участники:

Отправлено: 10:09, 03-02-2011 | #495