Solved New build memory_management BSOD (0x0000001a)

[IanCadman]

Hi

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.

Thanks

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

 

[Computerpete]

What memory banks have got are the single or dual

 

[IanCadman]

dual channel

 

[writhziden]

You have a bad memory module, slot, or your memory is not compatible with your system. First, follow the http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html.

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.

 

[IanCadman]

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

 

[IanCadman]

Update

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

 

[IanCadman]

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

 

[writhziden]

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.

 

[IanCadman]

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.

 

[writhziden]

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
  View 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 http://www.sevenforums.com/tutorials/700-system-restore.html 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?

 

[IanCadman]

Thanks for the help

Sorry I did mean Verifier and I followed those steps you posted

Verifier caused the gdrv.sys (i think it was) bsod immediately after I entered my password on the login screen.

I turned off verifier in safe mode to remove easy tune 6.

I turned verifier back on to confirm the gdrv.sys bsod had gone, which it had, so I then with verifier still on attempted to use a few programs (paint.net, Vs2010) ran world of warcraft and just used the pc generally for probably about 2 hours with no further bsod's

so unfortunately I don't have any more dmps from when verifier was running

 

[writhziden]

That's fine. You should disable Verifier for the time being. EasyTune6 can cause instability, so removing it was a good step. See if the system is now stable with the software removed and with Verifier disabled.

 

[IanCadman]

Thanks for all you help writhziden,

The system is stable for practically 99% of the time other than the first boot in the morning which is the only time it bsod's

I'm beginning to think this is something i'm going to have to live with for the time being since it is impossible to get consistent bsod's

this motherboard/Ram/Cpu combination was just intended as a start package to keep the initial PC cheap but usable and will be getting replaced soon hopefully with faster parts

 

[writhziden]

Let us know if you get another crash in the morning.

Also, if you do, try applying more support to the RAM by upping the voltage and changing the command rate to 2/2T/2N (depends on the BIOS settings whether you have the 2 followed by the T or N). I am currently downloading your motherboard manual to give more accurate steps...

BIOS Setting changes:

Bump the VTT Voltage to 1.2 V (or as close as you can get).

Change the Command Rate to 2​

 

[IanCadman]

Should I change the bios settings for tonight so that I can test it in the morning?

Since this morning (after all the verifier testing last night) I still got the bsod

 

[writhziden]

I would recommend waiting until tomorrow to change settings if you have another crash.

This mornings may have been a false positive due to Verifier being enabled. What did the crash point to? Do you have a .dmp for it?

 

[IanCadman]

I disabled verifier last night so this mornings was an "as normal" boot

I didn't have much time this morning but the bsod was really vague I will have a check if it created a dmp when I get home although I doubt it did since the bsod did not mention the usual "dumping physical memory to disk"

 

[Layback Bear]

Sorry if I missed it. Check your motherboard specs and make sure you have the 2 sticks of ram in the proper slots.

 

[IanCadman]

Hi Layback Bear,

Thanks for the help, the motherboard I have only has 2 slots so thankfully I can't get it wrong

 

[writhziden]

Alright, if the crash this morning was a normal crash with Verifier disabled, then make the BIOS changes tonight and see if the system still crashes tomorrow morning.