BSOD: MEMORY_MANAGEMENT Happens every day 0x0000001a

[talkiestwinner]

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 receive.

 

[Terronium 12]

Without looking at the dumps (someone with more experience in that area than myself will surely chime in), I can tell you right now that one (if not both) of your DIMMs are no good. Run the test again with one stick installed for about, I'd say 4-5 passes, if it fails then go to the next stick. If it happens again you need new RAM.

It could also be an OC-related error, if applicable. Perhaps there's not enough voltage, perhaps you're not running the proper timings.

 

[zigzag3143]

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 receive.

If memtest says there are that many errors it is either the memory or the mobo slot.

 

[talkiestwinner]

I think it is the mobo slots, but I've tried nearly all of them at this point. I'll probably fiddle with the RAM some more. As for wattage: I'm running a 550w PSU. I thought that would be enough. I'm thinking the problem is most likely the RAM slots, and if so, I will be very disappointed. I would still like someone to look at the dump files as I am not able to.

 

[zigzag3143]

I think it is the mobo slots, but I've tried nearly all of them at this point. I'll probably fiddle with the RAM some more. As for wattage: I'm running a 550w PSU. I thought that would be enough. I'm thinking the problem is most likely the RAM slots, and if so, I will be very disappointed. I would still like someone to look at the dump files as I am not able to.

All three point to memory management. Usually a driver. You can run driver verifier to confirm it.

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

 

[talkiestwinner]

I tried Verifier.exe, but invariably it would crash giving me a SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. After closing Verifier.exe through running "verifier /restart", which I read turns it off, I still got the same BSOD message about a special pool. Is this indicative of anything? I would assume MEMORY_CORRUPTION means it's my memory. I didn't let it run for 36 hours straight, because undoubtedly it would crash within a short amount of time and each time it would give me the same message without giving me any sort of feedback.

 

[zigzag3143]

I tried Verifier.exe, but invariably it would crash giving me a SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION. After closing Verifier.exe through running "verifier /restart", which I read turns it off, I still got the same BSOD message about a special pool. Is this indicative of anything? I would assume MEMORY_CORRUPTION means it's my memory. I didn't let it run for 36 hours straight, because undoubtedly it would crash within a short amount of time.

Special pool.... May just mean a driver and not the physical ram. When it crashed it should have created a new DMP and that might tell us which. Please upload the MDPS.

 

[talkiestwinner]

Okay, I updated the DMPs that I uploaded prior. The last one is the SPECIAL_POOL error. I ran verifier, and I believe I still am, and I knew that I could get the error when I restarted or turned off my computer. For some reason I had deleted the old files, so I ran it again and got the error. I'm sure it will persist now until I find a way to shut off verifier, but oh well.

On a side note: I have been getting the MEMORY_MANAGEMENT error when I end a game of League of Legends. It has happened while I've been playing other games as well (Borderlands).

 

[Beast52702]

Terronium 12 was talking about the voltage to your ram modules, not the wattage of your power supply. If the RAM is not getting sufficient voltage it will not run correctly at its given timings. You can adjust the ram voltage in the bios. Bios can be accessed at startup by pressing whatever key is denoted for system setup(usually says on bottom or top of screen). It may take a few restarts to figure out which key it is, depending on the speed of your boot menu.

I would look up the specs for your specific ram and ensure that the voltage setting in the bios atleast meets the minimum voltage.

All that aside, that many errors in memtest86+ points pretty strongly to corrupt memory. Very rare to get a mobo with all bad ram slots

 

[zigzag3143]

Most recent DMP was Related to Gigabyte Easy Energy Saver it's a motherboard utility that manage the power of CPU, fan and may others. Note: Located in \%Program Files%\Gigabyte\EasySaver\.

I would remove to test, or failing that update it to the newest version available.

Also related was gdrv.sys 3/12/2009 11:22:29 PM (Related to gdrv.sys Microsoft Register Server.). It is dated before win 7 was released so I suspect this OS was an upgrade.

Please run a system file check

Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Let us know the results from the report at the end.

 

[talkiestwinner]

I appreciate the help, but I ran a system file scan and it yielded no errors. I uninstalled the power save from GIGABYTE, which wasn't very useful in the first place, and yet I'm still getting the SPECIAL_POOL error.

On a different note, I've checked in my BIOS that my DRAM Voltage is at 1.51V, but my RAM specs say (Newegg.com - Patriot Gamer 2 Series 8GB (2 x 4GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) Desktop Memory Model PGD38G1333ELK) 1.65V is the voltage that it should be at. I think that might be the problem for the MEMORY_MANAGEMENT error, and I can always system restore to get rid of the special pool error to a time before I started verifier.exe.

I have also had a PNF error, which is about the third one down in the list. I think it might go hand in hand with the Memory Management one, but I'm not quite sure. If you want to check it, that would be fine, but if not, It doesn't matter right now.

 

[talkiestwinner]

I'm sorry, but I'm going to go ahead and bump this. I want to try and up the voltage on my RAM, and I believe I know how. Would this possibly solve the problem?

 

[zigzag3143]

I'm sorry, but I'm going to go ahead and bump this. I want to try and up the voltage on my RAM, and I believe I know how. Would this possibly solve the problem?

Wish I could give you a definitive answer, but it might or might not. If you know how and the machine isnt under warranty I would give it a shot.

 

[talkiestwinner]

Could it damage the RAM? If so I don't really care, but if it can damage other components I probably won't attempt it. I'm only looking to vamp it up to 1.65V (which is the spec) from 1.5.

 

[Sub Styler]

Bumping the voltage up to meet it's rated spec will not damage the ram or the board and if it does then will be covered by warranty. Memory that doesnt use XMP (and often Memory that does) isnt always detected correctly by the BIOS. You can safely change all the RAM settings in the BIOS to exactly match that or the RAM for the best possible chance at stability. This includes the bus speed, latency and voltage.

If you believe only the voltage to be an issue then just change that.

If the other settings dont look right either then you may have tune the bus and latency aswell. Depending on the Motherboard and BIOS changing the Bus frequency of the ram may directly alter the bus speed of the CPU, in this case you may need to change them from linked to unlinked or possibly change the ratio. It's getting a bit technical now so if you are unsure get the shop to do it.

DO NOT EXCEED THE RATED VOLTAGE, THIS WILL VOID YOUR WARRANTY AND IS LIKELY TO DAMAGE YOUR RAM.