General :: Android Gets Into A Hotboot Looping State For Unknown Reason

My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only. After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop). It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications.Forcing a reboot (by holding the power button) or removing the battery able me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.

After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.

I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.

I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?