Question SYSTEM_SERVICE_EXCEPTION: CAUSED BY DRIVER STORPORT.SYSTEM (0x0000003b)

Apr 12, 2024
16
1
15
I recently just upgraded my gaming build with a new motherboard and everything seemed to be fine for a bit. I was playing Spider-Man Remastered on the High settings and left it on pause during gameplay because I had to deal with something. I left it on for almost an hour. When I came back to resume playing, it went on without a hitch for a bit, but suddenly, the screen froze with an awful buzzing sound and then the PC just rebooted itself with no blue screen at all.

I checked Event Viewer and BlueScreenView, this is what I found.

Here's the link to the Minidump if you want to check on it yourself. https://www.mediafire.com/file/2g7yntr25xyu91e/041224-8187-01.dmp/file

From what I can gather, storport.sys has something to do with storage and memory.

I'm not sure if this is a RAM issue because I enabled XMP which made it run at a constant 3200mh. Besides the RAM, I'm suspecting it could be a power supply issue or my SSD is already dying (it's at 70% health which is apparently still healthy) Besides the XMP, I never overclock my computer. It might be worth noting that the game was installed in a WD Green SSD with 70% health. I know WD Greens are low-end and not really meant for storing games, but I'm not sure if that has anything to do with it. Just recently, I replaced it with a 512GB NVME SSD.

Can anybody help me with this? This is the first time this happened and it got me worried enough that I want to look this up before it happens again. For now, I've disabled XMP and see if that makes a difference. If anybody can help identify what could be the cause of those errors, I would pretty much appreciate it.


Specs:

Motherboard: Gigabyte B550M DS3H rev 1.5 (with updated BIOS)

GPU: Gigabyte GeForce GTX 1660 Ti (no overclock)

CPU: Ryzen 5 2600 (not overclocked)

OS: Windows 11

RAM: PNY XLR8 16GB (2x8) with 3200mh XMP compatibility

PSU: Corsair CV550 550W
 
Last edited:

Ralston18

Titan
Moderator
Take a look in Reliability History/Monitor for error codes, warnings, and even informational events being captured just before or at the times problems occurred.

Reliability History/Monitor is much more end user friendly than Event Viewer.

One thing to look for is increasing numbers of varying errors over time.

Along with some constantly occurring set of common errors.

Either situation being an indication of a faulty or failing PSU.

= = = =

Try to borrow another known working (from a system with no problems) PSU with at least 650 watts.

Install and test using only the cables that come with the borrowed/test PSU.

And, as always, before doing anything else be sure that all important data is backed up at least 2 x to locations off of the current problem PC. Verify that the backups are recoverable and readable.
 
  • Like
Reactions: BattaAug0201

USAFRet

Titan
Moderator
No, the OS is still the same one installed in my primary Kingston SSD which was from my previous motherboard. Could that have caused any issues?
Absolutely!

New motherboard + old OS can often have issues.

Possible outcomes if you do not:
1. It works just fine
2. It fails completely
3. It "works", but you're chasing issues for weeks/months.

Looks like you are at #3.
 
Apr 12, 2024
16
1
15
Take a look in Reliability History/Monitor for error codes, warnings, and even informational events being captured just before or at the times problems occurred.

Reliability History/Monitor is much more end user friendly than Event Viewer.

One thing to look for is increasing numbers of varying errors over time.

Along with some constantly occurring set of common errors.

Either situation being an indication of a faulty or failing PSU.

= = = =

Try to borrow another known working (from a system with no problems) PSU with at least 650 watts.

Install and test using only the cables that come with the borrowed/test PSU.

And, as always, before doing anything else be sure that all important data is backed up at least 2 x to locations off of the current problem PC. Verify that the backups are recoverable and readable.
Here's the .xml fiile.

https://www.mediafire.com/file/farep3nmerob3mb/Reliability.XML/file

I don't really know how to interpret what's written there, so you might be able to figure it out.

There were unexpected shutdowns on April 11th, but that was because I tried to boot RAM with XMP on while it was on socket A1/B1 instead of A2/B2 which caused the PC to restart every time I boot it up with the XMP enabled until I switched them to A2/B2. There doesn't seem to be much errors besides the that one crash that happened which occurred at 3:34.

I'm considering other causes for now instead of the PSU because I don't really have a way to borrow another PSU with at least 650 watts nor do I currently have the money to buy a new one. I can't borrow my friend's because he's using it. My salary won't come until next month, so hopefully by then, this can be figured out.

I'm running my machine at 2133 clockspeed RAM and I haven't encountered anything like it yet, but I'm only knocking on wood here. My gut tells me it might happen again eventually.
 
Last edited:
Apr 12, 2024
16
1
15
Absolutely!

New motherboard + old OS can often have issues.

Possible outcomes if you do not:
1. It works just fine
2. It fails completely
3. It "works", but you're chasing issues for weeks/months.

Looks like you are at #3.
Thanks for this tip. I'll reinstall the OS right now and see if it does something.
 
storport is scsci driver..used for example with your nvme drive
you should probably reinstall chipset drivers, if platorm didnt change too much, windows reinstall might not be necesary

you can also run memtest if you suspect ram instability
 
Apr 12, 2024
16
1
15
storport is scsci driver..used for example with your nvme drive
you should probably reinstall chipset drivers, if platorm didnt change too much, windows reinstall might not be necesary

you can also run memtest if you suspect ram instability
Did that, passed in all 4 tests.

For now, I'm not using the WD Green SSD and see if occurs again, but I'm still willing to brainstorm what could cause it.

I'll also reinstall Windows just to make sure.
 
Apr 12, 2024
16
1
15
Take a look in Reliability History/Monitor for error codes, warnings, and even informational events being captured just before or at the times problems occurred.

Reliability History/Monitor is much more end user friendly than Event Viewer.

One thing to look for is increasing numbers of varying errors over time.

Along with some constantly occurring set of common errors.

Either situation being an indication of a faulty or failing PSU.

= = = =

Try to borrow another known working (from a system with no problems) PSU with at least 650 watts.

Install and test using only the cables that come with the borrowed/test PSU.

And, as always, before doing anything else be sure that all important data is backed up at least 2 x to locations off of the current problem PC. Verify that the backups are recoverable and readable.
Here's a recording of the Reliability Monitor

https://streamable.com/pkhiou
 
Apr 12, 2024
16
1
15
Lots going in in Reliability History/Monitor....

Focus on fixing the New motherboard + old OS via a Windows reinstall.
I'm reinstalling Windows right now and the motherboard is installing drivers that it hasn't installed before. This could be it because I DID NOT uninstall the drivers of the last motherboard.

I'll let you know what happens.
 
Apr 12, 2024
16
1
15
Did a reinstall, also moved Windows to my brand new NVME. No problems so far. I'll update if it happens again.

I still would love to hear the opinions of others, though.
 
Apr 12, 2024
16
1
15
I hope that NVMe was the only drive physically connected when you did this install?
Uh... No. My Kingston 240GB was also hooked up when I installed it, which was the original drive Windows was installed in...

Do I have to reinstall it yet again while having the other SSD disconnected?
 

USAFRet

Titan
Moderator
Uh... No. My Kingston 240GB was also hooked up when I installed it, which was the original drive Windows was installed in...

Do I have to reinstall it yet again while having the other SSD disconnected?
Maybe.

What likely happened was the boot info for this new OS is merged with the old OS, on the Kingston.

There are commands to "fix it", but another fresh install is probably the easiest.

 
Apr 12, 2024
16
1
15
Uh... No. My Kingston 240GB was also hooked up when I installed it, which was the original drive Windows was installed in...

Do I have to reinstall it yet again while having the other SSD disconnected?

Maybe.

What likely happened was the boot info for this new OS is merged with the old OS, on the Kingston.

There are commands to "fix it", but another fresh install is probably the easiest.

Damn, how repetitive. Okay, I'm reinstalling it now WITHOUT the Kingston SSD.
 
Apr 12, 2024
16
1
15
Been doing a OCCT stress test for an hour now, it's still going fine. Normally, it would have crashed already by now if it's under this heavy load, but so far so good. I'm definitely still knocking on wood.

Not sure if it was me reinstalling Windows or disabling XMP, but I'm definitely replacing my 550w PSU with a new one within this month. You guys have any suggestions for a good 750w PSU that should last me a while when I upgrade?
 
Apr 12, 2024
16
1
15
Okay, I'm using a brand new NVMe as I've mentioned and I still have not connected my Kingston and WD Green, and I have noticed a few differences.

Before, I would get occasional microstutters where the computer would freeze for a split-second accompanied by a loud buzzing sound. That seems to have been fixed. (knock on wood)

My latency in LatencyMon has drastically improved and no longer reaches the red area like it did before.

Everything just "feels" faster

My downloads on Steam no longer randomly drop from 560mbps to 0 mbps for a few seconds like it used to whenever I download games to the WD Green.

I ran OCCT for almost two hours, no errors found. Before, it would usually find errors around 20 minutes in.

My NVMe's health is 100% whilst the WD Green was four years old and at 70% health with only 540 MB/s read and 430 MB/s write speeds while my brand new NVMe has up to 3500 MB/s. I have to say that the WD Green was used heavily for playing demanding titles such as Cyberpunk 2077, Red Dead Redemption II, Spider-Man Remastered, Apex Legends, and many other games since 2020. That could have worn the poor SSD down (and it's not even meant for gaming, apparently)

The audio no longer pops sometimes when I play music.

Granted, there were plenty of signs there was something wrong with my computer that I simply ignored, but I figured it was kinda getting worse until I finally got the crash that made me create this thread. I had no idea an SSD is capable of causing something like this considering that wasn't where my OS was installed.

Again, I'm knocking on wood here. I'll update if something happens again or if I finally upgrade my PSU.

I might consider enabling XMP again for a while and see if it was actually THAT that caused the crash and the SSD problems I experienced for the last two-ish years was not actually related to that. I've read that Ryzen 5 2600 does not actually support RAM speeds around 3000hz, so there's that.

I'll also eventually plug my Kingston back on because that's also pretty new with 100% health. My WD Green is four years old and never had Windows installed in it, I had a previous SSD that's even older than the WD Green that was made by Biostar that only had 120GB that came with my old motherboard, which was a A230 where Windows was installed before I bought the Kingston.

I guess this is a lesson learned to me: reinstalling Windows after a motherboard upgrade is a big deal.
 
Last edited:
Apr 12, 2024
16
1
15
Been playing for hours, never happened again. Looks like whatever it was was already taken care of, but I'll still keep knocking on wood.

If people still have any idea what they think caused it, I would like to hear it. I'll be buying a new PSU anyway to make sure.