Random BSOD after an hour of gaming, when idle, whenever it wants

Drannin · 02 Apr 2015

I just recently purchased an external backup drive. When I went to plug it in to my USB 3.0 ports it would not detect. I tried a 2.0 and sure enough it works. So I spend the next little while trying to update drivers to get the usb 3 working. Eventually I try another usb 3.0 and it works. I get the backup software installed and about an hour later the first BSOD happens. I uninstall the backup software, remove the drive and the BSOD's continue randomly. I decide that I must have messed something up trying to get the usb ports functioning properly and reload windows. The BSOD continue and I end up going into the bios to reset to defaults. I notice that I have a dimm slot reporting abnormal so I remove the dimm in question and the machine runs fine that evening. The next day the BSOD's are continuing. I put the dimm back in and start running memtest 86 for about 6 hours, no errors.

I'm at a loss as to what the issue is I suspect I may have to RMA the motherboard, which has been running like a top for the last 3+ years. Any help is appreciated.

essenbe · 02 Apr 2015

Hello Drannin, and welcome to the Forums. What I am getting from your dump files is

Code:

BugCheck D1, {0, 2, 0, fffff8800193f0d2}
*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys
Probably caused by : iaStorA.sys ( iaStorA+64024 )

Which is Intel Rapid Storage Technology (IRST)

Please uninstall it and see if that helps.

Also please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Please fill out your system specs in as much detail as possible and include your PSU and CPU cooler.

See if any of those things will help.

Drannin · 02 Apr 2015

Thanks for the help I'll report back after I get a chance to run those commands. I have a pair of older SSD in a raid and the one disk tends to throw smart events but it's done it for about a year with no discernible issues.

Golden · 02 Apr 2015

Drannin said:

Thanks for the help I'll report back after I get a chance to run those commands. I have a pair of older SSD in a raid and the one disk tends to throw smart events but it's done it for about a year with no discernible issues.

Is that by any chance a hardware RAID0? If so, that could be the issue.

essenbe · 02 Apr 2015

iaStor is the Intel Raid driver.

Drannin · 02 Apr 2015

Yes its just striped Raid 0. Maybe I have an excuse to buy a new one?

Drannin · 02 Apr 2015

BSOD In the middle of the first run so I don't know if it found anything. Second run reports:

Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.

So are we thinking that if I break the raid and reload onto the "Good" drive that my problems may disappear? Or could I be having a hardware issue with my sata controller?

Golden · 02 Apr 2015

I'm not sure what Steve thinks, but since one of the disks in the RAID0 is 'flaky', it might be best to remove that from the equation.

Drannin · 03 Apr 2015

I broke the raid and installed to the disk I believe wasn't having any issues. No BSOD overnight. Thank you Essenbe and Golden for taking your time to help me with my problem. I'll mark this solved tonite once im sure I'm stable again.

Golden · 03 Apr 2015

Let us know how it goes after a few days.