[SOLVED] CTD and BSOD, at a loss, please help!

[benjwyatt]

Please help!
I'm getting constant crashes with graphically demanding games. Doesn't happen with low intensity games.
I've tried:
Clean windows install, flashed bios, updated all drivers, I don't OC, uninstalling everything (GeForce Experience, Virus Protection, etc.), verified integrity of game files (happens with multiple games), contacted game manufacturer support (ran me through the playbook "Is your computer on?"), did every other "Try this if you have a crash" from every forum and google search I could find.

I'm out of options, so I'm posting here.

Performed all below with no errors:
Windows Memory Diagnostic
Crystal Disk Info (HDs good)
GPU-Z (I didn't notice any overheating)
/SFC and /DSIM

Below are the links to all my info, if you want any other reports/tests, let me know and I'll do them and post them ASAP.
I can make the reports, I just can't make sense of them.

DxDiag - https://drive.google.com/file/d/1NfykmVc2-BFkdUhdxrDTkVSumLstQMKa/view?usp=sharing
GPU-Z log (had it on during CTD) - https://drive.google.com/file/d/1sLQPNcFR9sXM5_MbiHHtwHT47VLRzd-Y/view?usp=sharing
CPU-Z - https://drive.google.com/file/d/1CC0lidPxUxBLwuTER7xIa1smr0rDf_2E/view?usp=sharing
msinfo.nfo - https://drive.google.com/file/d/1QBNsAZXS1uINpS_GmiavMAehPOo-nEe3/view?usp=sharing
BSOD dump file (mdmp) - https://drive.google.com/file/d/1weigd8lyoySlKLy8JdFgDMJXi6z1Tqb9/view?usp=sharing

Thanks in advance.

 

[Colif]

I have sent dump file link to a friend, he will reply at some stage.

Have you tried reinstalling GPU drivers using DDU and using different ones? I see you are on fairly new Nvidia drivers but I have seen people with 10 series cards having problems with the last few driver versions from Nvidia so try running DDU and run windows update after and let Windows find drivers for card, and see if that makes a differenece - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://pste.eu/p/pwKL.html

File information:	D2019-10-19_T12-27-41.mdmp (Oct 19 2019 - 12:27:42)
Bugcheck:	?
Driver warnings:	*** WARNING: Unable to verify timestamp for aswhook.dll *** WARNING: Unable to verify timestamp for nvwgf2umx.dll
Probably caused by:	(Process: Warhammer2.exe)
Uptime:	?? Day(s), ?? Hour(s), ?? Min(s), and ?? Sec(s)

This is not a standard minidump file. They are found in the C:\Windows\Minidump\ folder. However it may contain some useful information.

It appears as if Avast/AVG and your NVIDIA GPU driver crashed.

Have you tried playing the game while Avast/AVG is disabled?

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

well, I guessed Nvidia without seeing dumps.. bonus?

Strange that you flashed bios and yet Gardenmans dump doesn't show any system info which it would have got off the PC if it were in the dumps. Can be a sign of an old bios but not if you have newest?

You only on version 1809 of Win 10 as well.

Normally dump files include a list of drivers running on system but your file didn't include that info.
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

copy that file to documents
upload the copy from documents to a file sharing web site, and share the link in your thread so we can help fix the problem

 

[benjwyatt]

You guys are too awesome, thanks for such a quick reply!
I had tried it without AVG installed before, and most recent test AVG was disabled. But I'll try uninstalling again for this troubleshoot.
I'll get you my BIOS version on reboot.
And I'll try DDU, and Small Memory Dump, per your instructions.
I'll update you after. Thanks again guys.

 

[benjwyatt]

Here are the dump files from C:\Windows\Minidump\

File 1: https://drive.google.com/file/d/1ZBLiX-m7OmZUPQARsvU87qYPbYCNOWXY/view?usp=sharing

File 2: https://drive.google.com/file/d/1SCfLOdR6Fcz5jka8FExL77AujACvvEtK/view?usp=sharing

 

[benjwyatt]

BIOS version: https://drive.google.com/file/d/1KxKgFmNjWDWl_ZcC96CNma_uQWQMGT4Q/view?usp=sharing

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/Oegl.html

File information:	102319-8187-01.dmp (Oct 23 2019 - 16:10:53)
Bugcheck:	UNEXPECTED_STORE_EXCEPTION (154)
Probably caused by:	memory_corruption (Process: MemCompression)
Uptime:	1 Day(s), 15 Hour(s), 50 Min(s), and 42 Sec(s)

File information:	102319-15062-01.dmp (Oct 23 2019 - 18:46:55)
Bugcheck:	SYSTEM_SERVICE_EXCEPTION (3B)
Probably caused by:	memory_corruption (Process: aswidsagent.exe)
Uptime:	0 Day(s), 2 Hour(s), 31 Min(s), and 08 Sec(s)

I see a mention of another AVG file called aswidsagent.exe. Maybe Colif will have more ideas.

BIOS info was not included in the dump file.

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[benjwyatt]

Ok, I uninstalled AVG, ran DDU, reinstalled 440.97 NVidia drivers (without GeForce Experience), rebooting throughout. Tried game, crashed within 2 minutes. No new BSOD, so no new dumps. I believe that's everything you guys have suggested so far. Going to do some research on loading an earlier version of NVidia drivers to see what that does, but am open to any and all suggestions!

 

[benjwyatt]

Used DDU, then installed Nvidia driver 418.81, which is the oldest one they have on their site. Still crashing.

 

[gardenman]

Try using DDU again (in safe mode), boot back into normal mode and let Windows Update install a driver. It might be from Oct 2017 (that's when my driver is from). We've had luck with that specific driver. For me it's version 388.13 (Also known as: 23.21.13.8813).

 

[Colif]

So the msinfo link when clicked acts like its a video file, I have seen google do that twice and I don't understand it.

1st error has to do with virtual memory, which is page file or ram.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

 

[benjwyatt]

Want to thank you both again for helping! You're rock stars.

DDU'd, then installed 388.13 and still crashes.

I placed msinfo.nfo into a rar file, should hopefully download better:
msinfo.rar - https://drive.google.com/file/d/1LQ07At9oP4p4D0Sqiho_S0qLaeUETY6j/view?usp=sharing

I'll try pulling each RAM, running memtest and try playing with just one of each chip in, and see how it does.

 

[benjwyatt]

Latest BSOD dump file:

https://drive.google.com/file/d/1LX9a-Ds7q6hdfbIJNygxZEb8kzX6XKZJ/view?usp=sharing

 

[gardenman]

I ran the new dump file through the debugger and got the following information: https://pste.eu/p/AxL4.html

File information:	102719-19843-01.dmp (Oct 27 2019 - 19:38:56)
Bugcheck:	STORE_DATA_STRUCTURE_CORRUPTION (1C7)
Probably caused by:	ntkrnlmp.exe (Process: MemCompression)
Uptime:	0 Day(s), 7 Hour(s), 47 Min(s), and 56 Sec(s)

This information can be used by others to help you. I can't help you with this. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

There are errors I see all the time in here, and then there are lots I don't. this is one of the 2nd category

normally if I see weird errors I check ram first.

this one is saying same thing anyway -

The store component detected a corruption in its data structures.

This bugcheck can occur by memory corruption due to physical memory access. The causes for physical memory corruption include:

1. Defective RAM hardware
2. A driver or device incorrectly modifying physical pages via an incorrect DMA operation or associated MDL.
3. Corruption caused by a hardware device or firmware corrupting memory, such as firmware illegally modifying physical pages across a power transition.

 

[benjwyatt]

Memtest86 came back with a slew of errors, so I bought new RAM. Installed today. I'll run/test it for a few days and let you guys know!

 

[benjwyatt]

Looks like that was it! Bad RAM! Been running games hard on the new RAM for the last few days, all graphics maxed out, and not a single crash!
So, the key here was Memtest86, since it came back with all those errors, when the Windows Memory Diagnostic said everything was fine.
Thank guys, so happy to have a functional computer again! You're the best!