Windows 10: windows 10 BSOD dmp file: what is the next step?

I have BSOD for my WIndows 10 at https://imgur.com/a/ztBKdI3The dump files are at files.catbox.moe/humviv.zip Please advise the next step.

:)

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Unlocked Realtek HD Audio Drivers Windows 7 & 8 (With Dolby Digital Live and DTS Interactive)

DTS supported natively by Windows 8/8.1 and it should work on windows 10 too just DDL require to unlock your driver .

 

Windows 10 BSOD, don't know how to interpret the .dmp files

Edit: I now think this is a Dell problem, not a Windows problem. Thank you all for the suggestions, though. My suggestion is STAY AWAY FROM DELL.

Original post:

I'm running Windows 10, OS Version 10.0.18362 Build 18362

For more than a week, I’ve routinely been getting BSODs with the error message,
BAD POOL CALLER, multiple times a day.

To try and pinpoint the problem, I downloaded Visual Studio and WDK for Windows 10 Version 1903. I registered file associations for .dmp, .hdmp, .mdmp, .kdmp, and .wew. I launched wndbg and set the symbol search path to

SRV*C:\SymCache*Symbol information.

I then attempted to read the dmp files, but in each one I received the message:

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Wind32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Since I was unable to use wndbg correctly, I downloaded BlueScreenView. I hear that its reports are often inaccurate, but I figured a possibly-correct analysis was better than no analysis. In every crash, BlueScreenView identified
storport.sys and ntoskernel.exe as the culprits; iaStorAVC.sys was also mentioned in a handful of crashes. I’m not sure what to do with this info, though, as I can’t find any of these on the list of drivers in device manager.

You can probably tell I’m not knowledgeable about tech, and this stuff is outside my league. So, I’d be extremely grateful for step-by-step answers to the following questions:

1) What, if anything, should I do about storport.sys, ntoskernel.exe, and iaStorAVC.sys?

2) How can I set up the symbol search path for wndb to properly read dmp files?

Also, if someone wants to read one of my dmp files, I could try uploading some.

Thanks a bunch!