Restore media offers 64bit and 32 bit

Either is fine - it really makes no difference.  A 64-bit bios can boot either 32 or 64-bit media and the restore functionality is the same.  It sounds like your restore completed.  However, you were running Windows updates and got a BSOD - this is not uncommon - especially if some of those updates are for hardware.  I don't think the BSOD is related to Acronis or the restore, but something that occured as the result of an update. You can download bluescreen view and see what the BSOD error was and research it online for more inforation. 

The only real limitation of the Acronis restore media (when recovering), is that you want to be sure to boot it in the same method as the OS was installed (if your machine is capable of both legacy/mbr/csm and UEFI/GPT).  If your OS is installed in legacy mode, make sure to boot your recovery media in legacy mode.  If your OS is installed in EFI mode, make sure to boot your recovery media in EFI mode.  The reason this matters is because if you boot in UEFI mode, the reocvery will convert the disk to GPT and an EFI partion (which this converion often works, but not always if your image was legacy/mbr).  And if you boot in legacy mode, it converts the disk to MBR with an MBR parition scheme (which will render your system unbootable if you have a UEFI/GPT OS image). 

This thread has screenshots and more details with examples:  https://forum.acronis.com/forum/121829#comment-378318 

Thank you Bobbo, I cannot see how I have a choice when booting from Rescue Media that I am booting Legacy mode or UEFI mode. The BSOD message was Error Code: 0xc000000e

Peter,

If your bios is only legacy, it shoudl be booting in legacy mode. If you check the pictures in the link I posted above, it will show the difference between what the Acronis menu looks like when booted in a partiuclar mode (UEFI = black screen with old school white DOS menu.... Legacy = blue background with GUI menu icons).

You might want to check the bootorder in the bios and make sure the hard disk is still first and unplug any additional external drives - especially any that might be plugged in with eSATA.  

Otherwise, if the error showed up, I would go back and re-seat all drives in the chassis and make sure connectors are snug and if the error still returned, I would try a Windows startup repair using the Windows installer disk.  IF that doesn't help, you could try a parition restore from another backup (if you have one) and only restore the MBR parition and see if that helps.