Random BSOD, even while idle

[Uwen]

So here's whats been going on. For the last few weeks my PC has been restarting on its own. Most commonly at night, while playing Final Fantasy XI. Sometimes multiple times in a short span of time. Occasionally, it will also do it while I am not even home or awake.

I do not have the error codes listed by windows from a recent crash, but attached you will find the information requested in the BSOD posting instruction thread.

Basic PC info:
AMD Phenom II x6 1090T
ASUS Radeon HD6950 2GB
8GB Ram
Windows 7 Professional 32bit OEM - original installation
Approximate PC age: 2 years(probably a bit less)

 

[writhziden]

Problem Devices:

MpKsla26b2e8c	ROOT\LEGACY_MPKSLA26B2E8C\0000	This device is not present, is not working properly, or does not have all its drivers installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_03\4&177D5649&0&0020	The drivers for this device are not installed.
AODDriver4.1	ROOT\LEGACY_AODDRIVER4.1\0000	This device is not present, is not working properly, or does not have all its drivers installed.

• Microsoft Security Essentials is not properly installed. Uninstall through Start Menu -> Control Panel -> Uninstall a program. Then download a fresh copy of its installer and install it again. Microsoft Security Essentials - Free Antivirus for Windows
  
  
• The USB Controller can be found at your motherboard's support site. Please fill in your system specs to get help with such problems in the future by following http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html.
  
  
• Use the following sites to help with the AODDriver4.1 issue. Rage3D Discussion Area - View Single Post - The AODDriver4.1 service failed .... Cat 12.2 megaproblems
  
  http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html may help supplement the steps in that link.

 

[Uwen]

I did all of the things suggested and thought I had fixed the issue, until last night. This is a new dump and I copy/pasted the windows error info here.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 124
BCP1: 00000000
BCP2: 86FFD8FC
BCP3: 00000000
BCP4: 00000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

 

[writhziden]

You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   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. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html and use the following hardware checks to supplement that link.

• 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 http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html 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
  
  
• 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).
  
  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.

Remember to read closely through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html for the crash.