SSR 2013 R2 getting stuck constantly

Are you sure there is nothing in the Windows application event log? It sounds like a process is crashing which would normally be logged there.

Can you also confirm the exact version of SSR you have (check in Help/About for version details).

If you could provide a screenshot of the error, it would be helpful as well.

Version is 11.1.4.55331

I'm looking through the logs now. At 1:00AM Symantec starts the backup.
A bunch of SQL stuff, I/O is frozen, then I/O resumed.

Some ESENT warnings:
"DFSRs (1940) \\.\C:\System Volume Information\DFSR\database_CC12_5F3C_125F_2AAA\dfsr.db: A request to write to the file "\\.\C:\System Volume Information\DFSR\database_CC12_5F3C_125F_2AAA\dfsr.db" at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes succeeded, but took an abnormally long time (15 seconds) to be serviced by the OS. In addition, 0 other I/O requests to this file have also taken an abnormally long time to be serviced since the last message regarding this problem was posted 172812 seconds ago. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem."

Symantec messages that it completed successfully
A bunch of Security-SPP messages that the service is starting, then one that it stopped.

Then RunTask error. Every ten minutes RunTask.exe faulting application and a bunch of Software Protection service completions.

Meanwhile Symantec is down at the bottom chilling like this:

I can open Symantec and view everything, if I try to run a new backup it says recovery point from same job still in progress.

As the backup starts at 1am and the RunTask.exe error is not seen until 2:32am, I'm not convinced that is the cause of the issue you are seeing.

Can you export the application event log to .txt format and attach it here? Also, please provide the following log file:

C:\ProgramData\Symantec\Symantec System Recovery\Logs\Symantec System Recovery.log.txt

RunTask.exe is a Microsoft process so you may need to speak to them to understand why it's failing.

Here you are.

When was the last time you saw the issue with SSR? I ask because it looks like the backup was successful on the 27th:

2/27/2016 1:00:22 AM High Priority Info: Info 6C8F1F65: The drive-based backup job, Drive Backup of Recovery (*:\), (*:\), (C:\), has been started automatically. 0x00 (Symantec System Recovery)
2/27/2016 1:08:39 AM High Priority Info: Info 6C8F1FF2: Drive Backup of Recovery (*:\), (*:\), (C:\), the scheduled drive-based incremental backup job is completed successfully. 0x00 (Symantec System Recovery)
2/27/2016 1:09:31 AM Medium Priority Info: Info 6C8F1F5F: Created offsite copy [Offsite B]\CHMSERVER_C_Drive003_i006.iv2i.

27th was the last day it worked.

I saw the issue a couple more times before this, so I tried a bunch of the troubleshooting steps I mentioned above.

That's why this is weird it's showing it completed but, now it's stuck at 1% Creating Recovery Point.

Last time it did this was the 20th. I restarted the server Monday. Worked Tuesday to Sat. Stopped working again. Haven't been able to restart the server again yet.

Did it not fully complete on Sat? I can see it stopping at 1:09 then the 28th it says it's still in progress.

It was successful on the 20th, yes ..

2/20/2016 1:00:11 AM High Priority Info: Info 6C8F1F65: The drive-based backup job, Drive Backup of Recovery (*:\), (*:\), (C:\), has been started automatically. 0x00 (Symantec System Recovery)
2/20/2016 1:13:17 AM High Priority Warning:  0x800706BA (Symantec System Recovery)
2/20/2016 1:13:17 AM High Priority Info: Info 6C8F1FF2: Drive Backup of Recovery (*:\), (*:\), (C:\), the scheduled drive-based incremental backup job is completed successfully. 0x00 

I don't spot anything obvious that could be causing this so I think a support case may be needed as more detailed log analysis will be needed.

However, you may want to contact Microsoft first to try and get the issue with RunTask.exe fixed. It would be good to eliminate this as a possible cause..

Lol, well we've got a dilemma, I'm talking to Microsoft now and they keep telling me RunTask is your problem. Gah!

Oh, really?

Did they elaborate on that with any detail/evidence of why they think it's our problem?