Nah, if things were well, nothing could cause a bsod like that.
You either have a defective video card, it's overheating from too much dust or improper fan operation, or the network driver is causing corruption.
I am noticing HWiNFO64A.SYS becoming unloaded in the crashes. I would definitely uninstall that software.
Still the same 0x116 error.
I honestly don't think this had anything to do with the patches. Bad titling on my part.Am I just paranoid or is it starting to look like the last round of patches from Microsoft was filling holes with C4 rather than Spackle?
Absolutely nothing to do with MS patches at all. The problem is 100% specific to his machine.Am I just paranoid or is it starting to look like the last round of patches from Microsoft was filling holes with C4 rather than Spackle?
Well it took a while but it was a defective card. Why can't these things die a quick painless death instead of a slow death, painful to all who care about it?Nah, if things were well, nothing could cause a bsod like that.
You either have a defective video card, it's overheating from too much dust or improper fan operation, or the network driver is causing corruption.
I am noticing HWiNFO64A.SYS becoming unloaded in the crashes. I would definitely uninstall that software.
Still the same 0x116 error tdr error.
--------------
You can edit the registry to either increase the tdr timeout value or remove it all-together. This is a workaround type of fix:
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.