That's correct, it's a basic Windows driver, although Windows should really have it's own qualified driver for that card so you might want to try right clicking on the device in Device Manager, go to Update Driver Software. Search for it first to see if there's a Windows one you can use (default Windows drivers should never cause the system to blue screen but are likely to have reduced functionality than that of any driver you would download from ATI). You could also Browse for your driver software, and select Let me pick from a list of device drivers on my computer. Any Windows drivers there will have "Microsoft Corporation" listed next to them in brackets.

There are no log files attached here Vince. :/

Sorry, the log files are there but there are no generated log files from the BSOD. Can you double check those settings for the moment to make certain they are correct, and in the meantime, if any further stop errors occur, please can you keep an eye on the first set of numbers (octet) that appears in the stop error. If there really are controller problems on board (as suggested in the event logs), it could also explain why no further log files are being generated. The result of HDD/Controller problems would usually mean that the system has lost access to the disk. If the disk is not available, it will cause the system to freeze or blue screen, but there is also nowhere for the system to save their log files to. Common error codes that appear in the blue screen if this was the problem would be 0x7A (0x0000007A) and 0xF4 (0x000000F4).

If it's a hardware problem (such as the before mentioned controller issues), then re-installing Windows wouldn't resolve the problem, you would be back at square one. If we could at least get the error code can sometimes give us a hint of what the problem is, and then decide at this point what to do?

If that is the driver name that is appearing in the BSOD, then there's no reason why it wouldn't generate a log. Is there any chance you could double check the c:\windows\minidump folder to verify no logs have been generated here?

After a clean installation, you would need to follow the troubleshooting section again to ensure your setting are correct for generating the minidumps (in Windows 7, by default they only create full kernel dumps which are too big to upload here). If the minidump folder is still empty, we'll look deeper into possible HDD issues.

Can you also confirm the BSOD's continued before you had installed any additional 3rd party software and drivers? you shouldn't have need to install any 3rd party video drivers for example, there would have been already included... it's a mistake a lot of people make after a clean installation to solve a problem, install the same software that was installed previously, and not realizing that the problem has just been reloaded onto the machine once again.. even though from all indications so far suggest you may have more than one (likely hardware) problems to deal with here.

Hi Vince,

I think the confusion there is that your BSOD's are likely to have caused multiple problems, at least, there's not way that dust from video slot would have caused the previous stop errors.

The latest stop error you mentioned (0x116) however, is the result of TDR (Timeout Detection and Recovery), a feature of DirectX. When the system detects that there is no response from the GPU (timed out), it will try to recover from this condition by resetting both GPU and driver. A successful reset will leave a message in the system tray to show the recovery was a success. A failed reset will result in this BSOD. Due to the fact that the system was not able to recover from this condition is usually a pretty clear sign that the problem was caused by hardware, usually overheating, overclocking, insufficient power or general hardware failure will cause this. If clearing dust from the system has resolved the 0x116, then it seems overheating was the likely cause. Was anywhere else in the system clogged up at all?