BSOD while playing games.

Alright So I've posted on here before trying to get help for a BSOD problem, but had no luck. I'm here again to see if somebody knows a solution at this point. Here is what I know so far, my game crashes after 10-15 mins. of gameplay depending on the game. The BSOD would change from Memory_Management to System_Service_Exception and maybe even Pool Corruption. I believe the problem started after I updated to the newest video drivers and my games run fine without my graphics card installed(Ofcourse at a significantly lower setting). Memtest found no errors with the RAM. Also when I know my game is about to crash into a BSOD, if i tab out real wuick I could see it say that nvidia kernel driver stopped and recovered following up with a bsod almost instantly. Been looking on the web for answers for weeks and haven't found any. I've tried changing my drivers to an older version with no success. I'm stuck and I need some answers.

My specs are...
OS: Windows 7 Home Premium x64
CPU: AMD Phenom(tm) II X6 1075T Processor
Memory:8GB Kit (4GBx2), Ballistix 240-pin DIMM, DDR3 PC3-10600 memory module
HDD: HITACHI HDS721050CLA362 (500GB)
Graphics: NVIDIA GeForce GTX 260
Motherboard: ASUS M4A78LT-MLE
Security: MSE

The likely culprits are your graphics card or your PSU. What PSU are you using?

Obviously, there are other possible reasons for the crashes, but the two mentioned should be checked first.

As to the crashes, the latest was a MEMORY_MANAGEMENT, and the previous was a SYSTEM_SERVICE_EXCEPTION. The MEMORY_MANAGEMENT crash yielded little useful information. SYSTEM_SERVICE_EXCEPTION typically means a graphics card problem, but yours was indicating a network issue. The network relation could be a false positive, or it could be related to your Atheros driver that needs to be updated. I see a couple drivers that should be updated:

Code:

ASACPI	fffff880`04112000	fffff880`0411a000	Sun Mar 27 20:30:36 2005 (42476c4c)	00003c77		ASACPI.sys
L1C62x64	fffff880`11e46000	fffff880`11e58000	Tue Mar 31 23:09:17 2009 (49d2f6fd)	0001660a		L1C62x64.sys

For ASACPI.sys: ASUS - Motherboards- ASUS M4A78LT-M LE -> Download -> Windows 7 64bit -> Utilities -> ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit

For L1C62x64.sys: ASUS - Motherboards- ASUS M4A78LT-M LE -> Download -> Windows 7 64bit -> LAN -> Atheros AR8131 PCI-E Ethernet Controller V1.0.0.14 for Windows 7 32bit/7 64bit

All I know about my power supply that it is 500W. It's been with the comp ever since I got it and I don't know to much else about it.

I also updated those drivers but with still no luck. Still got the same BSOD's and also idk if ever mentioned it before but whenever my comp starts up after it crashes it has a 90% chance of BSOD a second time before it gets to fully startup windows and I'll have to wait a lil bit before i can turn it on without crashing again. I dont think it changes anything about the situation.

It changes a bit. That would indicate memory corruption that does not get cleared with one reboot. Could possibly mean a bad module or the modules you have are incompatible with the system.

• Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

Alright this is what you asked for, correct?

The good news is: Crucial guarantees those to work with AMD platforms, so compatibility is not an issue. Before checking the modules themselves through more rigorous methods, we should make sure it is not a software related problem or a problem due to data corruption.

• If you are overclocking any hardware, please stop.
  
  
• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Run SFC /SCANNOW Command - System File Checker up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of SFC /SCANNOW Command - System File Checker to provide us with the sfcdetails.txt file if errors occur.
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 209934
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset
  -> Restart your computer.

Alright So I went through everything. I only had to disk check twice with the second time saying that there were no problems and then I moved on to the next step. The scannow found nothing wrong so i moved on. Now the driver verifier had my game crash within like 2 mins. No big surprise ,but when it tried to make the dump file it only made it 70% and froze so i shut it down and restarted it. Except this time my comp never crashed during game play. I played for a good 3 hours on 2 different games that use to give me problems with Bsod. They worked perfectly and I just want to know what did the trick if it happens again.

See if Verifier is still enabled. Start an Elevated Command Prompt and type

verifier /query

and upload a screenshot of the results. Your crash may have been caused by the hard disk corruption/errors.

After running verifier /query, disable Verifier using the steps I gave in my previous post and see how Windows responds for a few days.

Ok here are the screenshots

Looks like Verifier was enabled correctly. Well done. Keep it disabled for now to see how the system responds. Let us know whether the problem is solved after doing your normal routine for a while. I usually recommend waiting twice as long as it normally takes to get a crash (based on your best guess as to how long it takes to get a crash on average).