[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

 

[evilldoll]

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.


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.

Understood. Thanks for the feedback; mighty fine tool you have.
I'm assuming WhoCrashed Pro isn't worth it either ?

 

[PC Tailor]

Understood. Thanks for the feedback; mighty fine tool you have.
I'm assuming WhoCrashed Pro isn't worth it either ?

No. 😆

Does exactly the same thing. Translates, doesn't debug.
Downfall for example if you are encountering RAM module errors, I can run extra commands to back trace stack text or whats ran through the memory, you can only do that with a debugger, whocrashed etc. will just translate the dump file and you can't manipulate the output.

I may share the package at some point - being as nearly everyone has excel. But I'd have to do more background work and write up the instructions

And thank you, very kind of you my friend. Let me know if you can think of any improvements to the report.

 

[evilldoll]

No. 😆

Does exactly the same thing. Translates, doesn't debug.
Downfall for example if you are encountering RAM module errors, I can run extra commands to back trace stack text or whats ran through the memory, you can only do that with a debugger, whocrashed etc. will just translate the dump file and you can't manipulate the output.

I may share the package at some point - being as nearly everyone has excel. But I'd have to do more background work and write up the instructions

And thank you, very kind of you my friend. Let me know if you can think of any improvements to the report.

First improvement I can think of is adding a donation link

 

[Colif]

Expecting people to understand the raw dump results is expecting too much, its why Gardenmen may link to the paste files, for me more than anything, he tries to work out what might be cause underneath reports (like you do) and doesn't expect the op to work out what all the pages in his paste are for.

So running all the extra steps might allow you to find answers without the op needing to understand how or what it all looks like in back end.

A lot of it is knowing what has caused problems in the past and recognising patterns. If X is crashing, its probably Y. Its actually easier to work out BSOD problems than it is to work out niggles that don't cause them. I spent 6 months trying to work out one of those on my PC.

 

[evilldoll]

Right, so since last Wednesday I replaced my ram, stopped the old Asus drivers and I believe I've ran the PC with a gaming running for 4 days straight(24 hours x 4) plus my daily "normal" usage and I'm fine and dandy.
Thank you gents again for all the help!

 

[PC Tailor]

Hopefully that's it solved then.
Hope we've been of some help my friend