Realtek HDA/UAD/Component Drivers
- Silverian
-
- Hors Ligne
- Poster 2
-
Enregistré
- Messages : 5
- Thanks: 4
Re: Realtek HDA/UAD/Component Drivers
il y a 1 heure 59 minutes - il y a 1 heure 41 minutesHello josefrancklin, thank you for your response!
- I am not not sure why, but even if hardware ID HDAUDIO\FUNC_01&VEN_10EC&DEV_0295&SUBSYS_103C8615 is present inside every HDXHAPHPNB.inf driver I have tested (supposed to be compatible), I am still getting the BSOD.
Hi Silverian,
I've just analyzed your issue. After a quick comparison between 6.0.9850.1 and 6.0.10013.1 versions of HDXHAPHPNB.inf, found no difference in registry entries, just a newer version.
Based on HDXHAPHPNB.inf, your system also uses an AMD driver "amdacpksl.sys", as this is slightly different in both versions, probably you may have compatibility issues when newer amdacpksl.sys drivers try to load on older systems.
Try to find driver updates for other AMD specific devices you can find under System Devices and/other categories at Device Manager and after try to update Realtek Audio Codec again.
Add: If you don't find any other AMD updates: try one of these Realtek versions from Windows Update that appears when searched your SUBSYS:
catalog.update.microsoft.com/Search.aspx?q=SUBSYS_103C8615
Note: your stuck version 6.0.9850.1 is not listed in search results.
Very good catch mentioning the AMD driver "amdacpksl.sys", a.k.a. as the AMD Audio CoProcessor, let me start by clarifying there is a known issue with this driver affecting HDAUDIO\FUNC_01&VEN_10EC&DEV_0295&SUBSYS_103C8615 that causes loud static / crackling noise, for that reason I am permanently avoiding the 6.x.x.xx versions and stuck with 2.xx.x.xx versions, right now I am using v2.89.0.86 in case you want to know.
On the other hand, I didn't know you could filter drivers in the Microsoft Update Catalog using the SUBSUYS, very interesting. I tested a couple but got the same BSOD result unfortunately.
Code:
[color=#1e1e1e]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000b50, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff804dc8b3a47, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for RTKVHD64.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2500
Key : Analysis.Elapsed.mSec
Value: 3609
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 1046
Key : Analysis.Init.Elapsed.mSec
Value: 11416
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.Version.DbgEng
Value: 10.0.29617.1000
Key : Analysis.Version.Description
Value: 10.2604.29.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2604.29.1
Key : Bugcheck.Code.LegacyAPI
Value: 0xa
Key : Bugcheck.Code.TargetModel
Value: 0xa
Key : Dump.Attributes.AsUlong
Value: 0x21808
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0x0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
Key : Failure.Bucket
Value: AV_RTKVHD64!unknown_function
Key : Failure.Exception.IP.Address
Value: 0xfffff804dc8b3a47
Key : Failure.Exception.IP.Module
Value: nt
Key : Failure.Exception.IP.Offset
Value: 0x2b3a47
Key : Failure.Hash
Value: {8427c922-ba45-a12b-e45a-4e0138637121}
Key : Faulting.IP.Type
Value: Paged
Key : Hypervisor.Enlightenments.ValueHex
Value: 0x749fcf96
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1
Key : Hypervisor.Flags.ApicEnlightened
Value: 1
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 1
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1
Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 0
Key : Hypervisor.Flags.MaxBankNumber
Value: 0
Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0
Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0
Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1
Key : Hypervisor.Flags.Phase0InitDone
Value: 1
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 1
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 38277359
Key : Hypervisor.Flags.ValueHex
Value: 0x24810ef
Key : Hypervisor.Flags.VpAssistPage
Value: 1
Key : Hypervisor.Flags.VsmAvailable
Value: 1
Key : Hypervisor.RootFlags.AccessStats
Value: 1
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 1
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1
Key : Hypervisor.RootFlags.MceEnlightened
Value: 1
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1
Key : Hypervisor.RootFlags.Value
Value: 1015
Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7
BUGCHECK_CODE: a
BUGCHECK_P1: b50
BUGCHECK_P2: 2
BUGCHECK_P3: 1
BUGCHECK_P4: fffff804dc8b3a47
FILE_IN_CAB: 083026-15296-01.dmp
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump
FAULTING_THREAD: [/color][color=#0000ff]ffff988566137080
[/color][color=#1e1e1e]WRITE_ADDRESS: fffff804dd5c54d8: Unable to get MiVisibleState
0000000000000b50
BLACKBOXBSD: 1 ([/color][color=#0000ff]!blackboxbsd[/color][color=#1e1e1e])
BLACKBOXNTFS: 1 ([/color][color=#0000ff]!blackboxntfs[/color][color=#1e1e1e])
BLACKBOXPNP: 1 ([/color][color=#0000ff]!blackboxpnp[/color][color=#1e1e1e])
BLACKBOXWINLOGON: 1 ([/color][color=#0000ff]!blackboxwinlogon[/color][color=#1e1e1e]) ([/color][color=#0000ff]!blackboxwinlogonnotify[/color][color=#1e1e1e])
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
IP_IN_PAGED_CODE:
nt!KeCancelTimer+67
fffff804`dc8b3a47 f00fba2f07 lock bts dword ptr [rdi],7
STACK_TEXT:
ffff948c`32bb8128 fffff804`dccc04e9 : 00000000`0000000a 00000000`00000b50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
ffff948c`32bb8130 fffff804`dccbb7a8 : 00000000`00000000 00000000`00000000 00000000`00000b50 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffff948c`32bb8270 fffff804`dc8b3a47 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`dc8d447b : nt!KiPageFault+0x468
ffff948c`32bb8400 fffff804`7dd10062 : 00000000`00000000 fffff804`7dece0d0 00000000`00000000 ffff9885`73ea9460 : nt!KeCancelTimer+0x67
ffff948c`32bb84a0 00000000`00000000 : fffff804`7dece0d0 00000000`00000000 ffff9885`73ea9460 ffff9885`74b06d00 : RTKVHD64+0x40062
SYMBOL_NAME: RTKVHD64+40062
MODULE_NAME: [/color][color=#0000ff]RTKVHD64
[/color][color=#1e1e1e]IMAGE_NAME: RTKVHD64.sys
STACK_COMMAND: [/color][color=#0000ff].process /r /p 0xffff9885604b1040; .thread /r /p 0xffff988566137080 ; kb
[/color][color=#1e1e1e]BUCKET_ID_FUNC_OFFSET: 40062
FAILURE_BUCKET_ID: AV_RTKVHD64!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {8427c922-ba45-a12b-e45a-4e0138637121}
Followup: MachineOwner
---------
[/color]
This is the .dmp WinDbg log in case anyone else is curious to assist.
Dernière édition: il y a 1 heure 41 minutes par Silverian. Raison: Testing result.
Connexion ou Créer un compte pour participer à la conversation.
Temps de génération de la page : 0.079 secondes