Solved BSOD On Normal Start up (Event 10, 20, 41, 1001, 1101, 6000 etc.)

[OpticArray]

Sorry that the title doesn't exactly describe the problem but I'm not exactly sure what to call it. Starting yesterday at start up my computer has been giving me a whole slew of errors in the event log along with BSOD with every normal start up. I haven't made any changes to the hardware or any changes to system files that I'm aware of and aside from some GPU related crashes here and there there weren't any problems to speak of until yesterday. So far I've run a full boot scan with Avast that returned with no results, a quick scan with Malwarebytes with no results, and a sfc /scannow that also said everything was fine. So all in all I'm not really sure what to do.

The Event IDs of the errors that appear in the event log are as follows: 3, 4, 10, 20, 41, 1001, 1101, 1530, 4105, 6000, 6008, 7000, 7001, 7009, 7026, and 10005.

I've attached the SF diagnostic tool zip as well with the problems starting at 3pm on the 28th. Any help would be greatly appreciated.

System specs are as follows:

OS - Windows 7 Home Premium 64bit

CPU - AMD Anthlon II X3 455 3.31 GHz

Motherboard - ASUS M5A 78L-M LX

Memory - Crucial 4GB DDR3?

PSU - Ultra 650w ATX

Graphics Card - HIS Radeon HD 6750 PCIe 1GB GDDR5

Hard Drives:

Western Digital WD Green WD10EARS 1TB 5400 RPM 64MB Cache SATA 3.0Gb/s 3.5"
Western Digital WD Green WD15EARS 1.5TB 64MB Cache SATA 3.0Gb/s 3.5"
Western Digital Caviar GP WD5000AACS 500GB 5400 to 7200 RPM 16MB Cache SATA 3.0Gb/s 3.5"


Edit: Alright so the problem appears to be connected to the GPU in some way, although to what extent (be it the drivers, card, power to the card etc.) I can't be sure. But so far the computer has stopped crashing when switching over to use the onboard graphics. It seems a little strange though as I switched over to the on-board and uninstalled the drivers, restarted the computer with the 6750 again and the computer was running fine, or at least it gave me more time (maybe two-three minutes compared to the usual 30 seconds/one minute) before crashing. But as soon as I finished installing Catalyst 13.4 freshly downloaded from AMD it crashed and gave me a BSOD. Also worthy of note while I say BSOD none of the screens have actually been blue, they're all either just completely black or a gray/green/teal color with vertical lines running through them. I'm not sure if it has any relevance but after booting into safe mode the first time and then going back to a normal startup Windows briefly displayed in the bottom right that my copy of Windows 7 was not genuine followed by an agonizingly long black screen and desktop loading.

In addition to the above edit I've also run a chkdsk on my main drive which returned errors that were fixed after a reboot and windows defender ran returning with no errors. And since it appears I forgot to mention it before I tried to do a system restore in safe mode to earlier yesterday, which went through successfully but didn't fix any of the problems. In the interest of being as thorough as possible over the last two days or so I've noticed a sound coming from the computer almost akin to that of when burning a disc or the hard drives doing a lot of work. This noise seems to appear most frequently when idle which I find to be a little odd but I'm unsure if it's at all connected. Hopefully this all helps shed a little light on my problem and again, I'd greatly appreciate any help you have to offer.

 

[koolkat77]

Hi and Welcome OpticArray

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

   Tip

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here... Stop 0x124 - what it means and what to try: Stop 124 Troubleshooting Strategy

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8004db8038, 0, 0}

Probably caused by : AuthenticAMD

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8004db8038, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------

BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

Followup: MachineOwner
---------

1: kd> !errrec fffffa8004db8038
===============================================================================
Common Platform Error Record @ fffffa8004db8038
-------------------------------------------------------------------------------
Record Id     : 01ce5c35a5498523
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 5/29/2013 6:28:07 (UTC)
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004db80b8
Section       @ fffffa8004db8190
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f53
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004db8100
Section       @ fffffa8004db8250
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 53 0f 10 00 00 08 03 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8004db8250

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004db8148
Section       @ fffffa8004db82d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f

Overclocking
If you are overclocking any hardware, STOP. Reset any changed values back to default.

Daemon Tools/Alcohol %

• Start Menu\Programs\DAEMON Tools Lite

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

As an alternative, many people recommend the use of Total Mounter or Magic ISO

Virus check
Scan your system with the following:

Kaspersky TDSSKiller - How to remove malware belonging to the family Rootkit.Win32.TDSS (aka Tidserv, TDSServ, Alureon)

ESET online scanner - One-time virus scanner free with ESET online scanner

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - SFC /SCANNOW Command - System File Checker
2. Disk check for errors on the hard drive - How to Run Disk Check in Windows 7
3. Troubleshoot applications by a clean boot - Troubleshoot Application Conflicts by Performing a Clean Startup
4. Memtest86+ paying close attention to part 3 - RAM - Test with Memtest86+
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure

Follow steps in the guide by Capt Jack Sparrow - Bug Check 0x116: VIDEO_TDR_ERROR Troubleshooting Tips | Captain Debugger

What you are experiencing is a TDR event (Timeout Detection & Recovery). There are many causes of these events, mostly hardware related. Please read my checklist below and see if you can diagnose your particular cause.

A couple of things jump out immediately. Your specs say you have 5GB of RAM, an odd number. That suggests that you added some RAM at some point. Mismatched or failing RAM modules can cause TDRs. You might want to test those sticks one at a time in Slot 1 before anything else. RAM problems can explain some of your other issues too.

Looking at some of your other posts I see you are running dual monitors also. This could be exposing a defect in your 9500GT that is triggering the TDRs. You should test with only one monitor attached to see if this is the case.

You are running lots of stuff on that box, so I would be as deliberate as possible in doing the diagnostic work.

*******
"Display driver xxxxx stopped responding and was recovered"

Timeout Detection & Recovery (TDR) = "Display Driver Stopped Responding and was Recovered" is a useful feature that started in Vista and is also in W7 that allows the OS to try and recover from a video timeout so that the system does not crash to a bluescreen. Symptoms included a screen flash with the TDR message appearing one or more times or the screen blinking out to black. If the system cannot recover it will crash (Stop Error 116 typical). The issue is that the video card is not responding as expected. The solution is in the: why?

There is no one-size-fits-all solution to TDR errors. But the problem is usually found in the local environment (your computer). Finding the cause is a matter of checking every possible cause and uncovering the culprit through a simple process of elimination. By methodically running down a checklist of diagnostic procedures you should be able to find the cause and can correct it.

There are numerous reports of hardware solutions to TDR's. The most common are:

• Poor Cooling
• Problems with the power supply
• Overclocking Issues
• Bad System memory or incorrect memory timings
• Defective PC Components

The order you do the diagnostics is not all that important. My personal strategy is to do the cheap & easy stuff first, the cheap & harder stuff next, and then the stuff that costs last. But whatever order you do it in you need to check or confirm the following:

SOFTWARE
Poorly written software and games will cause TDRs. But if this were the case it would affect lots of people, not just a few. Check the game's website & forums for patches and tips.
See if other people in the forums are having the same problem and if they were able to solve it and how.
You could also be asking too much of your video card. Check to see if your video card is tested and recommended for the game/program. Test the game at reduced settings.

WHAT ACTIONS CAUSE THE PROBLEM
It helps if you can isolate the actions that trigger the TDR. Most often it will be an application using 3D graphics. But if the incidents occur constantly it would point more towards defective hardware. If it happens more specifically (just when running Game X) it points towards overheating, settings, software, or driver issues.

GENERAL SYSTEM PERFORMANCE
You need to eliminate the possibility that your computer has a global problem. You can use a program like Prime95 to stress test your system. Free Software - GIMPS
You can run the "Stress Test" for a few hours or overnight. This will not tell you what the problem is, but it is helpful to uncover any issues your system has with instability and cooling.

OVERHEATING
Running a video intensive game for hours can generate some serious heat and overheating will cause video errors. You can check your temps by looking at your BIOS readings or use a free program like Speedfan SpeedFan - Access temperature sensor in your computer .
A real easy test is to just pull the side panel(s) off your case (You can also blow a house fan directly into the open case) and see if the problem goes away or gets better. If it does then the issue is definitely overheating. If you are overheating you need to look at installing some cooling upgrades. You want to look at ventilating the case (more or bigger fans), Upgrade your case to a larger gaming case (lots of fans, water-cooling), etc.
There are free utilities like BurninTest PassMark BurnInTest software - PC Reliability and Load Testing that you can use to test your system's cooling capability. Caution is recommended using these types of programs.

VIDEO DRIVERS
Bad drivers happen and they can get corrupted. Before installing or reinstalling any video drivers first completely uninstall all video software and the drivers. (Some people say to run a cleaner program from safe mode, some say this is unnecessary). Never rely on the driver package to overwrite the old drivers. Also: Delete the video driver folder (ex: C:\NVIDIA) in Windows Explorer (or windows may install the same drivers again!).
After uninstalling the old drivers and rebooting Windows 7 will install it's own WDDM 1.1 driver. Check for the video problem while using the generic Windows driver.
You can then install the latest drivers for your card (or try older drivers).
See This Tutorial: http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html#post414637

DEVICE MANAGER
Look in Device Manager and make sure there are no problem devices (yellow ! icon). Correct these by loading the correct drivers or disable the problem device and see if the video problem goes away.

POOR CONNECTIONS
Reseat video card and memory modules. Make sure the contacts are clean. Check all the electrical connections.

CHECK YOUR MOTHERBOARD VOLTAGES
In BIOS, check the listed voltages against the manufacturer recommended specs. Reset the voltages to factory defaults and see if the video problems disappear.

MEMORY
Memory errors can cause video problems. Run a program like Memtest86+ for at least 3 passes to see if there are any memory errors. Memtest86+ - Advanced Memory Diagnostic Tool .
You can also test for a bad memory module by installing one stick and testing, and then switch it out for the next stick, etc.

OVERCLOCKING
Overclocking can be a trial and error process. The clocks and/or multipliers you set or change for CPU, Memory, or GPU could be unstable. Eliminate this as a possibility by resetting these to their defaults to see if that clears the video problems. The simplest way to do this is to "Restore Bios Defaults", or Clear CMOS.

UNDERCLOCKING
Some people have reported that by going into the video cards control panel and "down-clocking" the cards performance settings they were able to clear up the TDRs. Since W7 does not seem to tolerate any hiccups in the GPU, this would allow you to run a poor perforning card in the W7 enviroment.
So for instance, you could set the GPU clock from a 777 MHz factory setting to 750MHz, and the ram clock from a 1126MHz factory setting to 1050Mhz, or similar small change for your particular card.

BIOS
Check for and install an updated BIOS, particularly if it says the newer BIOS corrects memory errors or bug fixes. You could also try loading the BIOS defaults.
While you are there, check the motherboard manufacturers forums to see if others are having issues with the same board.

WINDOWS POWER MANAGEMENT
Eliminate Power Management settings as a possible cause, especially if you are working with a laptop. These settings could be particularly important if the issue is in playing games.
Go to Control Panel > Hardware & Sound > Power Options. Under "Select a Power Plan" you will find that "Balanced" is the default setting.
At the bottom you will see a Down arrow next to "Show Additional Plans". Click that and select "High Performance". See if the TDR issue is affected.
Alternately, you can click "Change Plan Settings" next to the "Balanced" plan and change the setting to "Never" put the computer to sleep (This is the default on a desktop) and/or change when the display is turned off as a test.

POWER SUPPLY
You need to know that your power supply is delivering sufficient power. Power supply problems are the most common cause of video problems, especially using high end cards.
Check the power supply's amperage ratings. Be sure it has the ample amperage for your video card and the rest of the system.
Test the supply with multimeter to measure for a steady 12v to the card's power connectors. (The only true way to test a power supply would be to use the very expensive diagnostic equipment used in labs). But for us regular folks: I tested my power supply by hooking up my multimeter to the PCI-E connectors that I was using to power my video card (I used a spare pair from the power supply to run the card while I was testing). I then observed the meter while I used the computer, first watching the voltage, then the amps, to see if there was any drop-off or erratic behavior while booting or using the computer. My readings were rock solid. So I declared my power supply good.
Otherwise you need to replace the supply to eliminate this possibility. Or borrow one from another computer.

VIDEO CARD
I suspect that a video card must perform flawlessly to operate in a Windows 7 environment and run the most recent games. If you tried all the above diagnostics and no problems were found then that leaves you with only one possibility: a defective video card. Some brands have the problem more consistently than others. You could check their forums for clues.
You could try your card in another computer running W7 to see if the problem goes along with the card.
You could try a different card in your computer. I bought an inexpensive card to use. My TDR's disappeared using a "lesser" card. Or borrow a card from another computer.
Otherwise RMA or replace the card.

TDR complaints have come from PC owners running virtually every PC configuration. They occur regardless of which video engine, manufacturer, driver, or system used. They are too numerous to write off as a random problem, but at the same time if people are getting their systems to run correctly using the same hardware and software that you are then it follows that your problem must be solvable.

More Info Here:
Timeout Detection and Recovery of GPUs through WDDM
NVIDIA Statement on TDR Errors - NVIDIA Forums
27116: ATIKMDAG has stopped responding error message

 

[x BlueRobot]

[COLOR="red"]BugCheck 124[/COLOR], {[COLOR="Blue"]0[/COLOR], [COLOR="SeaGreen"]fffffa8004db8038[/COLOR], 0, 0}

Probably caused by : AuthenticAMD

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004db8148
Section       @ fffffa8004db82d0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : [COLOR="red"]Fatal[/COLOR]

Error         : [COLOR="Red"]BUSLG_GENERIC_ERR_*_TIMEOUT_ERR[/COLOR] (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f

It seems that a Machine Check Exception occurred, this means that the CPU detected a fatal hardware error, and then reported the error to the Windows operating system with WHEA.

The dump file indicates a generic bus error has occurred, I would begin with testing your graphics card which will be connected to your PCI/PCIe slot on your motherboard:

• http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

You may use this program to monitor your GPU temperature - GPU-Z Video card GPU Information Utility

Please check that your PCI/PCIe slots are free of any dust, and that all the cards are completely connected to the slot.

Enter your BIOS, and then post the voltage settings for the 3.3V, 5V and 12V values.

 

[OpticArray]

Alright I've now done all of the following:

Removed Daemon Tools

Another SFC /scannow - No errors

Ran Western Digitals "Data Lifeguard Diagnostic" on all three hard drives - All three passed

Ran another chkdsk on all three hard drives - No errors

Seven passes of Memtest86+ - No errors

Disabled HIS iTurbo application, was only using it to disable 2D clocks per a recommendation from HIS customer support for a crash in the past

Changed the power management settings and made sure to delete the AMD/ATI folders after uninstalling per your reply

Ran FurMark with the threads recommended setting for about ten minutes where my temperature leveled out at 70 degrees with no artifacts.

And at the moment I'm currently in the process of running the ESET online scanner which is at 99% with no problems detected. Although it has been at 99% for the last 50 minutes. I haven't had a crash again so far but I haven't installed the AMD driver again yet either.

The voltages in my bios are:
VCore - 1.368V
3.3V - 3.284V
5V - 5.040V
12V - 12.011V

Edit: ESET finished with nothing found.

Edit2: And once again immediately upon finishing the AMD driver install the computer gave me another BSOD.

 

[OpticArray]

Okay it seems like it's under control now. Although I'm still getting a User Profile Service, Service Control Manager, and WMI Error on start up but that's far superior to an almost immediate BSOD. In case it helps anyone else I uninstalled the AMD drivers through the control panel, ran CCleaner to clean up any temporary files/registry issues, rebooted into safe mode and ran Driver Sweeper to remove the ATI display and deleted any AMD/ATI folders on my C: drive and in both the Program Files and Program Files (86x). Then I rebooted again into a normal start up ran the AMD driver intall with custom checked instead of express and disabled everything except for the install manager and the display driver. So far it's running without crashing or any major errors and hopefully it stays that way.

Thank you guys for the help I appreciate it. I'll leave this thread marked as unsolved for a day or two to see if any problems resurface but as long as everything goes well I'll mark it as solved after that.

 

[x BlueRobot]

Thanks for the update, post back if you have any other problems or the issue has been completely resolved.

 

[OpticArray]

Everything is still running okay! Had a crash on my graphics card because I didn't have the 2D clocks disabled but running iTurbo again fixed that. It seems like the problem was definitely related to one of the graphics related programs AMD installs with its drivers if you do an express install, so this problem is solved. Thanks again for all the help you guys.

 

[x BlueRobot]

Welcome, glad everything is working okay now