Need help with MEMORY_MANAGEMENT 0x01A BSOD

Arc · 27 Jan 2015

Perhaps I am missing something ... I have asked for more help in your thread.

essenbe · 27 Jan 2015

Hi Grootindustriel, I ran all of your dump files and they really give me nothing more than what Arc is getting.

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
 contains the address of the PFN for the corrupted page table page.
 On a 32 bit OS, parameter 2 contains a pointer to the number of used
 PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8007df2d10
Arg3: 000000000000ffff
Arg4: 0000000000000000

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
 contains the address of the PFN for the corrupted page table page.
 On a 32 bit OS, parameter 2 contains a pointer to the number of used
 PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8007d692e0
Arg3: 000000000000ffff
Arg4: 0000000000000000

Lets try approaching it a different wy

Please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Also, please run check disk Disk Check

And run Seatools for Dos both the long and short test SeaTools for DOS and Windows - How to Use

Please let us know the outcome of those tests.

Grootindustriel · 28 Jan 2015

Thanks again for your help. I ran the sfc /scannow command and it said that it did not find any integrity violations, so that's good. I also ran Disk Check and it found no issues either.

I then ran SeaTools and booted it up, but it said that it could not find any drives and that I should check my cables. Is this normal? I'm not sure why it would say that - obviously my drive cables are fine since I'm using the system right now.

On a related note - should I open up my tower and reseat my RAM and/or re-plug in all of my peripherals? i'm not sure if that would help, but I feel like i should just keep trying things. I could also switch both of my memory sticks over to the two other slots in my MOBO and see if that does anything.

Let me know your thoughts on all of this and any next steps wherever possible.

Thanks!

Grootindustriel · 28 Jan 2015

Update: I changed my SATA settings in BIOS to IDE instead of AHCI (or whatever that one is) and got SeaTools to work. The short test passed. Should I do a Long Test, or would that suffice?

Grootindustriel · 28 Jan 2015

Also there were more BSOD's today. Keep in mind that one or two of them resulted from me forgetting to change my SATA setting's back to AHCI from IDE after running SeaTools, so it wouldn't let me boot up Windows until i changed it back. I've attached the dump files.

essenbe · 28 Jan 2015

Yes, run the long test too.

essenbe · 28 Jan 2015

There are no dump files in the DM Log you submitted.

Please run Blue Screen of Death (BSOD) Posting Instructions use option #2 and press the 'Grab All' button and give it time to work.

Also please make sure you are still configured to create Small Memory Dumps
Dump Files - Configure Windows to Create on BSOD

If you are using any disk clean up tools, please do not do it. Most of them, including Windows own, delete dump files by default, so please don't use any.

Grootindustriel · 29 Jan 2015

Sorry about that - I ran CCleaner so that's probably the culprit.

Well, I ran the long test in SeaTools and lo and behold, the test FAILED. I restarted and ran it again, and it failed again! I guess that's good news and bad news: that my SSD is the issue, but at least an issue has been found.

That being said, does this mean that my SSD is defective in some way? Are there log files from the SeaTools test that I need to grab from somewhere?

Let me know next steps - again, I appreciate all of your help!

essenbe · 30 Jan 2015

I would contact Crucial Support. Depending on who you get, their technical support is pretty good.

Grootindustriel · 30 Jan 2015

Will do!

Arc and Essenbe - thanks again for helping me out with this issue. You guys are out here fighting the good fight, doing the lord's work - one BSOD at a time.

Best,
Jeff