Solved Consistent BSODs, Inconsistent STOP codes, and more

[Inserio]

So, I've had a chronic problem with this desktop computer that a friend of mine helped me build. It's a Giga-Byte GA-EP43-UD3L motherboard [system specs are listed in the My System Specs at the bottom]. I've seen BSODs (and recently a Green one...) and all sorts of stuff, so I left it laying around for me to deal with later.

Now, it's later, and I've been trying to fix it. I thought I made progress when I tried to turn it on one day, and it started beeping at me. When I looked up what that could be, it was suggested that I try removing a RAM chip. That appeared to fix the problem, so I went on to order more RAM. (I was able, and still am able—depending on which RAM chips and slots I use—to run Win 7 [turning off Aero] on 2gb RAM).

I ran into a Green Screen of Death recently but that was while I was on just the 2GB RAM. I actually tried taking off and resetting everything on the motherboard I could. So, I took off the video card, all the RAM chips, the heatsink, and CPU. Then I reapplied thermal paste to the CPU and heatsink, put them back in, the video card back in, and now I'm here fiddling with the RAM chips.

Right now, if I unplug all the RAM and try to boot, I get 10 long beeps and no display. If I plug in 1 of my 4 RAM chips, it will boot up entirely. If I plug in a different one, to the same slot, I get like 38ish short-fast beeps on repeat. I JUST bought this RAM chip too. Right now, it appears half work and the other two don't. But I find that odd, because the first two I had were working for quite a while. Now it appears one of them doesn't work and one of the new ones I ordered doesn't work.

If I plug in the two that should be working to the first and second RAM slots, it fails to display anything and after about 30 seconds I get the quick beeps again. If I try the first and third slots, it boots. If I try the first and fourth, it also boots. If I leave those there and put one of the chips I'm not so sure about in the third slot, it appears to boot, but I get no display.

Once, after using it for about 6 hours with 4GB of RAM (slots 1 & 4), I got a green screen of death while running a video game emulator (NO$GBA). Then later I got a BSOD.

I had been running Driver Verifier, as I'd heard might help find a cause if there was one. Earlier while using it, it pointed at snapman.sys, so I went and uninstalled Acronis, which seemed to fix that. But, after running the emulator [NO$GBA.EXE] (both because that seems to help it happen sooner, and because I wanted to use it), it happened again.

So, I'm attaching the BSOD, according to the sticky. I ran the jcgiff2 thing last night, so I'll include a zip of that one in (BSOD_jcgriff_1) as well. I think one happened over night while I wasn't doing anything, as well, so I'm including one that I just finished running, along with the performance report (in BSOD_jcgriff_2).

Oh, and one more thing. The reason I actually had to ask for help is because I just couldn't find an answer anywhere. I ended up reformatting my harddrive and reinstalling windows, but the errors still occurred. Granted, the errors were a bit different than they are now (that was around last year—the first time I started encountering these issues)

Thanks,
Brian

 

[zigzag3143]

SIMPLE

Symantec is a frequent cause of BSOD's. I would remove and replace it with Microsoft Security Essentials AT LEAST TO TEST


http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080710133834EN

Microsoft Security Essentials - Free Antivirus for Windows

 

[Inserio]

Alright, thanks for the reply. I have now done that. So, if I encounter any more BSOD's, I will attach a new report.

 

[zigzag3143]

Alright, thanks for the reply. I have now done that. So, if I encounter any more BSOD's, I will attach a new report.

Good job and good luck.

 

[Inserio]

Another BSOD. I checked the dmp file, and it was a different error, interestingly enough.

Also, windows told me that I should run the Windows Memory Diagnostics Tool, so I did (Everytime it recovered from a BSOD, it asked me to send a report, so each time I did; it finally told me to do something). The results said "Hardware problems were detected. To identify and repair these problems, you will need to contact the computer manufacturer." I don't really know where I would go to solve that, however, because it was a friend of mine who helped me piece this one together—so I don't even think there is a manufacturer for it.

As I mentioned in the first post, I already tried a bunch of different combinations with the RAM. I don't know where to go from here. I'm attaching the jcgriff2 & performance results.

 

[zigzag3143]

Another BSOD. I checked the dmp file, and it was a different error, interestingly enough.

Also, windows told me that I should run the Windows Memory Diagnostics Tool, so I did (Everytime it recovered from a BSOD, it asked me to send a report, so each time I did; it finally told me to do something). The results said "Hardware problems were detected. To identify and repair these problems, you will need to contact the computer manufacturer." I don't really know where I would go to solve that, however, because it was a friend of mine who helped me piece this one together—so I don't even think there is a manufacturer for it.

As I mentioned in the first post, I already tried a bunch of different combinations with the RAM. I don't know where to go from here. I'm attaching the jcgriff2 & performance results.

Your DMP file from 3/10 @ 2:54pm still has symantec installed see snip.

 

[Inserio]

Your DMP file from 3/10 @ 2:54pm still has symantec installed see snip.

Well, I uninstalled it after I saw your message, which would've been 4-5 hours ago. It's 9pm here, EST. Doing a search for that file, I can't find it on my system currently. I used the Norton uninstaller that you linked to me and then rebooted before doing anything.

 

[zigzag3143]

Your DMP file from 3/10 @ 2:54pm still has symantec installed see snip.

Well, I uninstalled it after I saw your message, which would've been 4-5 hours ago. It's 9pm here, EST. Doing a search for that file, I can't find it on my system currently. I used the Norton uninstaller that you linked to me and then rebooted before doing anything.

Thats ok I thought you had removed it days ago. Sometimes these threads blur into one and another. Sorry

 

[Inserio]

So, do you have any idea? It'd be difficult for me to test each piece of hardware (on another computer) to figure out which piece is causing the error and if that's the only issue. If that's what I'll have to do, though, then so be it. If there's anything else, what would you recommend? and if that is what you recommend, which pieces do you think I should check first?

 

[zigzag3143]

So, do you have any idea? It'd be difficult for me to test each piece of hardware (on another computer) to figure out which piece is causing the error and if that's the only issue. If that's what I'll have to do, though, then so be it. If there's anything else, what would you recommend? and if that is what you recommend, which pieces do you think I should check first?

Two things you can do.

I forget (not on my computer atm) if you ran memtest or another memory diagnostic.

Memtest and driver verifier



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

* If you have raid update its Driver.



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.

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



Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff 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).

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 "Special Pool", "Force Pending I/O Requests" and "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.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

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.

 

[Inserio]

So, do you have any idea? It'd be difficult for me to test each piece of hardware (on another computer) to figure out which piece is causing the error and if that's the only issue. If that's what I'll have to do, though, then so be it. If there's anything else, what would you recommend? and if that is what you recommend, which pieces do you think I should check first?

Two things you can do.

I forget (not on my computer atm) if you ran memtest or another memory diagnostic.

Memtest and driver verifier



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

* If you have raid update its Driver.



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.

Yeah, I did these, prior. Reading what you quoted, many signs are pointing to a combination between bad RAM and bad slots. If the slots are bad, would I have to replace the entire motherboard?

BTW, I didn't do a memtest on each RAM, but on the first run it came up with errors. I might be able to do some individual tests later

 

[zigzag3143]

So, do you have any idea? It'd be difficult for me to test each piece of hardware (on another computer) to figure out which piece is causing the error and if that's the only issue. If that's what I'll have to do, though, then so be it. If there's anything else, what would you recommend? and if that is what you recommend, which pieces do you think I should check first?

Two things you can do.

I forget (not on my computer atm) if you ran memtest or another memory diagnostic.

Memtest and driver verifier



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

* If you have raid update its Driver.



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.

Yeah, I did these, prior. Reading what you quoted, many signs are pointing to a combination between bad RAM and bad slots. If the slots are bad, would I have to replace the entire motherboard?

BTW, I didn't do a memtest on each RAM, but on the first run it came up with errors. I might be able to do some individual tests later

Probably, or not use the bad one. You can ID which it is by using a known good stick in each slot one at a time.

 

[Inserio]

Eerily, I get hundreds of thousands of errors when I put in three memory chips. When I put in four, it refuses to even boot and it beeps really fast repeatedly. I tested one and it's working fine, but depending on where I put the chips and which ones, it creates different combinations that just don't make sense to me. I will think a chip won't be working, but then I put it in a different slot and it works. I will think a slot isn't working, but I put in a different chip and it works. I'm really confused.

{edit} Also, my USB keyboard doesn't seem to work during boot, besides during the BIOS, i.e. I can't use it during the Memtest. I hope it's okay for me to just shut it off.
At this point, I'm running a test with two cards, one of the new ones and one of the old ones. The other new one I already tested it and let it get to pass 7 with no errors. I'll see how these two fair up, then I'll test the other old one, but I think that one won't even start, so we'll see.

 

[zigzag3143]

You can figure out which is which.

Slot 1

mem a--- works or doesnt?
mem b...
mem c...
mem d...


Repeat for slot 2, 3, 4.


Post the chart

 

[Inserio]

Alright, will do. This will take a significant amount of time, however. I'll post and edit the data as I acquire it.

Slot 1
Corsair#1--won't boot, get lots of fast beeps
Corsair#2--pass 2 with no errors
OCZ#1--pass 2 with no errors
OCZ#2--pass 0 with 17 errors

Slot 2
Corsair#1--won't boot, get lots of fast beeps
Corsair#2--pass 2 with no errors
OCZ#1--pass 10 with no errors
OCZ#2--pass 0 with 460 errors

Slot 3
Corsair#1--won't boot, get lots of fast beeps
Corsair#2--pass 2 with no errors
OCZ#1--pass 8 with no errors
OCZ#2--pass 0 with 13 errors

Slot 4
Corsair#1--won't boot, get lots of fast beeps
Corsair#2--pass 2 with no errors
OCZ#1--pass 2 with no errors
OCZ#2--pass 0 with 19 errors

{edit} Since my USB keyboard doesn't seem to respond, I have to force shut down after each test, therefore, many of these will be partially done data or me stopping as soon as I see the errors.

{edit2} I mixed up which Corsair was which (now are labeled), so I'm redoing that data.

 

[zigzag3143]

If they dont fail after 2 passes you can move on

Are both pairs of memory the same specs?

Did the BSOD's start just after you added hardware?

 

[Inserio]

Yeah, I made sure they were the same. 2GB DDR2 PC2-6400 800MHz 240-pin, timing: 5-5-5-18.
New ones: http://www.amazon.com/Corsair-CM2X2048-6400C5-PC2-6400-240-Pin-Desktop/dp/B00160P77Y
Older ones: Amazon.com: OCZ OCZ2G8004GK DDR2 800MHz 4 GB (2 x 2 GB) Gold Edition Kit: Electronics

Results:
Corsair#1:bad memory? odd, because it will work when I plug in one other one in addition to it, but by itself, it won't even boot.
Corsair#2:RAM seems fine
OCZ#1:RAM seems fine
OCZ#2:bad memory
All DIMM slots appear to be functioning appropriately.

 

[zigzag3143]

Win 7 is really, really finicky about ram. Sometimes identical ram from the same manufacturer purchased at different time may not work together. Best way to buy RAM is in one package for that is the only way you can be sure they will match.

 

[Inserio]

Like a 4x[1,2,4] package? i.e. buy all the RAM I plan to use at the same time? Interesting. I'll have to consider that if I can't get this working as is. I may consider just buying a decent DDR3 capable motherboard and getting a 16GB RAM package, since they are ridiculously cheaper for DDR3.

 

[zigzag3143]

Like a 4x[1,2,4] package? i.e. buy all the RAM I plan to use at the same time? Interesting. I'll have to consider that if I can't get this working as is. I may consider just buying a decent DDR3 capable motherboard and getting a 16GB RAM package, since they are ridiculously cheaper for DDR3.

h

Good idea.

I have been helping someone (on another forum) with exactly this issue. 4 perfectly matched (same mfr, same model, same specs,) from a decent mfr and with 3 its fine, but four Ugh.