We have a 2012 R2 Server Standard VM running on Hyper-V 2008R2 Host for few months, then we migrated the 2012R2 VM to Hyper-V 2012R2 Host. Since then, the VM crashes twice a day with BSOD and no specific crash message.
The Hyper-V Host is running fine, and other instances (none is 2012) runs fine on it including some Linux based ones. The Hardware is latest Intel Xeon E2600 v3 with 32GB DDR4 RAM.On the old Hyper-V 2008R2 Host, everything was working perfectly fine.
The VM is 2012R2 Standard with 5160MB RAM assigned and 4 Virtual Processors.
What we have tried so far:
- Remove Device Manager devices, and allow windows to reinstall them
- Integration Tools says it is up to date
- Removed NIC and let windows reinstall, reinserted the IPs
- Ran chkdsk C: /R (it didn't do anything)
- Ran rootkit/virus scan, checked nothing suspicious in DriverView (all MSFT drivers loaded)
- Checked the BSOD dumps using Bluescreen View and WindDBG , the results are inconclusive (below):
- Performed memory diagnostic scan on the VM, no issues
- Ran Verifier, there was no drivers loaded other than MSFT drivers. Also checked Sigverif , and found no issues. Also updated mc_updateGenuineIntel.dll with updated Intel micro code update.
- The problem was happening with the disk in VHD format, so we converted it to VHDX but the error persisted. There were no errors while converting and have not seen anything indicating an issue with the VM (nothing missing, nothing corrupted). The VM runs
MSSQL 2012 DB.
- All Important, Critical and Optional Updates installed
- The old Host 2008R2 had NTFS partition, the new Host has ReFS partition
- The errors are:
Dump File | Crash Time | Bug Check String | Bug Check Code | Parameter 1 | Parameter 2 | Parameter 3 | Parameter 4 | Caused By Driver | Caused By Address | File Description | Product Name | Company | File Version | Processor | Crash Address | Stack Address 1 | Stack Address 2 | Stack Address 3 | Computer Name | Full Path | Processors Count | Major Version | Minor Version | Dump File Size | Dump File Time |
---|
122515-12671-01.dmp | 12/25/2015 6:49:40 PM | | 0x00000109 | a3a01f5a`5f41f5ae | b3b72be0`b1c1f78d | 00000002`000001a0 | 00000000`00000007 | ntoskrnl.exe | ntoskrnl.exe+14e8a0 | NT Kernel & System | Microsoft® Windows® Operating System | Microsoft Corporation | 6.3.9600.18146 (winblue_ltsb.151121-0600) | x64 | ntoskrnl.exe+14e8a0 | | | | | C:\Windows\Minidump\122515-12671-01.dmp | 4 | 15 | 9600 | 294,680 | 12/25/2015 6:50:16 PM |
122515-11640-01.dmp | 12/25/2015 9:27:37 AM | | 0x00000109 | a3a01f59`fda8b554 | b3b72be0`5028b853 | 00000003`000001a0 | 00000000`00000007 | ntoskrnl.exe | ntoskrnl.exe+14e8a0 | NT Kernel & System | Microsoft® Windows® Operating System | Microsoft Corporation | 6.3.9600.18146 (winblue_ltsb.151121-0600) | x64 | ntoskrnl.exe+14e8a0 | | | | | C:\Windows\Minidump\122515-11640-01.dmp | 4 | 15 | 9600 | 294,680 | 12/25/2015 9:28:15 AM |
122515-12687-01.dmp | 12/25/2015 4:35:47 AM | | 0x00000109 | a3a01f59`4068b8a2 | b3b72bdf`92e8b841 | 00000001`000001a0 | 00000000`00000007 | ntoskrnl.exe | ntoskrnl.exe+14e8a0 | NT Kernel & System | Microsoft® Windows® Operating System | Microsoft Corporation | 6.3.9600.18146 (winblue_ltsb.151121-0600) | x64 | ntoskrnl.exe+14e8a0 | | | | | C:\Windows\Minidump\122515-12687-01.dmp | 4 | 15 | 9600 | 294,680 | 12/25/2015 4:36:24 AM |
122515-55562-01.dmp | 12/25/2015 4:03:41 AM | | 0x00000109 | a3a01f59`0f68b8bc | b3b72bdf`61e8bbbb | 00000003`000001a0 | 00000000`00000007 | ntoskrnl.exe | ntoskrnl.exe+14e8a0 | NT Kernel & System | Microsoft® Windows® Operating System | Microsoft Corporation | 6.3.9600.18146 (winblue_ltsb.151121-0600) | x64 | ntoskrnl.exe+14e8a0 | | | | | C:\Windows\Minidump\122515-55562-01.dmp | 4 | 15 | 9600 | 294,680 | 12/25/2015 4:05:32 AM |
122515-10796-01.dmp | 12/25/2015 12:47:09 AM | | 0x00000109 | a3a01f5a`159604ec | b3b72be0`681607eb | 00000003`000001a0 | 00000000`00000007 | ntoskrnl.exe | ntoskrnl.exe+14e8a0 | NT Kernel & System | Microsoft® Windows® Operating System | Microsoft Corporation | 6.3.9600.18146 (winblue_ltsb.151121-0600) | x64 | ntoskrnl.exe+14e8a0 | | | | | C:\Windows\Minidump\122515-10796-01.dmp | 4 | 15 | 9600 | 294,680 | 12/25/2015 12:47:39 AM |
122415-21031-01.dmp | 12/24/2015 8:28:48 AM | | 0x00000109 | a3a01f59`81f1294f | b3b72bdf`d4712a8e | 00000002`000001a0 | 00000000`00000007 | ntoskrnl.exe | ntoskrnl.exe+14e8a0 | NT Kernel & System | Microsoft® Windows® Operat |
WINDBG Results:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response Time (ms) Location
OK c:\symbols\
Symbol search path is: c:\symbols\
Executable search path is:
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 9600.18146.amd64fre.winblue_ltsb.151121-0600
Machine Name:
Kernel base = 0xfffff802`d1417000 PsLoadedModuleList = 0xfffff802`d16eb630
Debug session time: Fri Dec 25 18:49:40.089 2015 (UTC - 5:00)
System Uptime: 0 days 7:16:02.043
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a01f5a5f41f5ae, b3b72be0b1c1f78d, 2000001a0, 7}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
Any advise on how to proceed from here to find a solution to this crash?