[SOLVED] Multiple random BSODs, all pointing to the kernel

I'm at the end of my rope windowssh blog. I have been dealing with random BSODs for a while now and I just don't know what to do. Please help me, I am desperate. Logs are attached.

PS If you guys can't help me, can you at least tell me how you analyze these files? WhoCrashed and BSV never flag any drivers, it's only ever the kernel.

• DESKTOP-CGKRNL1-Thu_01_07_2016_141525_12.zip (320.0 KB, 5 views)

Update following drivers
Driver Reference Table - asmtxhci.sys
Driver Reference Table - asmthub3.sys

Please uninstall everythingof AMDusing Display Driver Uninstallerand install new drivers from AMD. Be sure to ONLY install the display drivers using custom/advanced options.

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 tutorialto run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
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.

Thank you for responding! I tried looking for usb 3.0 drivers but they only seem to have support for up to Windows 8.1. Should I install those drivers?

Depends on their date, what are the dates of the drivers?

Hi, thanks for responding again!

The date on the 8.1 drivers are 2013/12/17. I tried installing them but my device manager did not change, and doesn't seem to show anything about USB 3.0. Here is a picture of it:



Do I need to do something different?

(Also I did the second step with DDU and installation of only the new driver)

No BSODs yet but I haven't been playing World of Warcraft which I suspect to be a possible cause.

Was the driver verifier step necessary or just a suggestion?

Necessary, the rest was to update old drivers and remove a driver.

Have been testing Driver Verifier for about 20 hours total with no crashes. Am I not supposed to run it 48 hours straight, or in total?

Also after turning it on my PC doesn't seem to be running any slower than normal. I followed the tutorial linked in your post. I have seen other tutorials however that suggest checking off a lot more options. Is there a reason why this tutorial doesn't have me do that?

48h, your system will resume after a reboot or startup however it isn't recommended to shut your system down.

There are only 3 options to check and every driver except for Windows drivers.

A system that can't proper handle stressed drivers will eventually slow down in performance.

I can't have the computer on overnight because of noise and heat, is this going to be a problem? Generally when I run into blue screens without Driver Verifier, they happen between 6-10 hours of the computer being on after I've been doing a bunch of gaming.

If Driver Verifier doesn't end up working, here are some details I haven't mentioned:
- I have noticed that the last few blue screens occurred when I had Skype running while gaming.
- I uninstalled the most recent cumulative Windows update and have been getting errors when trying to reinstall it.
- I have not installed chipset drivers yet because they seemed to cause problems when I installed before reformatting.
- I tried to install Realtek sound drivers but those errored out every time too, and troubleshooting told me to look for a Device Manager entry that wasn't there.