Storport.sys BSOD

U

UnfortunatePanda

Member
Joined
May 2, 2016
Posts
16
· OS - Windows 10
· x64 (64-bit)
· Original OS - Windows 10
· OS is an OEM version (came pre-installed on system)
· Age of system - 1 year
· have you re-installed the OS? - Yes, twice

· Intel Core i5 - 7300HQ @ 2.50 Ghz
· Video Card (Dedicated) - Nvidia Geforce GTX 1060 Max-Q
· Video Card (Integrated) - Intel HD Graphics 630

· System Manufacturer - Dell
· Exact model number - Dell Inspiron 15 Gaming 7577
· Laptop



Hello,

Iv'e recently tried to conduct one of my Dell updates on my PC, during which my PC unexpectedly crashed. After that My PC was running extremely slow and laggy, and it was impossible to play anything. I then decided to reinstall Windows to try resolve this issue. After re-installing Windows, I landed on the "Just a moment" screen, right before logging in fresh, and I was stuck there permanently. I restarted my laptop to see if it helped and it only asked me to Re-install windows again. I had to download a Windows Recovery Tool from the Microsoft website and I could finally reinstall Windows clean. Now I'm having a BSOD problem. Every time 10-20 minutes, I get the Bluescreen errors: IQRL_NO_LESS_OR_EQUAL and BAD_POOL_HEADER. From a bit of analyzing the DUMP files from BSODViewer, and it seems like Storport.sys is causing the problem. I don't quiet know what that is. Iv'e tried the following:

Windows Memory Diagnosis
Chkdsk
Sfc/Scan Now
Updated each driver from Device Manager
Uninstalled Intel Rapid Technology (Cant re-install it)
Used an application called: Free Windows Registry Repair
Used an application called: Driver Booster 6


Sorry, i'm really panicking and don't know what to do. Thanks for your time

View attachment SysnativeFileCollectionApp.zip
 
Hi. . .

Storport.sys is a Microsoft driver (meaning it is sacrosanct and the only way it gets updated/patched is via Windows Updates) and does appear on the stack in the 0x19 (bad pool caller) BSOD, but the dump lists as the probable cause:
Code: 
[font=lucida console]FAILURE_BUCKET_ID:  CORRUPT_MODULELIST_0x19_22

Unknown_Module_00000000`00000000  
[/font]
Driver Reference Table (DRT) | storport.sys

The second dump (0xa bugcheck - driver...IRQL) lists:
Code: 
Probably caused by : memory_corruption

You must run RAM and HDD tests.


Regards. . .

jcgriff2
 
Last edited:
This looks like mem corruption caused by a driver due to two reasons.

Code: 
1: kd> .bugcheck
Bugcheck code 00000019
Arguments 00000000`00000022

First, the 0x22 first parameter implies that we had an address in the stack go without a tracking entry, because it was freed or failed to be allocated to begin with. 0x19 dump is corrupt so there's not much digging we can do.

Code: 
1: kd> knL
 # Child-SP          RetAddr           Call Site
00 fffffd00`d3c37828 fffff805`43e23451 0xfffff805`43dc8040
01 fffffd00`d3c37830 00000000`00000019 0xfffff805`43e23451
02 fffffd00`d3c37838 00000000`00000022 0x19
03 fffffd00`d3c37840 00000000`00000000 0x22

Second, I also suspect a driver because the other dump (the 0xA) shows some plug and play issues:

Code: 
1: kd> !blackboxpnp
    PnpActivityId      : {00000000-0000-0000-0000-000000000000}
    PnpActivityTime    : 131883075286341307
    PnpEventInformation: 3
    PnpEventInProgress : 0
    PnpProblemCode     : 24

0x24 problem code tells us
This device is not present, is not working properly, or does not have all its drivers installed.
Click to expand...

The DeviceId string isn't helpful unfortunately in your case. If we check the stack at the time of the crash:

Code: 
1: kd> knL
 # Child-SP          RetAddr           Call Site
00 ffffeb81`10c375e8 fffff804`7ea6e869 nt!KeBugCheckEx
01 ffffeb81`10c375f0 fffff804`7ea6ac8e nt!KiBugCheckDispatch+0x69
02 ffffeb81`10c37730 fffff804`7e8ded70 nt!KiPageFault+0x44e
03 ffffeb81`10c378c8 fffff804`7e999e1e nt!MI_READ_PTE_LOCK_FREE
04 ffffeb81`10c378d0 fffff804`7e9e6809 nt!MmFreeContiguousMemory+0x3e
05 ffffeb81`10c37940 fffff807`240a5457 nt!HvlpFreeOverlayPages+0x9
06 ffffeb81`10c37970 fffff807`23fdfe20 storport!StorPortExtendedFunction+0x23437
07 ffffeb81`10c37a40 fffff807`23ffa3d3 iaStorAVC!Wcdl::Allocator::freeContiguous+0x20
08 ffffeb81`10c37a80 fffff807`23ff1d67 iaStorAVC!readSmartAttribsCompletion+0x2bf
09 ffffeb81`10c37b30 fffff807`23fee81c iaStorAVC!NvmRequest::complete+0x1b7
0a ffffeb81`10c37b70 fffff807`23fed2ef iaStorAVC!NvmePort::processCompletionQueueForSharedInterrupt+0x144
0b ffffeb81`10c37c00 fffff804`7e90eda7 iaStorAVC!NvmePort::dpc+0x47
0c ffffeb81`10c37c60 fffff804`7e90e3ee nt!KiExecuteAllDpcs+0x2e7
0d ffffeb81`10c37da0 fffff804`7ea63ea5 nt!KiRetireDpcList+0x1ae
0e ffffeb81`10c37fb0 fffff804`7ea63c90 nt!KxRetireDpcList+0x5
0f ffffeb81`11e2f6a0 fffff804`7ea63555 nt!KiDispatchInterruptContinue
10 ffffeb81`11e2f6d0 fffff804`7ea5eb01 nt!KiDpcInterruptBypass+0x25
11 ffffeb81`11e2f6e0 00000000`00000000 nt!KiInterruptDispatch+0xb1

We were executing some deferred procedure calls which involved the Intel Rapid Storage driver and non volatile storage (NVME). It was freeing contingious memory and hit a pagefault, therefore calling the bug check. If we check your sysinfo, you have a drive connected via NVME:

Code: 
Model    NVMe KXG50ZNV256G NVM

Looks to be an SSD?

Code: 
1: kd> lmvm iaStorAVC
Browse full module list
start             end                 module name
fffff807`23f60000 fffff807`24075000   iaStorAVC # (pdb symbols)          c:\symbols\sym\iaStorAVC.pdb\1D854E5ECD3247209E135B07E93C573C1\iaStorAVC.pdb
    Loaded symbol image file: iaStorAVC.sys
    Mapped memory image file: c:\symbols\sym\iaStorAVC.sys\5A7AE8C0115000\iaStorAVC.sys
    Image path: \SystemRoot\System32\drivers\iaStorAVC.sys
    Image name: iaStorAVC.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Feb  7 03:53:36 2018

Intel Rapid Storage is not necessary unless you're running in RAID, which it looks like you aren't. It's also historically buggy, so I'd uninstall it and see what happens. If you continue to crash, I would actually consider enabling Driver Verifier with pool options such as tracking to try and pinpoint a driver.
 
Hello,

Thanks for the quick replies, really appreciate it.

View attachment Minidump.rar

As requested, here's the Driver Verifier result from 24 hours yesterday. Iv'e already managed to uninstall Intel Rapid Storage Technology from my PC, but it hasn't solved the problem. Iv'e conducted a Memtest86 and the HDD test, also checked the health of my SSD and found nothing wrong. I'm still in the process of figuring out which SSD I have, and what firmware it is, before proceeding with the update.

jcgriff2 said:
Storport.sys is a Microsoft driver (meaning it is sacrosanct and the only way it gets updated/patched is via Windows Updates)
Click to expand...

Not sure what to do about this. Am I supposed to try downgrade my version of Windows to a previous build, somehow try undo some updates, i'm not sure how to work around that.

Also, a new problem. After using Driver Verifier and then getting a BSOD, my PC is running extremely sluggish ever since. Could there be a reason for that?


Thank you for your time,
Sincerely
Heavensdown
 
No - try to update your Intel rapid storage drivers.

I cannot open the dump.

Please try ZIPPING it and attach to next post. Thank you.

Regards. . .

jcgriff2
 
Last edited:
The driver is still loaded and on the system at the time of the DV crash dump.

Code: 
    Image name: iaStorAVC.sys
    Browse all global symbols  functions  data
    Timestamp:        Wed Feb  7 03:53:36 2018 (5A7AE8C0)
    CheckSum:         000E383B
    ImageSize:        00115000
    File version:     15.44.0.1010
    Product version:  15.44.0.1010
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0

Make sure you got all remnants of IRST via control panel, etc.

DV is actually also labeling it as the failing allocator for the contiguous memory I spoke about earlier:

Code: 
km:av_vrf_iastoravc!wcdl::allocator::freecontiguous
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top