BSOD at pretty random times

Hey guys, been getting alot of BSOD lately and not sure whats causing them. They dont seem to be happening for any real reason, they'll do it when im playing counter strike but then they do them when im just browsing the internet.

In the past its been heat thats caused alot of mine but my pc is fairly clean at the minute, thought it was a driver clash because I had forgot to get rid of my old GFX driver, got rid of it and it still happens. Been thinking it might be RAM? Had to some problems with it a while ago but it went away, Im just guessing though.

Would really appreciate any help because BSOD up to five times a day is not my idea of fun!

Cheers guys!

Arc said:

Does the BSOD continue to occur even when the Logitech headset is not connected?

Try it and let us know.

Some more things .... some good lot of tests may be needed to do depending on the result.

Also, uninstall AMD overdrive.

Let us know the the result.
___________________________________

Code:

BugCheck 124, {0, fffffa80079e3028, b61e2000, 135}

*** WARNING: Unable to verify timestamp for ladfGSRamd64.sys
*** ERROR: Module load completed but symbols could not be loaded for ladfGSRamd64.sys
Probably caused by : AuthenticAMD

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

Headset thing is interesting, not had any problems whilst I've been watching netlifx.

Cant find any reference to AMD overdrive? Am I being blind or looking in the wrong place?

And I uninstalled Daemon tools after reading it caused problems

Arc said:

Code:

AODDriver4.01    ROOT\LEGACY_AODDRIVER4.01\0000    This device is not present, is not working properly, or does not have all its drivers installed.

It may be used by any MSI programs too, like PC Alert.

I would suggest you to uninstall all the MSI bloatware. Also Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

As the headset driver is reported to be failed, I think it is better to see teh situation without it at first, before going for the next steps.

Ill got through and cut down the stuff on boot, had the headset in for the last few hours and had no problems though

Arc said:

It is needed to know the situation WITHOUT THE HEADSET PLUGGED IN. Not the reverse.

Fair enough, Ill leave it out for a while. Was trying to see if with it plugged in I ran into a problem, had none either way so far.

Arc said:

shuff264 said:

Arc said:

It is needed to know the situation WITHOUT THE HEADSET PLUGGED IN. Not the reverse.

Fair enough, Ill leave it out for a while. Was trying to see if with it plugged in I ran into a problem, had none either way so far.

BSODs are random, and that is why it is an issue.

A stop 0x124 is one of the most serious bugchecks that requires intense and long troubleshooting to get a success. No one can expect a single point remedy for it.

Stop 0x124 - what it means and what to try

But still, we have a failing module, and we need to be sure about that one at first.

Have patience. There is a very long way to go.

Fair enough mate. Like I said earlier I removed Daemon tools and since then its been better, dont know if thats related or not.