Question Random BSOD's but unsure what the cause is

[calvinhunt98]

So, over the last two days I have gotten a series of BSODs that I think are related to my audio drivers, or somehow my USB Mixer, but i am not certain and I am unsure how to find out.

Below I have copied my BSOD that is the most recent, however I noticed when I opened WinDbg, that it said downloading "ysusb_w10_64", which related to my USB Mixer's audio driver from Yamaha. I have the AG06, which requires a driver for windows, but for a long time I have had various issues that I could never find the cause of.

Sometimes I would have BSODs after waking my computer from sleep, which was happening a lot, but recently stopped. Yesterday I had a random serious of BSODs that I have no clue what the cause is from. I could really use some help on this one.

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000d, Attempt to release quota on a corrupted pool allocation.
Arg2: ffffe4865412ec00, Address of pool
Arg3: 00000000fffff802, Pool allocation's tag
Arg4: 1802d409e320bcea, Quota process pointer (bad).

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


KEY_VALUES_STRING: 1


PROCESSES_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: System manufacturer

SYSTEM_PRODUCT_NAME: System Product Name

SYSTEM_SKU: ASUS_MB_CNL

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 0702

BIOS_DATE: 12/21/2018

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: PRIME Z390-A

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: d

BUGCHECK_P2: ffffe4865412ec00

BUGCHECK_P3: fffff802

BUGCHECK_P4: 1802d409e320bcea

FAULTING_IP:
portcls!CUnknown::vector deleting destructor'+21 fffff8027a015f51 0f1f440000 nop dword ptr [rax+rax]

BUGCHECK_STR: 0xc2_d

CPU_COUNT: 10

CPU_MHZ: e10

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 9e

CPU_STEPPING: c

CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: A0'00000000 (cache) A0'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: CJHUNT

ANALYSIS_SESSION_TIME: 02-13-2019 20:06:11.0475

ANALYSIS_VERSION: 10.0.18303.1000 amd64fre

LAST_CONTROL_TRANSFER: from fffff80263155668 to fffff80262fbbb40

STACK_TEXT:
ffff830096277388 fffff80263155668 : 00000000000000c2 000000000000000d ffffe4865412ec00 00000000fffff802 : nt!KeBugCheckEx
ffff830096277390 fffff8027a015f51 : ffffe4865412ec00 ffffe4865ed53010 ffffd080625b9180 00000000fffff802 : nt!ExFreePoolWithTag+0x19e8
ffff8300962774c0 fffff8027a0019e0 : 0000000000000000 fffff80262ed08eb ffffe4865413b830 0000000000000000 : portcls!CUnknown::vector deleting destructor'+0x21 ffff8300962774f0 fffff8027a010755 : 0000000041555359 ffffe4865413c3a0 ffffe4865413b830 0000000000000000 : portcls!CUnknown::NonDelegatingRelease+0x30 ffff830096277520 fffff80278a46f8c : ffffe486497026e0 ffffe4865ed53010 ffffe4860000046d 0000000041555359 : portcls!CPortWaveCyclic::Release+0x15 ffff830096277550 ffffe486497026e0 : ffffe4865ed53010 ffffe4860000046d 0000000041555359 ffffe486497026e0 : ysusb_w10_64+0x26f8c ffff830096277558 ffffe4865ed53010 : ffffe4860000046d 0000000041555359 ffffe486497026e0 fffff80278a26780 : 0xffffe486497026e0
ffff830096277560 ffffe4860000046d : 0000000041555359 ffffe486497026e0 fffff80278a26780 0000000000000001 : 0xffffe4865ed53010 ffff830096277568 0000000041555359 : ffffe486497026e0 fffff80278a26780 0000000000000001 ffffe4865ed53010 : 0xffffe4860000046d
ffff830096277570 ffffe486497026e0 : fffff80278a26780 0000000000000001 ffffe4865ed53010 ffffe48600000c1f : 0x41555359
ffff830096277578 fffff80278a26780 : 0000000000000001 ffffe4865ed53010 ffffe48600000c1f ffffe4865413b830 : 0xffffe486497026e0 ffff830096277580 0000000000000001 : ffffe4865ed53010 ffffe48600000c1f ffffe4865413b830 ffffe4865413c050 : ysusb_w10_64+0x6780 ffff830096277588 ffffe4865ed53010 : ffffe48600000c1f ffffe4865413b830 ffffe4865413c050 fffff80278a3d3df : 0x1 ffff830096277590 ffffe48600000c1f : ffffe4865413b830 ffffe4865413c050 fffff80278a3d3df ffffe4865413c1a0 : 0xffffe4865ed53010
ffff830096277598 ffffe4865413b830 : ffffe4865413c050 fffff80278a3d3df ffffe4865413c1a0 ffffe4865413c4f8 : 0xffffe48600000c1f ffff8300962775a0 ffffe4865413c050 : fffff80278a3d3df ffffe4865413c1a0 ffffe4865413c4f8 ffffe4865413b830 : 0xffffe4865413b830
ffff8300962775a8 fffff80278a3d3df : ffffe4865413c1a0 ffffe4865413c4f8 ffffe4865413b830 ffffe4865413b830 : 0xffffe4865413c050 ffff8300962775b0 ffffe4865413c1a0 : ffffe4865413c4f8 ffffe4865413b830 ffffe4865413b830 ffffe4865413c3a0 : ysusb_w10_64+0x1d3df ffff8300962775b8 ffffe4865413c4f8 : ffffe4865413b830 ffffe4865413b830 ffffe4865413c3a0 fffff80278a2ea37 : 0xffffe4865413c1a0
ffff8300962775c0 ffffe4865413b830 : ffffe4865413b830 ffffe4865413c3a0 fffff80278a2ea37 0000000000000000 : 0xffffe4865413c4f8 ffff8300962775c8 ffffe4865413b830 : ffffe4865413c3a0 fffff80278a2ea37 0000000000000000 ffffe4865413c050 : 0xffffe4865413b830
ffff8300962775d0 ffffe4865413c3a0 : fffff80278a2ea37 0000000000000000 ffffe4865413c050 ffffe4865ed53010 : 0xffffe4865413b830 ffff8300962775d8 fffff80278a2ea37 : 0000000000000000 ffffe4865413c050 ffffe4865ed53010 ffffe4865413c1a0 : 0xffffe4865413c3a0
ffff8300962775e0 0000000000000000 : ffffe4865413c050 ffffe4865ed53010 ffffe4865413c1a0 ffffe4865413b830 : ysusb_w10_64+0xea37


THREAD_SHA1_HASH_MOD_FUNC: a2d3533f0a34cdc4e00362286a7842bb92b71efc

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 2017a09155a6d341a23514799697ac614b224940

THREAD_SHA1_HASH_MOD: e69233f6b901ec3a0983a238f670d56947a24bc1

FOLLOWUP_IP:
portcls!CUnknown::vector deleting destructor'+21 fffff8027a015f51 0f1f440000 nop dword ptr [rax+rax]

FAULT_INSTR_CODE: 441f0f

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: portcls!CUnknown::`vector deleting destructor'+21

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: portcls

IMAGE_NAME: portcls.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.17763.194

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 21

FAILURE_BUCKET_ID: 0xc2_d_portcls!CUnknown::vector_deleting_destructor

BUCKET_ID: 0xc2_d_portcls!CUnknown::vector_deleting_destructor

PRIMARY_PROBLEM_CLASS: 0xc2_d_portcls!CUnknown::vector_deleting_destructor

TARGET_TIME: 2019-02-14T00:43:28.000Z

OSBUILD: 17763

OSSERVICEPACK: 253

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 3192

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0xc2_d_portcls!cunknown::vector_deleting_destructor

FAILURE_ID_HASH: {d33e69f2-b187-c114-b0d4-e9229f27c9a8}

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

 

[Colif]

portcls.sys = Microsoft Class Driver for Port/Miniport Devices system driver file.

its not a file i see often. Sure looks like a USB type problem

Have you updated your BIOS recently? Check in system information and see what BIOS version you have. The newest is version 0805 dated 1st Feb 2019

Might also help to update Intel Management Engine Interface to latest version as it often matches the bios version - its under chipset

 

[calvinhunt98]

portcls.sys = Microsoft Class Driver for Port/Miniport Devices system driver file.

its not a file i see often. Sure looks like a USB type problem

Have you updated your BIOS recently? Check in system information and see what BIOS version you have. The newest is version 0805 dated 1st Feb 2019

Might also help to update Intel Management Engine Interface to latest version as it often matches the bios version - its under chipset

I am currently on BIOS update 0702, as I usually don't tend to do BIOS updates without a solid reason.

I have reinstalled the Intel Chipset Drivers again.

Well again I ask, is it possible that the issue is directly related to a problem with my USB Mixer? The AG06, or maybe a driver and how it functions with the OS?

 

[Colif]

it could be as I think minports are USB related. USB drivers are built into windows so not something we can update.

I suggested BIOS as it can fix compatibility problems with hardware, it may add support for it.

 

[axe0axe0]

Looks like an audio driver from Yamaha is causing issues.