Can Someone Explain This Minidump Debug Analysis For Me Please?
Ive been getting blue screen crashes for a while now and they only ever happen when i play the game world of warcraft. I WinDbg to try and understand what was happening, but due to my lack of understanding in this area, i cannot make any sense of the analysis. Perhaps someone can make sense of this for me?
kd> !analyze -v
**************************************…
* *
* 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 0×80000003. 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: 89c0cbc7, The address that the exception occurred at
Arg3: f7976cc0, Exception Record Address
Arg4: f79769bc, Context Record Address
Debugging Details:
——————
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 – The instruction at “0x%08lx” referenced memory at “0x%08lx”. The memory could not be “%s”.
FAULTING_IP:
+16
89c0cbc7 ff7010 push dword ptr [eax+10h]
EXCEPTION_RECORD: f7976cc0 — (.exr 0xfffffffff7976cc0)
ExceptionAddress: 89c0cbc7
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 4d8b48fb
Attempt to read from address 4d8b48fb
CONTEXT: f79769bc — (.cxr 0xfffffffff79769bc)
eax=4d8b48eb ebx=00000000 ecx=f126b544 edx=0000001e esi=00000000 edi=89c26814
eip=89c0cbc7 esp=f7976d88 ebp=f7976d98 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
89c0cbc7 ff7010 push dword ptr [eax+10h] ds:0023:4d8b48fb=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 4
DEFAULT_BUCKET_ID: COMMON_SYSTEM_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: 4d8b48fb
READ_ADDRESS: 4d8b48fb
FOLLOWUP_IP:
+16
89c0cbc7 ff7010 push dword ptr [eax+10h]
FAILED_INSTRUCTION_ADDRESS:
+16
89c0cbc7 ff7010 push dword ptr [eax+10h]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 89c1403d to 89c0cbc7
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7976d98 89c1403d 00000000 00000000 8a0382f8 0x89c0cbc7
f7976ddc 804f827a 89c13feb 8a248150 00000000 0x89c1403d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0×16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE
BUCKET_ID: 0x7E_BAD_IP_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
———
Related Posts:
Tags: Analysis | Debug | Explain | Minidump | Please | Someone | This
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
3 Responses to “Can Someone Explain This Minidump Debug Analysis For Me Please?”.
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: System
CONTEXT: f79769bc — (.cxr 0xfffffffff79769bc)
eax=4d8b48eb ebx=00000000 ecx=f126b544 edx=0000001e esi=00000000 edi=89c26814
eip=89c0cbc7 esp=f7976d88 ebp=f7976d98 iopl=0 nv up ei ng nz ac po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
89c0cbc7 ff7010 push dword ptr [eax+10h] ds:0023:4d8b48fb=????????
ExceptionAddress: 89c0cbc7
ExceptionCode: c0000005 (Access violation)
Attempt to read from address 4d8b48fb
FAILED_INSTRUCTION_ADDRESS:
+16
89c0cbc7 ff7010 push dword ptr [eax+10h]
///
Indicates a sub routine is attempting to push/copy data onto a buffer which would allow the developer of the “failed system routine” to stop the program at this break-point for analysis. The environment of the retail user is different that of the developer and so this operation has resulted in a fault.
////
This is a bug in a windows driver itself. Your game program W.O.W requested input from a windows system component which tried to read from a 32bit piece memory which failed due to miscalculation of size of allocated data marked as readable:
ExceptionCode: c0000005 (Access violation)
ds:0023:4d8b48fb=????????
datasegment and offset out of range / not readable.
To remedy the situation: Try running in compatibilty mode such as Windows 98,NT,2000.
OR
1. Start/Run/”c:boot.ini”
8. Modify /noexecute= for example to /noexecute=AlwaysOff to disable DEP (Data Execution Prevention) completely.
11. Sav and close file.
13. Reboot.
Could be a problem with device drivers, hardware or software. This problem can be solved by uninstalling new software, updating device drivers and making minor configuration changes . From http://fixit.in/bluescreenofdeath.html . You can also run a free registry scan using utilities from http://rgt.in
This forum probably isn’t technical enough for this question.
Try heading over to this one where more techies hang out.http://forum.sysinternals.com/forum_topi…
Leave a comment.