BSOD - iaStorA.sys+67218

[IV11]

During last two days I've received two BSODs, both related to "iaStorA.sys+67218".

Dump File040718-53734-01.dmpCrash Time2018-04-07 04:30:32Bug Check StringDRIVER_IRQL_NOT_LESS_OR_EQUALBug Check Code0x000000d1Parameter 100000000`00000008Parameter 200000000`00000002Parameter 300000000`00000000Parameter 4fffff803`43947218Caused By DriveriaStorA.sysCaused By AddressiaStorA.sys+67218File DescriptionIntel Rapid Storage Technology Enterprisedriver - x64Product NameIntel Rapid Storage Technology EnterprisedriverCompanyIntel CorporationFile Version4.6.0.1048Processorx64Crash Addressntoskrnl.exe+17dd70Stack Address 1Stack Address 2Stack Address 3Computer NameFull PathC:\WINDOWS\Minidump\040718-53734-01.dmpProcessors Count32Major Version15Minor Version15063Dump File Size1 522 732Dump File Time2018-04-07 05:24:52

(The 2nd one is attached)

1. I was unable to google any "iaStorA.sys"- related BSOD reports, containing "67218". While both my BSODs do contain this address.
2. There was no heavy IO.
3. The only device, attached to Intel C600+/C220+ controller is a DVD drive:I have never used it, actually. Just tested - it was able to read some files from an old CD.
4. The system is Dell T7910. Please find detailed "Intel® Driver & Support Assistant" report attached.
5. I've never seen any issues like that (on this system) before yesterday. The last event, related to "Intel C600+/C220+ series chipset" is from 2017-11-20, e.g. it looks like there are no recent changes here.
6. However during last few days I've updated:
   1. BIOS to A25 (http://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=JFV88 changelog says "Updated Chipset support")
   2. "LSI 3008 Firmware, Ph15" to "15.01.00.00 ,A04"
   3. "LSI SAS3008 Windows Drivers for Win10-64" to "2.51.21.0 ,A04 "
   4. <span style="color: # 444444; font-family: Roboto-Regular, Roboto-Light, 'Cordia New', 'Microsoft Sans Serif', Utsaah, 'Devanagari MT', 'Nirmala UI', Latha, InaiMathi, Gautami, 'Telugu Sangam MN', Tunga, 'Kannada Sangam MN', Kartika, 'Malayalam Sangam MN', Shruti, 'Nirmala UI', 'Gujarati MT', 'Gujarati Sangam MN', Vrinda, 'Bangla Sangam MN', 'Meiryo UI Reg', 'メイリオ Reg', 'MS UI Gothic Reg', 'Hiragino Kaku Gothic Reg', 'ヒラギノ角ゴ Pro W3 Reg', 'Microsoft YaHei', 微软雅黑, 'Hiragino Sans GB', 'Microsoft JhengHei', 微軟正黑體, 'Malgun Gothic', '맑은 고딕', Gulim, AppleGothic, 'Apple LiGothic', 'LiHei Pro', Osaka, STHeiti, 华文黑体, STXihei, 华文细黑, SimHei, 黑体, 'Arial Unicode MS', Arial, sans-serif; background...

[idata]

Hello i3v,

Thanks for your reply and the information you've provided us, in regards to your situation please allow us to research on it and as soon as we have additional information we'll contact you back for sure. Also, please remember that if you require more assistance or want to add additional details, we'll be glad to assist youRegards,Chris

[IV11]

Hi Chris,

It's nice to hear that. I hope you would be able to find and fix that bug.

Meanwhile, I've performed one more test - for about 2 days just Windows Defender "Full Scan" was running on this machine. After that 3 days there was yet another BSOD, quite similar to the previous two (see attached).

[IV11]

O-oups. I've accidentally clicked something, and now this thread is marked as "Assumed Answered". And it looks like I cannot revert this. If it's possible, could you please revert it?

[idata]

Hello i3v,

Thank you for the information you provided us and please don't worry about the assumed answer status you clicked by mistake, we are still investigating on your issue and will get back to you ASAP once we get an update.

Best Regards

Luis H

[IV11]

There was one more BSOD, 4 days later, on 2018-04-15 (see attached).

After that one, I've https://social.technet.microsoft.com/Forums/ru-RU/b0cd7b34-5d1c-4257-beb1-0a984ac2ffd1/kernel-memory... d5b92775-e277-448b-b5d9-61fe13cd1a26 decided to replace Intel driver with Microsoft "Standard SATA ACHI Controller". The system works OK since then (about a week already). I hope this fixed the issue for me.

[idata]

Hello i3v,

We are glad to hear that after replacing the Intel® driver with the Microsoft* Standard driver the system seems to be working properly.Thank you for providing us the steps you took in order to resolve the problem, we will leave you community post open for a few days in order to make sure that replacing the driver did actually solve the issue.Please don't hesitate to contact us back if you encounter further issuesBest RegardsLuis H

[IV11]

Luis,

OK. Thanks. Probably that's acceptable, cause it looks like noone else ran into the same issue by now.

[idata]

Hello i3v,

We are glad to hear that you are able to confirm that you system has been running stable, please don't hesitate to contact us back if you require further assistance.Best RegardsLuis H