BSOD error 0x3B (0xC0000005, 0xFFFFF88011162AB1...)

Hylander650 · 16 Oct 2016

Hey just posting a quick question. I looked up AODDriver and it is for an overclocking program called AMD Overdrive right? I tried to overclock my stuff once a long time ago before I got this new CPU, but couldn't get it to work, so I don't plan on trying it again and haven't tried on this new CPU. I don't mind uninstalling all of the overdrive stuff. I looked in my Programs and Features but there was no AMD Overdrive located on the list.

I have uninstalled my AMD drivers and reinstalled them a couple times now since the BSOD, and the AODDrivers seem to stick around, because there is 3 versions installed right now 4.0, 4.2.0, and 4.3. Torchwood recommended using CCleaner to remove the AODDrivers if found, but when I have tried using CCleaner I couldn't locate the AODDrivers or AMD Overdrive anywhere.

BorisTheAnimal · 18 Oct 2016

Hi Hyl.

You could try to use the AMD Clean Uninstall Utility, if you haven't done that already:

AMD Clean Uninstall Utility

And then just use the AMD Autodetect Tool:

AMD Autodetect

The AMD Clean tool should remove all stuff that is related to AMD.

Cheers, Boris :)

Hylander650 · 18 Oct 2016

I have used the AMD Clean Uninstall Utility before, but this time after running the AMD Clean Uninstall Utility and the computer reboot, I looked at the regedit where I found the AODDrivers and all 3 versions were still there.

And now I ran the AMD Auto-detect and its saying my graphics card is the "Radeon HD 8XXX Series PCIe (OEM)" which before when I would run the AMD Auto-detect it always gave me back my current graphics card, the "Radeon R9 2XX Series" I have the 270x.

It seems like its not recognizing the card anymore and is now recognizing the integrated graphics card that came with the PC or something.

Hylander650 · 18 Oct 2016

Well ignore most of my previous comment, I just manually installed the latest drivers for my R9 270x and after a reboot it looks like the computer is recognizing and using the right graphics card now. It was weird because I have used the Auto-detect ability a lot of times now and even after uninstalling the drivers previously it always showed the R9 270x, so this time it just scared me because it didn't recognize it at first.

But now were back to the AODDrivers still being installed, and it looks like it wont be uninstalled by the AMD Clean Uninstall Utility.

Hylander650 · 23 Oct 2016

So any advice on how to remove the AODDrivers? I've been looking up how to find and remove them with CCleaner but no luck so far. Anything else anyone has noticed that is out of place with my computer? Looking more and more like I will have to buy a new computer or something. Still haven't find out if the problem is hardware or software related.

Thank you all for the help on this situation, I hope we can find the problem soon so we can get it fixed or find out if I have to buy a new computer.

ICIT2LOL · 24 Oct 2016

WEll had a good old Google round and found this What is AODDriver.sys? - How to Fix AODDriver.sys Error now I am not suggesting you use it but as you can see it is involved with another dll - wmvbrcpl.dll what esxactly this means I don't know perhaps Boris might have an idea or two?

The only thing that is bothering me is that it looks like or is wanting to look like the Microsoft Fix it tool?

Hylander650 · 04 Nov 2016

Well I haven't been able to find out any more information on the AODDrivers problem besides this link http://www.tomshardware.co.uk/forum/...ddriver4-error
and this link provided by Torchwood https://www.google.co.uk/url?sa=t&rc...2euSBnaiWHz8gg

My situation is different compared to the links through, so I'm going to try my best attempt to clear the AODDrivers in the regedit and hope for the best. Got nothing else to loose and i will be more or less out of ideas on what could possibly be wrong with this computer after this. I really hope this solves the problem as I don't know of anything else that could be causing this problem.

ICIT2LOL · 04 Nov 2016

Well I am guessing that is your best bet now and if the AMD graphics go belly up it would mean they were essential for that function of the AMD stuff.

Now before you do that you could take the precaution of backing up the reg Registry - Backup and Restore at least you can merge entries back from that saved stuff if necessary.

I might have mentioned before I dropped AMD graphics years ago in favour of NVidia which I have never had a problem with but thing is you have and again I am assuming an expensive card which on a Google has been superceded by the 380X. Plus it is your budget and your choice of course.

Hylander650 · 04 Nov 2016

I just deleted all of the registries that had AODDriver in the name except for the LEGACY_AODDRIVER4.3 that I found wouldn't let me delete it. Uninstalled the AODDriver4.3 in the device manager, had a yellow exclamation mark next to it. Rebooted the computer and it started up no problem. Going to test some games and hope for the best.

And I am installing .NET Framework 4.6.2 because my .NET was outdated before.

ICIT2LOL · 04 Nov 2016

Ok well if it works even with that reg entry in it then lets hope it stays as is:)

Yep I have always kept those NET Framework stuff up to date too - not that I fully understand what they do but when I fixed my machines up for reading BSOD's I know it needs a certain NET Framework to do it so that is why I do that.