Help with BSOD

Question

Hello,

I was hoping to get some help with a BSOD error I've encountered

Minidump & sysinfo files: https://drive.google.com/drive/folders/1_g7tR8oz_TmakAH-v2VlKBHBdb7RN7KU?usp=sharing

So to provide some context at the time of the BSOD error I was playing a game of Call of Duty: Warzone 2 and the whole pc just went. To my knowledge I had nothing more running other than the game and what you'd describe as standard background processes.

I have taken a quick look at the dmp file with windbg and do have my suspicions as to what caused this. However, having minimal knowledge of windbg I won't put them on this just in case that sways whomever may pick this up to just agree with what I say.

If you need more info on this then just reply in thread.

Thanks,

Sean

Answer 1

Hi AW,

These are a great help though windbg still doesn't give me the straight answer of probably caused by like the screen shots do.

Originally i didn't have the symbols but now i do since i can see the folder on my computer for them

Have I missed something else or did you have to do something more specific to find it out the driver name.

Thanks

Sean

Answer 2

This article is a good start to analyze BSODs:

https://www.tenforums.com/tutorials/5558-windbg-basics-debugging-crash-dumps-windows-10-a.html 

There's a lot of good information at the Sysnative forums:

https://www.sysnative.com/forums/forums/bsod-crashes-kernel-debugging.15/

Answer 3

Hi AW,

May I ask how you read the minidump file since I don't know how to read them correctly. The online docs aren't the most useful as they can be very broad

As this is the first time this has happened i will leave it there for now and remove if it does become a problem and repeatedly happen.

I can take a stab at what is using that driver but I'm not 100% sure what it would be as I don't have cpu-z installed I would assume MSI afterburner & kombuster may use them for the OC monitors.

Thanks for your help on this
Sean

Answer 4

Hi Sean, the only third party driver involved in the faulting thread is AVG's virtual memory scanner driver avgVmm.sys.

If the BSOD is an ongoing occurence, I'd recommend removing AVG and just running Windows Defender to see if things stabilize.

Also, whatever apps you're running that use the cpuz\* drivers need to be updated. There's both cpuz150\_x64.sys and cpuz149\_x64.sys.

    Image name: cpuz150_x64.sys
    Timestamp:  Sat Jun 13 00:31:16 2020 (5EE391B4)