The second error happens because explorer.exe is clos[ed]ing.
Memory has been unallocated, however, another program (most likely a garbage-ware, or lame/poor written software app is having trouble shutting down on time, and when it does manage to finally shut itself down, it has to report to explorer.exe.
Now since explorer hasn't closed ALL the way, it gives you the error, and because it already unallocated the memory where the function that the lame program is called, it gives an error generated by the system, and the system tells you that it is explorer.exe's fault.
In some cases, this is caused by simply having an old install of windows (not re-installing for a few months).
In any case, I've seen this error many times, and it has never hindered work while the computer is running.
It's just a giant pain, and will not likely go away until you reinstall.
Best of luck.
