Well, you've got a few bugchecks in your event log. Just on a quick look, I saw 1 0x000000d1 and 3 0x0000003B. The D1 is more common in my experience, so I'd look at 3B which is"This error has been linked to excessive paged pool usage and may occur due to user-mode graphics drivers crossing over and passing bad data to the kernel code."http://msdn.microsoft.com/en-us/library ... 85%29.aspxI'd try some other graphics drivers(different versions) and make sure you really remove the old drivers first with drivesweeper.
I'll take a look at the memorydump when I have a minute, but I'd suspect the video card driver.
BINGO!! I too recommend this, please read details below for full explanation:
homer wrote:Event log and Dumps have been added!
Thanks Hammer! Yeah, I have a 580! I did try the other PCI Express slot, re-installed windows, still BSOD's
I put it back in the original!
Ah yes... GTX 580 card, I remember now!
Okay, just fyi, I have been having massive problems with my GTX 560 Ti card ever since I upgraded the nVidia driver from 314.22 to latest 320.xx driver versions ( all WHQL certified btw and recommended by Nvidia for my card ). There are known issues with GTX 5xx series cards and latest nVidia drivers ( the latest 320.xx series to be specific, the newer the driver, the more problems/crashes you will encounter ). This does not affect ALL GTX 5xx card owners, but it certainly affects quite a few including me! ( just google "nvidia driver 320 crashing gtx 560 ti 570 580" if you don't believe me, I researched this heavily myself to solve my crashing problem. Everyone with problems with latest driver says reverting to old stable 314.22 driver solves their problems, it did for me here!! I use Windows 7 64 bit SP1 with all or very nearly all updates applied fyi.
So, I recommend you uninstall latest nVidia driver, run Driver Sweeper ( twice!! once to clean, reboot, run again to make sure all traces are gone... ) , then install the old nvidia 314.22 WHQL driver, and see if that helps...
My system ran perfect for a month with that driver, then it started crashing again, more and more frequently until it got so bad that my system would not boot anymore ( new Antec PSU , that is not the problem ), it would crash while simply idling in the BIOS screen.. .grrr.. so thinking it was probably my used 5 year old Asus P5KC motherboard causing this problem, and not my video card, since I just had my EVGA GTX 560 Ti FPB card replaced under warranty just 10 months ago ( last Christmas ), I was scared to overclock the new card I had gotten back from EVGA. Never overclocked that vidcard, and it always ran cool ( 60C max under full load as measured in real time by MSi Afterburner utility which is quite "safe" for this class of card ). Since the card was never abused and only 10 months old, I assumed there was no way it could be "bad" again, it had to be this old motherboard in my mind. Since I have no other PCI Express card here to test with, and the fact that my old Asus P5KC mobo has no onboard video on it, I had to "guess" what was wrong, either mobo or vidcard...
So I chose mobo, and bought a new cheap Gigabyte G41 chipset S775 for $65 ( $74 with tax ). To add insult to injury, I got a flat tire on my bike on the way home from the computer store ( CC ), and had to push my bike home for 45 mins... at least it was 21C and sunny that day ( last Sat. ) so it was not so bad that way.
Finally got home, installed the new Giggy mobo, everything went fine at first, all drivers went in okay including the nvidia driver.. so I thought I had guessed "right" about my old Asus mobo being the problem here...WRONG!! As soon as I tried to watch any video/movie or play any 3D game, system immediately crashed and turned off on me... argh.. so it WAS my 10 month old ( back from RMA warranty ) GTX 560 Ti card that was screwed!! So I yanked it out, and am now using the onboard Intel gpu which this Giggy board has fortunately. System has not crashed once on me since I did that...totally stable with Intel gpu. I get paid Nov. 1st and am buying a new video card. I had to pay $20 shipping to ship my EVGA 560 Ti card back to EVGA RMA hq in California, last time I did this it took 2 weeks total turnaround time ( very fast actually! ) so I hope for the same timeframe here once more... I did run the card nearly 24/7 but only gamed on it for a few hours every other day or so, I had hoped it would last longer than 10 months though, sheesh...
So I plan to buy a new HD 7950 for $250 or so on Nov. 1st, then sell my GTX 560 Ti card on the newsgroups once I get it back from RMA warranty replacement. I won't sell it till I confirm the new video card is working fine in my system first for a few weeks though, not going through all this nonsense all over again...getting tired of reloading W7 too ( my W7 installation would not even go into Safe Mode with the motherboard chipset change, just crashed, forced to install W7 fresh all over again, argh... very time consuming to reload all my apps and settings ).
One thing I must mention is that EVGA warranty service is awesome! They approved my online RMA request within hours, and last time they shipped out my new replacement card the very day they received my old broken card!! Impressive...Kitchener to California and back in just 2 weeks, not too bad.. I just wish the cards would last longer than 1 year and now 10 months lol!!!
So, I recommend that you first revert your nVidia driver and see if that fixes the problem. I know you said you tested your video card fine in another system, but if it keeps crashing I would use onboard gpu for a while if you have that option, or try to get a different card to use in your system for testing purposes...
I looked at your log files, and your critical error codes were the same ones I was getting with my failing video card, namely EventID 7001 and 7031 ( although these are generic hw failure error codes, could be video card, could be mobo, or ram, etc. the only thing it really tells us is that there is a HW problem here ).
I have a feeling your GTX 580 card is giving you the grief here, but it is also possible that it might be your power supply or motherboard , very small chance ram is failing but you said you tested that in other system already so probably not.
Good luck with it all and let us know what your testing reveals...