The Furmark screen looks odd .... and that means your graphics card is not rendering the proper thing. A running furmark should look like this:
I think it is enough to address it as a failure from the part of the graphics card. I would suggest you to apply any other graphics card there and see the situation.
I thought it might have been just because I didn't check "dynamic background."
but I checked it and then ran it again.. and woah.. it looks very odd compared to your picture.
Sorry, it's probably a really basic answer, but.. how do I go about applying another graphics card there? >.<
Also, I don't know if this means anything but when I select either of the GPU benchmark preset settings (1080 or 720), it looks perfect just like in your screenshot. But if I select GPU stress test or GPU benchmark (user's settings) it looks all messed up like in my screenshots.
I get the same screen for all the tests.
If you can borrow a graphics card form your friends or family for a testing purpose only, you may apply that card and see if that causes the BSODs there or not.
But before that, I would like to wait and observe how it goes after the other things of post #10. If BSODs continue, further troubleshooting will be required.
I don't think I can borrow a graphics card from anyone right now, but I can try to find someone if I need to.
I've had a few BSOD's since my last post, but for some reason it went back to not writing a dump file.
But I tried something out and restored to a past version of my graphics driver and then I updated it to the current one again. I then opened furmark to see if it looks any different and it now looks just like how it's supposed to look. Hmm..
Didn't run it the whole time because I only wanted to show you how it looks now.
Got another BSOD and this time it recorded the dump.
It seems that LucidLogix Virtu is playing there behind the issue.
I would suggest you to get rid of it and see how it goes.Code:BugCheck 116, {fffffa8009d5f260, fffff88004d9ce34, 0, 2} Unable to load image VirtuWDDM.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for VirtuWDDM.sys *** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys Probably caused by : VirtuWDDM.sys ( VirtuWDDM+8e34 ) Followup: MachineOwner ---------
Hmm.. since deleting that I haven't had any BSOD's.
I even left my computer on for around 32 hours straight to see if it would crash during the night, and it was still the same when I woke up and during the day.
Going to give it a couple more days before I jinx myself, though.
Thanks for the help! I'll reply again in a couple days if there isn't any more BSOD's or before then if there was one..
Quote
