Windows 10: Having BSOD crashes even after 4 clean reinstalls

As the title states, I have been having a few BSOD crashes while using my computer (eg: Internet, Netflix and browsing files). Its a new build with every component new, except the GPU. I believe it might be hardware drivers as even after 4 clean re installs, its still giving me problems.

Specs:
APU: AMD A10-7890K
Motherboard: Gigabyte F2A88XM-D3H
RAM: DDR3 Kingston Hyper X 2x4GB
GPU: Nvidia GTX670
SSD: Corsair FORCE LE 240GB
PSU: Zalman 600W

Attachment 88561

:)

 

IRQL_NOT_LESS_EQUAL – storahci.sys

Occurred immediate after update.

History: never seen BSOD before now.

CPU: FX- 9370 : not overclocked GPU:RX-480 a sapphire Ram: Gskill 4 sticks of 8g HD: PNY SSD MoBo: Sabertooth 2.0 V2

Booted from harinsboot Usb to MiniXP ran disck program - no bad sectors.

Glaries Utilities- registry cleaner- found 180 errors and fixed them.

Ran malwarebits and other spyware programs and system was clean.

Reinstalled Sata driver multiple times, uninstalled and reinstalled. Also tried windows 8.1 drivers.

Still BSOD, at seemingly random points from working in excel 2013, remote desktops, playing overwatch. Usually crashed after 20-45 min of use.

If left standing alone the computer will only crashed every 1-2 hours.

Originally upgraded from Windows 7. Downloaded and created a install USB. Deleted and reformatted entire drive. Preformed clean install of windows 10, twice, successfully.

Computer ran without crashing for 1 whole day, until the most resent upgrade installed, within 15 min, BSOD.

Now crashing randomly again. Though now when the OS boots up after a crash, there is a notice from windows that says wattman setting where set to default after crash.

Setting where never adjusted from defaults. Insure if this is related.

 

Windows 10 - repeated bugcheck and reboot

Thanks for the reply. I updated the drivers from the links and just got another BSOD. I have noticed that I am much more likely to reproduce the BSOD when playing music, i.e., I can almost guarantee a crash within five songs. Although when investigating
this issue, after a clean rebuild of W10 I was getting the crashes before reinstalling my player (VLC) and the MP3 files, so I know it isn't that software.

Fred

 

There is only one crash dump in the zip. It is not enough to decide what is going on over that long time as you are explaining, still ......

Please disable XMP in the BIOS at the first place. Let the RAM run at 1333 MHz. Let us see any further crash dump after doing that.

 

sorry about that only just did a reinstall i do have a written list of BOSD codes i have gotten over the past week

 

I understood it, mate.
Please let us see any more crash dumps after disabling XMP.

 

Motherboard doesn't have an XMP profile. looked in all the bios tabs and found nothing. :/

 

For F2A88XM-D3H ..... M.I.T > Advanced Memory Settings > Extreme Memory Profile.

Attachment 88587

 

not there:
Attachment 88589

 

Another crash (APC_INDEX_MISMATCH). first time while browsing steam.
Attachment 88595

 

Can you set the Memory Frequency at 1333 MHz?

 

Nah seems to default on auto

 

I've booted in safe mode and haven't had a single crash, which tells it might be a driver.

 

APC_INDEX_MISMATCH is a memory related issue. Either it a failing memory hardware or a driver is passing bad info to the memory.

Enable Driver Verifier to monitor the drivers. Driver Verifier - Enable and DisableRun Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.



Information Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.


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 is no 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.

 

Ran Verifier for 24 hours strait and seems to have had no crashes.

Attachment 89307