multiple cause BSOD's back to 4hrs 50min +/- after 2 years HELP!

Been living successfully w/ BSOD's @ 20hr +/- intervals for the last 2 years. You can find some 2yr old posts in this forum & Intels forum when it was 7- 71/2 hr intervals. Then suddenly, with NO changes to the computer or software, it BSOD'ing every 4:50 +/-. Ran thru the normal routines, memtest86 5.1.0, 4 passes, w/ both sets of my G-skill memory (2 x 8gb DDR3-2133 & 8 x 8gb DDR3-1600) Ran scannow & verifier routines. Found nothing. Had a new, unused, Win7Pro x64 so I elected to do a clean install thinking that something may be defunct in the program itself or that the "RAID" setting in bios was causing the problem. F6'd the AHCI driver and set bios to AHCI. . Same BSOD's @ 4:50 +/-.(note: this was w/ only Win defender installed). Reran verifier at the suggested settings and got almost immediate BSOD. See result @ 5/22/2014, 4:11PM. Re-ran at normal settings and finally got a total lockup about 5:10hrs into it. CPU had all cores at 100% and task manager showed that Outlook was using 97% of that. Go figure. Had to do a hard reboot to safe mode and disabled verifier. Re-booted into windows. Checked all drivers against Intel & AMD and they are the latest where applicable. Checked for hardware problems by running stress tests using HD-Tune, Furmark (including CPU test), 3D_Mark, y-cruncher to 10,000,000,000 places & the complete AIDA test routine for 2 hours. All tests were run @ 42x100 and were completed successfully. Highest temp seen was 51C. HD's never went over 32c. I'm just old & retired but I've got better things to do than work on this thing. I need it up and dependable 24x7, or at least back to the 20+/- hr BSOD's. I have attached the DM & SF logs which probably contain some random BOSD's going back 2 years. At least they do in the Bluescreenviewer program I use. This was used to create the BOSD time interval PDF attach. Also attached is a fully exploded Win7 driver status screen shot, and just for the hell of it, a screenshot of the current desktop.

Your Intel Storage Technology driver is causing issues.

Code:

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

It's outdated which explains things.

Code:

10: kd> lmvm iaStorA
start             end                 module name
fffff880`0182e000 fffff880`01eb4000   iaStorA  T (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Thu Oct 18 14:00:54 2012 (507FFD86)
    CheckSum:         0008D6BD
    ImageSize:        00686000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update it here.

Don't know how to read your "code", but all driver and bios items are checked weekly and updated as required. Just manually checked all the device drivers listed in "caused by" column shown in the screenshot attached and they are up to date. I noted that the *.dmp file you used was dated 10/18/2012 when the BSOD's were on 20+/- hour intervals. It was uninstalled and re-installed many a time back then to no avail. You may also note that iaStorA has not been the cause of a BSOD since the clean install I did 5-6 days ago. Sure has been a lot of other ones since then though. (look at items 3 thru 24 which shows the BSOD's since then) All the other *.dmp files were prior to 9/5/2013.

Don't know what it may mean, but the one(1) common denominator in ALL the BSOD *.dmp files is a note that says:

" PSHED.dll fffff880`00c75000 fffff880`00c89000 0x00014000 0x4a5be027 7/13/2009 8:32:23 PM Microsoft® Windows® Operating System Platform Specific Hardware Error Driver 6.1.7600.16385 win7_rtm.090713-1255) Microsoft Corporation C:\Windows\system32\PSHED.dll ".

Thanks for your reply. Greatly appreciated.

No you dump files I used were yesterdays.
The "probably caused by" was storport.sys which is the microsoft storage port driver.
In BlueScreenView or Whocrashed that's all you see.

Upload all new dump files.

The program you are using is not very accurate and can easily point you in the wrong direction.

Attached are only the dump logs that have been created since the clean install on 5/20/2014. The previous attachments included logs back to before the clean install and that I had manually copied into the file folder c:\windows\minidump.

The one clue to the BSOD's both before and after the clean install is consistent time intervals. I can understand BSOD's based on a program conflict, or hardware failure, but these BSOD's don't occur on a random basis. The occur on a very specific timetable. And they occur no matter what program is running, or if I'm asleep !!. Almost like thay are clock based. This was true before the new install, and since.

Any and all help is deeply appreciated.

Your Intel Rapid Storage technology driver is still causing issues.

Code:

*** WARNING: Unable to verify timestamp for iaStorA.sys
*** ERROR: Module load completed but symbols could not be loaded for iaStorA.sys

Code:

10: kd> lmvm iastora
start             end                 module name
fffff880`01825000 fffff880`01eab000   iaStorA  T (no symbols)           
    Loaded symbol image file: iaStorA.sys
    Image path: iaStorA.sys
    Image name: iaStorA.sys
    Timestamp:        Thu Oct 18 14:00:54 2012 (507FFD86)
    CheckSum:         0008D6BD
    ImageSize:        00686000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Remove it all together.

latest iaStorA/iaStoreF drivers updated every day since 5/20/2014. Downloaded directly from Intel.
Been doing this "just in case".

Great idea doctor44-

Just did msconfig safe boot, went in and uninstalled, then deleted the Intel iaStorA & iaStorF drivers everywhere I found them in the Device control panel. Reset to normal boot. Took 2 warm reboots for Win7 to reinstall all the Microsoft generic drivers. The Intel C600 controller (rste ??) has disappeared from the device control panel but all the drives are up. So lets wait now and see what happens Maybe Intel can't write drivers for their own hardware. Seen it before.

Removing the Intel iaStorA & F drivers solved the issue. 1st time in the last 2 years this thing has seen "1d*" on the "uptime" clock. (see attachment). Posted this problem many times in many forums and no one ever suggested to "just delete it". I really didn't think the disk controller would work without it. I read 2 interesting posts last night on this issue and it seems it is very common on Intel x79 platforms and Intel has never managed to fix the drivers. One deals w/ complete removal of the 2 drivers in question, and the other w/ a rollback scenario to an older modded driver called "iaStor" to restore raid capability which I may try. Links here: Rapid Storage 11.5a - Bugs and removal notes & Intel AHCI/RAID Drivers » Modded Intel AHCI and RAID Drivers

Again, a very grateful "Thank You" to THEDOCTOR44