Memory Dump Crash Thingy =(

Hey Guys,

Anyone could help me out with the following error i seem to get. Not constantly but after a while.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 941523A4
BCP3: 8E1838C8
BCP4: 8E1834A0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102311-38922-01.dmp
C:\Users\Maarten\AppData\Local\Temp\WER-88436-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Above is the error report. In the BSOD it says it's doing a memory dump, and the last time it also made a weird noise.

Thanks, Sala

Salaction said:

Hey Guys,

Anyone could help me out with the following error i seem to get. Not constantly but after a while.


Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 1000007e
BCP1: C0000005
BCP2: 941523A4
BCP3: 8E1838C8
BCP4: 8E1834A0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102311-38922-01.dmp
C:\Users\Maarten\AppData\Local\Temp\WER-88436-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


Above is the error report. In the BSOD it says it's doing a memory dump, and the last time it also made a weird noise.

Thanks, Sala

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.

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.

Here are the contents of the Minidump File.

I did not had to go into Safe Mode btw to get them.

Greetings, Sala

Salaction said:

Here are the contents of the Minidump File.

I did not had to go into Safe Mode btw to get them.

Greetings, Sala

Memory management (possibly caused by your avg) Please run these two tests to find out



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.

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

I've ran a memtest, I've got 9000+ Errors about 7 minutes in. And correct me if i'm wrong but now i need to be removing RAM Sticks manually, as in removing the hardware?

I don't really feel comfortable with removing my hardware =O. Anything else i can do? Or better let someone do it that has experience with this?

Salaction said:

I've ran a memtest, I've got 9000+ Errors about 7 minutes in. And correct me if i'm wrong but now i need to be removing RAM Sticks manually, as in removing the hardware?

I don't really feel comfortable with removing my hardware =O. Anything else i can do? Or better let someone do it that has experience with this?

If you dont feel comfortable with it, take to a pro. If it is under warranty send it back.