Since I have no experience with the EaseUS backup software, I cannot judge whether removing it will help. I do seem to remember another thread which was using it and had some of the same problems as you. However, that system had also used a couple of other boot modifiers which could have been the actual cause of the problem. Although I do see some extra entries in your system, so you may be the same poster.
Try running the Reagentc command to see if you can register the Recovery Tools on your install. If you want to see what the path is to the Winre.wim file, use the Admin command window and do a
dir /a command in the hidden, system folder, C: \Recovery.
To illustrate the problem you seem to be having, in the BCD store, you are showing a GUID number for your RecoverySequence entry. That GUID number is showing a Ramdisk which loads the recovery tools from the L: drive, which it should not do.
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {65b0ddfa-1bee-11e4-9fc9-b4b7151f36a1}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {c9118be8-0f9d-11e4-bca5-d4d3f02c1aa1}
nx OptIn
Windows Boot Loader
-------------------
identifier {65b0ddfa-1bee-11e4-9fc9-b4b7151f36a1}
device ramdisk=[L:]\Recovery\65b0ddfa-1bee-11e4-9fc9-b4b7151f36a1\Winre.wim,{65b0ddfb-1bee-11e4-9fc9-b4b7151f36a1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[L:]\Recovery\65b0ddfa-1bee-11e4-9fc9-b4b7151f36a1\Winre.wim,{65b0ddfb-1bee-11e4-9fc9-b4b7151f36a1}
systemroot \windows
nx OptIn
winpe Yes
