[roger_smith]

Unless you have a definitive Indication, don't waste your time with a process of elimination.

To see exactly what's causing the BSOD, debug and analyze the MEMORY.DMP file located In the C:\Windows\MEMORY.DMP directory. Tools such as "WinDbg" perform the job well. By default, an "automatic memory dump" Is created at the time of the BSOD. For further analysis, you can configure a full memory dump via the Startup and Recovery options within the Windows environment. This will contain both user & kernel mode dumps.

I know I didn't go into detail, but I've been a computer repair tech for about 10 years now. I didn't need to go into a deep debug to sort this one out. chkdsk seem to get it back up and running and now i'll be imaging over to a replacement drive since this one is from 2008.

I'm not discounting windbg at all, trust me. I've used that many times in the past to find the cause of issues and fix them. In this case though I already had a pretty solid idea of the cause.