[_nobody_]

Hello jcgriff2,

Definitely, I need your help with this problem. Could you, please, look into the crashDUMP.txt file, and tell me what you see? :banghead:

This problem occurs from 0.4% to 2% cases (all others are successful)??? :grin:

************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
0: kd> .reload
Connected to Windows 7 7601 x64 target at (Fri Jan 22 09:18:30.114 2016 (UTC + 1:00)), ptr64 TRUE
Loading Kernel Symbols
.................................................
Loading User Symbols

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: fffff880009a8da8, Exception Record Address
Arg4: fffff880009a8600, Context Record Address

Debugging Details:
------------------


BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: 0

BUGCHECK_P3: fffff880009a8da8

BUGCHECK_P4: fffff880009a8600

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
+0
00000000`00000000 ??              ???

EXCEPTION_RECORD:  fffff880009a8da8 -- (.exr 0xfffff880009a8da8)
ExceptionAddress: 0000000000000000
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000

CONTEXT:  fffff880009a8600 -- (.cxr 0xfffff880009a8600)
rax=0000000000000000 rbx=000000000000000d rcx=fffffa80053b3450
rdx=0000000000000000 rsi=fffffa80053a66e0 rdi=fffff8a0002e52c0
rip=0000000000000000 rsp=fffff880009a8fe8 rbp=0000000000000001
 r8=fffff880009a9040  r9=fffff88001163140 r10=fffffa80045b8d30
r11=fffff880009a9158 r12=000000000000000d r13=fffff880015a0110
r14=fffffa8004efd010 r15=fffffa800454aa10
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
00000000`00000000 ??              ???
Resetting default scope

CPU_COUNT: 4

CPU_MHZ: 768

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000008

EXCEPTION_PARAMETER2:  0000000000000000

WRITE_ADDRESS:  0000000000000000 

FOLLOWUP_IP: 
storport!RaCallMiniportAdapterControl+29
fffff880`01588059 f7d8            neg     eax

FAILED_INSTRUCTION_ADDRESS: 
+0
00000000`00000000 ??              ???

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 10.0.10240.9 amd64fre

LOCK_ADDRESS:  fffff80002ed0da0 -- (!locks fffff80002ed0da0)

Resource @ nt!PiEngineLock (0xfffff80002ed0da0)    Exclusively owned
     Threads: fffffa8004577040-01<*> 
1 total locks, 1 locks currently held

PNP_TRIAGE: 
	Lock address  : 0xfffff80002ed0da0
	Thread Count  : 1
	Thread address: 0xfffffa8004577040
	Thread wait   : 0x8b

LAST_CONTROL_TRANSFER:  from fffff80002dbccc2 to fffff80002cc2cf0

IP_IN_FREE_BLOCK: 0

STACK_TEXT:  
fffff880`009a8fe8 fffff880`01588059 : 00000000`0000000d fffffa80`053a66e0 fffff8a0`00000000 fffff880`009a93b0 : 0x0
fffff880`009a8ff0 fffff880`015890c3 : fffff8a0`002dbf00 00000000`00000801 00000000`00000001 20206f49`02e5c588 : storport!RaCallMiniportAdapterControl+0x29
fffff880`009a9020 fffff880`015960ab : fffff8a0`002dacf0 fffff8a0`002daf30 fffff880`009a9100 fffff880`015828f1 : storport!RaidIsAdapterControlSupported+0x43
fffff880`009a9070 fffff880`015daae2 : fffffa80`053a66e0 00000000`00000001 fffffa80`053b11b0 fffffa80`053a66e0 : storport!RaidAdapterFilterResourceRequirementsIrp+0x7b
fffff880`009a90c0 fffff880`015dabf4 : fffffa80`053a66e0 fffff880`015a0110 fffffa80`053b1060 fffffa80`04efd010 : storport!RaidAdapterPnpIrp+0x1d2
fffff880`009a9120 fffff800`03089a55 : fffffa80`053a66e0 fffff880`009a9200 fffffa80`053b1060 fffff8a0`002e52c0 : storport!RaDriverPnpIrp+0x94
fffff880`009a9160 fffff800`0308ab23 : fffff8a0`002e52c0 fffff8a0`002cba80 fffff880`009a9310 ffffffff`800000f0 : nt!IopFilterResourceRequirementsCall+0xc5
fffff880`009a91d0 fffff800`0308b8e2 : 00000000`00000003 fffff8a0`00022290 fffff880`009a9640 00000000`00000000 : nt!IopQueryDeviceResources+0x313
fffff880`009a92b0 fffff800`030acf62 : fffff8a0`00000000 fffffa80`00000004 00000000`00000000 00000000`00000001 : nt!PnpGetResourceRequirementsForAssignTable+0x192
fffff880`009a9310 fffff800`030ad411 : fffffa80`00000000 fffffa80`0454aa10 00000000`00000000 00000000`00000001 : nt!PnpAllocateResources+0x82
fffff880`009a93c0 fffff800`030ad540 : fffffa80`00000001 00000000`00000040 00000000`00000000 fffffa80`0454aa10 : nt!PnpAssignResourcesToDevices+0xf1
fffff880`009a9460 fffff800`030bc4a5 : 00000000`00000000 fffffa80`045b1010 00000000`00000000 fffff8a0`00000000 : nt!PnpProcessAssignResources+0x100
fffff880`009a94b0 fffff800`02dce99e : 00000000`00000000 00000000`00000000 fffffa80`32706e50 00000000`00000084 : nt!PipProcessDevNodeTree+0xb5
fffff880`009a9720 fffff800`02dceebe : 00000000`00000000 00000000`00000001 00000000`00000001 00000000`000007ff : nt!PnpDeviceActionWorker+0x1ee
fffff880`009a97c0 fffff800`031fea11 : fffff8a0`0020f4c0 00000000`00000005 00000000`00000000 fffff8a0`002dbb60 : nt!PnpRequestDeviceAction+0x2be
fffff880`009a9830 fffff800`031ff431 : fffff8a0`002d8650 fffff800`00813c00 00000000`00000003 ffffffff`80000078 : nt!IopInitializeBootDrivers+0x4f1
fffff880`009a9900 fffff800`03202610 : 00000000`00000007 00000000`00000010 ffffffff`8000002c fffff800`0081b410 : nt!IoInitSystem+0x801
fffff880`009a9a00 fffff800`03152569 : 00000000`00000000 fffffa80`04577040 00000000`00000080 fffffa80`04510890 : nt!Phase1InitializationDiscard+0x1270
fffff880`009a9bd0 fffff800`02f69b8a : 00000000`00000000 fffff800`02f69b30 00000000`00000010 00000000`00000282 : nt!Phase1Initialization+0x9
fffff880`009a9c00 fffff800`02cbc8e6 : fffff800`02e47e80 fffffa80`04577040 fffff800`02e55cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`009a9c40 00000000`00000000 : fffff880`009aa000 fffff880`009a4000 fffff880`009a9540 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  storport!RaCallMiniportAdapterControl+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: storport

IMAGE_NAME:  storport.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5428b198

IMAGE_VERSION:  6.1.7601.18615

STACK_COMMAND:  .cxr 0xfffff880009a8600 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_NULL_IP_storport!RaCallMiniportAdapterControl+29

BUCKET_ID:  X64_0x7E_NULL_IP_storport!RaCallMiniportAdapterControl+29

PRIMARY_PROBLEM_CLASS:  X64_0x7E_NULL_IP_storport!RaCallMiniportAdapterControl+29

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_null_ip_storport!racallminiportadaptercontrol+29

FAILURE_ID_HASH:  {6dea86c2-e7c4-c349-9f6b-b80ce4018ab0}

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

0: kd> lmvm storport
Browse full module list
start             end                 module name
fffff880`01580000 fffff880`015e4000   storport   (pdb symbols)          d:\symbols\storport.pdb\1B6EF28010154E1F8D73630D15DAE0222\storport.pdb
    Loaded symbol image file: storport.sys
    Image path: \SystemRoot\system32\DRIVERS\storport.sys
    Image name: storport.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Sep 29 03:10:48 2014 (5428B198)
    CheckSum:         0003C22D
    ImageSize:        00064000
    File version:     6.1.7601.18615
    Product version:  6.1.7601.18615
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     storport.sys
    OriginalFilename: storport.sys
    ProductVersion:   6.1.7601.18615
    FileVersion:      6.1.7601.18615 (win7sp1_gdr.140928-1509)
    FileDescription:  Microsoft Storage Port Driver
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Thank you in advance for your help! :angel:
_nobody_

 

[jcgriff2]

Hi. . .

Bugcheck 0x7e (0xc0000005,,,) - thread threw an exception; exception = 0xc5 - memory access violation

The output lists the Microsoft driver storport.sys as the probable cause, which it cannot be. It is merely a default.

https://www.sysnative.com/drivers/driver.php?id=storport.sys

Run Driver Verifier - see if it flags any 3rd party drivers - http://www.techsupportforum.com/for...10-8-1-8-7-and-vista-bsod-related-473665.html

Let it run for 24 hours minimum.

Upon BSOD, run - http://www.techsupportforum.com/for...ions-windows-10-8-1-8-7-and-vista-452654.html

(You know the drill! - I need dumps + files)

What other cases are you taking about?

Is this your system?

Regards. . .

jcgriff2

`

 

[_nobody_]

Hey (mc)Griff2,

Very good post, says to me much more than what I can see. :thumb:

Now, let me answer your questions to the best I can/by situation allotted! :whistling:

This is a SKL-H (not sure if 4+4e, probably yes), DeskTop version test platform, and it runs in some adjacent lab, next to mine. The people put (also) INTEL RST driver there (as part of their setup), wiping out inbox WIN 7 64 SATA AHCI driver, an they are beating the whole setup up by stress testing to Death... :horse:

Now, INTEL claims RST driver also does support SATA AHCI mode, so does not matter if INTEL RST driver is placed instead of generic inbox (I assume WIN 7 64 6.1.7601.18615) SATA AHCI driver.

What I really do not get... These folks are running (they claim) RST INTEL driver, but generic inbox Microsoft driver storport.sys appears in crashDUMP??? :banghead:

Something is fishy here... Really! :grin:

Any thoughts??? :hide:

_nobody_

 

[jcgriff2]

I honestly have no idea what you're trying to tell me in your post as I don't understand the hardware end of this business. I sit squarely on the software side of the fence.

I'm sure that you're well aware that a debugger's purpose is to help find software faults (like when writing a driver or an app) -- and that, I am good at.

I have no idea what "AHCI" is or even what it stands for. I just learned ~2 years ago what "SATA" is (when I needed a new HDD, SATA & IDE was explained to me). No joke. I learned Windows under Vista and went behind the Desktop for the very first time in late 2007. That's the same time that I started to learn about Windbg too. Hardware confuses the hell out of me.

My hardware experience is limited to installing a new HDD and RAM in an OEM laptop. I've never built a system; never even opened one up.

So, with all that said -- sorry, but I cannot comment on something I don't understand or know about.

After this post, I'll be Googling to fond info on "SATA AHCI mode" as it means nothing to me at this time.

The above is no joke. I am 100% serious.

My college degree is in Accounting & Finance. I spent the majority of my career (not yet over) in State Sales & Use Tax law. I never took a computer/systems course.

However - I can see why they would first go after an Intel driver before the Microsoft driver. I know I would. Furthermore, it's not a stretch to assume that storport.sys + iastor.sys co-mingle. I myself would go after the Intel driver - never would assume that there is an issue with storport.sys.

Regards. . .

John

`

 

[satrow]

IntelRST adds one driver to the populated drive channels and one driver to the controller - they sit alongside the MS AHCI SATA drivers, in a JBOD scenario, that's just adding stuff that isn't needed, there's no RAID/caching drivers for RST to control.

See if you can get the BSOD data and attach it so we can dig deeper: http://www.techsupportforum.com/for...ions-windows-10-8-1-8-7-and-vista-452654.html

 

[_nobody_]

I honestly have no idea what you're trying to tell me in your post as I don't understand the hardware end of this business. I sit squarely on the software side of the fence.

My college degree is in Accounting & Finance. I spent the majority of my career (not yet over) in State Sales & Use Tax law. I never took a computer/systems course.

Hello John,

I understood your talk/writings. I appreciate your honesty. But, you are willing to learn, and combine your knowledge. You gave me some very good ideas/leads. I am trying to put puzzles together, and I do not have them yet. I do understand HW in very wide extend, since my profession indeed, is HW and SW. Last 20 years this all exploded, so I then lost the complete picture of the complex systems... Well! :banghead:

About till two years ago I was even not able to find with WIN 7 System Event logs, even did not understand how WIN 7 does Power Management, but things tunrned for 180 degrees, so now I am forced to understand much more. :grin:

I'm sure that you're well aware that a debugger's purpose is to help find software faults (like when writing a driver or an app) -- and that, I am good at.

Yes, obviously, I am aware of of HW and SW debbuggers. :thumb:

I have no idea what "AHCI" is or even what it stands for. I just learned ~2 years ago what "SATA" is (when I needed a new HDD, SATA & IDE was explained to me). No joke. I learned Windows under Vista and went behind the Desktop for the very first time in late 2007. That's the same time that I started to learn about Windbg too. Hardware confuses the hell out of me.

A bit of information for you (for better understanding):

AHCI - Advanced Host Controller Interface - this is a hardware
 mechanism that allows the software to communicate with Serial ATA (SATA)
 devices. It offers features such as hot-plugging and native command
 queuing (NCQ).

IDE - Integrated Drive Electronics - IDE is basically the "old" version of AHCI
 without hot-plugging and NCQ. (This is usually used during the Parallel ATA
 (PATA) era hard disks)

Now. AHCI mode and IDE mode -- what is it? IDE mode is to give you the
 greatest compatibility with older operating systems. While AHCI is as I
 mentioned above, modern version of the IDE -- use AHCI mode if you are
 running recent operating systems  (Windows Vista+ and Linux kernel from
 2.6.19+). IDE mode will allow you to connect older operating systems to
 SATA drives.

As I mentioned above, SATA is Serial ATA, and is the replacement for
 Parallel ATA (PATA) hard drives.

RAID - This is a storage technology where you combine multiple disks into a
 "single" unit, depending on the mode, there can be RAID-0 through RAID-6,
 and each with different configurations of the hard drive. I'll just explain the
 simple examples: RAID-0 which is striping but no parity or mirroring, this
 means there is no redundancy for data, If there is a failure on one disk, it
 will cause the data loss of the entire RAID array. Ex: You have 0110 as data
 to be written, 01 will go on Disk 1, and 10 will go on Disk 2, allowing for
 faster read/write access to the data.

RAID-1 - This is the opposite of RAID-0, which is mirroring without striping
 (no parity either). This basically means you have an exact clone of Disk 1
 on Disk 2, in case Disk 1 fails.

RAID0+1 does both what RAID 1 and 0 does, that is to say striping (writing
 data simultaneously to two [or more] drives. plus mirroring in case of
 failure) the minimum amount of drives required for this type of setup is 4
 IDENTICAL drives.

There are also RAID 2, 3, 4, 5 ,6. Which is just more implementation of
 different configurations of striping/parity/mirroring across drives.

That being said, your RAID mode will allow you for some type of RAID
 configuration, should you choose to do so.

Supplemental: Many SATA controllers can enable AHCI separately or in
 conjunction with RAID support. Intel recommends choosing RAID mode on
 their motherboards, which also enables AHCI, rather than AHCI/SATA mode
 for maximum flexibility (in case you ever want to build a RAID array), since
 there are some issues that occurs, usually BSOD, when you choose a
 different mode once an operating system has already been installed.

Supplemental: Many SATA controllers can enable AHCI separately or in conjunction with RAID support. Intel recommends choosing RAID mode on their motherboards, which also enables AHCI, rather than AHCI/SATA mode for maximum flexibility (in case you ever want to build a RAID array), since there are some issues that occurs, usually BSOD, when you choose a different mode once an operating system has already been installed.

However - I can see why they would first go after an Intel driver before the Microsoft driver. I know I would. Furthermore, it's not a stretch to assume that storport.sys + iastor.sys co-mingle. I myself would go after the Intel driver - never would assume that there is an issue with storport.sys.

And here is the essence. How it is possible that Microsoft puts its generic driver to handle only SATA AHCI mode "storport.sys" (sans/without anciend IDE and RAID), and then upon installing INTEL AHCI + RAID driver "iastor.sys" these two things live together? I am really confused here: why these two drivers MUST co-exist?

INTEL claims that their driver "iastor.sys" is able to handle SATA AHCI and RAID (if you do have RAID creations)???

Thank you,
_nobody_

 

[_nobody_]

IntelRST adds one driver to the populated drive channels and one driver to the controller - they sit alongside the MS AHCI SATA drivers, in a JBOD scenario, that's just adding stuff that isn't needed, there's no RAID/caching drivers for RST to control.

Thank you for posting your thoughts, satrow... I am thinking about what you wrote here... Really in depth! :whistling:

You would like to say, that "storport.sys" and "iastor.sys" are the two drivers for the INTEL RAID storage driver? Am I right/correct here? :uhoh:

Thank you,
_nobody_

 

[satrow]

And here is the essence. How it is possible that Microsoft puts its generic driver to handle only SATA AHCI mode "storport.sys" (sans/without anciend IDE and RAID), and then upon installing INTEL AHCI + RAID driver "iastor.sys" these two things live together? I am really confused here: why these two drivers MUST co-exist?

INTEL claims that their driver "iastor.sys" is able to handle SATA AHCI and RAID (if you do have RAID creations)??

I would guess that storport.sys is needed to hook into the Windows kernel/Ring0, it would be potentially risky/dangerous to allow 3rd party drivers direct access without a 'buffer'.

 

[satrow]

You would like to say, that "storport.sys" and "iastor.sys" are the two drivers for the INTEL RAID storage driver? Am I right/correct here?

Not quite, IRST has one driver hooked into the main AHCI/SATA Controller (iaStorA.sys, iaStorF.sys, iaStorS.sys or iastorV.sys?, depending on the controller chipset version?) and another (iaStor.sys?) hooked into each populated SATA channel. The stock Windows drivers remain.

The drivers might be hooked in the other way around, I don't have an IRST install here to check details.

When installed on a 'normal' system (jbod, just a bunch of disks), like most consumer and basic business PC's, they're simply not needed - but it's often tricky for the average user to find the base Intel chipset/graphics installer, it's probably easier for the PC OEM's to list IntelRST to cover more of the bases.

Windows can handle jbods fine out of the box on most recent Intel/AMD/Nvidia chipsets.

Keeping an efficient Windows install (hardware choices aside) is best done with the minimum number of 3rd party drivers/filters, if your motherboard has 'extra's' you don't use - maybe Firewire, bluetooth, parallel/serial ports, RAID, Ext. SATA etc. - turn them off at the BIOS/UEFI level, then the drivers for them shouldn't load.

John here, iirc, uses HP notebooks, he wipes them and clean installs them with Retail Windows. I can't fault him for that, study the System resources used by the HP software/drivers next time you get the chance.

Our colleague Patrick put together a good write up on uninstalling IRST (it can be a real pain, if not impossible short of a clean install - read the article's comments), it's well worth a read, especially when you have a machine in front of you with RST so that you can follow his method: Uninstalling the Intel(R) Rapid Storage Technology driver - Microsoft Community

 

[jcgriff2]

However - I can see why they would first go after an Intel driver before the Microsoft driver. I know I would. Furthermore, it's not a stretch to assume that storport.sys + iastor.sys co-mingle. I myself would go after the Intel driver - never would assume that there is an issue with storport.sys.

And here is the essence. How it is possible that Microsoft puts its generic driver to handle only SATA AHCI mode "storport.sys" (sans/without anciend IDE and RAID), and then upon installing INTEL AHCI + RAID driver "iastor.sys" these two things live together? I am really confused here: why these two drivers MUST co-exist?

INTEL claims that their driver "iastor.sys" is able to handle SATA AHCI and RAID (if you do have RAID creations)???

I can visualize iastor*.sys calling storport.sys rather than iastor*.sys containing duplicate code; IDK - just a guess.

Have you verified that both drivers are in fact loaded at the same time?

If I had the proper symbol files, it would be interesting to see a stack with both at the time of a BSOD. Seems very possible that storport.sys may be named as the probable cause, but iastor*.sys is the actual culprit.

Thank you for the hardware lesson!

Regards,

John

 

[_nobody_]

Thank you for interesting read. But I could not connect the dots... No too much information on the net.

Continuing to investigate this problem. To better to understand this problem, I went to see what I have as AHCI SATA driver, and here is what I found on my PC (HP EliteBook 840 G1):

Exactly this image, which does mean that it came via updates for WIN 7 64 Ultimate (what I have on my PC).

And this is also true:

Date & Version of drivers: 07/27/2015, 14.6.0.1029
WHQL: 29/07/15
Official: NO
Under: Windows 7/8/8.1/10 (32/64)
Release note: NO

For:
PCI\VEN_8086&DEV_8C02&CC_0106.DeviceDesc = 'Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_8C03&CC_0106.DeviceDesc = 'Intel(R) 8 Series Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_8C82&CC_0106.DeviceDesc = 'Intel(R) 9 Series Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_8C83&CC_0106.DeviceDesc = 'Intel(R) 9 Series Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_9C02&CC_0106.DeviceDesc = 'Intel(R) 8 Series/C220 Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_9C03&CC_0106.DeviceDesc = 'Intel(R) 8 Series Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_9C82&CC_0106.DeviceDesc = 'Intel(R) 9 Series Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_9C83&CC_0106.DeviceDesc = 'Intel(R) 9 Series Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_9D03&CC_0106.DeviceDesc = 'Intel(R) 6th Generation Core Processor Family Platform I/O SATA AHCI Controller' 

PCI\VEN_8086&DEV_A102&CC_0106.DeviceDesc = 'Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_A103&CC_0106.DeviceDesc = 'Intel(R) 100 Series/C230 Chipset Family SATA AHCI Controller' 

PCI\VEN_8086&DEV_8D02&CC_0106.DeviceDesc = 'Intel(R) 9 Series Chipset Family SATA AHCI Controller'

PCI\VEN_8086&DEV_2822&CC_0104.DeviceDesc = 'Intel Chipset SATA RAID Controller'

PCI\VEN_8086&DEV_282A&CC_0104.DeviceDesc = 'Intel Chipset SATA RAID Controller'

So, I see that I indeed have MSFT driver, which is actually 'Intel Chipset SATA RAID Controller'.

Now, I also found this on the net, trying to understand what driver storport.sys represents:

https://msdn.microsoft.com/en-us/library/windows/hardware/ff567541(v=vs.85).aspx

https://msdn.microsoft.com/en-us/library/windows/hardware/ff551359(v=vs.85).aspx

From this what I read, storport.sys is Microsoft RAID driver, but for server (I have just laptop here) capabilities.
______

Now, said that, the following is probably true (I am talking about DT, WS and server class of PCs (lot of this is Satrow's repetition, but I wanted to write it myself for better understanding):

The inbox RST storage Windows driver for servers DT+WS+Servers is storport.sys . For better/faster or better architecture (not sure here) INTEL adds its own RST drivers: one driver hooked into the main AHCI/SATA Controller (iaStorA.sys, iaStorF.sys, iaStorS.sys or iastorV.sys?, depending on the controller chipset version?) and another (iaStor.sys?) hooked into each populated SATA channel. The inbox storport.sys Windows driver (for some unknown reason) remains as basic foundation.

Thus, this BSOD comes out of storport.exe, but it is caused by one of anothers. Probably correct vision is that iastor*.sys calling storport.sys .

But I need to think/investigate more.

Thank you,
_nobody_