Windows 10: I keep getting BSOD and I do not know the cause, I am going to add DMP files, hope someone...

Microsoft R Windows Debugger Version 10.0.18362.1 AMD64 Copyright c Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\081021-10593-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP 12 procs Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 19041.1.amd64fre.vb_release.191206-1406 Machine Name: Kernel base = 0xfffff801`7e400000 PsLoadedModuleList = 0xfffff801`7f02a1d0 Debug session time: Tue Aug 10 15:01:34.033 2021 U

:)

 

BSOD with DMP files and MSInfo

I have used the verifier app and collect the dmp files along with the MSInfo32.

I been receiving the BSOD for a bit and I had the motherboard replace at the Company's helpdesk requested it. I knew that was not the issue. I know is a driver issue but don't know how to fix it and what is exactly causing the issue. I believe is the Cisco
VPN software that is causing it.

When the BSOD happened under the verifier app the

DRIVER_VERIFIED_DETECTED_VIOLATION (xxxxx.sys) The xxxx.sys is the name of the driver that caused the crash.
If it is listed please note it and tell us what it is.

the xxxx.sys was something like vpnxxx64.sys I believe..can't remember it exactly.

here is the link to OneDrive to see the DMP files and the MSInfo32 files.

022417-11640-01.zip

 

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!

 

how do you read the BSOD error message?

good question *Wink

i have a suggestion

copy and paste the dmp file into a different location and then rename it txt

see if that helps

i hope you know how to change file extentions *Smile