Periodic ntoskrnl blue screens

Tenz_One

Reputable
Nov 26, 2014
7
0
4,510
New PC build, most everything works fine, except i get a blue screen every day or two

here are my specs:

Win7 Ultimate
Core i7 4790
asus Z97-AR Mobo (updated firmware)
8GB DDR3 12800 Memory (800Mhz)
AMD Radeon HD 6870 1GB DDR5
Samsung 840 EVO 250 gig SSD (OS drive (latest firmware, samsung utility reporting as healthy)
Seagate ST3100033AS 1TB data drive

Here is a link to my minidumps, 5 of them zipped

https://www.dropbox.com/s/9spfzoy2hmng4qf/bluescreendmps.zip?dl=0

Any help would be greatly appreciated. I have already removed all non-essential peripherals.

I noticed that my front panel USB 2.0 port acts weird, so i will be disconnecting the header from the mobo later today to see if that might be the case. i just am not great at looking over these minidumps. If any other info is needed, i can provide..

Thanks in advance for any and all help
 


Paul,

I do not have the Asus ai suite installed, nor PCProbe

I will remove Virtualclonedrive, but i also do not have anydvd installed.

I also ran the sptd.sys remover.

i will update on if the problem is solved by removing these two items. as far as the ah9b6kvg.sys, i cannot seem to find it on my hard drive.
 



I did.. enable hidden and system to be shown.. I see where it shows in the bluescreenview output, as well as another one of the dumps has another odd .sys that one is al9vede6.sys. neither of which can i find on my hdd though (checked SSD and HDD)

Im going to run a couple malware scans to be safe though.
 


yea, i would find it odd being such a new build that i would be infected, but crazier things have happened.. ill update with results.

MalwareBytes found a couple of items Couple of PUPS, but also a couple trojan elements.. def could be related
 


we had another crash on the 29th below is the dmp file

https://www.dropbox.com/s/kxyo895odhgfdv9/112914-5116-01.dmp?dl=0

while doing some internetting, i found some resources saying to turn on Microsoft driver verifier. So i did that, and it has still not crashed, but they said it might give us more detailed dmps if and when it crashes again. I am going to cross reference schedule tasks with the date and times of the bsods, see if that has any useful information.
 
Welp, i decided to run memtest overnight and ended up with 32 errors... so it very well may be the RAM..... going to run it stick by stick now to single out which one is faulty and RMA it. i will have a look at that quhwm.sys