Question BSOD File Dump Analyze

[itsdarby]

Issue started when I started playing ARK: Survival Evolved. I've tried most everything I could find on the internet to do - including rolling back GPU drivers, doing a memory test, re-installing the game, verifying game files, etc. but I still get BSOD'd almost every day.

I viewed the event log file dump and it says it's related to "ntoskrnl.exe+3f88c0".

Any ideas? When I search that on Google, it just returns me to the same troubleshooting steps that didn't work previously for me.

 

[Colif]

What are specs of the PC?
what have you tried already? (so I don't suggest again)

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

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

 

[itsdarby]

Next time I get blue screened I'll post the memory dump here.


My system specs are:

EVGA 3070 FTW3
10700KF
Kraken Z63
MSI Z490 Unify
G.Skill Trident Z (2x16GB) DDR4-3600 CL16
970 Evo Plus 1TB M.2 (x2)
SeaSonic Focus Plus 850 Gold
Corsair LL120 (x6)

I really appreciate the help!

 

[itsdarby]

Sorry for posting on such an old thread - I can make another post if needed, mods.

I thought I had solved my issue but I just had my first BSOD in months.

Here is the link to the Minidump zip file via dropbox (I think I did this right): https://www.dropbox.com/s/ol2kkmex8laquzd/MiniDump BSOD 10.29.zip?dl=0

 

[Colif]

It sure took its time.
No point starting new one just because its not a common error

Conversion of dumps

report - Click run as fiddle to see report


File: 102922-5796-01.dmp (Oct 30 2022 - 07:17:20)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: Maine-WinGDK-S)
Uptime: 0 Day(s), 23 Hour(s), 53 Min(s), and 33 Sec(s)

So its not telling me a lot.
Process named is the victim, part of an Obsidian game from what I can tell.

Possible causes -

May 06 2013

ScpVBus.sys

Scarlet.Crush Productions Scp Dual Shock 3 Virtual Bus driver http://forums.pcsx2.net/

Used as a driver for Playstation controllers

i have seen this cause errors recently

May 08 2020

ene.sys

RGB driver used by Ptolemy Tech Co., ASUS, Gigabyte, MSI, and others

Might help to check rgb software is up to date

update or remove Precision
Possibly updated version of Icue.
download Win10 Auto Installation Program (NDIS) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

 

[ubuysa]

This looks like hardware to me - and RAM in particular. The function calls in the stack text are all related to virtual memory management. We're deleting an address space; we see nt!MmFreeVirtualMemory > nt!MiDeleteVad > nt!MiDeletePteRun > nt!KeBugCheckEx. Note that Vad is Virtual Address Space and Pte is Page Table Entry. This is all RAM related...

0: kd> knL
# Child-SP          RetAddr               Call Site
00 ffff9002`ab2bf188 fffff800`134c33e9     nt!KeBugCheckEx
01 ffff9002`ab2bf190 fffff800`134c3b9e     nt!MiDeletePteRun+0x17b9
02 ffff9002`ab2bf3a0 fffff800`134c477b     nt!MiDeleteVaTail+0x6e
03 ffff9002`ab2bf3d0 fffff800`134ceac0     nt!MiDeletePagablePteRange+0x4ab
04 ffff9002`ab2bf6e0 fffff800`13526e17     nt!MiDeleteVad+0x360
05 ffff9002`ab2bf7f0 fffff800`1388aaac     nt!MiFreeVadRange+0xa3
06 ffff9002`ab2bf850 fffff800`1388a585     nt!MmFreeVirtualMemory+0x4ec
07 ffff9002`ab2bf9a0 fffff800`1360aab5     nt!NtFreeVirtualMemory+0x95
08 ffff9002`ab2bfa00 00007ff9`2dcad484     nt!KiSystemServiceCopyEnd+0x25
09 00000049`fe77e4f8 00000000`00000000     0x00007ff9`2dcad484

I notice that you're running EVGA Precision, and the driver is two years old...

0: kd> lmDvmdriver_x64
Browse full module list
start             end                 module name
fffff800`48010000 fffff800`4801d000   driver_x64   (deferred)             
    Image path: driver-x64.sys
    Image name: driver-x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 20 14:45:05 2020 (5F1583C1)
    CheckSum:         00014E29
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Are you using Precision to overclock RAM (in particular) or CPU? The stack text above looks like RAM might be the issue but it's essential with any BSOD to remove all overclocks (and undervolts) before looking anywhere else.

 

[itsdarby]

This looks like hardware to me - and RAM in particular. The function calls in the stack text are all related to virtual memory management. We're deleting an address space; we see nt!MmFreeVirtualMemory > nt!MiDeleteVad > nt!MiDeletePteRun > nt!KeBugCheckEx. Note that Vad is Virtual Address Space and Pte is Page Table Entry. This is all RAM related...

0: kd> knL
# Child-SP          RetAddr               Call Site
00 ffff9002`ab2bf188 fffff800`134c33e9     nt!KeBugCheckEx
01 ffff9002`ab2bf190 fffff800`134c3b9e     nt!MiDeletePteRun+0x17b9
02 ffff9002`ab2bf3a0 fffff800`134c477b     nt!MiDeleteVaTail+0x6e
03 ffff9002`ab2bf3d0 fffff800`134ceac0     nt!MiDeletePagablePteRange+0x4ab
04 ffff9002`ab2bf6e0 fffff800`13526e17     nt!MiDeleteVad+0x360
05 ffff9002`ab2bf7f0 fffff800`1388aaac     nt!MiFreeVadRange+0xa3
06 ffff9002`ab2bf850 fffff800`1388a585     nt!MmFreeVirtualMemory+0x4ec
07 ffff9002`ab2bf9a0 fffff800`1360aab5     nt!NtFreeVirtualMemory+0x95
08 ffff9002`ab2bfa00 00007ff9`2dcad484     nt!KiSystemServiceCopyEnd+0x25
09 00000049`fe77e4f8 00000000`00000000     0x00007ff9`2dcad484

I notice that you're running EVGA Precision, and the driver is two years old...

0: kd> lmDvmdriver_x64
Browse full module list
start             end                 module name
fffff800`48010000 fffff800`4801d000   driver_x64   (deferred)            
    Image path: driver-x64.sys
    Image name: driver-x64.sys
    Browse all global symbols  functions  data
    Timestamp:        Mon Jul 20 14:45:05 2020 (5F1583C1)
    CheckSum:         00014E29
    ImageSize:        0000D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:

Are you using Precision to overclock RAM (in particular) or CPU? The stack text above looks like RAM might be the issue but it's essential with any BSOD to remove all overclocks (and undervolts) before looking anywhere else.

When this issue initially started happening, it was when I was playing ARK: Survival Evolved and I just chalked it up to the game being terribly optimized. It happened so frequently that I looked for solutions everywhere and people said undervolting my 3070 could help with game issues - as well as reverting to an older GPU driver. Since I've updated my GPU driver to the most recent (10/27) and reverted my GPU back to the OG settings within MSI Afterburner. I just use EVGA Precision X for a custom fan curve on the GPU since the fans were constantly turning off and on throughout the day.

 

[ubuysa]

If the minidump you uploaded was the most recent BSOD you've had, could you please upload the kernel dump - it's the file C:\Windows\Memory.dmp? It will be to large to upload here so please upload it to the cloud with a link to it here.

I can see you have two 16GB RAM sticks, so I'd be tempted to run with just one stick at a time to confirm whether this is RAM related.

 

[itsdarby]

If the minidump you uploaded was the most recent BSOD you've had, could you please upload the kernel dump - it's the file C:\Windows\Memory.dmp? It will be to large to upload here so please upload it to the cloud with a link to it here.

I can see you have two 16GB RAM sticks, so I'd be tempted to run with just one stick at a time to confirm whether this is RAM related.

So after months of having no issues, it once again happened. I'm going to try to run with one RAM stick -- would it be as simple as it won't boot if one stick is bad or will I need to put it under some stress to see if it causes another BSOD?

https://www.dropbox.com/s/9n7sxizi56ooolf/BSOD February 8.zip?dl=0 ---- there's the link to the most recent BSOD if needed/interested. Let me know if I did that correctly or if you can even access it.

I also just completed running Windows Memory Diagnostic and it said that hardware problems were detected. Is that pretty much a definitive answer that it's bad RAM?

 

[johnbl]

So after months of having no issues, it once again happened. I'm going to try to run with one RAM stick -- would it be as simple as it won't boot if one stick is bad or will I need to put it under some stress to see if it causes another BSOD?

https://www.dropbox.com/s/9n7sxizi56ooolf/BSOD February 8.zip?dl=0 ---- there's the link to the most recent BSOD if needed/interested. Let me know if I did that correctly or if you can even access it.

I also just completed running Windows Memory Diagnostic and it said that hardware problems were detected. Is that pretty much a definitive answer that it's bad RAM?

you can not say it is a problem with your RAM sticks, All we know is that the virtual memory address had a single bit corruption.
01100011 vs 11100011

you have a lot of work to do, you have to update to the current bios version, update the cpu firmware and update the various drivers to the most current version. Then you need to delete this driver
ScpVBus.sys Sun May 5 14:31:26 2013 using microsoft autoruns64Autoruns for Windows - Sysinternals | Microsoft Learn (note: not likely the cause of this bugcheck)

then you need to turn off the system virtual memory reboot and turn it back on to deleted the virtual memory (pagefile.sys)

if you reinstall ScpVBus.sys you need a version dated in 2016 or newer. The old version had a bug that caused memory corruption.

after doing these updates you would want to retest for failure.

note: the single bit error was in virtual memory so you do not know where and when it occurred. It could have been in the RAM timings but it could be RAM in the cpu, cache ram in the drive, corruption of the pagefile.sys you can not know with this bugcheck. the pagefile.sys will store this type of corruption across multiple reboots so you need to delete the pagefile or you will never know if you fixed the problem. Bios updates will give the best default RAM timiings, driver updates will fix certain bugs in the storage drivers.

Processor Version Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
running at Current Speed 3762MHz
slight underclock unexpected. Best to update BIOS