Another storport.sys BS0D But With A Time Element

Arelem · 04 May 2014

Hi, I'm another of those souls being afflicted by the storport.sys BSoD. I have tried several of the solutions I have found around n' about the interwebs but with no luck.

This one seems different in that there is a time element involved. If I am on my PC for 4 or 5 hours, nothing happens. But if I have it on for 10 or 12 hours or longer, it will happen. This has gotten very noticeable since I have rejoined the SETI@Home program and leave it on 24/7. It reboots once almost everyday.

The computer should be completely updated, patched and otherwise up-to-date.

I've exhausted my resource as a tech support guy and hope someone in SevenForums World can help.

Thanks.

Arc · 04 May 2014

Hi.

The BSOD is caused by Intel Rapid Storage.

BugCheck D1, {773400270008, 2, 0, fffff8800190c0d2}

*** 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 )

Followup: MachineOwner
---------

IRST fails very often, and no other action than uninstalling it can make the system free from this error in the long run.

But in your existing situation you cannot uninstall IRST; because it is set to SCSI mode. Every attempt to uninstall will be reverted at the next restart. In order to get rid of IRST, you need to perform a clean reinstall of windows, followed by a little adjustment in BIOS.

Boot into the BIOS. Enter into Advanced BIOS setup. Change the storage controller mode .... from SCSI/RAID to AHCI/ATA/IDE whichever is available. Then reboot.

Upon reboot, windows will not be bootable any more, because it needs the storage controller present on which it was originally installed.

And at this time you need to perform a clean reinstall.

If you set AHCI, the new storage controller will be msahci.sys
If you set to IDE/ATA, the new storage controller will be pciide.sys
None of them fails and causes a BSOD.

Sorry for such a hectic suggestion, but there is no other way to deal with this issue for a long run.

Arelem · 04 May 2014

Crap. I will just probably deal with it then until I build a new system then.

Thank you for your help.

Arelem · 04 May 2014

One more question, if I may. Might the BSoDs stop if I add a second drive and make use of the RAID function? Currently I'm not.

Arc · 04 May 2014

Arelem said:

One more question, if I may. Might the BSoDs stop if I add a second drive and make use of the RAID function? Currently I'm not.

RAID will not make you free of problems, but will cause new problems.