Windows 10: BSOD Issues. Unable to access the MEMORY.DMP file

Hello,


Writing to ask for assistance with determining my BSOD issues. Been receiving numerous BSOD within the last 24hrs and I'm not sure why. Additionally, my level of knowledge in this realm is limited so I'm not really equipped to determine the cause.


Background: Homebuilt PC. Receiving numerous MCE, and at least one WUE which caused a freeze of my machine and BSOD. Saw a significant increase within the last 36 hours. The token answer is "it's something hardware related to the CPU, HD, GPU, RAM, PSU" .... Which doesn't necessarily narrow it down


I've ran the Intel CPU diagnostic tool and it's given me a Pass for the CPU and GPU. Drivers are up to date on the motherboard, the GPU, and CPU. Not sure if correlated, but I am experiencing a failed Wireless module in the device monitor which I've tried to correct with driver updates and the like. No joy, resorted to using a CAT6 connection instead.


CPU temp idles around 32C, GPU idles around 40C. Experience no higher temps on the CPU than 65C, 72 on GPU.


Additionally, able to locate the minidump files and open up the windbg after downloading the dev kit tools. It looks greek to me and not sure how to interpret it which is sort of why I am here. I am unable to access the MEMORY.dmp file in the system root as it says access is denied. I am the only administrator on this machine.... so I'm slightly confused as to how that is possible.


sample of minidump files from recent events can be found here: https://drive.google.com/open?id=1zaLb4ktVNmW2lfF287kih_0SqMGoQDWn


Thank you for any and all help. Thanks!


Hardware:

No overclocking or adjustment to BIOS made.

Intel I7-9700K

MSI Z390 Gaming Carbon AC Motherboard

16 GB TForce Xcaliber 4000 Mhz DDR4

MSI RTX 2060 Super

Corsair 850W Modular PSU

.... Plenty of cooling fans and the case is clean as a surgeons table....

:)

 

Unknown BSOD and missing DMP files.

Hello, my grandma is experiencing BSODs on her PC when the update for "Intel Corporation - Graphics Adapter WDDM1.0, WDDM1.2, WDDM1.3 released in August 2015 is trying to install. I'm accessing her PC using TeamViewer, i do not have a physical access to
it right now. When i installed Windows 10 to her PC this summer i have set it to record a full memory dmp, but there are no generated .dmp files neither in Minidump nor in C\Windows. THIS is
a link to the attached Event logs and SysInfo.nfo log along with a screenshot of the update. There are no .dmp files as i already said, i tried installing the update manually 3 times just to be sure that there are no dmp files. Every time the PC crashed with
a BSOD but there weren't any .dmp files.

 

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!