BSOD and crashes playing BF3, happens with 2 different GPUs

Hi all, and first of all thank you in advance, even if you don't manage to solve my issue :)

First things first, what happens:

I have played BF3 since it was out, and a couple of weeks ago it started crashing more and more often. Now I can barely play for 5 minutes. It also occurs with Mass Effect 3, but I haven't tested other games.

Most of the crashes no longer lead to BSODs, I "only" need to Ctrl-Alt-Del out of the game, but sometimes I'll have a cold BSOD.

Note that I had for a while a second GPU from the same model (except 1Gb of RAM instead of 2) and switching between them did not solve the issue.

My Windows is a Home Premium x64 version, which I bought with the computer and installed myself. I built the PC (and installed the OS) in early November 2011.

I hope you guys can acces the specs I entered in my profile, otherwise I'll copy/paste them.

I have run the BSOD Dump & System File Collection app, and attached the zipped result, let me know if anything is missing. Note that some dumps might be old, as I used to have a malfunctioning GPU which was replaced by the store where I bought my computer.

I also attached the perfmon html file as advised.

I'm running AVG Antivirus Free, which is always turned on, and Windows Update are made on a regular basis.

Here's a quick summary of what I tried so far:

- Uninstalled everything Logitech-related
- Uninstall/Driver Sweeper/Re-install NVIDIA drivers several times, with WHQL and BETA drivers
- Installed the last NVIDIA drivers from MSI's website
- Unplugged every USB device except mouse & keyboard
- Uninstall and re-install both Origin and BF3
- Uninstalled several non-critical applications

I am at a loss, not being able to play my games is really no fun, so I hope you'll be able to help

Once again, thanks in advance!

Code:

Start Menu\Programs\MSI Afterburner	DJU\Dju:Start Menu\Programs\MSI Afterburner	DJU\Dju

The above has known problems with Windows 7. Recommend removing MSI Afterburner.


AVG does not seem to be starting on startup. Was that intentional?


Crashes are pointing to memory problems or driver conflicts.

• If you are overclocking any hardware, please stop.
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
     Warning

  Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.
  
  
• 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 213245
  • 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.

Related to asmtxhci.sys XHCI Host Controller Driver from ASMedia Technology Inc. Yours is from 2010. I would re-install the newset available.

ASMedia Technology Inc. ????

writhziden said:

Code:

Start Menu\Programs\MSI Afterburner    DJU\Dju:Start Menu\Programs\MSI Afterburner    DJU\Dju

The above has known problems with Windows 7. Recommend removing MSI Afterburner.

Okay, I can certainly do that, even though I'm currently using it to underclock my GPU which is factory overclocked.

writhziden said:

AVG does not seem to be starting on startup. Was that intentional?

It certainly is not intentional, but the weird thing is it DOES start with Windows I'm puzzled on this one.

writhziden said:

Crashes are pointing to memory problems or driver conflicts.

I'll run Windows Memory Diagnostic Tool this night, will post the results

writhziden said:

If you are overclocking any hardware, please stop.

See above, my GPU is overclocked by default, how can I circumvent that?

writhziden said:

An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following: [snip]

I'll see tomorrow what the result of the above is, and if I still get crashes I'll do the Driver Verifier bit

zigzag3143 said:

Related to asmtxhci.sys XHCI Host Controller Driver from ASMedia Technology Inc. Yours is from 2010. I would re-install the newset available.

ASMedia Technology Inc. ????

As I don't seem to find a more recent one, I have currenty uninstalled (via the Windows Programs and Features application) the USB 3.0 driver. Do you think there might be leftover files and/or registry entries I should delete?

Anyway, going to sleep now, thanks a lot for the help so far, I'm impressed!

One new thing that I started thinking about: Is it possible that the RAM can be fine but the mobo is bad? Or is MemTest a surefire way of pinpointing RAM issues?

CaptainDju said:

One new thing that I started thinking about: Is it possible that the RAM can be fine but the mobo is bad? Or is MemTest a surefire way of pinpointing RAM issues?

Memtest only tests ram BUT by taking a known good stick and running it in each mobo slot you can tell if an individual slot is bad,

Okay, so as the MemTest errors all seemed to point to the same memory area that was below the first 4Gb, I tried removing the first DIMM and played for a while.

After 1.5 hours with not a single glitch, I'm starting to think I got my culprit.

Will run a MemTest with the remaining DIMM overnight.

CaptainDju said:

Okay, so as the MemTest errors all seemed to point to the same memory area that was below the first 4Gb, I tried removing the first DIMM and played for a while.

After 1.5 hours with not a single glitch, I'm starting to think I got my culprit.

Will run a MemTest with the remaining DIMM overnight.

good job and good luck