Memory_Managment Bsod

Hello people. Yesterday i had a Memory_managment Bsod once and i can't figure out why. I run memetest86 and no errors appeared. Also i physically cleaned the memory sticks. Before the bsod i was just reading pdfs and listening to music.

I also had some other bsods that i tried to fix the past month.

Lastly 3 days ago i clean installed my gpu,chipset drivers and installed the new ones(i don't know if this helps)

Thanks.

(dump file and v2 collector)
Update your browser to use Google Drive, Docs, Sheets, Sites, Slides, and Forms - Google Drive Help

I took a quick look at your earlier dumps and up[dating the chipset driver was wise, the amdkmdag.sys chipset driver was implicated in a couple of those earlier dumps. I can see in your latest dump that this driver has been updated.

There were other likely causes in some of those dumps; VBoxSup.sys in one - that's a VirtualBox driver of course, another is RPCRT4.dll - the RPC runtime which was involved is the crash of services.exe, the rtp_filter.sys driver - a component of Avria Security. I'm not sure what caused the services.exe process crash, but VBox and Avira were both implicated in these BSODs.

The most recent MEMORY_MANAGEMENT bugcheck was caused because the paging hierarchy was corrupted. This doesn't necessarily mean you have a RAM problem, it's just as possible that a driver caused a page table corruption. In the dump the pointer to the virtual address that caused the corruption is pointing at a user-mode address (0x00007ffe50e0d134), so this corruption was caused by user-mode code. Unfortunately the kernel dump doesn't contain user-mode code, and we couldn't debug it anyway without the relevant symbol files.

If it happens again make a note of exactly what you were doing at the time.

Firstly thx for replying so quick and giving time for my problem.

The rtp_filter was indeed from the avira software which i deleted, and VBoxSup.sys occured when i turned on virtualization from bios.

Can i somehow enable user-mode code or somehow provide you with that info?

Finally could this user-mode address occurred due to the virtualization option in bios or from the new gpu driver?

some how... i had this problem before,
then i reinstalled my w10. and never touch the core option again i dont know what is the relation.

and im not using vendor driver again (except if w10 not detect it). i turn on telemetry (some of them) so i believe microsoft will ready the conflict and trying to solved it, (i dont know today, since support for w10 already end except security. cmiiw)

and the most important one i stop using ccleaner and other 3rd party software except revo uninstaller, i use defender, build-in cleaner, build- defrag.... and no more reboot or BSOD

Thx for replying.

I understand what you saying but its kinda hard for me to disable some of these options. I am still in university and using Vms is a big deal. I also don't use any cleaner apps. Now about the windows drivers. I only have installed gpu,chipset,audio,wifi,bluetooth,bios drivers from the manufacturer.

When i let windows pick for ex. the wifi and bluetooth drivers bsod's occured and they pointed to those two drivers conflicting with the system.

Xmp also turned on or off from the bios is the same for the bsod problems

Thx for the info though. If i keep having the same problems and can't figure out why i will try to use the windows drivers or maybe change to win11 for the support.

The only people who can debug user code are the app developers. What the MEMORY_MANAGEMENT dump indicated was that the page table corruption was most likely caused by a user-mode driver and not a kernel driver - that means it was a driver supplied with an app. I have no way of knowing which app's driver was at fault - or even if it really was a user-mode driver.

Windows 10 IS still supported, it's just no longer receiving feature updates. Using VMs is fine, but if you use a third-party hypervisor (like VirtualBox) you must keep it updated (which it appears to be). Windows updates will keep Hyper-V updated.

I'm concerned that you say that Windows driver updates for your WiFi/Bluetooth caused BSODs? The WiFi/Bluetooth drivers you have are dated August 2022. Your best option is to download the Intel Driver & Support Assistant and use that to find drivers for your Intel devices.

There are some odd drivers that you have installed, I suggest you review whether you really need them...

• inpoutx64.sys - this is a driver that allows direct access to hardware ports, it's supplied by Hirez.co.uk. It seems to be a 32-bit driver and was last updated in 2006, although the version you have is dated 2008 - which is still pre-Windows 11.
• vbaudio_vmvaio64_win10.sys - this is an audio driver belonging to VB_Audio. It's not a problem it's just old - the version you have is dated January 2019. It will be worth looking for an update if there's one available.
• THXVAD.sys - this is another audio driver apparently from THX. Again it's not necessarily a problem it's just old, the version you have is dated September 2019. It will be worth looking for an update if there's one available.
• bddci.sys - this is a driver from the Bitdefender Antimalware product (and there are other Bitdefender drivers loaded). It's also old, dated Sept 2022. If you've had Avira and Bitdefender installed then I'm not surprised you've been having BSODs. You must not install more than one realtime antivirus tool. All third-party antimalware products can cause BSODs, I've seen more than I can count, and Bitdefender is one of the worst offenders. I would recommend you uninstall Bitdefender using the specific tool. Windows Firewall and Windows Defender are all you need.

Any of the above drivers could have caused the MEMORY_MANAGEMENT BSOD you recently had. If you must use third-party drivers and tools then you MUST keep them updated.

ubuysa said:

Any of the above drivers could have caused the MEMORY_MANAGEMENT BSOD you recently had. If you must use third-party drivers and tools then you MUST keep them updated.

about this, i forgot to tell you haris...
that happen to me when i use 3rd party drivers updater.. like iobit driver booster(or somethine like that, forgot the name) etc

While i was trying to figure out the drivers you mentioned another memory_managment occured.

DESKTOP-S95DQ1U-(2023-06-09_15-56-55).zip - Google Drive

I was searching the drivers while also being in a zoom call and with google open.

- - - Updated - - -

Hello EnvioX. No i didn't use any driver updater. Only windows updates and the official drivers from the websites of the manufacturers

That recent BSOD is the same as the earlier one. Can you please download and run Speccy. Allow it to analyse your system and then click File > Publish Snapshot. You'll be given a URL, please post that URL on here.

There are a lot of curious messages logged in your Application log.

There is an issue with Handbrake, you don't have the necessary .NET runtimes...

Code:

Event[4056]:
  Log Name: Application
  Source: .NET Runtime
  Date: 2023-06-09T14:21:19.7490000Z
  Event ID: 1023
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S95DQ1U
  Description: 
Description: A .NET application failed.
Application: HandBrake.exe
Path: C:\Program Files\HandBrake\HandBrake.exe
Message: You must install .NET to run this application.

App: C:\Program Files\HandBrake\HandBrake.exe
Architecture: x64
App host version: 6.0.11
.NET location: Not found

Learn about runtime installation:
https://aka.ms/dotnet/app-launch-failed

Download the .NET runtime:
https://aka.ms/dotnet-core-applaunch?missing_runtime=true&arch=x64&rid=win10-x64&apphost_version=6.0.11

There is an issue with Zoom, a RADAR_PRE_LEAK_64 is a memory leak warning indicating that allocated memory is not being freed. Make sure you have the latest version of Zoom and that it's properly installed...

Code:

Event[4051]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2023-06-09T12:41:39.8940000Z
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: DESKTOP-S95DQ1U
  Description: 
Fault bucket 1324068231775086225, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Zoom.exe
P2: 5.14.11.17466
P3: 10.0.19045.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

Attached files:
\\?\C:\Users\DESKTO~1\AppData\Local\Temp\RDRDA57.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA68.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDA79.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAA5.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDAE5.tmp.txt

These files may be available here:


Analysis symbol: 
Rechecking for solution: 0
Report Id: 35b37792-b3c8-4938-98b6-57f9530eb176
Report Status: 268435456
Hashed bucket: b8defb2bcf2ad7ea2260090aa5556691
Cab Guid: 0

There is also an issue with some unknown service that is not freeing registry used memory. Check via services.msc that all services have a 'Log On As' value of either 'Local System', 'Local Service', or 'Network Service'...

Code:

Event[3923]:
  Log Name: Application
  Source: Microsoft-Windows-User Profiles Service
  Date: 2023-06-08T22:11:06.6110000Z
  Event ID: 1512
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-S95DQ1U
  Description: 
Windows cannot unload your registry file. The memory used by the registry has not been freed. This problem is often caused by services running as a user account. Try configuring services to run in either the LocalService or NetworkService account. 

 DETAIL - Access is denied.


Event[3924]:
  Log Name: Application
  Source: Microsoft-Windows-User Profiles Service
  Date: 2023-06-08T22:11:06.6550000Z
  Event ID: 1517
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: N/A
  User: S-1-5-21-1553950508-3893454900-2628569581-1001
  User Name: DESKTOP-S95DQ1U\DesktopPol
  Computer: DESKTOP-S95DQ1U
  Description: 
Windows saved user S-1-5-21-1553950508-3893454900-2628569581-1001 registry while an application or service was still using the registry when the user logged off. The memory used by the user registry has not been freed. The registry will be unloaded when it is no longer in use. 

 This error may be caused by services running as a user account. Try configuring services to run in either the LocalService or NetworkService account.

yes. I Downloaded handbrake and it asked me to install that net 6.0.16 which i did. Before that i unistalled the vb_audio. Couple minutes after the NET the bsod occured. I also checked the services and all the services are assigned with 'Local System', 'Local Service', or 'Network Service'

Heres is the speccy
http://speccy.piriform.com/results/n...zFoxV08UR2Rvob

Also i created a restore point before the Net install. Should i delete handbrake and do the restore point?