DPC Watchdog crashes

[CraigM]

Hi all,

 

I'm having some issues with my main DC at the moment and hope someone can help. The server is running 2012R2, fully patched as of the July Cummulative Update. The hardware itself is an Intel 2600GZ 1U server, firmware fully patched and up to date. The server is backed up using Veeam Agent Free Edition (latest version) to our NAS over ISCSI (NAS also has its latest firmware applied)

 

Since a month ago when executing Veeam backups, I've had the server blue screen multiple times on me. Since the crash is happening late at night when no one is around, the system hangs until the next morning, every time the failure is caused by DPC_WATCHDOG timeouts. I've even had the server corrupt its firmware from after hanging overnight due to the crash. When I get in, the memory dump is like 35% complete and I have to reboot before it is allowed to finish the process of the dump. BlueScreen Viewer doesn't give much info apart from DPC_WATCHDOG as the culprit.

 

The weird thing is that prior to this, Veeam has been backing up the server for well over a year now, every night without issue. I'm wondering if the issue hasn't been caused by the last Cummulative Update, since the server was behaving fine in the time frame before this patch was installed.

 

Does anyone have any idea on what could be causing this issue all of a sudden? I've read all sorts of possibilities out there but I'm not sure what would be the next step to try.

 

Thanks!

[computer_expert]

Doe Veeam require .net? if so, make sure you install the august 2018 update for .net as the july release broke lots of stuff.

 

https://blogs.msdn.microsoft.com/dotnet/2018/07/20/advisory-on-july-2018-net-framework-updates/

[CraigM]

Doe Veeam require .net? if so, make sure you install the august 2018 update for .net as the july release broke lots of stuff.

 

https://blogs.msdn.microsoft.com/dotnet/2018/07/20/advisory-on-july-2018-net-framework-updates/

 

Thanks for this, I looked at the Veeam System Requirements and it does indeed require .Net 4.5.2. The server has 4.6.1 installed. I also managed to find later Intel RAID drivers, which I will try updating and installing this weekend when it's quiet and I can babysit the server and watch what happens while I am still on site.

 

Thanks again, hope that some combination of this actually helps stabilise things again.