*******************************************************************************
* *
* 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: f7741291, The address that the exception occurred at
Arg3: f54eeb60, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nadim+2291
f7741291 8b5048 mov edx,[eax+0x48]
TRAP_FRAME: f54eeb60 -- (.trap fffffffff54eeb60)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=85a97d60 edx=00000000 esi=00000000 edi=85a97d60
eip=f7741291 esp=f54eebd4 ebp=f54eebf8 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nadim+0x2291:
f7741291 8b5048 mov edx,[eax+0x48] ds:0023:00000048=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from f7740bc0 to f7741291
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f54eebf8 f7740bc0 85a970cc 00000000 f773f4ad nadim+0x2291
f54eec3c 804f0473 85afa030 85374d50 8549a0c0 nadim+0x1bc0
f54eec4c 80585208 85374dc0 8549a0c0 85374d50 nt!IofCallDriver+0x3f
f54eec60 805860e6 85afa030 85374d50 8549a0c0 nt!IopSynchronousServiceTail+0x6f
f54eed00 80586128 00000118 00000000 00000000 nt!IopXxxControlFile+0x607
f54eed34 804dfd24 00000118 00000000 00000000 nt!NtDeviceIoControlFile+0x28
f54eed34 7ffe0304 00000118 00000000 00000000 nt!KiSystemService+0xd0
0012fcbc 00000000 00000000 00000000 00000000 SharedUserData!SystemCallStub+0x4
FOLLOWUP_IP:
nadim+2291
f7741291 8b5048 mov edx,[eax+0x48]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nadim+2291
MODULE_NAME: nadim
IMAGE_NAME: nadim.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 429b692b
STACK_COMMAND: .trap fffffffff54eeb60 ; kb
FAILURE_BUCKET_ID: 0x8E_nadim+2291
BUCKET_ID: 0x8E_nadim+2291
Followup: MachineOwner
---------
Thank you for your report.
I forwarded your message to the Net Activity Diagram developer.
He will work to fix this problem in the next version of the program.
Sincerely,
Alexander.
| Alexander Bednyakov
| MetaProducts Corporation
Could you please test the updated version of Net Activity Diagram?
Please uninstall the previous version, reboot Windows (so NAD can remove libraies locked by Windows in run time) and install the new version. You can download it from: http://www.metaproducts.com/download/nadsetup2.exe
Please write me about the result. Thank you.
Best regards,
Alexander Bednyakov
MP Staff