BSOD while playing any game, multiple error codes

The crashes were caused by your New DeathAdder Mouse driver danew.sys. Re-install the latest driver for the device. You will find the device under mice and other pointing devices inside device manager.


To fully re-install a driver, use the following steps.

1. First, download the latest driver. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Find the device you are trying to uninstall by expanding the appropriate set of devices
7. Right click the device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Find the device you are trying to uninstall by expanding the appropriate set of devices
8. Right click the device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

Since this is a mouse driver, you may want to set up your power settings so the power button shuts down your computer or restarts your computer since you will not be able to use the mouse after uninstalling it. See OPTION THREE of Power Button - Start Menu

Done that all, got back into playing some games after a couple of days off, got a blue screen while playing Diablo 3. I've attached the dump file that it made.

A friend I was playing with at the time said that it might be a motherboard problem, and I'm actually a little freaked out at the idea of needing to replace a motherboard less than a year after I bought this one.

It is possible it is the motherboard. It could be other hardware, as well. Run some hardware checks.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• You may want to run Memtest86+ again at some point. It is up to you, and should be run when it is convenient to get 7-10 passes. Failing RAM can be finicky, and Memtest86+ may not test the portion of RAM that is failing on the first run.
  
  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.

Ran the windows test last night,

The Windows Memory Diagnostic tested the computer's memory and detected no errors.

Will run the next tests when I have a free day to sit down and actually do stuff.

Good news about Windows Memory Diagnostic. Run at whatever pace is necessary for troubleshooting not to get in the way of your life. We are patient, so there is no rush.

Have not had the chance to run the next set of tests yet, but had another blue screen, thought it couldn't hurt to add it in with the other ones.

The most recent crash points to a memory fault. The process running at the time is mumble.exe which is part of your Mumble application. Up to you whether you want to remove it to see if it is the cause of crashes. It appears to be a one time incident, so I do not think it necessary to remove unless you know it was running on other occasions during a crash.

Hi, bit of an update, I sent an email to the store that I bought the motherboard from, and they had a look at, turns out it was a funky install of Win7. There was an old hard drive that I was too lazy to remove, and the boot manager managed to get on it. Long story short, old hard drive removed, clean install of Win7, and there have been no more blue screens.

They also said that there might be something wrong with my graphics card, so I'm in the process of claiming the warranty on that before it gives me any problems.

Thank you for all the help writhziden, you've given me great advice and I've leant a bit about how to error check with my computer.