Need help with MEMORY_MANAGEMENT 0x01A BSOD

[Grootindustriel]

Thanks for taking the time to help me out. I recently built a new rig (see tech specs in my account) and it's been running smoothly so far. However, I keep getting recurring, yet random, BSOD's with the same error codes - MEMORY_MANAGEMENT 0x000001A. There's no fluctuation in the error codes - it's always the same.

That being said, I'm hoping there's no serious issue with my build's hardware since all parts are brand new. I ran memtest for 8 passes which resulted in 0 errors, so I'm confident my RAM is not the issue. Could it be just a driver, or is something going on with how my OS (Windows 7 Home Premium) is doing its memory management?

I've attached dump files in the requested SF/Zip format per the BSOD posting guidelines. Any and all help is truly appreciated. I can't stress how frustrating it is to save up and put together your dream build, only to have it have sporadic BSODs...

Thanks!

 

[Arc]

Hi Grootindustriel.

Uninstall AVG using AVG Remover. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Download, install and update those, and then run full system scans with both of them, one by one.

Let us know the result.
______________________________________________

fffff880`07465878  fffff880`03d638b0Unable to load image avgidsdrivera.sys, Win32 error 0n2
[COLOR=Red]*** WARNING: Unable to verify timestamp for avgidsdrivera.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsdrivera.sys[/COLOR]
 avgidsdrivera+0x1a8b0

 

[Grootindustriel]

Thanks for your help. I went ahead and ran the AVG Uninstaller and installed Microsoft Security Essentials and MWB. I've updated both of them and have ran a full system scan with them both - they each found 0 problems.

That being said, I'm hoping this fixes the problem and I don't have anymore BSOD's from here on out. I'll definitely update this post with a new dump file if I do experience another BSOD.

Thanks again!

 

[Grootindustriel]

Okay so per my last post I went ahead and did everything you suggested. However, I got another BSOD on 1/11, this time being Error Code 7A KERNEL_DATA_INPAGE_ERROR (which I've never gotten before). So just about five minutes ago I ran the SF program to pull all of the dump info, and during this process it BSOD'd AGAIN, this time with the same ol' 1A - MEMORY_MANAGEMENT Error.

I've attached the most recent dump files for your review, the one dated 1-11 is the 7A and the one dated 1-14 is the 1A. Thank you again for helping me sort this out! (what a headache!)

Edit: I should note that the 7A on 1-11 occured when i plugged my headphones into the headphone port on the front of my case. Nothing special or out of the ordinary when it happened.

 

[Arc]

I am getting symbol error while loading the crash dump.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Then enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[Grootindustriel]

Thanks for you help. After you posted that I did just what you said - disabled all programs at startup, and ran Driver Verifier. When driver verifier was active, it resulted in NO BSOD's. After it going for 24 hours with no problem, i let it run for an additional 24 hours and still no BSOD's. I then disabled Verifier and the machine ran for three days without any issues whatsoever.

I thought the problem was fixed and was about to report back, however, just today I got a 1A MEMORY_MANAGEMENT BSOD. My comp was powered off, and this resulted from me just turning my tower on (which is different from previous ones).

I grabbed the most recent dumps from today. Thanks again for all of your help - it's very much appreciated.

 

[Arc]

Now test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+
​

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result.

 

[Grootindustriel]

I did as you said and ran memtest86+ and decided to cover a lot of ground and do 12 complete passes, which resulted in 0 errors found. I attached a screenshot of the confirmation. After doing so, I started my computer up and immediately received a 7F bsod. (i'm at work right now but when I get home I'll upload the dump file)

That being said, what are the next steps? Again I really appreciate all of your help!

 

[Arc]

So it is another bugcheck code, 0x7F?

Last time I got symbol errors ... may be this time the dumps will be readable. Please upload those new ones. I would prefer to have a look at those before suggesting you the further steps, specially when the bugcheck is a different one.

 

[Grootindustriel]

I've attached my most recent dump files. Another happened today: MEMORY_MANAGEMENT per usual...lol

 

[Arc]

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

 

[essenbe]

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

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

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 http://www.sevenforums.com/tutorials/433-disk-check.html

And run Seatools for Dos both the long and short test http://www.sevenforums.com/tutorials/313457-seatools-dos-windows-how-use.html#Part3

Please let us know the outcome of those tests.

 

[Grootindustriel]

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]

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]

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]

Yes, run the long test too.

 

[essenbe]

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

Please run http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html 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
http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

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]

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]

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

 

[Grootindustriel]

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