Continuous BSOD after memory errors

donmiq said:

zigzag3143 said:

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?

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 said:

zigzag3143 said:

donmiq said:

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

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.

donmiq said:

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

zigzag3143 said:

donmiq said:

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!

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.

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

donmiq said:

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

Warm but no problem.