I have been battling with the MEMORY_MANAGEMENT BSOD for months now, and I am running out of ideas what to try, so if anyone is able to provide any way to try and fix it that doesn't include reinstalling the OS, I would be endlessly grateful. It seems to happen mostly while playing games, sometimes when closing applications, few times even when browsing around or watching a video on YouTube.
Another thing that often happens shortly after a BSOD reboot is that the computer freezes for a moment and then monitor goes blank and shows "no signal" while the computer fan starts making noise in a rhythm like if it was rowing a boat (short loud spin followed by longer more silent spin). The computer is basically dead at that point (like it is in some endless hibernation mode) and only a hard reset on the case helps.
The first boot after either of the above problems results in painfully slow boot where windows loading/signing in screen takes probably a whole minute, while under normal circumstances the whole system boots in probably less than half a minute.
One of the biggest problems in trying to fix the problem is that it is impossible to reproduce the BSOD at will. Sometimes in happens 3 days in a row, sometimes there are 2 weeks without any issues. This makes it very hard to just disable various applications/services and see if it helps or not.
I have gone through dozens of threads on various forums, and so far I have tried:
OS: Windows 10 Home, Version 1909, build 18363.900
Motherboard: Asus Prime X470-Pro
CPU: AMD Ryzen 7 2700X
GPU: Radeon RX580
RAM: Corsair Vengeance LXP 16GB (2x8GB) DDR4
Storage: Samsung SSD EVO 850 (main drive with OS), Samsung SSD 860 EVO and Seagate ST3160811AS SATA Hard Drive (extra storage drives)
BSOD MiniDump links:
Latest BSOD (June 30th): https://drive.google.com/file/d/1jeCqcbWcsxbwqAi_mUybPNQBNhzuR_AP/view?usp=sharing
Previous BSOD: (June 18th): https://drive.google.com/file/d/1se7XmAdVi8nGRxHSsy6l0fptBXehb0XA/view?usp=sharing
Throughout the months it seemed to juggle between hal.dll and ntoskrnl.exe, but the last 3 crashes have been reported under hal.dll
If there is any critical information I have missed to provide, please let me know. Thanks in advance.
Another thing that often happens shortly after a BSOD reboot is that the computer freezes for a moment and then monitor goes blank and shows "no signal" while the computer fan starts making noise in a rhythm like if it was rowing a boat (short loud spin followed by longer more silent spin). The computer is basically dead at that point (like it is in some endless hibernation mode) and only a hard reset on the case helps.
The first boot after either of the above problems results in painfully slow boot where windows loading/signing in screen takes probably a whole minute, while under normal circumstances the whole system boots in probably less than half a minute.
One of the biggest problems in trying to fix the problem is that it is impossible to reproduce the BSOD at will. Sometimes in happens 3 days in a row, sometimes there are 2 weeks without any issues. This makes it very hard to just disable various applications/services and see if it helps or not.
I have gone through dozens of threads on various forums, and so far I have tried:
- Updated latest Windows updates (sometimes I forget to update them right away)
- Updated GPU drivers
- Updated BIOS
- Updated chipset drivers
- Memtest (no errors)
- chkdks (no errors)
- sfc /scannow (error was found, repaired, BSOD occurred again, no error even after BSOD)
- Driver verifier (found an error with vgk.sys, removed the program, no errors afterwards, BSOD occurred again)
OS: Windows 10 Home, Version 1909, build 18363.900
Motherboard: Asus Prime X470-Pro
CPU: AMD Ryzen 7 2700X
GPU: Radeon RX580
RAM: Corsair Vengeance LXP 16GB (2x8GB) DDR4
Storage: Samsung SSD EVO 850 (main drive with OS), Samsung SSD 860 EVO and Seagate ST3160811AS SATA Hard Drive (extra storage drives)
BSOD MiniDump links:
Latest BSOD (June 30th): https://drive.google.com/file/d/1jeCqcbWcsxbwqAi_mUybPNQBNhzuR_AP/view?usp=sharing
Previous BSOD: (June 18th): https://drive.google.com/file/d/1se7XmAdVi8nGRxHSsy6l0fptBXehb0XA/view?usp=sharing
Throughout the months it seemed to juggle between hal.dll and ntoskrnl.exe, but the last 3 crashes have been reported under hal.dll
If there is any critical information I have missed to provide, please let me know. Thanks in advance.
Facebook
Twitter
Instagram