mbevks You look at the eopkg history to get a list of the packages that have been updated/rolledback. This will allow you to narrow the problem. According to your summary it doesn't seem to be related to an application but to something broader so focus on the system level things (kernel, drivers, system libraries, ...). You can check the journal logs of the problematic boot to see what are the last things the system when doing when it stopped responding.
Once you get a view on what could be the cause, you can search it on google and look on the bug tracker of the problematic software to see if someone else already reported the issue and what was the answer, if there is a fix, etc. Finally you can report it on the Dev Tracker.
Of course all this depends on your skills, but trying to find things by yourself is a good way to learn things and of course you can ask for help anytime. Of course it is more likely specific to your setup which can make it harder for other comunity members to assist you (it is easier when other people can reproduce the problem on their end).