Continuous BSOD after memory errors

[donmiq]

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.

 

[zigzag3143]

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.

 

[donmiq]

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?

 

[zigzag3143]

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.

 

[donmiq]

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

 

[zigzag3143]

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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[donmiq]

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.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

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.

 

[donmiq]

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.

 

[zigzag3143]

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?

 

[donmiq]

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?

Here's what's happened since I last posted. After I went into safe mode, I ran verifier and removed the existing settings and saw that daemon tools was the likely culprit for preventing the boot into Windows.

I then uninstalled it and ran verifier again and everything was working fine until I tried installed Windows updates, only for it to blue screen when it installs them on boot up. I went into safe mode and it reverted the updates.

Saw that eset smart security was causing the bsod and uninstalled that. Now I have avg and have been running with verifier and haven't crashed yet. I'm hoping to god that daemon and eset were the cause as it would be so stressful for it to be a hardware issue, such as the psu.

Is there anything you can think of with the given information? I thank you very much for helping me thus far.

EDIT: I can provide all the minidumps that have happened since, there are about 3-4. Some say ntoskrnl.exe but that hasn't happened since.
Edit 2: Nevermind, just happened again while playing Skyrim. This time it said page fault in non paged area, blaming ntoskrnl again. Uploaded the dump.

 

[zigzag3143]

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?

Here's what's happened since I last posted. After I went into safe mode, I ran verifier and removed the existing settings and saw that daemon tools was the likely culprit for preventing the boot into Windows.

I then uninstalled it and ran verifier again and everything was working fine until I tried installed Windows updates, only for it to blue screen when it installs them on boot up. I went into safe mode and it reverted the updates.

Saw that eset smart security was causing the bsod and uninstalled that. Now I have avg and have been running with verifier and haven't crashed yet. I'm hoping to god that daemon and eset were the cause as it would be so stressful for it to be a hardware issue, such as the psu.

Is there anything you can think of with the given information? I thank you very much for helping me thus far.

EDIT: I can provide all the minidumps that have happened since, there are about 3-4. Some say ntoskrnl.exe but that hasn't happened since.
Edit 2: Nevermind, just happened again while playing Skyrim. This time it said page fault in non paged area, blaming ntoskrnl again. Uploaded the dump.

I dont know what you are using ( i suspect blue screen view) to read the cause of these bsod's. This last one was related to NDproxy.sys. That is the OS NDIS update in SP-1.

Here are the things I see that can be the cause

1-a 6 year old driver (RTCore64.sys) I would update it

2-AVG. Strictly in terms of bsod's AVG can cause them as much as anyone else EXCEPT Microsoft Security essentials.

I dont use it but it does cause substantially less BSOD's than the competitors

Download tools and utilities | AVG Worldwide

AVG Removal Tool


Microsoft Security Essentials - Free Antivirus for Windows

If the above dont cure it I would start thinking about a clean install. I know it is a PITA but often it is quicker just to get it over with.

 

[donmiq]

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?

Here's what's happened since I last posted. After I went into safe mode, I ran verifier and removed the existing settings and saw that daemon tools was the likely culprit for preventing the boot into Windows.

I then uninstalled it and ran verifier again and everything was working fine until I tried installed Windows updates, only for it to blue screen when it installs them on boot up. I went into safe mode and it reverted the updates.

Saw that eset smart security was causing the bsod and uninstalled that. Now I have avg and have been running with verifier and haven't crashed yet. I'm hoping to god that daemon and eset were the cause as it would be so stressful for it to be a hardware issue, such as the psu.

Is there anything you can think of with the given information? I thank you very much for helping me thus far.

EDIT: I can provide all the minidumps that have happened since, there are about 3-4. Some say ntoskrnl.exe but that hasn't happened since.
Edit 2: Nevermind, just happened again while playing Skyrim. This time it said page fault in non paged area, blaming ntoskrnl again. Uploaded the dump.

I dont know what you are using ( i suspect blue screen view) to read the cause of these bsod's. This last one was related to NDproxy.sys. That is the OS NDIS update in SP-1.

Here are the things I see that can be the cause

1-a 6 year old driver (RTCore64.sys) I would update it

2-AVG. Strictly in terms of bsod's AVG can cause them as much as anyone else EXCEPT Microsoft Security essentials.

I dont use it but it does cause substantially less BSOD's than the competitors

Download tools and utilities | AVG Worldwide

AVG Removal Tool


Microsoft Security Essentials - Free Antivirus for Windows

If the above dont cure it I would start thinking about a clean install. I know it is a PITA but often it is quicker just to get it over with.

I'm pretty sure that rtcore driver is from msi afterburner. I had only just installed that before the other blue screens. I don't know how to manually update the driver or check how old or new it is, so all I can do is uninstall the program.

Yeesh, AVG too? I wonder what AntiVirus I would be able to have besides Microsoft's. Is it normal to have these many issues with antiviruses?

I would just do a clean install right now but I've already done that twice and it proved to do nothing. Is it possible it could be the ram despite 22 passes, the psu, the motherboard, or any other piece of hardware? I just want to be able to enjoy the computer I blew my money on.

Again, thanks. You are my only hope.

 

[zigzag3143]

Here's what's happened since I last posted. After I went into safe mode, I ran verifier and removed the existing settings and saw that daemon tools was the likely culprit for preventing the boot into Windows.

I then uninstalled it and ran verifier again and everything was working fine until I tried installed Windows updates, only for it to blue screen when it installs them on boot up. I went into safe mode and it reverted the updates.

Saw that eset smart security was causing the bsod and uninstalled that. Now I have avg and have been running with verifier and haven't crashed yet. I'm hoping to god that daemon and eset were the cause as it would be so stressful for it to be a hardware issue, such as the psu.

Is there anything you can think of with the given information? I thank you very much for helping me thus far.

EDIT: I can provide all the minidumps that have happened since, there are about 3-4. Some say ntoskrnl.exe but that hasn't happened since.
Edit 2: Nevermind, just happened again while playing Skyrim. This time it said page fault in non paged area, blaming ntoskrnl again. Uploaded the dump.

I dont know what you are using ( i suspect blue screen view) to read the cause of these bsod's. This last one was related to NDproxy.sys. That is the OS NDIS update in SP-1.

Here are the things I see that can be the cause

1-a 6 year old driver (RTCore64.sys) I would update it

2-AVG. Strictly in terms of bsod's AVG can cause them as much as anyone else EXCEPT Microsoft Security essentials.

I dont use it but it does cause substantially less BSOD's than the competitors

Download tools and utilities | AVG Worldwide

AVG Removal Tool


Microsoft Security Essentials - Free Antivirus for Windows

If the above dont cure it I would start thinking about a clean install. I know it is a PITA but often it is quicker just to get it over with.

I'm pretty sure that rtcore driver is from msi afterburner. I had only just installed that before the other blue screens. I don't know how to manually update the driver or check how old or new it is, so all I can do is uninstall the program.

Yeesh, AVG too? I wonder what AntiVirus I would be able to have besides Microsoft's. Is it normal to have these many issues with antiviruses?

There are a few issues with malware apps. They have to be "hooked" into the OS kernel to work, but at the same time that hook looks like malware so a two edge sword.

I dont use MSE because I use a combined malware/firewall but MSE is the cause of the fewest BSOD's Everyone has to decide which malware app best serves them.



I would just do a clean install right now but I've already done that twice and it proved to do nothing. Is it possible it could be the ram despite 22 passes, the psu, the motherboard, or any other piece of hardware? I just want to be able to enjoy the computer I blew my money on.

If a previous clean install didnt cure the problem it is probably hardware. I would start with ram as you have, then cpu, mobo, etc.

Try this free stress test: Free Software - GIMPS

Prime95 Setup:
- extract the contents of the zip file to a location of your choice
- double click on the executable file
- select "Just stress testing"
- select the "Blend" test. If you've already run MemTest overnight you may want to run the "Small FFTs" test instead.
- "Number of torture test threads to run" should equal the number of CPU's times 2 (if you're using hyperthreading).
The easiest way to figure this out is to go to Task Manager...Performance tab - and see the number of boxes under CPU Usage History
Then run the test for 6 to 24 hours - or until you get errors (whichever comes first).
The Test selection box and the stress.txt file describes what components that the program stresses.

Again, thanks. You are my only hope.

we will worry this out but it may take some investigating

 

[donmiq]

It's just so odd, my laptop also running Windows 7 Ultimate x64 hasn't had a stop error in ages with eset. That probably goes to show that's it's not the application anyway though, since it could be the hardware.

Here's the thing with the clean install, and even with what I'm running right now. It doesn't constantly crash. Per my original post, it did that twice where I had to reinstall, but so far it only crashes every so often, usually when I'm in a game. I have tested the gpu using furmark though.

I am a bit obsessive when it comes to explaining things, thus I feel as if I am explaining this whole thing incorrectly. The main reason being because I want to be in denial that the hardware is at fault since that's a major hassle to take care of, not to mention testing it. I'm not at home with the computer right now so unfortunately I can't do anything at the moment.

Just to confirm, the crashes don't happen all the time (minus the aforementioned), but maybe once, or twice a day when the system is feeling particularly confident I won't drop it from my roof. Also, whether this is directly related or not, I haven't had the errors occur until after I install the drivers for everything, such as the gpu, chipset, usb, lan, etc.

I'm sorry for tossing you around and if you're confused. If there's anything I can answer to help you understand this whole thing better, just ask. I will be home Monday night to actually test the ram in the OS. I wish I could pay you for your services, truly.

 

[zigzag3143]

It's just so odd, my laptop also running Windows 7 Ultimate x64 hasn't had a stop error in ages with eset. That probably goes to show that's it's not the application anyway though, since it could be the hardware.

I dont usually say what products I use but in this case I also swear by ESET. I too am suspecting hardware and not software.

Here's the thing with the clean install, and even with what I'm running right now. It doesn't constantly crash. Per my original post, it did that twice where I had to reinstall, but so far it only crashes every so often, usually when I'm in a game. I have tested the gpu using furmark though.

If it is only in games it is Graphics related but could be power, G ram, the card, heat, dust, etc. These are the most annoying to worry out but we will.

I am a bit obsessive when it comes to explaining things, thus I feel as if I am explaining this whole thing incorrectly. The main reason being because I want to be in denial that the hardware is at fault since that's a major hassle to take care of, not to mention testing it. I'm not at home with the computer right now so unfortunately I can't do anything at the moment.

Be obsessive We are (my partner (JMH) and I)

Just to confirm, the crashes don't happen all the time (minus the aforementioned), but maybe once, or twice a day when the system is feeling particularly confident I won't drop it from my roof. Also, whether this is directly related or not, I haven't had the errors occur until after I install the drivers for everything, such as the gpu, chipset, usb, lan, etc.

I'm sorry for tossing you around and if you're confused. If there's anything I can answer to help you understand this whole thing better, just ask. I will be home Monday night to actually test the ram in the OS. I wish I could pay you for your services, truly.

Thanks for the post. It isnt often we get response from the people we help and it does make a difference.

Ken

 

[donmiq]

It's just so odd, my laptop also running Windows 7 Ultimate x64 hasn't had a stop error in ages with eset. That probably goes to show that's it's not the application anyway though, since it could be the hardware.

I dont usually say what products I use but in this case I also swear by ESET. I too am suspecting hardware and not software.

Here's the thing with the clean install, and even with what I'm running right now. It doesn't constantly crash. Per my original post, it did that twice where I had to reinstall, but so far it only crashes every so often, usually when I'm in a game. I have tested the gpu using furmark though.

If it is only in games it is Graphics related but could be power, G ram, the card, heat, dust, etc. These are the most annoying to worry out but we will.

I am a bit obsessive when it comes to explaining things, thus I feel as if I am explaining this whole thing incorrectly. The main reason being because I want to be in denial that the hardware is at fault since that's a major hassle to take care of, not to mention testing it. I'm not at home with the computer right now so unfortunately I can't do anything at the moment.

Be obsessive We are (my partner (JMH) and I)

Just to confirm, the crashes don't happen all the time (minus the aforementioned), but maybe once, or twice a day when the system is feeling particularly confident I won't drop it from my roof. Also, whether this is directly related or not, I haven't had the errors occur until after I install the drivers for everything, such as the gpu, chipset, usb, lan, etc.

I'm sorry for tossing you around and if you're confused. If there's anything I can answer to help you understand this whole thing better, just ask. I will be home Monday night to actually test the ram in the OS. I wish I could pay you for your services, truly.

Thanks for the post. It isnt often we get response from the people we help and it does make a difference.

Ken

Hi, I'm going to be home at the end of today and I just wanted to clarify something so I'm good to go for 6-24 hours for the test. It's only been in games so far but it has only happened maybe 10 times at the most, and it seems after I boot back into Windows it doesn't do it again in-game.

Actual clarification now: should I sill have verifier enabled while doing prime95? Also, since I have an i5 2500k, could I use the IntelBurnTest? Or does prime 95 do something ibt doesn't?

Thanks!

 

[zigzag3143]

It's just so odd, my laptop also running Windows 7 Ultimate x64 hasn't had a stop error in ages with eset. That probably goes to show that's it's not the application anyway though, since it could be the hardware.

I dont usually say what products I use but in this case I also swear by ESET. I too am suspecting hardware and not software.

Here's the thing with the clean install, and even with what I'm running right now. It doesn't constantly crash. Per my original post, it did that twice where I had to reinstall, but so far it only crashes every so often, usually when I'm in a game. I have tested the gpu using furmark though.

If it is only in games it is Graphics related but could be power, G ram, the card, heat, dust, etc. These are the most annoying to worry out but we will.

I am a bit obsessive when it comes to explaining things, thus I feel as if I am explaining this whole thing incorrectly. The main reason being because I want to be in denial that the hardware is at fault since that's a major hassle to take care of, not to mention testing it. I'm not at home with the computer right now so unfortunately I can't do anything at the moment.

Be obsessive We are (my partner (JMH) and I)

Just to confirm, the crashes don't happen all the time (minus the aforementioned), but maybe once, or twice a day when the system is feeling particularly confident I won't drop it from my roof. Also, whether this is directly related or not, I haven't had the errors occur until after I install the drivers for everything, such as the gpu, chipset, usb, lan, etc.

I'm sorry for tossing you around and if you're confused. If there's anything I can answer to help you understand this whole thing better, just ask. I will be home Monday night to actually test the ram in the OS. I wish I could pay you for your services, truly.

Thanks for the post. It isnt often we get response from the people we help and it does make a difference.

Ken

Hi, I'm going to be home at the end of today and I just wanted to clarify something so I'm good to go for 6-24 hours for the test. It's only been in games so far but it has only happened maybe 10 times at the most, and it seems after I boot back into Windows it doesn't do it again in-game.

Actual clarification now: should I sill have verifier enabled while doing prime95? Also, since I have an i5 2500k, could I use the IntelBurnTest? Or does prime 95 do something ibt doesn't?

Thanks!

Dont run prime while in verifier. Do one at a time. Read the prime instructions for specifics

 

[donmiq]

Thanks for the clarification. I am going to do blend and small fft since I read fft doesn't test much memory, even though I ran memtest.

Wanted to update you on something though. After not being home since Friday, this is the first thing i see on my monitor when I turned it on: http://imgur.com/IYiYC.jpg. Looks like the culprit is leaving a message for me. I have to manually change my ram to 1600 since it defaults to 1333, so that's the only reason it shows 1333 mhz. It still boots fine.

 

[donmiq]

Ran both blend and small fft for about 9 hours each. No fails, and temp never passed 73c.

 

[zigzag3143]

Ran both blend and small fft for about 9 hours each. No fails, and temp never passed 73c.

Warm but no problem.