Windows 10: Somewhat uncommon BSOD

Ran it for ~35 mins. Remained at a stable 80-81 degrees throughout. I assumed the enable log actually saved it and I was dumb enough to have the wrong active window open to take a screenshot of the current window so I don't actually have a screenshot. Also these sorts of issues did happen when I had another gpu a while back, not to say it wasn't worth testing it. I have used furmark previously to test stability a while back too without concerning temps.

 

Was the previous GPU in the same slot?

 

Yes it was. Never tried the other slots.

 

I hope you don't mind to try another slot then currently?

What slot are you exactly using?
Attachment 58689

 

I used the first pciex16 since it was the most logical and it also spaced things out when I had my sound card in. I can try the 2nd slot providing I can deal with less performance (though a quick google seems to suggest I shouldn't notice).

 

Even if you would notice, please try it for testing purpose.

 

That comment was more towards if I noticed it and had to do it for ~5 weeks. Though I suppose there's always turning the settings down too. Nevertheless I was and will be trying it. In some ways it'd be more convenient if I could be sure they'd happen a little more consistently.

 

You can try running driver verifier to see if it helps forcing the bluescreens.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

I did try late last year to use driver verifier. It managed to bsod straight away and I had to system restore. Should I try again? I also removed the sb audigy driver that was on since the last bsod since I didn't originally do that.

 

Yes please, this time try to disable verifier (in a few ways possible) before using a system restore please.

 

Bsod happens straight away mentioning irql_not_less_or_equal. Then after using the command prompt to disable it I got a bsod, then it reset with another bsod mentioning "system service exception". One more restart and it restarts just fine. Though it does have an error for "Tablet version mismatch- Please reinstall the tablet software", presumably my bamboo fun tablet that I probably had it's drivers before updating to windows 10. It doesn't often get used and have had times without installing the drivers previously when not using it for a while. Wasn't sure if you just wanted the minidump, but the full thing is attached below. As well as the pop up message in case it has any relevance to something happening. Last time I tried using driver verifier I did try not using system restore, Though maybe I didn't give it another chance after the 2nd bsod after the command prompt usage, I can't quite remember. I just recall overall letting it reset a fair amount of times.

 

3 of the 4 dumps are corrupted, meaning the size of the file is incorrect (0KB)
Attachment 58793

It seems the audio drivers are getting part of it.
You did already check GIGABYTE - Moederbord - Socket 1155 - GA-Z77X-UD5H (rev. 1.0)
and reinstall/update the drivers, right?
Code: ffffd000`20c080f8 fffff800`376d9438Unable to load image \SystemRoot\system32\drivers\MBfilt64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for MBfilt64.sys *** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys MBfilt64+0x9438 3: kd> lmvm MBfilt64 start end module name fffff800`376d0000 fffff800`376de000 MBfilt64 T (no symbols) Loaded symbol image file: MBfilt64.sys Image path: \SystemRoot\system32\drivers\MBfilt64.sys Image name: MBfilt64.sys Timestamp: Fri Jul 31 05:40:32 2009 (4A7267B0) CheckSum: 0000FF02 ImageSize: 0000E000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4[/quote]

 

The realtek ones I figured I'd get direct from the link when you listed the drivers to update. In previous installations for windows 7 I did install form the motherboard site. I decided to try the motherboard one, it updated the speaker and mic drivers after restart, then gave a bsod. I tried relaunching it and it bsod straight away in windows and I couldn't go back in until I disabled driver verifier in the command prompt which I assumed would be fully disabled now. I have loaded the verifier to disable the settings and restarted just in case. The Atheros driver as well as other were gotten from the mobo site, atheros for example was using the windows 8 driver since there wasn't a win 10 version available.

Other drivers only listed for windows 7 or 8 (or 8.1) I didn't install for this installation were:
Creative SB X-Fi driver
Realtek Function driver for Realtek Azalia audio chip (Including Microsoft UAA Driver in English edition)
Intel SATA Preinstall driver
(For AHCI / RAID Mode)
Hot fix (windows 8 only, not 8.1)
(Note) After installed IRST driver, please install Hot fix.
Marvell Storage Utility
Intel VGA Driver (I believe I disabled it in the bios for some reason)

I'm assume you're right with there being an issue with the audio drivers.

Edit: Though I should say that some may have been installed pre the windows 10 update and before trying the driver booster thing as well as previous installations.

 

Do you have a restore point prior using driver booster?
It is important to get rid of the installed drivers.

This time the Intel audio driver tried to access invalid memory for which it didn't have permission to.
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff8015285c038, address which referenced memory[/quote]

 

Unfortunately I don't, I did have one but I guess it's been too long and since been removed. I suppose I should reset my pc and then continue to diagnose the issues after updating the drivers? If that's what needs to be done, is the option to keep my files fine?