I've got a hyperV 2012 system with several VM's. One of the VM's has thrown a BSOD a couple of times in the last month and I was wondering if the procedure for figuring out the cause is a little different under hyperV.
The BSOD I'm getting is a memory management bugcheck 1a. The crash dumps don't show any "smoking guns":
| 050815-12437-01.dmp | 2015-05-08 9:47:02 AM | MEMORY_MANAGEMENT | 0x0000001a | 00000000`00005003 | fffff700`01080000 | 00000000`00001810 | 00000000`00000000 | ntoskrnl.exe | ntoskrnl.exe+72a40 | NT Kernel & System | Microsoft® Windows® Operating System | Microsoft Corporation | 6.1.7601.18798 (win7sp1_gdr.150316-1654) | x64 | ntoskrnl.exe+72a40 | C:\Windows\Minidump\050815-12437-01.dmp | 4 | 15 | 7601 | 286,248 | 2015-05-08 9:48:47 AM | ||||
| 042115-12906-01.dmp | 2015-04-21 12:16:16 PM | MEMORY_MANAGEMENT | 0x0000001a | 00000000`00003452 | 00000000`7efb1000 | fffff700`010804e0 | 000000ab`00000000 | fltmgr.sys | fltmgr.sys+42ec | Microsoft Filesystem Filter Manager | Microsoft® Windows® Operating System | Microsoft Corporation | 6.1.7600.16385 (win7_rtm.090713-1255) | x64 | ntoskrnl.exe+72a40 | C:\Windows\Minidump\042115-12906-01.dmp | 4 | 15 | 7601 | 286,248 | 2015-04-21 12:18:45 PM |
Googling around for this issue points to memory HW problems in the computer but being a hyperV system with many other VM's active I don't see how that could be it. The VM in question is a server 2008R2 in "terminal server" mode, fully patched. Nothing of note in the event logs and nothing (other than updates last month) was done on the server lately.
Any ideas on how I could proceed to track this down? Thanks.
-- Al