Skip to main content

BSOD still there - in the Win PE Recovery Disk

Thread needs solution

Hi all,

I also experienced the now semi-solved issue with a BSOD after reboot on WinXP SP3.

The new v468 snapAPI driver solved this in normal running Windows XP, but:

I do get the same BSOD when I try to use the generated WinPE recovery disk (based on WinPE 2.1, created by Acronis WinPE ISO builder). Seems the WinPE generator software still only uses the bugged driver.

Has anyone similar issues?

Anyone with an idea how to fix this?

0 Users found this helpful

I don't know if this would work or not, but have you tried replacing both the snapman.sys and snapapi.dll files in the C:\Program Files\Acronis\WinPE\WinPE\Files\Drivers folder with the updated version (468) and then recreating the WinPE ISO?

The other files in the update don't seem to be included in the WinPE files.

----

Post edited to include snapman.sys.

Thanks for the tip. I tried it and it works all right. :-)

Use both snapapi.dll and the snapman.sys from the drivers folder.

I hope Acronis fixes the product in the next update to cover this automatically. End-Users having to fiddle / copy around with individual driver files to fix bugs isn't the ideal way to deliver production grade software IMHO.

I had run a test after posting and found that the snapman.sys file was also updated. I suspected it would be, but it I didn't see it in the extracted files. I had to leave before posting the information. I've edited my post above to include it.

Thanks for posting back that replacing both the snapman.sys and snapapi.dll files worked.

Acronis should modify the update installer so that the appropriate WinPE files also get updated.