Rightho! So my computer has been BSoDing for a while now. I did get it checked out by some overly expensive computer repair man. He basically told me that my computer was dusty and that it needed hovering... So I hovered it and the BSoDs calmed down... However after a few months it came back again.

This is basically what happens:

• I open the game (see list below)
• Game plays fine fow about 10-15 minutes
• Computer BSoD's and restarts

It happens on a fair few games:

• Minecraft
• L.A Noire
• Sims 3
• and more

I was reading over some other threads and it seems that I should mention that I do have Norton 360 installed.
I have uploaded my PCHF BSoD stuff to Mediafire and you can check out my System Specs on my profile page.
Thanks in advance!
Kezz

download speedfan and let us know what it says.
http://www.almico.com/speedfan446.exe

Thanks for the reply! I really appreciate it

I'm presuming you want the fan speed and the temperatures. If you want anything else just let me know!

Fan1: 495 RPM
Fan2: 800 RPM
Fans 3-5 are 0 RPM

GPU: 55C
Temp1: 86C
Temp2: 36C
Temp3: -57C
HD0: 32C
Temp1: 40C
Core 0: 43C
Core 1: 38C
Core 2: 43C

In fact after writing this I saw the Exotics page. It looked interesting so I thought I'd post that too:

MediaFire link to Exotic Screenshot

Thanks again!

@merlin and anyone else who has been watching this:

In an effort to sort it all out I uninstalled about 30-ish unused program's from my PC. When I next played L.A Noire, to test if it had fixed the problem, it still BSoD-ed but after about 30 minutes.

Thanks again for your help!

Hello.

Please download this tool and save it to the desktop. Run it as admin and attach the produced archive. If the archive size is over 1MB, upload it here.

Also, let's do a more aggressive temperature test.
Download this http://damage.vigilantesoftware.com/ and this http://www.alcpu.com/CoreTemp/
Start both applications at the same time, for about 10 minutes. Then create a screenshot of the core temp window, by simply pressing the F9 key.

Now download this http://www.ozone3d.net/benchmarks/fur/
Run the burn in test for 10 minutes and create a screenshot of the main window, attach both images here.

Those temps are mighty high especially if your just surfing the web/ My bet is it is the heat causing your meltdowns. run the tests mkey posted.

PCHF Archive: attached
Core Temp Screenshot: attached (also I noticed that the CPU made a completely different sound to how it normally does when it BSoDs. When BSoD is imminent the CPU makes a violent whirring sound that is quite loud. Core Damage only made a small fan noise. Although by about 5 minutes the small fan noise became faster.)
Burn in test: attached (my computer became as slow as fudge and the background scared me. Also the CPU sounded the same as it does before a BSoD)

EDIT: I uploaded this post beffore the FurMark attachment because I was worried it would BSoD the PC and lose all the stuff I wrote.

As I predicted, FurMark caused a BSoD after 2 minutes.

You have only very old memory dumps in that archive, for some reason new dumps are not generated properly. I analyzed three of them, which go back to April of this year and they all point in the same direction: VIDEO_TDR_FAILURE which is consistent with what you're telling us. That may be a GPU driver problem or a problem with the GPU itself. However, I need fresh memory dumps.
Once you started the furmark application, did you catch a glimpse of the the GPU temperature, where was it heading?

Go to

Code:

c:\windows\minidump

folder and delete all the .dmp files you have there, there are loads of them and they are all old.

Now go to startup and recovery options dialog as stated here http://www.pchelpforum.com/xf/threa...se-read-before-posting-in-this-section.27453/ and make sure it matches these


Finally, reset your page file. Go to control panel > system > advanced system settings (list on the top left) > performance settings button > advanced tab > virtual memory change button.

Uncheck "automatically manage paging file size for all drives" and on the list choose every drive/partition you have a paging file installed on. Select "no paging file" and press set after each selection. Confirm with OK and reboot.

Once back in windows, go back to this window, check "automatically manage paging file size for all drives" and click OK. Reboot once again.

When all of this is completed, cause a few more crashes and rerun the log collector.

Okie dokie! Done the first set of instructions! I thought that, before I get on to causing crashes, I should let you know that it was storing dumps into some massive file. The other one when you select Small Memory Dump. Also, although it should restart on every crash, it stopped doing so a couple of months ago. I have to manually turn it off at the plug to get it off.

I caused the crashes with FurMark (hope this is ok) and the GpU temp got to about 108C when te crash happened. I'll be uploading the PCHF stuff shortly!

That temperature is extremely high, at least 15°C above the comfort zone.
One of the moves you'll want to pull asap is cleaning inside your case. Here's some solid information on the subject http://www.pchelpforum.com/xf/threads/all-browsers-are-using-too-much-cpu.136134/#post-862836
Cleaning the CPU area should be easy, however if your GPU is working up such temperatures, it may very well be possible it's heavily clogged and it will probably need to be disassembled before you can clean the dust out.

Avoid stressing your system further before you follow through with these actions.

Surprise, surprise there are no dumps to export when using your PCHF. Does this mean my computer is not in fact BSoD-ing?

Do you see a blue screen when crashing or not?

Sometimes memory dumps are not generated due to improper settings (more info in the pinned prework topic) or some other software/hardware related problem.

Ah actually no... It just all goes black :/ Have I been mega nooby? I was told it was a BSoD but now I'm not too sure.