Lots of BSOD's Seemingly Without Cause

Well, something must have changed since Windows updated, as I'm now getting very frequent BSOD's again. I once even got a BSOD, restarted and before the computer even started up, I got another BSOD...

Here's the requested data: JOSHDESKTOP-2016_07_14_(木)_173041_19.zip

Not sure what more to say, I am running the Windows 10 Preview Build 14379, but I don't think that's the cause.
Any idea of how to solve this problem? Thank you!

NOTE: Not entirely sure, but I believe there might be a BSOD log in there that was caused by me when I accidentally killed the system process svchost... Just ignore that I guess?

axe0 said:

Please remove / disable items from the startup in taskmanager
These programs could interfere with the boot process giving you trouble and increase the boot time.


Alright, thanks for letting us know :)

Unfortunately the other BSOD that wasn't caused by accident was improper saved being it an invalid file size of 0KB.
This basically means that we cannot help as there is nothing to analyze.
Please make a photo whenever another occurs.

Ah, okay. I will make sure to do that in the future. Actually, I do have a couple pictures I just happened to take, although the quality isn't great, the stop code is "SYSTEM_SPACE_EXCEPTION" Unfortunately, that's all the information Windows 10 gives... BSOD's used to be less friendly, but more informative........ a while before that, I got couple "BAD_POOL_HEADER"s too. Not sure if that helps much, but other than that, all they say is the usual " Your PC ran into a problem and needs to restart. We're just collecting some error info and then we'll restart for you. (x% complete) If you'd like to know more, you can search online later for this error: <error>" or the newer " Your PC ran into a problem and needs to restart. We're just collecting some error info and then we'll restart for you. x% complete For more information about this issue and possible fixes, visit Access Denied If you call a support person, give them this info: Stop Code: <error>" with the QR code to the support page...

axe0 said:

You're sure the 'system_space_exception' is what you saw on the screen?
If so it would be a new BSOD because there is no information about it.

The bad pool header is usually caused by drivers, at least there are not yet other known usual causes for this crash.
Though with the TP version I prefer to look at both sides, but driver bugs & Windows bugs.

Ah, I did misread it... It's really blurry, it turns out it's just that service exception when I killed svchost. :/ I'll make sure to get the next BSOD's error though.

Finally got a BSOD and wrote it down... Not sure if the logs were written this time, but I got a BAD_POOL_HEADER and also a PAGE_FAULT_IN_NONPAGED_AREA error saying that atikmdag.sys failed.

Anyways, here's the data collection zip: Attachment 91831

axe0 said:

Please revert back the BIOS to a non-beta version. Is there a specific reason why you're using the beta version?

Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
Attachment 91860

Code:

1: kd> lmvm atikmdag
Browse full module list
start             end                 module name
fffff804`d6450000 fffff804`d7def000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Mar 21 15:19:43 2016 (56F002FF)
    CheckSum:         0192B06F
    ImageSize:        0199F000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Uhh.. My BIOS? I do believe there are no Gigabyte beta BIOS releases, but if you mean OS, I'm using a beta version of Windows 10 because there was something I needed in it that wasn't available in the releases. I can't remember what it was now, but something I needed was missing.

And about the AMD drivers, that'll take a bit more time.