Holding your users accountable for their actions is one of the trickiest things about being an IT Consultant. If a user tells you he didn’t delete or move a file you can’t just sneer at him and accuse him of lying, no matter how much you want to. You must have proof. A nice solid document showing the who, when, and where of the users malfeasance. Enter file system auditing.
In the course of running my vast empire it occasionally occurs that one of my subjects neglects to follow my sage advice regarding backups and is struck by the horror of data loss. In the event of such a cataclysmic situation I turn first to my trusted allies at Recover My Files.
In the course of my time as the undisputed overlord of all things technology related it has frequently fallen to me to delve into the Windows Event Logs in search of proof that a mischievous user has deleted their own files or to wrest from them a reason for the demise of a database. Each time I gird myself to wade through the logs I cringe for a moment at the lack of functionality inherent in the basic Event Log Viewer until I remember that I no longer use that malformed and crippled child of Redmond for my log perusal. I have moved on to better things, specifically the Event Log Explorer from FSPRO Labs.
STOP: C000021a {Fatal System Error}
The session manager Initialization system process terminated unexpectedly with a status of 0xc000026a (0×00000000 0×00000000)
The system has been shut down.
No one wants to see something cryptic and terrifying instead of their comfortable windows login page, but sometimes it happens. Sometimes you just get a flash from the screen and then the system reboots, but behind that flash is one of these nasty messages. Since my loyal subjects fear and despise these dreaded visitations by the BSOD I feel it is my sworn duty to vanquish them, read on for some comforting steps to recover from a BSOD attack.
Translator
Donate
