To: Ed Forrest who wrote (16879 ) 2/26/2001 11:58:19 AM From: mr.mark Read Replies (2) | Respond to of 110653 hi ed re, "I have a Bootlog.txt file.It is a hidden file. Have you looked to see if you have one?" yes, i just did. not there, and i do have folder options set to show hidden files. win2000 has an 'event viewer' that supposedly let's users see system logs and security logs, etc. a blue screen of death (bsod) flashes its usual coded jargon for a few fast seconds, then reboots. i changed the setting to not automatically reboot, because i want to further investigate these bsod's, and the event viewer isn't cutting it for me. i'm just not seeing enough detail. i must be doing something wrong, or not right, as the case may be. <g3> i have gotten two bsod's in the last two days. yesterday's message was very long and i only saw the very beginning before auto reboot (as i stated, that won't happen again because i've changed that parameter). the bsod error message was:"a device driver has corrupted the executive memory pool" a second bsod occurred after i'd disabled auto reboot, and i was able to review everything it said. basically it read:"PAGE_FAULT_IN_NONPAGED_AREA" in addition, there was reference to vsdatant.sys , which looks to be a TRUE VECTOR zonelabs device driver. that sort of points me in a direction. returning to the bootlog.txt file topic, i have discovered a couple logs in win2000 that i wish to view, but i'm encountering difficulty doing so. there is a ntuser.dat.LOG file and a software.LOG file that both appear to open with notepad, but the trouble is that when i attempt to open them, i get this message:"the process can't open the file because it is being used by another process" i'm fresh out of ideas on how to open these two files with notepad if/when my system keeps telling me the process is in use. i can't see it running anywhere. perhaps i'll give end-it-all a shot, then try opening the two LOG files. if anyone has any ideas (they don't have to be earth-shattering!) on any of the above, please chime in. :) mark