Getting BSOD on Dell PE R440 with Server 2016 When Virtualization is Enabled

0
0
Asked By TechGuru99 On

Hey everyone, I'm pulling my hair out over here and really need some help! Over the weekend, we updated two Server 2016 Hyper-V hosts in separate offices with the latest Windows patches, and both crashed in the middle of the update—BSOD with a Memory Management error. One of the servers managed to fix itself and I can log in, but it still crashes occasionally. The other server has the same BSOD issue during boot-up. The weird part is, if I disable Virtualization in the BIOS, I can log in and use the server just fine. Unfortunately, I need the VMs on this host because they're running as DCs and member servers. So I'm wondering, why does enabling Virtualization in the BIOS cause the host to BSOD on startup? It was working perfectly before the Windows updates. I thought the 3 VMs in Hyper-V might be hogging memory, so I set them to not start automatically when the host boots, but that didn't help either. Here's what we've done so far: I finished all Windows Updates, rebooted multiple times with virtualization disabled, updated the BIOS to the latest version, and ran SFC /Scannow and DISM Restorehealth several times, but no luck. Any thoughts or suggestions would really be appreciated!

3 Answers

Answered By VM_Wizard88 On

I ran through all the recommended firmware updates from the lifecycle controller, but no luck—still getting BSOD. Did you have any other suggestions? Maybe I missed something?

Answered By ServerMaster42 On

Have you checked to see if you updated all firmware components too? Sometimes, the issue can be tied to outdated drivers or firmware like the PERC H350 RAID Controller or the iDRAC. Make sure you've got everything up to date through the Dell lifecycle manager. It’s possible there was a bug related to virtualization that was fixed in one of those updates. If that doesn’t solve it, you might want to consider rolling back or even migrating to slightly newer hardware as a last resort.

Answered By TroubleShooter77 On

I did the full update on the lifecycle too and sadly, the problem’s still here. I guess it’s more complicated than just firmware updates.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.