Jump to content

Recommended Posts

Posted

I have 1 hyper-v Host server which i upgraded over the holidays - it was running Server 2012 R2 reliably.

I then clean installed Server 2016 and re-configured as a hyper-v host ( i never do OS upgrades, always clean install)

It ran fine for the 2 weeks, first day back last monday and it Blue screened with a DPC_Watchdog_error, did a dump and re-booted. 13 hours later it crashed again with the same BSOD. Using blue screen view it highlighted 2 items - hal.dll and ntoskrnl.dll

It then ran fine from wednesday until this morning when it happened again (i thought it was cured) but now I just have ntoskrnl.dll showing as an issue after i disabled the onboard Broadcom cards, even though they were working fine on 2012 R2.

I have other ML350 G6 servers on 2016 all with the same drivers, all running fine for months. Only difference is this one is running as a host.

 

Whats the next step to try and resolve this permanently?

Posted

Did you update/upgrade any firmware for raid controllers/BIOS etc if it's an older model? (Or iscsi if you're linking it that way etc)

 

Steve

Posted
Did you update/upgrade any firmware for raid controllers/BIOS etc if it's an older model? (Or iscsi if you're linking it that way etc)

 

Steve

 

Yes, all up to date from the HP website! Same drives /firmware as all other servers of same model and OS.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...