Blue Screen 0x00000124 and HAL.dll error encountered after accidently unplugging an iSCSI port on Windows Server 2016 HyperV

  • Thread starter Thread starter Jovi Tan
  • Start date Start date
J

Jovi Tan

Guest
Hi,


We ran into an issue with our HyperV server on 5 April 2019 between 5:35pm to 5:50pm GMT+8.

A LAN cable connected to one of the iSCSI ports on the HyperV was accidentally disconnected. This caused the HyperV to run into a bluescreen with stop code 0x00000124 due to HAL.dll. We actually had another iSCSI port on the Hyper V that still remained conencted when the incident occured.


Even though the incident happened due to the accidental disconnected of the HyperV iSCSI ports, we were quite suprised because it should not cause a bluescreen in normal circumstances. Have viewed a couple of articles mentioning that stop code 0x00000124 could be due to overheating or defective hardware, however we doubt so since this is the first time it happened and it only happen at the moment iSCSI port LAN cable was disconnected.


I have attached the Windows minidump for reference:-

https://acclivis-my.sharepoint.com/...1PqHyeYk7DH5gBUaRZIv4gd6Aue7F7xTYzBA?e=YEoqjq

Hope to get some advise on this as we are quite lost on what could have happened.


Many thanks!


Best Regards,

Jovi

Continue reading...
 
Back
Top