Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.

Windows 7: New build memory_management BSOD (0x0000001a)

27 Jun 2012   #1

Windows 7 Ultimate x64
New build memory_management BSOD (0x0000001a)


I've recently finished a new build but for the first 2 boots of every day I get the memory_management BSOD and then I will not happen again until the next day no matter what I do. I have also had the Page Fault in Nonpaged Area BSOD and multiple process exceptions if window actually starts during the first 2 boots.

The most annoying thing is that after this the computer is completely stable I can turn it off for 4 hours and restart it or restart it immediately and everything works so the turn around time for testing is very long.

I ran a memtest yesterday and no errors occurred.
I ran a memtest this morning the first time I booted the PCand it found thousands of errors within the first 2gb. I thought this must point at the stick nearest the processor being bad, I decided to change the sticks around to rule out the motherboard slot hopefully running memtest again and getting thousands of errors in the second 2Gb but no such luck.

I've left the offending stick (I think) of memory in the PC by its self while I have come to work so hopefully memtest will find some errors with it throughout today.

Has anyone ever experienced this or have any clues as to what I can try next.


(i've attached a pic of the memtest from this morning I think)

My System SpecsSystem Spec
27 Jun 2012   #2

Windows 7 home premium 64 bit

What memory banks have got are the single or dual
My System SpecsSystem Spec
27 Jun 2012   #3

Windows 7 Ultimate x64

dual channel
My System SpecsSystem Spec

27 Jun 2012   #4

Windows 7 Home Premium 64 Bit

You have a bad memory module, slot, or your memory is not compatible with your system. First, follow the

Then proceed through Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. (You already essentially did part 2 as you are supposed to stop if you get errors).

Check memory compatibility:
  • Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.
My System SpecsSystem Spec
27 Jun 2012   #5

Windows 7 Ultimate x64

I will follow through these instructions tonight

I should have the correct RAM since OCZ3P1333LV4GK is on the gigabyte supported memory list for the motherboard

Thanks for the help
My System SpecsSystem Spec
27 Jun 2012   #6

Windows 7 Ultimate x64


I've attached my dmp's (although some might be AHCI/IDE errors)

Memtest ran 26 passes on one stick of ram today so I removed this stick and inserted the other into the same slot and errors occurred straight away so I tried it in the other slot and 7 tests passed without fail so i'm back on the original stick while I grab the CPU-Z screenshots and dmps.

One thing I did notice is that while running memtest a stick of ram ran at 7-7-7-16 in the slot nearest the cpu and the same stick ran at 6-6-6-20 in the second slot dunno if this is normal behaviour

Any help would be brilliant thanks
My System SpecsSystem Spec
27 Jun 2012   #7

Windows 7 Ultimate x64

I decided to have a look at the dump since i'm a programmer I thought it would be best to try and get up to speed with bsod dumps anyway heres a screenshot of one of the dumps
My System SpecsSystem Spec
27 Jun 2012   #8

Windows 7 Home Premium 64 Bit

Hard to say whether that is normal behavior for your board. I am not familiar with that particular problem. Is it Memtest86+, the BIOS, or CPU-Z that is showing the different timings?

I know sometimes Memtest86+ shows incorrect timings for some boards if the modules are moved. You can manually set them in your BIOS to 7-7-7-16 and see if it resolves the problem and also see if errors then show up for the module. Perhaps the errors only occur at those timings when Memtest86+ uses its diagnostic tools on those settings. Let us know if you find out whether Memtest86+ gives errors all the time with those timings. I am fairly sure that module is faulty if you are getting errors with it almost immediately in the first slot but not with the other module, though.

Also, you neglected to mention if you have crashes running with the module that is suspected to be good and the suspected bad module removed.
My System SpecsSystem Spec
28 Jun 2012   #9

Windows 7 Ultimate x64

Memtest86+ was showing the different timings.

As for crashes with the suspected bad module removed, the system is completely stable after the first bsod with either stick or both which is the most annoying part.

Anyway last night I decided to run validate.exe to try and get the bsod to occur since the most annoying thing is that I can only get the bsod once a day in the morning

so I got a constant gdrv.sys blue screen to do with easy tune 6 so I removed that and the PC was happy with validate.exe running no problems

until this morning when again first boot bsod and no more after that.

I contacted where I got the ram from for an RMA which they issued but also stated that if the ram isn't faulty they will charge me for the re-delivery (a charge which is if I incur I may aswell have just bought new ram)

The next step is going to be booting tomorrow morning with only one stick of Ram since its only the first boot of the day that fails.

Then see where I end up.
My System SpecsSystem Spec
28 Jun 2012   #10

Windows 7 Home Premium 64 Bit

When you say validate.exe, do you mean Verifier?

Did you use these settings:
a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. In Windows 7:
  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 218754
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
verifier /reset
-> Restart your computer.

Also, have you since disabled validate.exe (whatever that is) or Verifier if you meant Verifier?
My System SpecsSystem Spec

 New build memory_management BSOD (0x0000001a)

Thread Tools

Similar help and support threads
Thread Forum
Hey, since 2 days ago I'm getting BSOD's at seemingly random intervals. I've provided an SF Dump in the attachments, and here's the error; Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7601. Locale ID: 1043 Additional information about the problem: ...
BSOD Help and Support
BSOD Memory_Management 0x0000001A
Hi all, I've been experiencing numerous BSOD on a new build Zotac ID90 running Windows 7. The BSOD message is always "MEMORY_MANAGEMENT" leading me to suspect that this may be an indication of faulty RAM. I'm about to run a series of memtest86+ tests but wondered if anyone can spot anything else...
BSOD Help and Support
BSOD MEMORY_MANAGEMENT ntoskrnl.exe 0x0000001a
This is unbearable. Win7-64b Had constant mem management bsods when putting together a new system, ran verifier and mem test for going on 13hrs and both came up fine. Replaced the motherboard and still had the same errors, thought it might be a corrupt install so clean installed win7...
BSOD Help and Support
BSOD: MEMORY_MANAGEMENT Happens every day 0x0000001a
This has been happening ever since I built my computer. I tried memtest86, but it said I had 400,000 errors, and it was checking my CPU for some reason. I'm running Windows 7 on a 64bit computer. It isn't even a month old yet, I had to install the OS, full retail. I appreciate any help I can...
BSOD Help and Support
BSOD Memory_Management Stop: 0x0000001a
Hi, I have a VOSTRO 1500 upgraded from Windows XP to Windows 7 However, after the upgrade i've been getting the bluescreen attached. Please advise? anyone..? Thanks!
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:16.
Twitter Facebook Google+