System Logging Tools

I'm currently experiencing the occasional BSOD. Unfortunately it seems that the current tools that I use to log system information do not actually save until properly exited, thus when I experience a BSOD the file is wiped clean and I cannot check up on various processes and temperatures etc... Perhaps someone here would be so kind as to recommend a tool that writes straight to a log file without the problem of losing data if a BSOD occurs.

Cheers

I think windows event viewer logs bsods.

type "event viewer" in the windows search box (start menu) or un "Run" if you're using an older version.

Look under Windows Logs> System

I am aware of the Windows Event Viewer, I probably should have put this in the OP. Unfortunately it does not categorically state what was occurring in my system before the point of the BSOD.

BlueScreenView will go so far as to tell you what line in what system file caused the BSOD, assuming your system was able to write a dump file.

You're probably better off testing one piece at a time, CPU benchmark, GPU benchmark, MemTest, hard drive diagnostics, and figure out which is causing the problem. Since it's a BSOD, no programs will get a chance to output up-to-date logs at the time of crash. Only the OS gets that chance, and it generally doesn't do ****.

However, you could try things like ProcessHacker (advanced task manager) or hwmonitor (temperatures).

For individual benchmarks:

CPU: http://www.techspot.com/downloads/4965-intelburntest.html
GPU: http://event.msi.com/vga/afterburner/download.htm (Kombustor install included in the Afterburner files)
RAM: http://www.memtest.org/
HDD: http://www.hdtune.com/ (Never used it, but it looks alright)

Testing RAM through a USB/CD/Floppy boot disk will be better.

Also things you can try through Command Prompt without 3rd party stuff:

chkdsk [drive letter] /r
Scans the entire drive/partition for file structure and data corruption.

sfc /scannow
Scans the operating system's files for corruption.

If the BSODing happens in Safe Mode as well, it's almost assuredly a hardware problem, requiring at least a reinstall of the OS.