[SOLVED] BSOD KMODE_EXCEPTION_NOT_HANDLED portcls.sys

[evilldoll]

Hi gents,

God a weird BSOD just now.

Below is my minidump
https://we.tl/t-frVculN5GI

It's related to portcls.sys, and couldn't find any relevant info on the web.

Notes(recent stuff that I did before I started getting bsod):

• recently update windows 10 to build 1903
• installed an elgato stream deck (updated drivers after bsod)
• recently update my bios to the latest build (ASUS z 390f Gaming)
• AFTER the BSOD happened I updated my realtek drivers and voicemeter banana to the latest versions

Later edit:
- the reason I update bios and windows was because, before, when exiting a game(Black Desert, not sure if relevant) a few times, Windows completely froze, while still able to move my mouse around. I could highlight "items" on the desktop once, then it froze completely(could still move mouse).
Had to hard reset the PC.
Then the PC would boot in UEFI BIOS , for some reason, and even after restart it would to to BIOS settings. After around 3 restarts, the PC would hang on a blank(but active monitor) screen at which point I would hard stop the PC.
After I started the PC, it booted up normally, no crash dumps no nothing.


Cheers,
EvillDoll

P.S.: omg my first post, after years of lurking lol

 

[PC Tailor]

Welcome to the forums my friend / lurker!

I have debugged your dump file (thank you for attaching) and you can view the report here: https://pste.eu/p/ccKC.html

Summary of findings:

BugCheck 1E, {ffffffffc0000005, fffff80461204fc1, 0, ffffffffffffffff}
Probably caused by : portcls.sys ( portcls!CIrpStream::GetLockedRegion+c1 )

KMODE_EXCEPTION_NOT_HANDLED (1e)

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.

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)
This error can often be software, but can be hardware.

MODULE_NAME: portcls
IMAGE_NAME: portcls.sys

Some things to consider:

• I noticed you are runnig BIOS 805, however the latest is 1105.
• If you have updated BIOS, you will also want to make sure your Intel Management Engine Driver is also updated, as this has to be "aligned" with the BIOS.
• You had quite a lot of third party drivers running at the time of the crash.
• I would potentially query your joystick drivers.
• For some reason, one of your RAM modules did not pull through correctly, are you using mixed modules? or did all 4 modules come from 1 pack?
• Are you running any OC at all?

@Colif may have some experience with the modules loaded.

 

[evilldoll]

Welcome to the forums my friend / lurker!

I have debugged your dump file (thank you for attaching) and you can view the report here: https://pste.eu/p/ccKC.html

Summary of findings:


Some things to consider:

• I noticed you are runnig BIOS 805, however the latest is 1105.
• If you have updated BIOS, you will also want to make sure your Intel Management Engine Driver is also updated, as this has to be "aligned" with the BIOS.
• You had quite a lot of third party drivers running at the time of the crash.
• I would potentially query your joystick drivers.
• For some reason, one of your RAM modules did not pull through correctly, are you using mixed modules? or did all 4 modules come from 1 pack?
• Are you running any OC at all?

@Colif may have some experience with the modules loaded.

Ah, you're perfectly right, the website actually has a newer BIOS version, as I used EZ update to upgrade it. Will update and revert back.
Don't have a joystick installed :S
Third party drivers? Anything specific?
All 4 modules come from the same pack, got these way back when, and still using them.(I should probably update them as they're pretty old)
Regarding OC, I'm just using the XMP I profile from the motherboard.

 

[Colif]

system sure thinks it has a joystick in it -you have 4 logitech drivers on PC - Do you use a gamepad?

portcls is Microsoft Class Driver for Port/Miniport Device - seems to tie into Audio, see if any newer drivers for the Soundblaster

Or maybe update whatever this is - VB AUdio Voicemeter? now I know where I seen this before... searching for portcls I found a post talking about removing the Virtual audio cable to fix a BSOD - https://www.vb-audio.com/Voicemeeter/

vbaudio_vmvaio64_win7.sys	21/04/2014, 10:05:09	VB Audio	Virtual Audio Driver
vbaudio_vmauxvaio64_win7.sys	06/07/2014, 08:56:06	VB Audio	Virtual Audio Driver
vbaudio_cable64_win7.sys	14/08/2014, 07:15:25	VB Audio	Virtual Audio Driver

As Win 7 drivers sure will trip up win 10

funny, asus replace ASio.sys with ASio2.sys and yet you have both installed. Stop it Asus, please stop using the 2012 drivers.
Full set, Asus mobo and Asus GPU (just like me)

 

[evilldoll]

system sure thinks it has a joystick in it -you have 4 logitech drivers on PC - Do you use a gamepad?

portcls is Microsoft Class Driver for Port/Miniport Device - seems to tie into Audio, see if any newer drivers for the Soundblaster

Or maybe update whatever this is - VB AUdio Voicemeter? now I know where I seen this before... searching for portcls I found a post talking about removing the Virtual audio cable to fix a BSOD - https://www.vb-audio.com/Voicemeeter/

vbaudio_vmvaio64_win7.sys	21/04/2014, 10:05:09	VB Audio	Virtual Audio Driver
vbaudio_vmauxvaio64_win7.sys	06/07/2014, 08:56:06	VB Audio	Virtual Audio Driver
vbaudio_cable64_win7.sys	14/08/2014, 07:15:25	VB Audio	Virtual Audio Driver

As Win 7 drivers sure will trip up win 10

funny, asus replace ASio.sys with ASio2.sys and yet you have both installed. Stop it Asus, please stop using the 2012 drivers.
Full set, Asus mobo and Asus GPU (just like me)

Got the following USB devices plugged in:

• two webcams (I live stream) - 2x logitech
• elgato streamdeck
• ergodox ez keyboard
• at 2020 microphone
• logitech g502 wireless mouse

The above doesn't account for 4 drivers thou. Maybe there's a separate driver for my old wired mouse?

If this happens again and is related to portcls I'll disable VB AUdio Voicemeter and see if it occurs again. Had no clue tho, their site says w10 -.-

I've just updated the bios to 1105 and ME to the latest version.

The SoundBlaster is using the latest version.

 

[Colif]

old trick, relabel win 7 drivers as win 8 or win 10. Beats making new ones. They may have submitted them to MIcrosoft to get digitally signed to work with win 10.

Chinese site shows the drivers are part of Mouse drivers. its common to have more than 1 driver for devices, not much to worry about there.

 

[evilldoll]

Happened again:
https://we.tl/t-ghEwz93XiD

This time with a ntoskrnl.exe
bugcheck WHEA_UNCORRECTABLE_ERROR bsod

Removed voicemetter from my pc.

As far as I know WHEA is a hardware error, god dammit.

Note: seems to always happen after I close a specific game, Black Desert Online.(don't really play anything else so dunno if it's really that specific to the game itself)

later edit: also loaded optimized default, putting my ram at 2133 instead of it's "default" 2666(or w/e it was )
later later edit: swapped dimm's slots

 

[Colif]

WHEA errors can be both hardware or software. If they still return after the ram changes, read on.
WHEA errors are called by the CPU but not necessarily caused by it.
They can be caused by any hardware
They can be caused by over heating
They can be caused by overclocking software (see below)
They can sometimes be caused by other drivers.

what are you using AI suite for? one cause of BSOD is software like it that can change CPU values.
Try removing it and GPU Tweak 2, as both use Asio.sys which I have seen cause these errors.
remove MSI Afterburner if its installed (I don't see it)

 

[evilldoll]

WHEA errors can be both hardware or software. If they still return after the ram changes, read on.
WHEA errors are called by the CPU but not necessarily caused by it.
They can be caused by any hardware
They can be caused by over heating
They can be caused by overclocking software (see below)
They can sometimes be caused by other drivers.

what are you using AI suite for? one cause of BSOD is software like it that can change CPU values.
Try removing it and GPU Tweak 2, as both use Asio.sys which I have seen cause these errors.
remove MSI Afterburner if its installed (I don't see it)

Allright, cheers, I'll remove both AI Suite and MSI Afterburner if this happens again.

 

[evilldoll]

WHEA errors can be both hardware or software. If they still return after the ram changes, read on.
WHEA errors are called by the CPU but not necessarily caused by it.
They can be caused by any hardware
They can be caused by over heating
They can be caused by overclocking software (see below)
They can sometimes be caused by other drivers.

what are you using AI suite for? one cause of BSOD is software like it that can change CPU values.
Try removing it and GPU Tweak 2, as both use Asio.sys which I have seen cause these errors.
remove MSI Afterburner if its installed (I don't see it)

Quick question, when you mentioned GPU Tweak 2, were you referring to MSI Afterburner?

Cheers,
Evil

 

[PC Tailor]

Quick question, when you mentioned GPU Tweak 2, were you referring to MSI Afterburner?

Cheers,
Evil

GPU Tweak is Asus Suite software.
Also uninstall MSI Afterburner

 

[Colif]

I thought I saw something on there that implied GPU Tweak 2 was on there.. Nevermind, Afterburner is something that can also cause these errors.

paste site is being strange and rejecting links

 

[evilldoll]

I thought I saw something on there that implied GPU Tweak 2 was on there.. Nevermind, Afterburner is something that can also cause these errors.

paste site is being strange and rejecting links

Cheers.
Removed MSI Afterburner and all stuff related to AI Suite + VoiceMeter and seems to be ok, for now.
Will wait a bit and revert back.

 

[axe0axe0]

WHEA errors are called by the CPU but not necessarily caused by it.

Depends on the type of the error, most often it is an error reported by the CPU, but sometimes it's also a PCI/Bus error or a boot error, the latter is the case here.

@evilldoll, could you export the events from System in eventviewer.msc and upload it. I suspect the events may reveal something about the 0x124.
Also, please ensure every setting for the RAM and CPU in the BIOS are at stock.

 

[evilldoll]

So, as of the 15th I haven't had any other BSODs, until today -.-.
Minidump attached:
https://we.tl/t-JUyt7kztdQ
Event log:
https://we.tl/t-IWhQs1iUXH

Notes;
Update windows 10 to PRO from HOME recently (3 days ago, ish)
Update video card just now
CPU is stock(removed AI suite some time ago and restored bios to optimized defaults)
RAM is on XMP II. Going stock(default) lowers the freq. to 2133. Should I set timings to auto ?

 

[evilldoll]

Seems to be happening again and it's driving me crazy.
My last dumps:
https://we.tl/t-L0weUCadcU

Had a "clean" period between 18 august and today but it seems it's happening again.
I ran a memtestx86 for one pass and had no error. Will run a 4 pass later.
Reinstalled display driver with DDU under safe mode.

Ordered new RAM(I can rma them wihin a month, no questions asked if I still get BSODS).

I thought I saw something on there that implied GPU Tweak 2 was on there.. Nevermind, Afterburner is something that can also cause these errors.

paste site is being strange and rejecting links

Depends on the type of the error, most often it is an error reported by the CPU, but sometimes it's also a PCI/Bus error or a boot error, the latter is the case here.

@evilldoll, could you export the events from System in eventviewer.msc and upload it. I suspect the events may reveal something about the 0x124.
Also, please ensure every setting for the RAM and CPU in the BIOS are at stock.

GPU Tweak is Asus Suite software.
Also uninstall MSI Afterburner

Sorry for the quotes, I'm not sure how to tag someone on the forums.
Cheers,

Later update: I think I mentioned this before, but the bsods seems to always be happening while I play a specific game, Black Desert Online (albeit, that's what I mostly do on my home PC, not sure if related, but figured I'd mention it)

 

[PC Tailor]

I have run the dump files and the full reports can be viewed here:

Dump 1: https://pste.eu/p/exGV.html MEMORY_MANAGEMENT
Dump 2: https://pste.eu/p/FXOh.html KMODE_EXCEPTION_NOT_HANDLED
Dump 3: https://pste.eu/p/HAxD.html MEMORY_MANAGEMENT
Dump 4: https://pste.eu/p/JwlX.html MEMORY_MANAGEMENT

Summary of findings:

BugCheck 1A
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Bugcheck Description:
MEMORY_MANAGEMENT
"This indicates that a severe memory management error occurred. Parameter 1 identifies the exact violation. For full details of each P1:

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x1a--memory-management"

About your bugcheck:
"Running the Windows Memory Diagnostic tool or memtest could be useful as well to exclude any kind of problem affecting the physical memory modules.

This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis.

• Confirm that hardware is compatible with your system.
• View the third party modules of the report to view which drivers may be misbehaving."

Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

Based on what we're looking at, I highly suspect we could be look at hardware diagnosis soon. I'll add some more info today - I have just run the dumps for now.

 

[Colif]

Ordered new RAM(I can rma them wihin a month, no questions asked if I still get BSODS).

The errors are all blaming different things, sure looks like could be ram, but if he has already ordered new ram, is it worthwhile testing the current ones?

 

[evilldoll]

Thanks for the quick feedback gents, really appreciate it. I honestly hope it's the damn ram.
One more thing I'll try is to run the PC, for the next few days, without my webcams and streamdeck and see how that goes.

 

[evilldoll]

I have run the dump files and the full reports can be viewed here:

Dump 1: https://pste.eu/p/exGV.html MEMORY_MANAGEMENT
Dump 2: https://pste.eu/p/FXOh.html KMODE_EXCEPTION_NOT_HANDLED
Dump 3: https://pste.eu/p/HAxD.html MEMORY_MANAGEMENT
Dump 4: https://pste.eu/p/JwlX.html MEMORY_MANAGEMENT

Summary of findings:


About your bugcheck:
"Running the Windows Memory Diagnostic tool or memtest could be useful as well to exclude any kind of problem affecting the physical memory modules.

This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis.

• Confirm that hardware is compatible with your system.
• View the third party modules of the report to view which drivers may be misbehaving."

Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

Based on what we're looking at, I highly suspect we could be look at hardware diagnosis soon. I'll add some more info today - I have just run the dumps for now.

So if I'm reading the reports correctly, three out of those 4 bsods are due to BlackDesert or does it mean the app that was running when the bsod occured was Black Desert ?

 

[Colif]

if you hadn't ordered ram already I would have suggested you at least let memtest run 4 passes.
can you give me specs of the PC again? PC tailors dumps from a month ago are likely 404 errors now and he didn't include them in his last postings

So if I'm reading the reports correctly, three out of those 4 bsods are due to BlackDesert ?

No, it was what crashed, its not the cause

it could be it uses enough ram to cause the parts of chip that are faulty to flip out and cause random errors

 

[evilldoll]

if you hadn't ordered ram already I would have suggested you at least let memtest run 4 passes.
can you give me specs of the PC again? PC tailors dumps from a month ago are likely 404 errors now and he didn't include them in his last postings




No, it was what crashed, its not the cause

it could be it uses enough ram to cause the parts of chip that are faulty to flip out and cause random errors

https://we.tl/t-HtBoorwXd0 - dx diag

 

[evilldoll]

I've also disabled AsUpIO.sys and AsIO.sys with Autorun as it seems uninstalling aisuite didn't actually remove the drivers.

 

[evilldoll]

I have run the dump files and the full reports can be viewed here:

Dump 1: https://pste.eu/p/exGV.html MEMORY_MANAGEMENT
Dump 2: https://pste.eu/p/FXOh.html KMODE_EXCEPTION_NOT_HANDLED
Dump 3: https://pste.eu/p/HAxD.html MEMORY_MANAGEMENT
Dump 4: https://pste.eu/p/JwlX.html MEMORY_MANAGEMENT

Summary of findings:


About your bugcheck:
"Running the Windows Memory Diagnostic tool or memtest could be useful as well to exclude any kind of problem affecting the physical memory modules.

This can be driver or hardware based. If you are encountering other hardware issues, you may have to look at hardware diagnosis.

• Confirm that hardware is compatible with your system.
• View the third party modules of the report to view which drivers may be misbehaving."

Some things to consider:
I would highly advise you to view the full report above, as this will contain much more detail as to the bugcheck and modules running at the time.

Based on what we're looking at, I highly suspect we could be look at hardware diagnosis soon. I'll add some more info today - I have just run the dumps for now.

Also, if you don.t mind me asking, what tool are you using to get those awesome outputs ?

 

[PC Tailor]

The errors are all blaming different things, sure looks like could be ram, but if he has already ordered new ram, is it worthwhile testing the current ones?

Agreed no point in testing - if you're wondering, my programs has an automatic set of "generic actions" in the "about your bugcheck" section, I just expand with the some things to consider bit manually mself based on what I see.

Also, if you don.t mind me asking, what tool are you using to get those awesome outputs ?

It's my own program. I do a lot of manual debugging so I actually created an Excel package and script that runs and extracts all the information I want automatically and creates the report. Then based on experience I will run some further commands manually if I see necessary (although usually not required). Also makes it really easy to update and change accordingly.

The advice etc. in it will constantly be expanded based on experience, so often the "about bugcheck" is a mix of my input, other experts input (like Colif & Gardenman) and microsoft development knowledge resources.

Gardenman has a better self made program that is excellent.

unfortunately there aren't any great and versatile solutions online, its why myself, Colif, and Gardenman often advise against using WhoCrashed etc. because it often doesn't give you half the info you need and blames the wrong things.