Windows Server SystemPost your Windows Server System question here. Besides Windows Server 2003, Windows Server System also includes other Microsoft Server software (such as BizTalk Server, Exchange Server, ISA Server & others).
Mission Statement
WindowsBBS is an online community dedicated to easily accessible technical support for those using Microsoft operating systems and other Windows software.
Our goal is to become the leading resource for computer users that require assistance with their day-to-day computer usage, including full support for networking PC's, virus & malware removal, system upgrades and general support questions.
Here is my dump, I was wondering if there is any way to pin point where this is truly coming from. RealTimeControl is my custom application, but it doesn't seem to give me any hints as to where this might be coming from. Thanks ahead of time.
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: 80540a24, The address that the exception occurred at
Arg3: b9a7acf0, 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:
nt!KiServiceExit2+0
80540a24 fa cli
TRAP_FRAME: b9a7acf0 -- (.trap 0xffffffffb9a7acf0)
ErrCode = 00000000
eax=00000001 ebx=7ffdf6cc ecx=00000001 edx=ffffffff esi=00714750 edi=0001022a
eip=80540a24 esp=b9a7ad64 ebp=b9a7ad64 iopl=0 nv up ei ng nz na po cy
cs=2100 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010283
nt!KiServiceExit2:
80540a24 fa cli
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: INTEL_CPU_MICROCODE_ZERO
BUGCHECK_STR: 0x8E
PROCESS_NAME: RealTimeControl
CLI_FAULT_INSTR:
nt!KiServiceExit2+0
80540a24 fa cli
LAST_CONTROL_TRANSFER: from 7c90eb94 to 80540a24
STACK_TEXT:
b9a7ad64 7c90eb94 badb0d00 ffffffff 0012dce8 nt!KiServiceExit2
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012dce8 00000000 00000000 00000000 00000000 0x7c90eb94
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiServiceExit2+0
80540a24 fa cli
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!KiServiceExit2+0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: CLI_FAULT
BUCKET_ID: CLI_FAULT
Followup: MachineOwner
---------
Didn't find the information you thought to find? Check out these Similar Threads
Memory checking programs are not adequate because they don't test the memory the way that Windows uses it. Most, if not all, memory checkers use read/write cycles when scanning memory. Since Windows is executing code from the memory, it uses execute cycles. Execute cycles are physically different from read/write cycles and are more vulnerable to parity errors. It is possible for memory checking programs to find parity errors if the memory is extremely faulty.
