[SOLVED] Need help interpreting this memory.dmp

[cloudropis_1]

Woke up to find my PC on the home screen as it had rebooted.

https://pastebin.com/wjsDnps8

The part in italian says "The system found a buffer overflow in this application's stack. This overflow may cause unauthorized users to take control of the application".

This is on a very recent installation of W10 that should be clean, with no hardware changes to muddle the OS, the hardware itself has also been tested recently through prime95, memtest86 etc

 

[Colif]

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 . . .

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. Memtest is created as a bootable USB so that you don’t need windows to run it

 

[cloudropis_1]

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 . . .

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. Memtest is created as a bootable USB so that you don’t need windows to run it

Is there a reason the minidump is preferable to the full dump?
I have tested this ram just a few months ago, with zero errors, I may give memtest another run but isn't it more likely to be a pure software mishap?

 

[Colif]

Is there a reason the minidump is preferable to the full dump?
I have tested this ram just a few months ago, with zero errors, I may give memtest another run but isn't it more likely to be a pure software mishap?

The person I ask to check dumps has slow internet, the size difference between a full dump (can be over 1gb) and minidump (mostly a few mb) is enough to make a difference. THat is why I ask for minidumps, most of the necessary info is in them.

if prime 95 found no problems, you can probably skip memtest

 

[cloudropis_1]

The person I ask to check dumps has slow internet, the size difference between a full dump (can be over 1gb) and minidump (mostly a few mb) is enough to make a difference. THat is why I ask for minidumps, most of the necessary info is in them.

if prime 95 found no problems, you can probably skip memtest

I was away for work, when i came back my pc rebooted again before i could switch to minidumps.
https://pastebin.com/EfsVzVTh
I'm gonna switch over minidumps now and wait for the next crash

 

[Colif]

i will give link to my friend but he is asleep right now so it won't be looked at for about 6 hours at least, so might get another crash in that time.

 

[gardenman]

will give link to my friend but he is asleep

He needs to upload actual minidumps first. Not pastebin links to the debugger output.

Note that you may need to copy the minidump to the desktop or documents folder first before uploading. If you don't, you might get permission errors that prevent it from upload correctly.

memory.dmp's and minidumps contain the same info (for me). Others have the ability to read deeper into the memory.dmp than I can. memory.dmp files are often corrupted, either during the save process or the upload/download process. My connection is slow, at about 1 GB per hour, a 4 GB file will take about 4 and a half hours. So I often spend hours downloading what ends up being a unusable corrupted file. That's why I prefer minidumps.

 

[cloudropis_1]

He needs to upload actual minidumps first. Not pastebin links to the debugger output.

Note that you may need to copy the minidump to the desktop or documents folder first before uploading. If you don't, you might get permission errors that prevent it from upload correctly.

memory.dmp's and minidumps contain the same info (for me). Others have the ability to read deeper into the memory.dmp than I can. memory.dmp files are often corrupted, either during the save process or the upload/download process. My connection is slow, at about 1 GB per hour, a 4 GB file will take about 4 and a half hours. So I often spend hours downloading what ends up being a unusable corrupted file. That's why I prefer minidumps.

Ye ye, figured as much. I also wouldn't be able to upload the full dumps in the first place because they are nearly 4 gigs and my upload is trash. "Unfortunately" I haven't got another crash since switching to minidumps, will upload them as soon as they happen again.
In the meanwhile i ran sfc /scannow and the DISM utility, the latter of which actually reported some corrupted files that were succesfully repaired. The only thing that changed in my setup, right before getting these errors, was installing updates KB5004331 and KB5005033, i may try to uninstall them if this persists. I also got the issue where youtube on chrome would only load empty gray squares unless i spammed the cache cleaning refresh (ctrl+f5) several times, which i assumed to be a chrome issue but also to have been actually fixed after running DISM? Hopefully that was all that it needed. I'm gonna leave the PC on and see if it holds up til tomorrow morning

 

[Colif]

4gbs is way over the limit.

BSOD will happen if they want to, no rush

I have had 2 BSOD in 6 years, a 6 year gap between them is just about right for me. I have seen over 1000 of other peoples in that time...

 

[cloudropis_1]

4gbs is way over the limit.

BSOD will happen if they want to, no rush

I have had 2 BSOD in 6 years, a 6 year gap between them is just about right for me. I have seen over 1000 of other peoples in that time...

and @gardenman , finally got another one, also found out that, even though windows was set to do full memory dumps, it did also create minidumps for the first two crashes, so now i've got all 3 of them covered
https://1drv.ms/u/s!AszPI4pVTqe0hVjL2uuuEHsSdTdq?e=VTCTq0

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://jsfiddle.net/5zL013f2/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	082121-7609-01.dmp (Aug 21 2021 - 10:21:18)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	3 Day(s), 5 Hour(s), 16 Min(s), and 33 Sec(s)

File information:	081821-7296-01.dmp (Aug 17 2021 - 18:13:22)
Bugcheck:	KERNEL_SECURITY_CHECK_FAILURE (139)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 3 Hour(s), 45 Min(s), and 51 Sec(s)

File information:	081821-7140-01.dmp (Aug 18 2021 - 05:03:55)
Bugcheck:	KMODE_EXCEPTION_NOT_HANDLED (1E)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 10 Hour(s), 23 Min(s), and 19 Sec(s)

Motherboard: B450M DS3H-CF
You are using BIOS version F61a. The gigabyte website is currently not cooperating with me, and I cannot tell which Revision of the motherboard that you have, therefore I cannot tell you if there are possible updates or not. If there are, please don't update just yet. Wait for more instructions.

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

 

[cloudropis_1]

I have rev 1.0 of that mobo, of which f61 is indeed the latest bios

 

[Colif]

Xbox controller? first crash seems to tie into usage of an xbox controller
xusb22.sys is in error stack, last thing before crash started anyway. Xbox 360 Common Controller for Windows Driver

USB drivers basically built into windows 10. Makes it difficult to figure out a solution.
Maybe update Oculus as its gamepad related.

Other 2 BSOD not as obvious

 

[cloudropis_1]

Xbox controller? first crash seems to tie into usage of an xbox controller
xusb22.sys is in error stack, last thing before crash started anyway. Xbox 360 Common Controller for Windows Driver

USB drivers basically built into windows 10. Makes it difficult to figure out a solution.
Maybe update Oculus as its gamepad related.

Other 2 BSOD not as obvious

What happened, when the bsods started the 16th, is that I turned the pc back on after a Windows update, and I got the gray box on the lower right about configuring my Mayflash f300 (which w10 sees as an Xbox controller because of xinput). That gray message box you get any time you install a new peripheral. It happens sometimes that w10 feels the need to rerun the setup for peripherals I use often, but It could be something went wrong there as it was also applying the windows update. Damn me for leaving it plugged on during update installation
How do I "uninstall" the peripheral so that windows runs its setup again? From device manager?

Also what's Oculus? Don't have anything of that sort, like a VR, installed

 

[Colif]

Dec 14 2020

ViGEmBus.sys

Oculus Virtual Gamepad Emulation Bus driver

might be part of AMD GPU Drivers, not sure

best way to remove peripheral is unplug it, drivers won't run if its not plugged in.

if its only started due to that, we can see if rest of cause is windows
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:

Repair-WindowsImage -Online -RestoreHealth
and press enter

SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

 

[cloudropis_1]

Dec 14 2020

ViGEmBus.sys

Oculus Virtual Gamepad Emulation Bus driver

might be part of AMD GPU Drivers, not sure

best way to remove peripheral is unplug it, drivers won't run if its not plugged in.

if its only started due to that, we can see if rest of cause is windows
right click start button
choose powershell (admin)
type SFC /scannow and press enter
once its completed, copy/paste this command into same window:

Repair-WindowsImage -Online -RestoreHealth
and press enter

SFC fixes system files, second command cleans image files, re run SFC if it failed to fix all files and restart PC

I already mentioned in the previous post I run them both, got some repairs from the latter, and still got the third bsod after that
I still need to use that peripheral, I can't just forego it completely, that's why I aimed for a reinstall.

Forgot to mention a thing. I ran memtest and got hundreds of errors. A friend asked if I was running my ram on xmp (3200mhz), which I did, and explained that memtest errors on overclocked ram are not necessarily indicative of defective ram, as they may be caused by incorrect wattage by the xmp settings, the PSU, the mobo, my own house wirings... I disabled xmp and got 0 errors on tests done at 2133mhz

I'm gonna see if crashes still happen with xmp profile disabled and the peripheral unplugged if not needed, but please let me know how to remove and reinstall the latter from device manager or whatever, just not using it isn't an option for me.

Btw would you suggest uninstalling those windows updates as I mentioned before and see if it changes anything?

 

[Colif]

how many times did you run memtest without xmp on? not sure about the factors but he might be right. I know xmp isn't guaranteed but I still be annoyed to not be able to use it. I would question ram that throws errors in xmp

if you got ram errors I would be tempted to run this as well
https://www.guru3d.com/files-details/prime95-download.html
Prime 95 how to Guide: http://www.playtool.com/pages/prime95/prime95.html
it checks CPU and ram

sorry if you have already, and about sfc... i may have missed it. Its 6am here.