Jump to content
LaptopVideo2Go Forums

Latest Realtek Audio Codecs


Recommended Posts

nope.  sorry rick.  problem not resolved with the newly released R2.75 v6.0.1.7246 drivers.  :no:

 

reformatted and clean installed win7 x64 edition with old original intel hd graphics drivers, marvell lan drivers & intel 1000 wlan drivers on the vaio vpceb44fx notebook computer.  tried to install realtek hd audio 7246 drivers after that and boom!  BSOD during driver installation and no audio after rebooting from crash.  the problem lies somewhere with the RTKVHD64.sys file, the Realtek CoInstaller DLL files or the Realtek APO DLL files causing the BSOD crash on driver setup.

 

update: replacing just that rtkvhd64.sys file with the 7195 version made the installation work (no crash) though it broke the digital signature and made it an "unsigned" driver package and I had to click on Yes or OK to continue installation.  So far I'm glad Microsoft has not posted any newer Realtek HD audio drivers than 7195 on Microsoft Update Catalog.

 

I know for a fact that the 7195 drivers (dated 3/11/2014) were the last ones to install & work properly on the sony vpceb laptop and the crashes started to happen with attempting to install 7203 drivers (3/19/2014) and greater.

 

Latest crash dump info saved from BlueScreenView:

==================================================
Dump File         : 052114-42822-01.dmp
Crash Time        : 5/21/2014 10:26:11 AM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`032d0153
Parameter 3       : fffff880`037cb018
Parameter 4       : fffff880`037ca870
Caused By Driver  : RTKVHD64.sys
Caused By Address : RTKVHD64.sys+3b9970
File Description  : Realtek® High Definition Audio Function Driver
Product Name      : Realtek® High Definition Audio Function Driver
Company           : Realtek Semiconductor Corp.
File Version      : 6.0.1.7246 built by: WinDDK
Processor         : x64
Crash Address     : ntoskrnl.exe+6b153
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\052114-42822-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 5/21/2014 10:27:37 AM
==================================================
 

Link to post
Share on other sites
  • Replies 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

  • erp-ster7n

    405

  • stasio

    216

  • alanfox2000

    71

  • Andi_84

    70

Top Posters In This Topic

Posted Images

I thought the reason Realtek released this new build so soon was because knew about the issue and had fixed it... Guess I was mistaken

Link to post
Share on other sites

not so.  I'll report the crash problem with the 7246 driver to Realtek asap.

the fault is in the main driver file rtkvhd64.sys

Link to post
Share on other sites
  • 3 weeks later...

Realtek HD Audio driver v6.0.1.7255 from ASUS.

Good to use on ASUS ROG Motherboards & Laptops (and non-Sony VAIO machines of course).

7255 also crashed with BSOD on driver setup on my bro's Vaio VPC laptop with 64bit Win7.

seems like the drivers from 7203 to 7255 have been acting like "radioactive" on there.

 

WinDBG crash report on v7255 of the rtkvhd64.sys file:

 

===================================================

Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.22616.amd64fre.win7sp1_ldr.140303-2307
Machine Name:
Kernel base = 0xfffff800`03214000 PsLoadedModuleList = 0xfffff800`03458890
Debug session time: Mon Jun  9 01:37:24.339 2014 (UTC - 7:00)
System Uptime: 0 days 0:04:29.790
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff8000327f153, fffff880037a8018, fffff880037a7870}

*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys
Probably caused by : RTKVHD64.sys ( RTKVHD64+15500 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8000327f153, The address that the exception occurred at
Arg3: fffff880037a8018, Exception Record Address
Arg4: fffff880037a7870, Context Record Address

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP:
nt!memcpy+223
fffff800`0327f153 8a040a          mov     al,byte ptr [rdx+rcx]

EXCEPTION_RECORD:  fffff880037a8018 -- (.exr 0xfffff880037a8018)
ExceptionAddress: fffff8000327f153 (nt!memcpy+0x0000000000000223)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000003
Attempt to read from address 0000000000000003

CONTEXT:  fffff880037a7870 -- (.cxr 0xfffff880037a7870)
rax=0000000000000000 rbx=0000000000000004 rcx=fffff880037a8773
rdx=0000077ffc857890 rsi=0000000000000000 rdi=fffff880037a8770
rip=fffff8000327f153 rsp=fffff880037a8258 rbp=0000000000000002
 r8=0000000000000004  r9=fffff880037a8770 r10=0000000000000000
r11=fffff880037a8770 r12=00000000c0000023 r13=fffff8a004aa4010
r14=0000000000000086 r15=fffff880037a8344
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
nt!memcpy+0x223:
fffff800`0327f153 8a040a          mov     al,byte ptr [rdx+rcx] ds:002b:00000000`00000003=??
Resetting default scope

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000003

READ_ADDRESS:  0000000000000003

FOLLOWUP_IP:
RTKVHD64+15500
fffff880`0a41f500 4c8d9c24a0000000 lea     r11,[rsp+0A0h]

BUGCHECK_STR:  0x7E

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from fffff80003545ada to fffff8000327f153

STACK_TEXT:  
fffff880`037a8258 fffff800`03545ada : fffff6fb`7e200298 ffffffff`ffffffff fffff880`0a7c8350 0000007f`ffffffff : nt!memcpy+0x223
fffff880`037a8260 fffff800`03545974 : 00000000`00000004 fffff8a0`04aa4010 fffff880`0a7c8450 00000000`00000000 : nt!RtlpQueryRegistryDirect+0x4a
fffff880`037a8290 fffff800`0354578e : fffff880`0a7c83f0 00000000`c0000034 fffff880`037a8410 00000000`00000000 : nt!RtlpCallQueryRegistryRoutine+0xc0
fffff880`037a8310 fffff880`0a41f500 : fffff880`0a7c8450 00000000`00000001 00000000`00000000 00000000`00000000 : nt!RtlQueryRegistryValues+0x242
fffff880`037a83e0 fffff880`0a64180c : fffffa80`069b37d0 00000000`90170112 00000000`90170112 00000000`00000000 : RTKVHD64+0x15500
fffff880`037a8490 fffff880`0a616dfa : 00000000`ffc00000 fffffa80`036a8818 fffff880`00000000 00000000`00000000 : RTKVHD64+0x23780c
fffff880`037a8760 fffff880`0a40c19b : fffffa80`078a4660 00000000`27bb2037 fffffa80`036ee98c fffffa80`036ee000 : RTKVHD64+0x20cdfa
fffff880`037a8a30 fffff880`0a60d3e3 : fffffa80`00000000 fffffa80`07900fc0 fffffa80`07900fc0 fffff880`03563180 : RTKVHD64+0x219b
fffff880`037a8b80 fffff880`05c2316c : 00000000`00000001 fffffa80`03f51060 fffffa80`03f511b0 fffffa80`0790b290 : RTKVHD64+0x2033e3
fffff880`037a8bf0 fffff880`05c1efce : fffff8a0`0454c6c0 fffff8a0`0207f090 fffff800`034302d8 00000000`00000000 : portcls!PnpStartDevice+0x7c
fffff880`037a8c50 fffff800`035813d3 : 00000000`00000001 00000000`00000001 fffffa80`078a4ba0 fffffa80`03563040 : portcls!EnqueuedIoWorkItemCallback+0x26
fffff880`037a8c80 fffff800`032915b9 : fffff800`03430200 fffff800`03581301 fffffa80`03563000 fffffa80`03563040 : nt!IopProcessWorkItem+0x23
fffff880`037a8cb0 fffff800`03526d6a : 00000000`00000000 fffffa80`03563040 00000000`00000080 fffffa80`0354a5a0 : nt!ExpWorkerThread+0x111
fffff880`037a8d40 fffff800`03279266 : fffff880`035d3180 fffffa80`03563040 fffff880`035ddfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`037a8d80 00000000`00000000 : fffff880`037a9000 fffff880`037a3000 fffff880`037a81f0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  RTKVHD64+15500

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHD64

IMAGE_NAME:  RTKVHD64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5384728c

STACK_COMMAND:  .cxr 0xfffff880037a7870 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_RTKVHD64+15500

BUCKET_ID:  X64_0x7E_RTKVHD64+15500

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

Link to post
Share on other sites

Thanks for reporting, this sucks

Link to post
Share on other sites
  • 2 weeks later...

yea.  perhaps a sony vaio bios update might help but there's none available for my bro's VPC E series laptop that would make the Realtek Audio 72xx drivers work without crashing.  even the recent 7259 driver also crashed with blue screen error on driver installation on the vpceb44fx laptop.

Link to post
Share on other sites

Thanks again for letting us know and saving us the trouble

Link to post
Share on other sites

Do you know the source of this latest 7259 Realtek driver?

 

I prefer the original source because the file dates aren't all messed up

Link to post
Share on other sites

new drivers - same result; crashed with BSOD stop error 7E - "System Thread Exception Not Handled" on my brother's Win7 Sony Vaio VPCEB44FX notebook computer (recently tested with v7272, haven't tried 7260 from Dell but I know that one will crash on my bro's VAIO machine as well).

 

bsod crash report from BlueScreenView attempting to install Realtek HD Audio driver v6.0.1.7272:

==================================================
Dump File         : 070414-40653-01.dmp
Crash Time        : 7/4/2014 11:54:59 AM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`03287153
Parameter 3       : fffff880`037a1018
Parameter 4       : fffff880`037a0870
Caused By Driver  : RTKVHD64.sys
Caused By Address : RTKVHD64.sys+3c4400
File Description  : Realtek® High Definition Audio Function Driver
Product Name      : Realtek® High Definition Audio Function Driver
Company           : Realtek Semiconductor Corp.
File Version      : 6.0.1.7272 built by: WinDDK
Processor         : x64
Crash Address     : ntoskrnl.exe+6b153
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\Windows\Minidump\070414-40653-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 7/4/2014 11:56:36 AM
==================================================
 

possible things I may try later on: upgrading the vaio laptop RAM from 4GB to 8GB, installing a faster CPU (maybe upgrading from an intel i3 core cpu to an intel i5 core cpu)

 

I may install the 7260 driver on my aunt's Dell Inspiron 580 machine since that one uses Realtek audio hardware.

Link to post
Share on other sites
  • 2 weeks later...

Anyone have the source for the latest build 7283?

Link to post
Share on other sites

Realtek Audio 7283 drivers from MSI (for MSI GT70 Dominator Pro Dragon Edition notebook PC)

 

7283 drivers have also crashed my bro's Sony VAIO VPC laptop with BSOD during driver installation thru Device Manager a few days ago.

Link to post
Share on other sites

Thanks allot for the link and status... I hope to get a 'hand me down' VPCEE2E1E in the next month from a friend, this info will be useful when it comes to what driver I can install

Link to post
Share on other sites
  • 2 weeks later...

7285 is out, anybody have a source?

Link to post
Share on other sites

7285 is out, anybody have a source?

 

yup.  Toshiba.  I'll install Toshiba's Realtek Audio 7285 drivers (posted date says 7/23/2014) on my dad's Toshiba Satellite C55Dt laptop with Windows 8.1 x64 edition.

crashes with BSOD (during driver install) on Sony Vaio VPC E series laptops like my brother's vpceb44fx Windows 7 laptop...as usual.

Link to post
Share on other sites

How the f@#$ do you find the source, I tried for days and could not

Link to post
Share on other sites

New Realtek 7293 branch, hope now that we are off the 728x branch the bluescreen will be gone

 

http://www.mediafire.com/download/81e58j6rhe692qu/hda_7293_PG397_Win8.1_Win8_Win7_WHQL.7z

 

From the looks of the repack, they look to be from DELL. Have not found the link yet, but if you do please share

Link to post
Share on other sites

How the f@#$ do you find the source, I tried for days and could not

 

the 7285 drivers may have been posted July 23 on the Toshiba support site but that doesn't mean they were easily accessible on that day as it may take several days for them to be publicly mentioned on their web site.

 

New Realtek 7293 branch, hope now that we are off the 728x branch the bluescreen will be gone

 

http://www.mediafire.com/download/81e58j6rhe692qu/hda_7293_PG397_Win8.1_Win8_Win7_WHQL.7z

 

From the looks of the repack, they look to be from DELL. Have not found the link yet, but if you do please share

 

I don't think they're from Dell; otherwise that download should have contained a version.txt file.  All Dell driver downloads should contain the version.txt file.

 

Checking the Station Drivers forum site recently, a mentioned link to the 7293 drivers is from ASUS.

 

And again, the Realtek Audio 7293 drivers worked ok on many name brand PCs but not under the Sony Vaio VPCEB44FX laptop as the drivers also crashed with blue screen error on there.

 

BlueScreenView crash report on the 7293 drivers on the Vaio VPCEB44FX laptop:

==================================================
Dump File         : 081114-56659-01.dmp
Crash Time        : 8/11/2014 10:52:45 AM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff800`032ca153
Parameter 3       : fffff880`037bd008
Parameter 4       : fffff880`037bc860
Caused By Driver  : RTKVHD64.sys
Caused By Address : RTKVHD64.sys+3c6e60
File Description  : Realtek® High Definition Audio Function Driver
Product Name      : Realtek® High Definition Audio Function Driver
Company           : Realtek Semiconductor Corp.
File Version      : 6.0.1.7293 built by: WinDDK
Processor         : x64
Crash Address     : ntoskrnl.exe+6b153
Stack Address 1   : 
Stack Address 2   : 
Stack Address 3   : 
Computer Name     : 
Full Path         : C:\Windows\Minidump\081114-56659-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 262,144
Dump File Time    : 8/11/2014 10:54:28 AM
==================================================
Link to post
Share on other sites
  • 2 weeks later...

7318 out on Windows Update, maybe these v73x finally solve the bluescreen problem

 

http://download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/08/20675759_f63840c70102b9a96c1a710f06a6220d9309888b.cab

Link to post
Share on other sites

no rick.  I've just tested the 7312 drivers from Station Drivers and they also crashed with BSOD on the Vaio VPCEB44FX laptop.

And I think the 7318 drivers you just mentioned will also crash.  But please do mention the 7318 drivers on the Station Drivers forum site (um those are 64bit versions, right?).

 

Update Sept. 7: Found the source of the 7312 drivers - ASUS.

Link to post
Share on other sites

nope.  no improvement on the vaio laptop.  7324 also crashed during driver setup.

 

Update [9/2/2014]: Rick, I found the REAL cause of why the newer Realtek HD Audio drivers from 7203 to 7324 crashed during driver setup on my brothers' Sony VAIO VPCEB44FX laptop.

 

Software conflict between the Alps Touchpad driver and the newer Realtek Audio drivers.  YES that was it!

 

I uninstalled the Alps Touchpad drivers, rebooted the Sony laptop and then installed the Realtek HD Audio 6.0.1.7324 drivers and now they install and work as expected.  No more crashes. YAY! :D

 

I can live without the Alps Touchpad drivers v7.105.529.104 since they're from early 2010 and there are no more updates to those anyway and the touchpad on the Vaio laptop is still functional using the built-in Microsoft generic Win7 mouse drivers.

Link to post
Share on other sites

so ricktendo64, check your friend's Sony Vaio laptop and see if his touchpad uses Alps or Synaptics drivers.

If it uses Alps touchpad drivers, remove them, reboot and try to install the newer Realtek audio drivers.

If it uses Synaptics touchpad drivers, update them and then install the latest Realtek audio drivers.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...



×
×
  • Create New...