unexpected shutdown BSOD

Good job! Pain55,

I placed a referal link to here back at your original thread.

I have to agree about those .dmp files. You need special programs to read them.
I have been looking at this link: Configuring the "Debugging Tools"

I hope once I read through it enough, and understand how to set up the tools on my machine I will be able to help more.

Hello and Welcome !

Run a Hardware Diagnostic (Memory and Hard Drive) follow this link for instructions Hardware Diagnostic !! « Captain Debugger

Try this free video stress test: FurMark: Graphics Card Stability and Stress Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net

FurMark Setup:

- If you have more than one GPU, select Multi-GPU during setup
- In the Run mode box, select "Stability Test" and "Log GPU Temperature"
Click "Go" to start the test
- Run the test until the GPU temperature maxes out - or until you start having problems (whichever comes first).
- Click "Quit" to exit

Try this free stress test: Free Software - GIMPS

Prime95 Setup:

- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Hope this help,
Captain

pain55 said:

Thanks my friend, you've been of great help.

Your welcome,

pain55 said:

I just wanted to know, have I collected the dumps correctly, or have I missed anything out?

That, I could not tell you for sure, but from Capt. Jack's response I don't think so.

The windows_nt6_bsod_jcgriff2.zip file was developed by one of the members here at W7F ( jcgriff2 ) to gather information to help diagnose BSODs, and looks to be a pretty comprehensive report.
You do not need the tools I mentioned earlier to view it, just okay or allow your way through it to view.

When I made my Good Job! post I only saw 1view of your report. By the time I recieved notification of Capt. Jack's reply there were two, and now there are five.



In my humble opinon, I think what is happening here is:

• Capt. Jack has reviewed your report has made his recommendations as to how you are to proceed, and is awaiting your results.
• Other BSOD Diagnosticians have also reviewed your report, but hesitate to post anything until you post back for fear of going down a blind alley. Sort of what we were doing in your original thread.
• Successful troubleshooting follows an organized set of steps, and you have taken the first by posting the windows_nt6_bsod_jcgriff2.zip file.

Is whocrashed part of what you were asked to do? I don't see it listed above...

Hello,

You files doesn't have a Dump file. Seeing at your previous thread you have mentioned that you never had BSOD. Then you won't have any Dump files. By default WER is set to generate Dump files upon crash.

Whocrashed just get the probable cause from a Dump file most of time it blames the Windows Kernel is not very reliable.

Now about your issue i suspect it might be a Hardware issue in that case the Dump files won't be very helpful even if you had one.

Hope this helps,
Captain