Można coś z tym zrobić? W czym właściwie wynika problem, w SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, tak mam to rozumieć?
Kod: Zaznacz cały
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_qfe.130704-0421
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b340
Debug session time: Sat Dec 20 10:14:13.968 2014 (UTC - 5:00)
System Uptime: 0 days 2:55:55.554
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: 01010201, The address that the exception occurred at
Arg3: b134ca08, Exception Record Address
Arg4: b134c704, Context Record Address
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+b6dd7
01010201 ?? ???
EXCEPTION_RECORD: b134ca08 -- (.exr 0xffffffffb134ca08)
ExceptionAddress: 01010201
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 01010201
Attempt to read from address 01010201
CONTEXT: b134c704 -- (.cxr 0xffffffffb134c704)
eax=00000031 ebx=cffb0000 ecx=00000000 edx=b0344158 esi=88b4f000 edi=02000000
eip=01010201 esp=b134cad0 ebp=6140008a iopl=0 nv up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
01010201 ?? ???
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
EXCEPTION_PARAMETER1: 00000000
EXCEPTION_PARAMETER2: 01010201
READ_ADDRESS: GetUlongFromAddress: unable to read from 8055fb68
01010201
FOLLOWUP_IP:
athuw+b6dd7
b02dadd7 ?? ???
FAILED_INSTRUCTION_ADDRESS:
+b6dd7
01010201 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from b134cbc8 to 01010201
SYMBOL_ON_RAW_STACK: 1
STACK_ADDR_RAW_STACK_SYMBOL: ffffffffb134cb30
STACK_COMMAND: dds B134CB30-0x20 ; kb
STACK_TEXT:
b134cb10 72ee0a72
b134cb14 00007838
b134cb18 00000029
b134cb1c 00007828
b134cb20 66964300
b134cb24 0000782c
b134cb28 8db6d861
b134cb2c b02dadd7 athuw+0xb6dd7
b134cb30 88b4f000
b134cb34 00000000
b134cb38 88b4fc78
b134cb3c b02dd3aa athuw+0xb93aa
b134cb40 b134cbc8
b134cb44 86e68000
b134cb48 88b4f000
b134cb4c 86e6b91c
b134cb50 b02a5914 athuw+0x81914
b134cb54 00000400
b134cb58 00000001
b134cb5c b134cbc8
b134cb60 00000000
b134cb64 88b4fc78
b134cb68 00000001
b134cb6c 00000000
b134cb70 00000001
b134cb74 b134cb8c
b134cb78 804dc1a0 nt!KeWaitForSingleObject
b134cb7c 86e6b8e4
b134cb80 00e68000
b134cb84 00000001
b134cb88 00000000
b134cb8c b02a61a6 athuw+0x821a6
SYMBOL_NAME: athuw+b6dd7
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athuw
IMAGE_NAME: athuw.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e32158c
FAILURE_BUCKET_ID: 0x7E_BAD_IP_athuw+b6dd7
BUCKET_ID: 0x7E_BAD_IP_athuw+b6dd7
Followup: MachineOwner
---------
podaj model.