BSOD Memory Management, error 0x000000a1 (I think)

Is Windows 7 x64

Full Retail

- Hardware is about a month old, got them all in and put it together the 22 of November.


- Only installed the OS once.

So I bought the components to my new computer and assembled them a month ago. Since then I have been getting BSOD errors every few days and its becoming more common. It seems to be the same error and I just cannot figure out what the problem is. I've checked EVERYTHING from the memory to the GPU and just can't figure out what is wrong. Here is some info that it gives me after a crash:


BCCode: 1a
BCP1: 0000000000008884
BCP2: FFFFFA8004A0F5E0
BCP3: FFFFFA8005850E10
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

It says Memory Management is the problem at the top of the BSoD as well


Any and all help is greatly appreciated and Merry Christmas!

thestergin said:

Is Windows 7 x64

Full Retail

- Hardware is about a month old, got them all in and put it together the 22 of November.


- Only installed the OS once.

So I bought the components to my new computer and assembled them a month ago. Since then I have been getting BSOD errors every few days and its becoming more common. It seems to be the same error and I just cannot figure out what the problem is. I've checked EVERYTHING from the memory to the GPU and just can't figure out what is wrong. Here is some info that it gives me after a crash:


BCCode: 1a
BCP1: 0000000000008884
BCP2: FFFFFA8004A0F5E0
BCP3: FFFFFA8005850E10
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

It says Memory Management is the problem at the top of the BSoD as well


Any and all help is greatly appreciated and Merry Christmas!

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

It seems that I did not have the memory dump set to small memory dump, but kernal. I apologize for that and thank you for trying to help! Is there anything else I can try to do to get you that info or do I need to wait for another crash? I don't mean to waste your time its just that I spent a fair amount on this PC and its frustrating to see it acting like this. Thank you again for the help!

Wait might this be it?

if you don't have already please download cpu-z at CPUID - System & hardware benchmark, monitoring, reporting and upload a snapshot under cpu and a snapshot
under memory.

scrooge

thestergin said:

Wait might this be it?

These crashes were caused by memory corruption (probably a driver). Please run these two tests to verify your memory and find which driver is causing the problem.

If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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.

Driver Verifier - Enable and Disable


Further Reading
Using Driver Verifier to identify issues with Windows drivers for advanced users

Here are the pics for you Scrooge.

And ZigZag I first off want to say that I'm not overclocking, and that I will run the memtest86 program and let you know whats up. The driver verifier kind of scares me so if I can't find anything I'll do that last lol.

what voltage are you using on the memory?

you may need to bump up the voltage just a bit to get a more stable system.

scrooge

Well... I don't know to be honest! How can I check and what would you recommend be a good voltage?

So I ran, and am still running the MEMTEST86 program. Something strange happened though where the screen filled up with the letters "thv0" but the program was still running. Not sure what happened but I restarted and its doing the tests again.

Sadly though I crashed again this morning so if MEMTEST doesn't find anything I may have to test the drivers. Any suggestions?