Realtek HDA/UAD/Component Drivers

Re: Realtek HDA/UAD/Component Drivers

1 วัน 7 ชั่วโมง ที่ผ่านมา
#
Hello fiko,

I didn't test that specific version yet, but I have tested one of the HP versions that you shared days ago 6.0.10016.1. Let me give it a try and I will reply back.
สมาชิกต่อไปนี้บอกขอบคุณ: fikotr74

กรุณา เข้าสู่ระบบ หรือ สมัครสมาชิกใหม่ เพื่อเข้าร่วมวงสนทนา

Re: Realtek HDA/UAD/Component Drivers

1 วัน 5 ชั่วโมง ที่ผ่านมา - 8 ชั่วโมง 25 นาที ที่ผ่านมา
#
fiko ,

I have tested the suggested 6.0.10013.1 ALL OEM  from the Microsoft Windows Catalog and the same BSOD popped out unfortunately  .

This is the WinDbg .dmp log:
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: fffff800d5eb3a47, address which referenced memory Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for RTKVHD64.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2593 Key : Analysis.Elapsed.mSec Value: 2614 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: 1078 Key : Analysis.Init.Elapsed.mSec Value: 4164 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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: 0xfffff800d5eb3a47 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 Key : WER.System.BIOSRevision Value: 15.55.0.0 BUGCHECK_CODE: a BUGCHECK_P1: b50 BUGCHECK_P2: 2 BUGCHECK_P3: 1 BUGCHECK_P4: fffff800d5eb3a47 FILE_IN_CAB: 083026-15734-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]ffffd7897df95080 [/color][color=#1e1e1e]WRITE_ADDRESS: fffff800d6bc54d8: 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 fffff800`d5eb3a47 f00fba2f07 lock bts dword ptr [rdi],7 STACK_TEXT: ffff8080`8360d128 fffff800`d62c04e9 : 00000000`0000000a 00000000`00000b50 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx ffff8080`8360d130 fffff800`d62bb7a8 : 00000000`00000000 00000000`00000000 00000000`00000b50 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffff8080`8360d270 fffff800`d5eb3a47 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`d5ed447b : nt!KiPageFault+0x468 ffff8080`8360d400 fffff804`d65303d2 : 00000000`00000000 fffff804`d66f00d0 00000000`00000000 ffffd789`7e736bf0 : nt!KeCancelTimer+0x67 ffff8080`8360d4a0 00000000`00000000 : fffff804`d66f00d0 00000000`00000000 ffffd789`7e736bf0 ffffd789`7dce0bc0 : RTKVHD64+0x403d2 SYMBOL_NAME: RTKVHD64+403d2 MODULE_NAME: [/color][color=#0000ff]RTKVHD64 [/color][color=#1e1e1e]IMAGE_NAME: RTKVHD64.sys STACK_COMMAND: [/color][color=#0000ff].process /r /p 0xffffd789794aa040; .thread /r /p 0xffffd7897df95080 ; kb [/color][color=#1e1e1e]BUCKET_ID_FUNC_OFFSET: 403d2 FAILURE_BUCKET_ID: AV_RTKVHD64!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {8427c922-ba45-a12b-e45a-4e0138637121} Followup: MachineOwner ---------[/color]

And...
 

Please allow me to clarify this is the first time I used Driver Fusion, I have been using Iobit Driver Booster for about 5 years. What would you suggest at this point?
Last edit: 8 ชั่วโมง 25 นาที ที่ผ่านมา by Silverian. เหตุผล: Added WinDbg .tmp code
สมาชิกต่อไปนี้บอกขอบคุณ: admin, fikotr74

กรุณา เข้าสู่ระบบ หรือ สมัครสมาชิกใหม่ เพื่อเข้าร่วมวงสนทนา

Re: Realtek HDA/UAD/Component Drivers

21 ชั่วโมง 8 นาที ที่ผ่านมา - 20 ชั่วโมง 38 นาที ที่ผ่านมา
#
fiko ,

I have tested the suggested 6.0.10013.1 ALL OEM  from the Microsoft Windows Catalog and the same BSOD popped out unfortunately  .

And...

Please allow me to clarify this is the first time I used Driver Fusion, I have been using Iobit Driver Booster for about 5 years. What would you suggest at this point?


Is your system installed as an old MBR or UEFI? Because many current drivers now only support UEFI. If it's MBR, I think you can only use MBR-supported drivers.
I'm experiencing the same problem on a PC that doesn't support UEFI. That's the last thing that came to my mind.

I use "Driver Genius" and "Driver Booster".
Last edit: 20 ชั่วโมง 38 นาที ที่ผ่านมา by fikotr74.
สมาชิกต่อไปนี้บอกขอบคุณ: THEBOSS619

กรุณา เข้าสู่ระบบ หรือ สมัครสมาชิกใหม่ เพื่อเข้าร่วมวงสนทนา

Re: Realtek HDA/UAD/Component Drivers

15 ชั่วโมง 13 นาที ที่ผ่านมา - 14 ชั่วโมง 49 นาที ที่ผ่านมา
#
  • 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.
Last edit: 14 ชั่วโมง 49 นาที ที่ผ่านมา by josefrancklin. เหตุผล: Add information
สมาชิกต่อไปนี้บอกขอบคุณ: THEBOSS619, fikotr74

กรุณา เข้าสู่ระบบ หรือ สมัครสมาชิกใหม่ เพื่อเข้าร่วมวงสนทนา

Re: Realtek HDA/UAD/Component Drivers

8 ชั่วโมง 23 นาที ที่ผ่านมา
#
fiko ,

I have tested the suggested 6.0.10013.1 ALL OEM  from the Microsoft Windows Catalog and the same BSOD popped out unfortunately .

And...

Please allow me to clarify this is the first time I used Driver Fusion, I have been using Iobit Driver Booster for about 5 years. What would you suggest at this point?


Is your system installed as an old MBR or UEFI? Because many current drivers now only support UEFI. If it's MBR, I think you can only use MBR-supported drivers.
I'm experiencing the same problem on a PC that doesn't support UEFI. That's the last thing that came to my mind.

I use "Driver Genius" and "Driver Booster".

 
My Windows 11 NVME is formated with GPT partition using entirely UEFI, CSM is disabled and Secure Boot is enabled on my BIOS.

 
สมาชิกต่อไปนี้บอกขอบคุณ: fikotr74

กรุณา เข้าสู่ระบบ หรือ สมัครสมาชิกใหม่ เพื่อเข้าร่วมวงสนทนา

เวลาที่ใช้ในการสร้างหน้าเว็บ: 0.085 วินาที
ขับเคลื่อนโดย ระบบฟอรัม Kunena