AnsweredAssumed Answered

BSOD issues Windows 10 x64 multiple drivers

Question asked by zombiefaace on Apr 13, 2016
Latest reply on May 3, 2016 by vpand4

Hey all, first and foremost I want to say that I work in IT, so this is about to be a pretty technical post, and I thank anyone willing to take the time to assist me. Normally these kind of issues I've been able to handle, but I've been having issues in the past few days and can't seem to resolve it on my own, so I'm hoping the experts on these forums will be able to give me a little insight.


My system specs are as follows:
Lenovo y700-15ACZ Laptop 15.6 Inch

AMD A10-8700P 10 Core APU Driver Version: 15.201.1301.1007 date 9/25/2015 (Driver for the Radeon R6 GPU portion of the APU Core)
AMD Radeon R9 M385X Driver Version: 16.150.2211.1001 date 4/3/2016 (Dedicated gaming graphics card)
16GB's of RAM

500GB SSD and 1TB HDD

Here's a copy of the Overview from the Crimson Radeon Settings:

Radeon Software Version - 16.4.1

Radeon Software Edition - Crimson

Graphics Chipset - AMD Radeon R6

Memory Size - 1024 MB

Memory Type - DDR3

Core Clock - 800 MHz

Windows Version - Windows 10 (64 bit)

System Memory - 16 GB

CPU Type - AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G



Radeon Settings Version - 2016.0403.2360.41341

Driver Packaging Version - 15.201.1301.1007-150925a-294812C-Lenovo

Provider - Advanced Micro Devices, Inc.

2D Driver Version -

Direct3D® Version -

OpenGL® Version -

OpenCL™ Version -

AMD Mantle Version -

AMD Mantle API Version - 98309

AMD Audio Driver Version -


I'm having an issue where no matter what driver I'm using (Even the one provided by the manufacturer) I'm getting random lock ups and BSOD's when just doing normal tasks in Windows even (Browsing the web for example) I read via the AMD site that the current Radeon R6 APU driver I have installed is the only one supported for my current APU 16.3.2 and 16.4.1 are NOT currently supported. And when I do a full clean uninstall (With DDU and the AMD Clean Uninstall Utility) and leave my laptop without a driver I have no issues, however I can't play games and that's what I purchased this laptop for!!! I have a couple of Event Viewer Logs as well as BSOD Dumps I'd like to include in this post and see if anyone has the same hardware as me and has had this issue and resolved it, or if this is just a known issue with the current software and I'm SOL until AMD comes out with a fix. I'm copying and pasting my logs below. (FYI I've gone as far back driver wise to 15.12 which I believe was released August/September last year for this device)



Event Viewer Logs:


Level: Error, Source: Application Error, Event ID: 1000

Faulting application name: tbaseprovisioning.exe, version:, time stamp: 0x56b4dcb7

Faulting module name: KERNELBASE.dll, version: 10.0.10586.162, time stamp: 0x56cd55ab

Exception code: 0xe0434352

Fault offset: 0x000bdad8

Faulting process id: 0x4b4

Faulting application start time: 0x01d19598af252f4c

Faulting application path: C:\Windows\SysWOW64\tbaseprovisioning.exe

Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll

Report Id: 0f5087e5-fae7-45ae-bd40-462a77c4db0c

Faulting package full name:

Faulting package-relative application ID:


Level: Error, Source: .NET Runtime, Event ID: 1026

Application: tbaseprovisioning.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.InvalidOperationException

   at System.ServiceModel.Security.SecurityUtils.GetCertificateFromStoreCore(System.Security.Cryptography.X509Certificates.StoreName, System.Security.Cryptography.X509Certificates.StoreLocation, System.Security.Cryptography.X509Certificates.X509FindType, System.Object, System.ServiceModel.EndpointAddress, Boolean)

   at System.ServiceModel.Security.SecurityUtils.GetCertificateFromStore(System.Security.Cryptography.X509Certificates.StoreName, System.Security.Cryptography.X509Certificates.StoreLocation, System.Security.Cryptography.X509Certificates.X509FindType, System.Object, System.ServiceModel.EndpointAddress)

   at System.ServiceModel.Security.X509CertificateRecipientServiceCredential.SetCertificate(System.Security.Cryptography.X509Certificates.StoreLocation, System.Security.Cryptography.X509Certificates.StoreName, System.Security.Cryptography.X509Certificates.X509FindType, System.Object)

   at System.ServiceModel.Configuration.X509RecipientCertificateServiceElement.ApplyConfiguration(System.ServiceModel.Security.X509CertificateRecipientServiceCredential)

   at System.ServiceModel.Configuration.ServiceCredentialsElement.ApplyConfiguration(System.ServiceModel.Description.ServiceCredentials)

   at System.ServiceModel.Configuration.ServiceCredentialsElement.CreateBehavior()

   at System.ServiceModel.Description.ConfigLoader.LoadBehaviors[[System.__Canon, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]](System.ServiceModel.Configuration.ServiceModelExtensionCollectionElement`1<System.ServiceModel.Configuration.BehaviorExtensionElement>, System.Collections.Generic.KeyedByTypeCollection`1<System.__Canon>, Boolean)

   at System.ServiceModel.Description.ConfigLoader.LoadServiceDescription(System.ServiceModel.ServiceHostBase, System.ServiceModel.Description.ServiceDescription, System.ServiceModel.Configuration.ServiceElement, System.Action`1<System.Uri>, Boolean)

   at System.ServiceModel.ServiceHostBase.LoadConfigurationSectionInternal(System.ServiceModel.Description.ConfigLoader, System.ServiceModel.Description.ServiceDescription, System.ServiceModel.Configuration.ServiceElement)

   at System.ServiceModel.ServiceHostBase.ApplyConfiguration()

   at System.ServiceModel.ServiceHost.ApplyConfiguration()

   at System.ServiceModel.ServiceHostBase.InitializeDescription(System.ServiceModel.UriSchemeKeyedCollection)

   at System.ServiceModel.ServiceHost.InitializeDescription(System.Type, System.ServiceModel.UriSchemeKeyedCollection)

   at System.ServiceModel.ServiceHost..ctor(System.Type, System.Uri[])

   at RootPaApp.RootPaWindowsService.startThread()

   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object)

   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)

   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)

   at System.Threading.ThreadHelper.ThreadStart()



Here's the BSOD WinDBG output:

Loading User Symbols

Mini Kernel Dump does not contain unloaded driver list


*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *




Use !analyze -v to get detailed debugging information.



BugCheck 124, {0, ffffe001b34ca8f8, 0, 0}



Probably caused by : AuthenticAMD



Followup: MachineOwner




1: kd> !analyze -v


*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *





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.


Arg1: 0000000000000000, Machine Check Exception

Arg2: ffffe001b34ca8f8, 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















ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre




ffffd001`e25245b0 fffff802`6ea2b7b1 : 00000000`00000000 ffffe001`b34ca8d0 fffff802`6e94d6a0 fffff802`6ea0e340 : nt!WheapCreateLiveTriageDump+0x81

ffffd001`e2524ae0 fffff802`6e88bc10 : ffffe001`b34ca8d0 00000000`00000000 fffff802`6e68bc40 00000000`00000000 : nt!WheapCreateTriageDumpFromPreviousSession+0x2d

ffffd001`e2524b10 fffff802`6e88cd55 : fffff802`6e94d640 fffff802`6e94d640 fffff802`6e94d6a0 fffff800`2f470880 : nt!WheapProcessWorkQueueItem+0x48

ffffd001`e2524b50 fffff802`6e6cc6a9 : fffff802`6ea0e200 ffffe001`b3e9a040 fffff800`00000000 ffffe001`b4597438 : nt!WheapWorkQueueWorkerRoutine+0x25

ffffd001`e2524b80 fffff802`6e75e895 : 00000205`bcbbbdff 00000000`00000080 ffffe001`b288b680 ffffe001`b3e9a040 : nt!ExpWorkerThread+0xe9

ffffd001`e2524c10 fffff802`6e7c2906 : fffff802`6e998180 ffffe001`b3e9a040 fffff802`6e75e854 00000000`00000000 : nt!PspSystemThreadStartup+0x41

ffffd001`e2524c60 00000000`00000000 : ffffd001`e2525000 ffffd001`e251f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16








FOLLOWUP_NAME:  MachineOwner
























FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_bus_prv



FAILURE_ID_HASH:  {6fd7875b-9a1b-9e09-d6d6-816026a875c8}



Followup: MachineOwner