Very odd; the debugger is saying that it's unable to read KLDR_DATA_TABLE_ENTRY. The exact error is "Unable to read KLDR_DATA_TABLE_ENTRY at fffffa80`18ba1760 - NTSTATUS 0xC0000147"
What level of dump is configured? Perhaps set it to "kernel memory dump" and get it to BSOD again and see if the dump is more useful. I'll help if you like or the debugging tools are available without the rest of the SDK or the like. DAMIEN SOLODOW Systems Engineer 317.447.6033 (office) 317.447.6014 (fax) HARRISON COLLEGE ________________________________ From: [email protected] [[email protected]] on behalf of Webster [[email protected]] Sent: Saturday, August 31, 2013 12:22 PM To: [email protected] Subject: [NTSysADM] Server 2012 DMP file It has been a long time since I had to analyze a crash dump file. One of my new Hyper-V 2012 lab servers keeps giving me a Bug Check when I run the failover cluster validation tool. The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef (0xfffffa8018c8d3c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 083013-10795-01. Bugcheck EF is CRITICAL_PROCESS_DIED Is there a quick way to process the DMP file to see what critical process is having the issue without having to install all the Windows Debugging tools? Just in case someone has some spare time to help a brother out, https://dl.dropboxusercontent.com/u/43555945/MEMORY.zip https://dl.dropboxusercontent.com/u/43555945/MEMORY.DMP The DMP file is 885MB and Zip is 95MB. Thanks Webster
