Restore complets successfully but BSOD on boot...

[kirkgj]

... using Veeam Endpoint to backup server to local NAS. Restore completes successfully but the server BSOD with pcw.sys. Able to boot into safe mode. Not sure why the restore from Veeam is not working.

Hardware: Dell R220
OS: Windows Server 2008 R2 std.

Kirk

[Mike Resseler]

Kirk,

Are you restoring to the same hardware? PCW.sysv(performance counters for windows) BSOD can be caused by a few things and the most common is a hardware or software change...

If this is not the case, can you do the entire restore again? After the BMR, before rebooting, please go to the tools menu in the recovery media and export the logs to a flashdrive or your NAS or something. Upload these files to a dropbox or onedrive or similar. Then sent a DM to Dima P. from the forums here and give him the download location of the files so we can investigate

Thanks

Mike

[Vitaliy S.]

I have seen BSODs caused by some antivirus software installed in the system, worth checking as well.

[Dima P.]

Hello Kirk,
Please send me a PM with the download link. Thanks

[kirkgj]

Message sent to Dima with the logs.
The restore is to a different server but the same model from Dell, a poweredge R220. Original server was replaced with same under warranty... or should be exact same. There could be some hardware differences or maybe a bios setting that is presenting a hardware difference. Looking into the bios now.
Thanks,
Kirk

[kirkgj]

Also, no antivirus on this server has ever been installed.

[Dima P.]

Kirk,
Thanks! I’ll pass the logs to QA but they will start checking the logs only on Monday. I'll follow up once we find anything.

[VER]

Any news on this? I'm experiencing the same (bsod due to pwc.sys after a bare metal restore), in my case on a HP folio 1040 though.

[Dima P.]

Hello Wouter,
The logs of the OP are still under investigation. If you experience the same behavior please collect the restore log (it should be placed in your backup repository) and share it with me via dropbox or googledrive. Thank you.

[guebert]

Hallo,

Has the problem been solved? How?

Michael

[Vitaliy S.]

Hi Michael,

Can you please collect the logs and let our dev team take a look?

Thanks!

[guebert]

Vitaliy,

I do not have this problem at the moment. I'm interested in this topic, because I intend to use Endpoint BAckup and want to know, if it works. So (how) did you (Veeam) solve the problems?

Michael

[Vitaliy S.]

Michael, I haven't heard from our dev team yet, but I will double-check tomorrow and will let you know.

[Dima P.]

Hi guys,

A private fix is on its way. I’ll update this thread when its ready so we can start testing the solution. Thank you for your patience.

[Dima P.]

Hi all,

I’ve just shared the fix with Kirk. Let’s see how it goes.

[hoFFy]

Did the fix work? Has it been a fix for creation of backups, or a fix for restoring from backups? I'm asking, because this could mean that eventually many backups are not restoreable, if the patch isn't applied. If the patch could be somehow applied in case of restore is needed, then it's not THAT critical. But if this means that backups are eventually not useful... OMG

Correct me, but I assume the fix will be also a part of the upcoming VEB version next month?

[Vitaliy S.]

Correct me, but I assume the fix will be also a part of the upcoming VEB version next month?

Yes, that's correct.

[Dima P.]

Panic mode - off

The fix refers to the Recovery Media and drivers injection into restored machine: some users reported it caused hardware conflicts with the OS.

[hoFFy]

Panic mode - off

[VER]

Hi all,

I’ve just shared the fix with Kirk. Let’s see how it goes.

Is the fix applicable to case 00951035 as well? Haven't heard anything from support so far...........

[Vitaliy S.]

Wouter, according to this case history, our support team replied 15 minutes ago with the fix instructions.

[VER]

Wouter, according to this case history, our support team replied 15 minutes ago with the fix instructions.

Received it a couple of minutes after my post, thanks.

Followed the instructions and was able to succesfully perform a bare metal restore.

[AidasIT]

I also have this exact problem at the moment.
Upon bare metal recovery (to the same machine, same HD) unable to boot with BSOD message specifying pcw.sys
Custom build with Asus P8Z77-V PRO motherboard and OCZ Vertex SSD.
Unable to open support case from withing Veeam software, as machine is not bootable for the moment.
I understand this is related to driver injection upon recovery? Would recovery logs be needed too, or possible to receive generic fix?

Many thanks
Aidas

[Vitaliy S.]

Recovery logs would be definitely welcomed, however you can open a support case from another computer and give a reference to this thread, so that your engineer could understand what fix is required. Thanks!

[Dima P.]

Aidas,

I've sent you a PM with a fix and instructions. Let me know if it helps.

[davrex]

Iam also having this problem to restore 2 computers does the fix work on already backup data or only on new backups?
Is it possible to get the fix?

[AidasIT]

Aidas,

I've sent you a PM with a fix and instructions. Let me know if it helps.

Have raised support ticket yesterday as suggested, promptly received instructions for a fix - and the issue was fixed after 1st attempt.
Brilliant stuff!

Many thanks
Aidas

[Vitaliy S.]

Is it possible to get the fix?

Yes, just open a support case for that. Thanks!

[kirkgj]

As the original poster, I thought I would update this thread with my results.
I was able to get the restore to boot successfully by selecting boot from last known good configuration after pressing F8 following the restore. That solved my immediate need.
I did receive the fix from Veeam earlier but didn't have a chance to test it. I then received another new Dell R220 this week. I have tried the fix and it solved the problem completely. Restore completes and the server boots properly on the first try.

Kirk

[Dima P.]

Thanks for checking the fix. I am glad to confirm that this drivers issue will be addressed in the 1.1 release. Moreover, it will be possible disable the driver injection upon bare metal recovery. Stay tuned!