Continuous BSOD after memory errors

Hi, I have quite a peculiar issue. Keep in mind this has happened twice already. I'll be playing a game or just browsing the internet and all of the sudden I won't be able to do anything else and a whole bunch of referenced memory errors pop up. I restart and after the Windows 7 is loading splash screen, a bsod is shown and it continues like that until I reinstall Windows.

My first thought was obviously the memory, so I ran memtest and it got 22 passes, so I stopped. Next was the hdd and I ran a long generic test on it which lasted 4 hours and was fine. I've stress tested the gpu and cpu and both have seemed to be stable as well. I would test the psu but I am unsure how to do so with a multimeter.

I was playing SC2 and I got a bsod, so I thought I was a goner again, but it thankfully did not do the continuous bsod, and actually let me back into windows. I am assuming that bsod is what's in the zip.

I will provide more details if need be. I just built this system so it's a bit unfortunate. Thanks in advance!

EDIT: System specs are in the drop down on the bottom left of this post.

donmiq said:

Hi, I have quite a peculiar issue. Keep in mind this has happened twice already. I'll be playing a game or just browsing the internet and all of the sudden I won't be able to do anything else and a whole bunch of referenced memory errors pop up. I restart and after the Windows 7 is loading splash screen, a bsod is shown and it continues like that until I reinstall Windows.

My first thought was obviously the memory, so I ran memtest and it got 22 passes, so I stopped. Next was the hdd and I ran a long generic test on it which lasted 4 hours and was fine. I've stress tested the gpu and cpu and both have seemed to be stable as well. I would test the psu but I am unsure how to do so with a multimeter.

I was playing SC2 and I got a bsod, so I thought I was a goner again, but it thankfully did not do the continuous bsod, and actually let me back into windows. I am assuming that bsod is what's in the zip.

I will provide more details if need be. I just built this system so it's a bit unfortunate. Thanks in advance!

EDIT: System specs are in the drop down on the bottom left of this post.

No DMP files included in upload please try this method


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.

Alright, so it figures it was on kernel memory dump and not minidump. Therefore, I do not have anything in my minidump folder as it wrote a huge 500mb file in my Windows directory named MEMORY.dmp.

I won't upload it for obvious reasons, but is there something I can do with it to get you the information you need, instead of waiting for it to blue screen again?

donmiq said:

Alright, so it figures it was on kernel memory dump and not minidump. Therefore, I do not have anything in my minidump folder as it wrote a huge 500mb file in my Windows directory named MEMORY.dmp.

I won't upload it for obvious reasons, but is there something I can do with it to get you the information you need, instead of waiting for it to blue screen again?

You could download Blue screen view and run it but the application often incorrectly blames OS files.

Alright, it happened while I was away from the computer. This time I got the dump.

donmiq said:

Alright, it happened while I was away from the computer. This time I got the dump.

Memory corruption. Could be ram or a driver (probably a driver)

Please run these two tests to verify your memory and find which driver is causing the problem.


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

zigzag3143 said:

donmiq said:

Alright, it happened while I was away from the computer. This time I got the dump.

Memory corruption. Could be ram or a driver (probably a driver)

Please run these two tests to verify your memory and find which driver is causing the problem.


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 have already tested the ram using memtest with 22 passes and 0 fails. I'm not sure how much testing is needed. I would think the ram should be good with that many passes? It would be wonderful if it was just a driver, but I need to know which one. So the point here is to have the blue screen happen? And when it happens, it will report to me which one failed? Or am I supposed to do different things and repeat what I think causes the crash? Sorry for the dumb questions, I've just never done this before.

Ok, right after the splash screen it crashes. I am able to go into safe mode. How do I know which driver it is? Am i supposed to use process of elimination until I can boot into Windows? Thanks.

donmiq said:

Ok, right after the splash screen it crashes. I am able to go into safe mode. How do I know which driver it is? Am i supposed to use process of elimination until I can boot into Windows? Thanks.

The fact that you can boot into safe mode suggests it is a driver. Which one is hard to say given you cant run verifier.

Do you by chance have a backup you can restore from?