I thought about all of those too. But if it really was the GPU, what really causes this issue then? And why does it only actively cause problems in the driver verifier and not in any stressing program? Also, why does it happen so randomly?
I will try the other PCI-e slot later next week. Maybe on monday, depends how much stuff do I have to do.
I really can't answer those questions other than just hazard a guess. It could be that there is some specific action the graphics card does that causes it. With cards and CPU's, the arbitrary stress tests are different than practical, actual usage. The tests are designed to just stress the heck out of cards to try to determine stability, but actual usage is quite different. I overclock a lot. I have passed Prime95 for 18 hours of tests, which supposedly means the overclock is stable. But started a game and crashed instantly. The stress tests are good and necessary, but actual usage needs to be tested also.
Most people like to use Video Card - Stress Test with Furmark as a stress test, but it is brutal and stresses the card just for the simple sake of stressing it. It is very brutal, and a few years ago both AMD and Nvidia tried to outlaw it. They indused code into their BIOS for the cards, where if the card detected Furmark, it would automatically throttle. I'm not sure if it is still that way though. But, it is quite brutal. I like http://unigine.com/products/heaven/ , because to me it is stressing an actual usage scenario. It is closer to an actual usage than most others, but still stresses the heck out of the card. It will run it at max. and temps will skyrocket, which is what a stress test does. But, I just find it more practical than the others, but still does not mean it is perfectly stable. You can't manufacture any man made test which will duplicate actual usage in every situation. Usage scenarios are whatever the game developers put in the code and those scenarios are pretty much an endless range possibilities. That just what I think.
Ok, now I got the BSoD again after switching between several games
Firstly, CS:GO froze, then my screen lost connection to my GPU, and was searching for a signal. When it got the signal, CS:GO was solid white, and was not responding.
When I got the CS:GO closed, I first tried a game called as "Trove". I was able to play it freely with no issues at all. Then I tried to boot QuakeLive from steam, and it crashed straight away in the boot loading screen. Also, as in previous BSoDs, I had to re-plug my mouse and wifi-adapter.
I still haven't tried switching PCI-E slots. Been busy with school. I'm just wondering why I have to replug my mouse and wifi adapter after every single BSoD, just to make them respond again. It is somehow related to this, but how? Does it refer to the mobo being broke, or is it just coincidence?
Whenever you take a few minutes from gaming ant move your card to another pcie slot, you will be closer to finding out what your problem is. you may try working through this to find the USB problem USB Driver - General Fix for Problems
OK. Did the USB thing, and switched my GPU's pcie slot, stressed the GPU and everything was stable. Actually, this spot even has better air flow than the upper one.
Let's see what's going to happen in the testing phase.
Ok, BSoD occurred, and so motherboard's pcie slot is not the one at the fault here. Same chaïn reaction happened, as previously, but with ArcheAge this time.
Anyways, still after BSoD I gotta replug my mouse and wifi adapter, so that problem was not fixed.
So, should I RMA my GPU or PSU now then?
Also, I will not be doing that anytime soon, because I'm not going to be in the apartment where I live at the holiday week I have soon'ish.
How about trying to switch drivers to AMD Catalyst 14.7 Beta Driver for Windows using the same procedure as before.
Also please Upload the list of all the third party drivers Using NirSoft DriverView :
- Download and execute Driverview
- View > Hide Microsoft Drivers
- Edit > Select all
- File > Save Selected Items
- In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
- Zip the .txt file and upload it.
There is AMD 14.9 driver published.Should I try that after 14.7?
As it seems more stable than the beta driver, I will try that out first.
Last edited by TheJmJ; 02 Oct 2014 at 08:04.
The one I linked to has been stable for many of the R9 Cards, that's why I suggested it. I am getting concerned about your USB problems. That is a function of your Motherboard and has been a problem ever since this thread was started.
Oh, allright. I installed the 14.9 instead tho, so I will see how it goes.
Also, here are my drivers.
Attachment 335420
UPDATE: I was checking the Even logs for the BSoDs, and this is what I found
1.10.2014 23:06:39 > Display driver amdkmdap stopped responding and has successfully recovered.
1.10.2014 23:09:27 > The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
1.10.2014 23:09:36 > The previous system shutdown at 23:08:11 on 1.10.2014 was unexpected.
Last edited by TheJmJ; 02 Oct 2014 at 12:47.
Quote