SQL on Server 2016 causing BSOD

[ITGURU]

I have 2 identical servers hardware wise which I have upgraded (by a clean install) to Server 2016. Both servers have backup tape drives and run Arcserve Backup software.

The first one i did ages ago was fine, been running for months without issue.

 

However, the second one ran fine for a month. The tape drive in this one is used rarely as the other server has higher capacity drive. However, I then decided to install the Arcserve Backup software onto the server, which includes SQL server.

 

On 11th April i installed CA Arcserve Backup to the server

on 16th April the server BSOD with DPC_Watchdog_error and rebooted.

On 17th April it BSOD again , same error

On 23rd April again

On 26th April again

 

On 27th april i uninstalled CA Arcserve Backup as that was the only change since it seemed stable after first upgrade.

Been running fine since.

 

How do i got about troubleshooting this.. the server was fine on 2012 R2., and so is the other one with identical hardware. All tape drivers are up to date.

[computer_expert]

what patch level is the SQL server installation at (eg 2012 SP3 CU16)?. SQL 2012 and 2014 need to have certain updates installed to be compatible with server 2016 Edited May 12, 2018 by computer_expert

[ITGURU]

what patch level is the SQL server installation at (eg 2012 SP3 CU16)?. SQL 2012 and 2014 need to have certain updates installed to be compatible with server 2016

 

According to Programs and features, CA Arcserve installs SQL server 2008. Although it says it's not compatible with 2016, I have 2 other servers running the same software with tape drives on the same model of server.

 

There is just this 1 particular server (same model as above 2) which Blue screens when the software is installed. only other difference is this server is running the hyper-v role. I moved all VMs to another host, and it still crashed, and only seems stable without Arcserve installed.

[3s-gtech]

Can you in-place upgrade the SQL Server to a newer version once it's on? Should still work afterwards, I don't believe much changes in the connection.