I work at an IT repair shop and we are constantly (as you can imagine) running across bluescreen issues. My normal process for diagnosing these goes like this.
1. test ram with windows memory diag
2. analyze dump files with bluescreenview
3. test hard drive for bad sectors
4. scan for viruses
if all the above come out good/clean and the .dmp files don't point to anything definitive i continue with a few more steps
5. update all drivers from manufactures website
6. uninstall any unecessary apps
7. uninstall/reinstall antivirus software
8. test run for 12 hrs to see if bluescreen occurs - if no bluescreen's we give back to customer - if bluescreens occur again for customer or one occurs during 12 hr run then i continue with a few more steps
9. hook up a new power supply of at least 100 watts greater than one currently installed and let it run for 12 hrs - if no bluescreens we give it back to customer - if it still bluescreens we replace the ram and give it back to customer
10. if we still see bluescreens after replacing the ram we backup data and wipe the system
What do you think of what i'm doing here and can anyone provide input on a better way to be more thorough on reading dump files? It seems like i'm running constantly into ntfs.sys, hal.dll, ntoskrnl.exe bluescreens and from what i read on these they don't point to anything definitive...