- Scheduled wake from bios
- Hardware such as network card, keyboard, or mouse
- Scheduled tasks (find in control panel -> admin tools -> task scheduler)
My bios doesn't support scheduled wake, so I can't see how this could be a factor in my case. I obviously want my keyboards and/or mouse to be able to wake my computer when I press it. The network card is disabled from waking. It has to be a scheduled task right? Who knows.
I researched this issue time and time again and all will say go to the command line and enter "powercfg /lastwake" and "powercfg /devicequery wake_armed". Last wake supposedly tells you what woke up your computer, but I get some shitty "Wake History Count - 1 Wake History  Wake Source Count - 0" which tells me or anyone else NOTHING. Device query tells your what devices can wake your computer. Only things are the keyboard and mouse, soooo.... yeah, I'm at a wall.
There's this magical thing called scheduled tasks/task scheduler in control panel. You can see the tasks that are able to wake your computer, which is great, but some brilliant Microsoft engineer thought it great to show tasks located in child folders and not in the parent. I have no belief that it is challenging to fix that especially since it is a simple tree traversal. I digressed enough. I found a magical left over task called mcupdate_scheduled in Microsoft/Windows/Media Center which from what I see looks like precisely what is waking my computer given that it scheduled to run at the time and has permission to WAKE MY COMPUTER to run the task. Who the heck thought it is a good idea to give an updater WAKE permission as if it were an important update. I don't think media center exists anymore, so the task should have been wiped along with Windows 7. Granted that this is easily overlooked, I am lenient on this, but the permission to wake the computer is an unacceptable annoyance for this task and I can't see why it decided to start running once Windows 8 was installed. Moreover, it can't find whatever file it was supposed to run, making it a useless task. DISABLED!
Anyway, I scoured all of the tasks and it looks like that could have been the problem. I'll see what happens tomorrow.