Frequent and multiple different BSOD Errors with no clear pattern

[essenbe]

Run http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

Watch your video card temps. They will rise very high very quick. If they get too high, stop the test.

 

[Caridor]

I ran the test, my first GPU didn't seem to rise at all for most of the test, starting at 29, ending at 30C.
The second GPU rose up to 80C and then leveled out.
I didn't notice any artifacting.

 

[essenbe]

If that's true, something is wrong. The top GPU is usually the hottest as it gets less airflow and it can't run Furmark and not get very hot. Remove your Cards and run 1 at a time in both slots. If you are running SLI, there is a problem.

 

[Caridor]

Hang on, I think i made a mistake.
GPU1 was on the bottom, and GPU2 was on the top.
Here's a screen shot.

 

[essenbe]

It's only using 1 GPU. Give this a try http://www.geeks3d.com/20101209/tip...nd-crossfire-support-for-opengl-applications/

 

[Caridor]

Ok, so I enabled SLI and furmark says that both GPU's are levelling out at about 80C.
But it hasn't solved the BSOD.
I've had 2 since doing it, one was the same IRQL and the other said "Memory Management"

I did another one of those scans to generate the DXdiag, in case it will help.

 

[essenbe]

Did it BSOD during the test? It wasn't to fix the problem, it was to see if your Graphics cards can withstand the test. There still are no dump files. Everything is exactly the same. Check this and make sure you are configured for Small Memory dumps and make sure you have a folder named Minidump in C:/Windows. http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

 

[Caridor]

Oh it's not created automatically?
Well, that's why I'm not getting dumps then.

And nope, no crashes during the test.

 

[essenbe]

BTW, you may want to set everything back to the way it was before you changed it to force Furmark to use both cards. Also, due to the memory management, run this test.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask​

 

[Caridor]

Ok, I've done all 3 methods in that link about crash dumps and still no joy.
I'll run the memtest when I go to bed.

 

[essenbe]

If it gets an error you can stop it.

 

[Caridor]

So 10 hours of testing later, 8 passes and 0 errors.
So I guess that means it's not a problem with the ram.

 

[essenbe]

OK, we'll try this, I just hope it will create a dump file. Just be sure to create a restore point before enabling Driver Verifier.

Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

What is Driver Verifier:
It puts stress on the drivers, and therefore it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How we know that DV is enabled:
It will make the system bit slow and sluggish.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there are no Restore points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Caridor]

Now I really have no idea whats going on.
But I followed the steps you said, created the restore point, ran the verifier, shut down, started up again and since then, I haven't got a single BSOD, even playing things like Dota which were massive crash creators before. I don't understand.
I'm not complaining, but I don't understand.

If it's still going strong by friday, I'll mark this as solved.
Thank you for all your help Essenbe.

 

[essenbe]

I hope your good luck continues. Keep us posted please.

 

[Caridor]

Will do.
It's very wierd though.

 

[essenbe]

I agree. Driver Verifier is designed to make it crash. There should be no way it keeps it from crashing. It is putting extra stress on all the drivers you selected.

 

[Caridor]

Ok, just got a BSOD but there isn't a file in the minidump folder.
Would it have put it somewhere else with Verifier running?

 

[essenbe]

No, it should be in the minidump folder.

 

[Caridor]

Well, sadly not, the minidump folder is empty.
I guess if it's only going to crash once every 5 days or so, it's probably good enough.