Sign in with
Sign up | Sign in
Your question

BSOD "MEMORY_MANAGEMENT", 0x0000001E and 0x0000001A

Tags:
  • RAM
  • Gigabyte
  • Memory
  • Blue Screen
  • Memory Management
Last response: in Memory
Share
September 27, 2014 6:38:29 PM

Hello, first of all, this is my system:

MOBO Gigabyte G1 Sniper M3.
Intel i5 2310,
Gigabyte GTX 650 Ti Boost.
4 GB of RAM 1333, Kingston.
PSU Corsair TX550M.
Windows 7 Ultimate 64 bits


Ok, to the issue. Since today, I have been having random BSOD, here are the screenshots of it:

http://imgur.com/USEYH0U,RYfbi0D#1

The first image happened on safe mode, the second one in normal mode after starting windows.

Also, as one of the BSOD screenshots said MEMORY_MANAGEMENT, I started running memtest86+, and if I am right, the red is bad, right?, Haha, screenshots:

http://imgur.com/a/88Ods

Would appreciate ANY help to localize the issue.

Thanks in advance!

More about : bsod memory management 0x0000001e 0x0000001a

a b } Memory
September 27, 2014 6:40:01 PM

Can you zip the dmp files and upload them somewhere then post the link? It you can still get into it
September 27, 2014 6:45:47 PM

I definitely would like to post them, however, for a strange reason, the crashes didnt generate any minidump files, actually only 1, which is 0 kbs and shows nothing in the blue screen viewer software.
Related resources
a b } Memory
September 27, 2014 7:31:21 PM

ok then lol mmm cant help that if theres nothing to look at
September 27, 2014 7:41:04 PM

Well, I understand. All I have is the BSOD screenshots, which show a MEMORY_MANAGEMENT error, bugcheck codes 0x0000001A and 0x0000001E.

Im running memtest86+ right now with only 1 stick. Will run with the other one as soon as this ends Will report back with results/screenshots of memtest.
a b } Memory
September 27, 2014 7:43:43 PM

Yeah a dmp file would help so I could see what else in installed. Sometimes its something installed that can cause the crash
September 27, 2014 11:59:45 PM

UPDATE: Sooo, tested each stick separately and here are the results:

First stick:

http://i.imgur.com/yKRUtYJ.jpg -> no issues apparently...

Second stick:

http://i.imgur.com/mZXSunM.jpg -> also no issues...

So, if they have no issues individually, how come they generated 225 errors together?

ALSO, finally manage to find the minidump file of the last BSOD. Somehow it weights 200mb so I will just post a screenshot of it, its all the info it have with it.

http://i.imgur.com/EDAdLAe.png

Would appreciate any help.
a b } Memory
September 28, 2014 12:05:30 AM

200mb for one file? Cant really tell if I dont know what else is on the system
September 28, 2014 12:09:57 AM

Yeah... its weird, anyways...

I posted my system's info in the OP. What else would you need to know so you can help me?

Thanks in advance!
a b } Memory
September 28, 2014 12:15:49 AM

So is that dmp file a dmp file or a memory.dmp which is what I think it is
September 28, 2014 12:32:58 AM

Yeah, it is the MEMORY.DMP one, which contained apparently the information of the last BSOD.
a b } Memory
September 28, 2014 12:47:44 AM

Disable auto restart if it crashes again. See if it shows the name of a file
September 28, 2014 1:13:26 AM

It is already like that, both BSOD didnt show any files.

I am running again memtest with both sticks inserted... and now there are not errors... how come?, only 1 pass so far though...

Also, ran chkdsk and came with 0 errors according to it. So maybe not HDD issue. I will reinstlal Windows just in case it was a drier issue, I was planning to reformat already anyways, so this is a good opportunity.
a b } Memory
September 28, 2014 11:30:02 AM

if windows was installed while the machine had memory errors, you really need to check all of the core windows files with the
system file checker
start cmd.exe as a admin
run
sfc.exe /scannow

this will check the core files for corruption.

best to only provide memory dumps after you have reinstalled, if you install with a USB device always run the system file checker to confirm the install.

September 28, 2014 1:35:54 PM

Yeah, I ran scannow and it did indeed fix various files. But just in case, I am performing a reinstall right now, want to be 100% sure.
September 29, 2014 1:23:11 AM

Not BSODs after windows reinstall. Will report back if they come again.
!