Case No: 07251670
Summary:
We have been running v11 with no issue. Upgraded to v12, and now getting BSOD within a couple of minutes after the "Veeam Backup Service" is started
Detail:
The BSOD error is:
PAGE FAULT IN NONPAGED AREA
The Veeam backup machine is a HP Microserver Gen8 running Windows Server 2019, used for backing up VMs from VMWare vSphere.
BSOD didn't seem to start occurring until after the "Upgrade remote components" wizard is finished, (this wizard appears the first time running the Veeam console after upgrading to v12). This component upgrade is done on a couple of remote servers, and also locally to the backup server. The four services it seems to install/upgrade are:
Veeam VSS Hardware Provider Service
Veeam Backup VSS Integration Service
Veeam Data Mover Service
Veeam Installer Service
I have narrowed it down to mainly be the "Veeam Installer Service" on the backup server. If this service is running when the Veeam Backup Service is running, then I will get the BSOD every time. (I say "mainly" because I am relatively certain I also got the BSOD when the Veeam Installer Service was stopped and the Veeam Backup VSS Integration Service was enabled, but can't seem to reproduce this again).
I have analysed the minidump with BlueScreenView and the red coloured line is:
ntoskrnl.exe ntoskrnl.exe+4b560 fffff800`7bc0a000 fffff800`7c676000 0x00a6c000 0x3b89c92f 27/08/2001 1:44:39 PM
I have sent a copy of the minidump in the case submission
To attempt to resolve the issue I have tried upgrading drivers. Am on latest BIOS and storage controller firmware. RAM test finds no errors in memory. Have Windows patches up to date.
chkdsk c: no issues. sfc /scannow no issues. Also ran DISM /Online /Cleanup-image /Restorehealth .
I am not able to run backups because I need to sync the SOBR and syncing the SOBR requires the "Veeam Installer Service" to be running.
I had no BSOD issues with v11 and prior.
Many Thanks.
-
- Enthusiast
- Posts: 90
- Liked: 23 times
- Joined: Jun 17, 2012 1:09 pm
- Full Name: Nev
- Contact:
-
- Enthusiast
- Posts: 90
- Liked: 23 times
- Joined: Jun 17, 2012 1:09 pm
- Full Name: Nev
- Contact:
Re: v12 BSOD
This one has now been resolved, many thanks to Veeam support from analysing minidump file to find the problem.
There was an old Backup Exec driver hanging around on the system causing a conflict. Once removed, BSOD seems to be no longer occurring.
There was an old Backup Exec driver hanging around on the system causing a conflict. Once removed, BSOD seems to be no longer occurring.
-
- Product Manager
- Posts: 10099
- Liked: 2693 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: v12 BSOD
Thank you for sharing the solution.
I‘m glad it works now.
Best,
Fabian
I‘m glad it works now.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Bing [Bot] and 52 guests