windows 7 takes a dmp again

BSOD again, multiple errors in event log. should i wipe my hard drive and start all over? I have build 7100, i was told i could upgrade to 7600 and have less problems? how do i do this? Heres the .dmp file.

jamesandalexis said:

BSOD again, multiple errors in event log. should i wipe my hard drive and start all over? I have build 7100, i was told i could upgrade to 7600 and have less problems? how do i do this? Heres the .dmp file.

James

this dump was caused by memory corruption. there wasn't much to identify what caused the corruption. Wiping your hard drive isnt going to do it I suggest if you are overclocking stop. download and run memtestx86 preferably overnight. also you might want to run a system file checker to verify the system files it is run by the following start>search>cmd>right click and run as admin>sfc /scannow

let us know the results
and let us know if you need some help with this

Ken

i used a much more simple tool, windows memory diagnostics, it told me that one of my four corsair dominator 2gig sticks were bad even which one. i emailed corsair and they are shipping me a return pkg for new matched sticks. as for sfc.exe, i have done this and it seems that after running it multiple times inder different scenarios everything checks out. so the question is(ken); you are familiar with my multiple threads, could this bad stick been a main cause for my problems? would it be cause for sooo many errors in event log, such as "sidebyside" and other various errors?

jamesandalexis said:

... so the question is(ken); you are familiar with my multiple threads, could this bad stick been a main cause for my problems? would it be cause for sooo many errors in event log, such as "sidebyside" and other various errors?

While Ken's busy...

I'm only peripherally familiar with your multiple tales of computer woe, but bad memory can cause absolutely any symptom at all. Hence, it is almost pointless to continue to troubleshoot other symptoms until you've received your new RAM and you've checked that it tests out as being reliable.

I still have 4gigs of good reliable ram on deck. This is really frustrating. Win7 ran purrrfect from inception untill about a month ago for me. I made absolutely no changes to my system at that point, only after. Now when i get home from work I look to see what new horror awaits me. Last night it was my nvidia driver, it kept crashing(never had that problem before), so i had to wait out the crashes untill finally this morning i was able to go to nvidia and update(only cause win7 didnt crash). I would upload my minidump files but the only current ones are realative to this driver failure and I dont know if it will help. ALTHOUGH, my event viewer is chock'full of all kinds of goodies. Even a few bugcheck codes. If i should upload the stuff from event viewer let me know(and know how), if you want the minidump files anyway i can do that too. Thank you all for your help and time.

jamesandalexis said:

I still have 4gigs of good reliable ram on deck. This is really frustrating. Win7 ran purrrfect from inception untill about a month ago for me. I made absolutely no changes to my system at that point, only after. Now when i get home from work I look to see what new horror awaits me. Last night it was my nvidia driver, it kept crashing(never had that problem before), so i had to wait out the crashes untill finally this morning i was able to go to nvidia and update(only cause win7 didnt crash). I would upload my minidump files but the only current ones are realative to this driver failure and I dont know if it will help. ALTHOUGH, my event viewer is chock'full of all kinds of goodies. Even a few bugcheck codes. If i should upload the stuff from event viewer let me know(and know how), if you want the minidump files anyway i can do that too. Thank you all for your help and time.

As a suggestion, treat individual problems as unrelated until/unless you have substantial reason to believe otherwise. We all have a tendency to try to form imaginary links between our different computer problems, but from a troubleshooting perspective that is frequently counter-productive.

Treat each problem as separate. Start a new thread in the most likely-looking section of the forum. Be descriptive and unemotional (emotion and ranting puts off potential helpers). Talk about the symptoms you see, not your own diagnoses.

When it comes to BSODs, event logs are almost entirely useless. Upload minidumps and nothing but minidumps, unless specifically asked to do otherwise for some situational reason. Don't assume that BSODs are in any way linked to anything else you may observe in the event logs. The majority of the time they're not.

These are just general principles. It's not in any way aimed just at you or your predicament, but I hope you'll find it useful.