Am currently facing an BSOD issue where i am trying to analyse the issue. I have tried using the Windows debugger to find the Root cause but am struck up there , where i need your help.
Below is the Crash dump analysis output , which says Mcpdh.exe is the reason for the BSOD, but i would like to know where exactly the issue lies with in the mcpdh.exe as the this mcpdh.exe is an custom application. I would appreciate if we could really point out which line or function in the application(mcpdh.exe) has caused the BSOD.
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: 80932514, The address that the exception occurred at Arg3: baf6fb64, 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".
Thank you for visiting the Microsoft forum. This forum focuses on Perfmon and diagnostic tools. I am moving your question to the moderator forum ("Where is the forum for..?"). The owner of the forum will direct you to a right forum.
