Every 5/6 weeks i have to remove the side of my computer and blow it out with a can of compressed air,  if i don't do this my computer crashes  (Monitor goes black, seconds later computer will reboot itself) 

 

I bought my computer in August 2013,  6 weeks later it started to crash, i reinstalled and updated everything but was still crashing.   I done some research and decided to blow out the computer with gas,  and bingo it worked perfect......for another 5/6 weeks,  and it started to crash again,  i have being doing this process every 5/6 weeks since August 2013, if i forget, it crashes.   When i open up the computer, it always looks clean anyway so i don't understand it. 

 

After a crash i get this little screen like this.........

 

Problem signature:

  Problem Event Name: BlueScreen

  OS Version: 6.1.7601.2.1.0.768.3

  Locale ID: 2108

 

Additional information about the problem:

  BCCode: 116

  BCP1: FFFFFA8019EEB4E0

  BCP2: FFFFF880066FE128

  BCP3: FFFFFFFFC000009A

  BCP4: 0000000000000004

  OS Version: 6_1_7601

  Service Pack: 1_0

  Product: 768_1

 

Files that help describe the problem:

  C:\Windows\Minidump\071515-14398-01.dmp

  C:\Users\poppet\AppData\Local\Temp\WER-98967-0.sysdata.xml

 

The research i have done points me in the direct of a driver problem.  

 

I am not looking for a golden answer here as i know these are very hard to figure out 

 

Here is my Question:

 

I can live with this problem ok, and if that's what i have to do, well so be it  BUT is it normal that such a small amount of dust can cause this so regularly

 

My house is spotless clean 

 

My house is spotless clean 

 

 

You can come over then. HELP ME WITH THIS MESS!

Friends of mine quite often ask if I can fix there pc. The very first thing that I do is fire the compressor up & blow um out, 9 times out of 10 it fixes the problem ?. For you sounds maybe more like a small build up of dust then temps get too high , you could try reseating the cooler on the cpu , get a cpu temp monitoring software maybe (HWMonitor) is one & see if things are getting hot

Good luck

Riche

If it is a driver problem, then it would probably occur more frequently. Since it's just a plain blue screen without any details of a specific driver, then it's probably hardware. Knowing how hot FSX can make a CPU and GPU, I would also suggest you monitor your temps.

The bugcheck code is 0116 which indicates a driver issue. It would be nice to see the error report. You can download the BSOD Viewer at the following link - http://www.nirsoft.net/utils/blue_screen_view.html. Note at this link a sample BSOD report. If you look below the dump report to the File Names, anything showing up in pink (you might like that color) indicates the most likely drivers that caused your crash.

 

I seriously doubt it is a problem with dust or dirt in your system. Maybe if the computer is really old and you bought in in 2007 and never opened it up and cleaned it, then it might be a little dirty.

 

Best regards,

Thank you Riche and Daniel for you reply's

 

 

 

The bugcheck code is 0116 which indicates a driver issue. It would be nice to see the error report. You can download the BSOD Viewer at the following link - http://www.nirsoft.n...creen_view.html. Note at this link a sample BSOD report. If you look below the dump report to the File Names, anything showing up in pink (you might like that color) indicates the most likely drivers that caused your crash.

 

Hello Jim,  i see what you mean about the pink thing      I downloaded the file here it is.  Click on it and it will blow the pic up 

 

Hello Jim, i see what you mean about the pink thing I downloaded the file here it is. Click on it and it will blow the pic up

The nvlddmkm.sys belongs to the Nvidia device display drivers. The dxgkrnl.sys and dxgmms1.sys are Windows OS system drivers related to graphics. What you need to do is uninstall your Nvidia drivers and then run a system registry cleaner like CCleaner. I use Advanced System Care 8 at least once a week to keep my system clean. CCleaner works well too. You just want to clean the registry. Once your registry has been cleaned, then go to the C:\Nvidia\DisplayDriver folder and reinstall your latest drivers. Make sure you right click the installer and select Run as Administrator. Make sure UAC is disabled and make sure any anti-virus program is not running in the background to scan the display driver installer.

 

You should also scan your system for corrupted system files - https://support.microsoft.com/en-us/kb/929833 . You can run this program before or after uninstalling/reinstalling your display drivers.

 

Hope this helps.

 

Best regards,

Great Jim, thank you for the information, I will report back after the weekend.

As an addition to Jim's advice.

 

Instead of using CCleaner use DDU, it's designed to remove GFX drivers:

 

http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

 

Also i have been having BSODs with the latest nVidia driver 353.30.  Uninstalling these drivers did nothing for me, i have had to roll back to 350.12

Also i have been having BSODs with the latest nVidia driver 353.30. Uninstalling these drivers did nothing for me, i have had to roll back to 350.12

Good advice Ian in regards to the NVidia driver removal program. I was going to mention that but I'm not familiar with it.  CCleaner does not remove the NVidia files but does remove the entries in the registry.  In regards to your BSOD's, make sure you have Admin Privileges and you are in charge of your computer and not your computer system. The fact that you have to roll back to a previous driver indicates to me that your anti-virus or Windows UAC did not allow the new driver to make changes to your registry thinking the change was some evil hacker trying to take over your computer by changing a registry entry. When you rolled back, the registry liked the old driver entries. This is about the only explanation I can see why new drivers work for the majority but not for some. There just is not that much of a difference in drivers.

 

Best regards,

 

 

Good advice Ian in regards to the NVidia driver removal program.

 

Thanks Jim, DDU uninstalls everything nVidia (or for that matter ATI) related including registry entries.

 

I install everything as admin, it's something with 353.30, I have used DDU to uninstall each driver and in turn install the next one up.  The only one that causes BSODs is 353.30.  My system is far from unique, but i do run nVidia surround, certainly there are people on the forums experiencing BSOD with 353.30, my system is stable now on 353.06.

 

I am somewhat different to Elaine in that my system would die within about 30 minutes of either GTA V or P3D, but only on 353.30, every other driver i tried worked fine.  The other option would be to remove my overclock, but considering 06 works i'll leave it until the next driver release.

Ok Jim I removed old drivers, used Ccleaner to clean registery and reinstalled Drivers, So far so good. Thank you Jim for the advice.