New
#21
You're welcome, as always Arc.
Just some things I noticed in Speccy. They may or may not be causing a problem. I'm not sure how any of them would cause a video card problem.
1. Bitdefender and Windows Defender are both running.
2. You are also using AVG Tune up
3. You are using Team Viewer at this time.
3. You have a Asus P9X79-WS Quad channel with 3 of the 8 ram slots used. It should be 2, 4, 6, or 8 slots used.
4. Your ssd in hook to Sata II at 3.0 gb. instead of Sata III at 6.0 gb.
With all that information we still need to know what power supply you are using.
You state that it is a custom build so if you could put your power supply in your system specs.
You need at a minimum a 550W quality power supply with two 6 pin connectors for the video card.
Last edited by Layback Bear; 20 Oct 2014 at 12:18.
Icit2lol, when I clicked the Yellow button in your recommended program I get this:
I assume disabling it would be a good idea?
I think this is what you wanted to see:
Layback Bear, I've got a 750w power supply from Cooler Master. Also, the RAM setup isn't causing the issue, I only took one of my RAM sticks out to see if it would stop causing this issue, so it was happening before hand.
Thanks for the help guys.
have you had any more BSODs? If you have upload the same file again. Did you reinstall the driver like the tutorial said and run Furmark again? Set the custom fan profile?
I installed the driver as recommended in the tutorial. As soon as I went to run Furmark, Blue screen.
Rebooted and ran it again. Got to the 13 Minute mark and it was at 89 Degrees. Went to take a picture and Blue Screened again.
Dump files attached.
Same thing again Video TDR
I'm not really sure reinstalling the drivers would help or not. If you do, try a different driver and use the same procedure. NVIDIA Drivers - Avoid ProblemsCode:BugCheck 116, {fffffa8013fc4010, fffff8800ff7851c, ffffffffc000009a, 4} *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+91951c ) Followup: MachineOwner nvlddmkm start end module name fffff880`0f65f000 fffff880`10333000 nvlddmkm T (no symbols) Loaded symbol image file: nvlddmkm.sys Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys Image name: nvlddmkm.sys Timestamp: Sat Sep 13 14:59:50 2014 (5414A236) CheckSum: 00C8E3A6 ImageSize: 00CD4000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Also, you may check and see if you have the latest DirectX How to install the latest version of DirectX
Also please go to device manager and expand graphics adapters and post a screenshot of the wholw device manager. This will tell you how to post a screenshot.
Screenshots and Files - Upload and Post in Seven Forums
I assumed you meant expand Display Adapters in the Device Manager.
I tried using Arc's idea again, installing the older driver. While this does seem to make the crashes less frequent, it still happened.
Already have the latest DX.
Unless you are overheating, the problem is your Card, Motherboard or PSU. You may try putting it in a different slot on your motherboard, just to see.
Though it is not an even regularity, but it is there. BSOD during Furmark. That is the point.
Your GPU is failing to handle a stress. Sometimes it cannot, sometimes it can, but not for a long time, and sometimes it manages the stress for a fairly good time. Overall, it has started failing.
Still, a good firs step will be to try the GPU in a different PCIe slot, as essenbe suggested. You have alternative slots .... If the issue continues even in the other slot, you will have to apply a different card, at least on a test basis.
I hoovered out the PC. (Paying particular attention to in and around the graphics card)
I also pushed it in, to ensure it was fully connected. No crashes since then.
It's still early days and it could very well happen again. At the very least it seems to of improved the stability. Or it could be a coincidence.
Last edited by Owen27; 21 Oct 2014 at 07:30.