Trouble with BSOD: MEMORY_MANAGEMENT Error After RAM Change

0
1
Asked By TechieNinja42 On

I've been dealing with a persistent BSOD that shows a MEMORY_MANAGEMENT error. Despite changing my RAM, the problem hasn't gone away. I recently updated my drivers, which caused my BIOS settings to reset. After enabling EXMP, I encountered a kernel error, so I reverted those settings. Now, the BSOD keeps appearing.

I've tried running my PC with just one stick of RAM, and it seems to work fine, but when I install either of the new RAM sticks, I keep getting the error. This happens regardless of whether I place the sticks in slots 1 and 3 or 2 and 4. Is there something I'm missing in diagnosing this? I've read about mini dump files that can help identify the problem, but I'm not sure how to interpret them. Any insights would be greatly appreciated!

3 Answers

Answered By DebugGizmo88 On

First things first, you should definitely gather those dump files. They contain crucial info on what's causing your BSODs. If you can boot into Windows or Safe Mode, go to C:WindowsMinidump and check for any files there. If you find them, zip the folder and upload it to a file-sharing site like Catbox or MediaFire. Having multiple dump files is ideal so check back frequently after any BSOD incidents. Also, follow this guide to set your system to create small memory dumps in the future, which might help in pinpointing the issue more accurately.

Answered By MemoryMaven15 On

Absolutely, follow the bot's suggestion and run a memory test. Use memtest86 or memtest86+ on both old and new RAM. It can help confirm if there's a problem with the sticks themselves. If memtest shows errors, you might need to rethink your RAM or check for compatibility issues.

Answered By ByteBuster19 On
TechyGuru22 -

Seeing ntoskrnl.exe in the dumps could indicate several potential issues, including corrupted system files or problematic drivers. You might want to consider running a system file check (using 'sfc /scannow' in the command prompt) and updating or reinstalling your drivers. Sometimes, performing a clean boot can help in diagnosing if it's actually a driver causing the conflict.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.