Quote: Originally Posted by gigagiggles
Unless the OS is caught in an endless loop during shutdown, it would be logging events as they occur. Pay a visit to the Event Viewer and see if there are any commonalities during shutdowns.
aah, excellent. I knew there was a bootlog and hoped there might be something like that for shutdown, too.
EDIT: I followed the 'view-details-last-shutdown-computer' tutorial, but can't find anywhere that will give me any details on what programs where doing what/when, etc.
EDIT2: scratch that, I understand how the log works, now (I've been expecting to see a list of events in a file, not each individual event separately logged as it is). According to the log, from the first to the last 'shutdown' related processes displayed, it only takes 1:30 to shutdown the PC. ...I'm going to have to time it tonight, 'cause it seems much much longer than that.
also, if you don't mind, I have two tangential questions:
- what's the best way to go about learning more about what Event Viewer tells me (specifically about 'kernal-power' critical events? -- I got a blue screen that auto-rebooted this morning before I could finish reading it, and these logs don't seem to tell _me_ anything helpful, it's always just 'kernal-power'. ... I don't know if that means my power supply fluctuated too much, or if kernal-power relates to the improper shutdown that followed the event, rather than the cause of the event.)
- also in Event Viewer is listed a few "controller error on \Device\Harddisk2\DR2" (which I assume means an external drive, since I only have one local disk (unless this is referring to my D: partition?). An error I thought was resolved which I made a thread about a few weeks back has been persisting lately, where my external takes a notable amount of time to display in my computer (it typically is visible as a 'device' in TrueCrypt sooner than Computer displays its unencrypted partition, that's how slow Windows 'autorun' type responses are being to its connection) and I also can't get my external drive to safely eject. ... not sure if this is what these disk error messages are about.