Latest Realtek Audio Codecs

[Andi_84]

New Realtek HD audio driver versions 6.0.1.6865 (for Windows 8 / Windows 7 / Vista) and 5.10.0.6865 (for Windows XP) are available from Intel's download center.

Release date: 2nd April 2013

Driver build date: 19th March 2013

Download link: AUD_Win8_Win7_6.0.1.6865_PV.exe (154 MB)

Update 8th April 2013: New versions (6.0.1.6873 and 5.10.0.6873) available, see post 52.

Best regards,

Andi

Edited April 8, 2013 by Andi_84

[Andi_84]

New Realtek HD audio driver versions 2.71 [6.0.1.6873 (for Windows 8 / Windows 7 / Vista) and 5.10.0.6873 (for Windows XP)] are available from Realtek.

Update 30th October 2013: New versions (6.0.1.7071 and 5.10.0.7071) available, see post 54.

 

Driver build date: 29th March 2013

From the changelog:

--------
History:
--------
Driver Package R2.71
    Realtek HD Audio Driver support all of Realtek HD Audio Codec .
    1. Vista, Windows 7, Windows 8 WHQL Supporting: 
            ALC882, ALC883, ALC885, ALC886, ALC887, ALC888, ALC889, ALC892, ALC899, ALC861VD, ALC900
            ALC660, ALC662, ALC663, ALC665, ALC668, ALC670, ALC671, ALC672, ALC676, ALC680
            ALC221, ALC231, ALC233, ALC260, ALC262, ALC267, ALC268, ALC269, ALC270, ALC272, ALC273, ALC275, ALC276, ALC280, ALC282, ALC283, ALC284, ALC286, ALC290, ALC292, ALC383
    2. Windows 2000/XP WHQL Supporting: 
            ALC880, ALC882, ALC883, ALC885, ALC886, ALC887, ALC888, ALC889, ALC892, ALC899, ALC861VC, ALC861VD, ALC900
            ALC660, ALC662, ALC663, ALC665, ALC668, ALC670, ALC671, ALC672, ALC676, ALC680
            ALC221, ALC231, ALC233, ALC260, ALC262, ALC267,ALC268, ALC269, ALC270, ALC272, ALC273, ALC275, ALC276, ALC280, ALC282, ALC283, ALC284, ALC286 ALC290, ALC292, ALC383
    3. HDMI Device WHQL Support: ATI HDMI Devices
    4. OS Supporting: Microsoft Windows XP, Windows 2000, Windows Server 2003, Vista, Windows Server 2008, Windows7 - x86/x64
    5. Pack with Microsoft High Definition Audio UAAV1.0a(5013) For Windows 2000 SP4, XP SP1, XP SP2, Server 2003 SP1.
    6. Add/Fix
        1.) Driver :
            1. Customizations.
            2. Add Codec ALC233, ALC284, ALC286, ALC292, ALC383, ALC668, ALC900

Best regards,
Andi

Edited April 29, 2014 by Andi_84

[erp-ster7n]

Realtek HD Audio 5.10.0.7030 (W2K/XP) & 6.0.1.7030 (Vista/7/8) drivers from ASUS (file size 288Mb - WHQL)

[Andi_84]

New Realtek HD audio driver versions 2.72 [6.0.1.7071 (for Windows 8.1 / 8 / Windows 7 / Vista) and 5.10.0.7071 (for Windows XP)] are available from Realtek.

Driver build date: 22nd October 2013

From the changelog:

--------
History:
--------
Driver Package R2.72
    Realtek HD Audio Driver support all of Realtek HD Audio Codec .
    1. Vista, Windows 7, Windows 8, Windows 8.1 WHQL Supporting: 
            ALC882, ALC883, ALC885, ALC886, ALC887, ALC888, ALC889, ALC892, ALC899, ALC861VD, ALC867, ALC900
            ALC660, ALC662, ALC663, ALC665, ALC668, ALC670, ALC671, ALC672, ALC676, ALC680
            ALC221, ALC231, ALC233, ALC235, ALC255, ALC260, ALC262, ALC267, ALC268, ALC269, ALC270, ALC272, ALC273, ALC275, ALC276, ALC280, ALC282, ALC283, ALC284, ALC286, ALC290, ALC292, ALC383
    2. Windows 2000/XP WHQL Supporting: 
            ALC880, ALC882, ALC883, ALC885, ALC886, ALC887, ALC888, ALC889, ALC892, ALC899, ALC861VC, ALC861VD, ALC867, ALC900
            ALC660, ALC662, ALC663, ALC665, ALC668, ALC670, ALC671, ALC672, ALC676, ALC680
            ALC221, ALC231, ALC233, ALC235, ALC255, ALC260, ALC262, ALC267,ALC268, ALC269, ALC270, ALC272, ALC273, ALC275, ALC276, ALC280, ALC282, ALC283, ALC284, ALC286 ALC290, ALC292, ALC383
    3. HDMI Device WHQL Support: ATI HDMI Devices
    4. OS Supporting: Microsoft Windows XP, Windows 2000, Windows Server 2003, Vista, Windows Server 2008, Windows7, Windows 8, Windows 8.1 - x86/x64
    5. Pack with Microsoft High Definition Audio UAAV1.0a(5013) For Windows 2000 SP4, XP SP1, XP SP2, Server 2003 SP1.
    6. Add/Fix
        1.) Driver :
            1. Customizations.
            2. Add Codec ALC255, ALC235, ALC867.
            3. Support Windows 8.1.

Best regards,

Andi

[StefanG3D]

Realtek Semiconductor Corp. - Audio Device (MS update)

DriverVer=01/05/2014, 6.0.1.7133

 

This driver is listed only for Windows 8.1 at Microsoft, but installs fine on Windows 7.

It comes with 54 installer files, so it should work for a lot of devices.

[ricktendo64]

Woa, thanks

[StefanG3D]

DriverVer=01/21/2014, 6.0.1.7161 (MS update)
32bit
64bit
 

This driver is listed only for Windows 8.1 at Microsoft, but installs fine on Windows 7.

It comes with 55 installer files, so it should work for a lot of devices.

[Andi_84]

New Realtek HD audio drivers for Windows 8.1, 8 and 7 are available from Intel's download center.

 

Version: 6.0.1.7183

Release Date: 5th March 2014

Driver build date: 24th February 2014 (DriverVer=02/24/2014, 6.0.1.7183)

 

Download link: AUD_Win7_8_8.1_6.0.1.7183.zip (212 MB)

 

 

Best regards,

Andi

[StefanG3D]

Realtek High Definition Audio
Version: 6.0.1.7195
Versionsdatum: 11.03.2014

this driver comes from Microsoft with 57 installers, should work for most rigs

64bit
http://download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20635257_bf96457336883f69f8156a5bf545ca9c2b476444.cab
32bit
http://download.windowsupdate.com/c/msdownload/update/driver/drvs/2014/03/20635256_7f12638d4f3e9845b63fe34cd612162e06b220c5.cab

[StefanG3D]

Gigabyte v7209 - untested

 

Acer v7203 - untested

Edited April 29, 2014 by StefanG3D

[Andi_84]

Gigabyte v7209 - untested

 

 

Driver build date: 25th March 2014 (DriverVer=03/25/2014, 6.0.1.7209)

Driver includes 57 .inf-Files, so it should install on virtually any system with Realtek sound chip.

 

 

Best regards,

Andi

[erp-ster7n]

Gigabyte v7209 - untested

 

Acer v7203 - untested

 

 

 

Driver build date: 25th March 2014 (DriverVer=03/25/2014, 6.0.1.7209)

Driver includes 57 .inf-Files, so it should install on virtually any system with Realtek sound chip.

 

 

Best regards,

Andi

 

 

DRAT!  the 7203 and 7209 Realtek HD Audio drivers crashed bigtime with BSODs on my brother's Sony VAIO VPCEB44FX Win7 64bit laptop computer during driver setup.   :mad:

whether I installed these newest drivers either by the setup program or thru device manager, Windows 7 crashes with a BSOD stop error 0x000007E and the driver installation gets botched.

 

I've gone back to using the Realtek HD Audio 6.0.1.7195 or earlier drivers on the Sony laptop, which don't crash.  AVOID any 72xx build drivers if using Realtek Audio hardware on certain Sony brand laptops.

 

on the other hand, I installed the 6.0.1.7209 drivers on my father's Toshiba C55Dt laptop with Windows 8.1 64bit edition and they worked fine.

 

Update 1: also installed the 32bit version of the 7209 audio driver on my cousin's HP Pavilion dv6648se laptop with pre-installed 32bit Vista SP2 Home Premium edition and worked out okay

[ricktendo64]

My friends VAIO VPC-L22DFX also had a blue screen when I gave him 7203 to install (it uses HDXPCEE3.inf)

 

Let me know when this is fixed for you please

[StefanG3D]

v7213 with ASIO control panel

click below the green rectangle, where it reads  "javascript:Show_DriversDig(1)"

 

not tested

[erp-ster7n]

My friends VAIO VPC-L22DFX also had a blue screen when I gave him 7203 to install (it uses HDXPCEE3.inf)

 

Let me know when this is fixed for you please

 

nope.  not fixed with v6.0.1.7203 of the audio driver.  also crashed with BSOD during installation (always uses HDXRT.inf file) on the Sony laptop.

 

v7213 with ASIO control panel

click below the green rectangle, where it reads  "javascript:Show_DriversDig(1)"

 

not tested

 

version 6.0.1.7213 recently available from ASUS (64bit Windows versions only).

 

my results of the 7213 driver:

 

my dad's Toshiba C55Dt laptop w/ x64 Win8.1 > installed & ran fine, DTS tab shows up in Realtek HD Audio Manager control panel app and can run DTS Studio Sound program (also available from Toshiba support site)

my aunt's Dell Inspiron 580 desktop PC w/ x64 Win7 SP1 > installed & ran fine

my bro's Sony Vaio VPCEB44FX laptop w/ x64 Win7 SP1 > also crashed with BSOD like with the 7203 and 7209 releases; gone back to the stable 7195 release

[ricktendo64]

CRAP!!!

 

BTW I have a VAIO VGC-LV190Y, it uses HDXRT.inf and I have not had the BSOD problem... Only my friend's VAIO that uses HDXPCEE3.inf has the BSOD issue

[StefanG3D]

 

version 6.0.1.7213 recently available from ASUS (64bit Windows versions only).

 

OK, that's easier than struggling with chinese websites :D

 

---

Just stumbled over this codec at Microsoft, but i don't know the purpose

 

Realtek I2S Audio Codec

Version: 6.2.9600.4095

Versionsdatum: 09.04.2014

32bit / 64bit

 

[ricktendo64]

Looks like its for tablets

 

http://driveridentifier.com/scan/desktop.php?scanid=5E79E5DBE7464EE58B5CA55760277EE9

 

http://driveridentifier.com/scan/desktop.php?scanid=40D99517D6F6415396DA00B070BAD846

[ricktendo64]

7233 is out, you think you can check it on your bros VAIO and let us know the results

 

http://dlcdnet.asus.com/pub/ASUS/misc/audio/Realtek_Audio_Win7-8-8-1_VER7233.zip

 

I notice a dll has changed names from RtkAPO64.dll to RltkAPO64.dll, maybe this solves the problem

[erp-ster7n]

nope.  7233 also crashed with bsod during driver installation on my bro's Sony VAIO E series laptop.

Seems like it currently hates any Realtek audio drivers higher than 7195.

I've determined that I won't install anymore 72nn audio drivers on there until either Realtek releases new generic drivers on their web site or Sony releases newer Sony OEM specific Realtek audio drivers on the Sony support site.  Latest Sony based version of the Realtek Audio drivers I found there is 6.0.1.7177.  Though that one seems to be for SVF1521BGXB and similar models, that driver also worked fine on my bro's VPCEB44FX laptop.

 

update: I recently installed Windows Debugging tools on my bro's Win7 laptop and ran WinDbg.exe.  Loaded the memory.dmp file into the debugger and the cause of the BSOD is the RTKVHD64.sys file, according to WinDbg.  So I'll definitely stay away from using any new realtek audio drivers like 7203 to 7233 until a newer official one appears on either the Realtek web site or the Sony support site.

 

Google search on Realtek HD Audio BSOD.

[ricktendo64]

7240 has been officially released (let me know the results)

 

http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false

[erp-ster7n]

AHH F*CK SH*T! :mad:

 

Even the officially released R2.74 Realtek HD Audio 6.0.1.7240 driver crashed with BSOD Stop Error 7E during driver setup on the Sony Vaio VPCEB44FX notebook computer.  whether I use the setup.exe program or Device Manager to install the 7240 driver, it consistently crashes with BSOD Stop Error 7E.  After rebooting from the crash I get no audio at all, just like the previous drivers from 7203 to 7235.   GRRRRRRR!

 

ok, I've emailed Realtek about the crashing problems on the Sony Vaio laptop and will wait for them to respond.  Uninstalled the 7240 driver and I'm now back to using Realtek HD Audio driver 7195 on the Vaio laptop.

[ricktendo64]

What is the hardware id of this problem machine?

[erp-ster7n]

This is the hardware ID used on the Vaio VPCEB44FX laptop:

HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_104D4600&REV_1000

 

Even updating to 7240 thru Device Manager (installing 7240 over 7195) caused BSOD.

 

Here is a recent report generated by BlueScreenView (copied from a txt file):

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

Dump File         : 051614-26582-01.dmp

Crash Time        : 5/16/2014 8:37:12 AM

Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code    : 0x1000007e

Parameter 1       : ffffffff`c0000005

Parameter 2       : fffff800`032d2153

Parameter 3       : fffff880`037b6018

Parameter 4       : fffff880`037b5870

Caused By Driver  : RTKVHD64.sys

Caused By Address : RTKVHD64.sys+3b92f0

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.7240 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\051614-26582-01.dmp

Processors Count  : 4

Major Version     : 15

Minor Version     : 7601

Dump File Size    : 262,144

Dump File Time    : 5/16/2014 8:38:26 AM

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

 

And a few days ago, I generated a report from WinDbg and this was the output (also copied from a txt 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.22556.amd64fre.win7sp1_ldr.140101-1436

Machine Name:

Kernel base = 0xfffff800`03219000 PsLoadedModuleList = 0xfffff800`0345d890

Debug session time: Wed May 14 22:44:26.741 2014 (UTC - 7:00)

System Uptime: 0 days 0:06:33.193

Loading Kernel Symbols

...............................................................

................................................................

...............................

Loading User Symbols

 

Loading unloaded module list

....................

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

 

Use !analyze -v to get detailed debugging information.

 

BugCheck 7E, {ffffffffc0000005, fffff80003284153, fffff880037cb018, fffff880037ca870}

 

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

*** ERROR: Module load completed but symbols could not be loaded for RTKVHD64.sys

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

Probably caused by : RTKVHD64.sys ( RTKVHD64+153c0 )

 

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: fffff80003284153, The address that the exception occurred at

Arg3: fffff880037cb018, Exception Record Address

Arg4: fffff880037ca870, Context Record Address

 

Debugging Details:

------------------

 

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

 

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`03284153 8a040a          mov     al,byte ptr [rdx+rcx]

 

EXCEPTION_RECORD:  fffff880037cb018 -- (.exr 0xfffff880037cb018)

ExceptionAddress: fffff80003284153 (nt!memcpy+0x0000000000000223)

   ExceptionCode: c0000005 (Access violation)

  ExceptionFlags: 00000000

NumberParameters: 2

   Parameter[0]: 0000000000000000

   Parameter[1]: 0000000000000003

Attempt to read from address 0000000000000003

 

CONTEXT:  fffff880037ca870 -- (.cxr 0xfffff880037ca870)

rax=0000000000000000 rbx=0000000000000004 rcx=fffff880037cb773

rdx=0000077ffc834890 rsi=0000000000000000 rdi=fffff880037cb770

rip=fffff80003284153 rsp=fffff880037cb258 rbp=0000000000000002

 r8=0000000000000004  r9=fffff880037cb770 r10=0000000000000000

r11=fffff880037cb770 r12=00000000c0000023 r13=fffff8a0048905d0

r14=0000000000000086 r15=fffff880037cb344

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`03284153 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: The call to LoadLibrary(exts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

The call to LoadLibrary(kdexts) failed, Win32 error 0n2

    "The system cannot find the file specified."

Please check your debugger configuration and/or network access.

 0000000000000003 

 

FOLLOWUP_IP: 

RTKVHD64+153c0

fffff880`0a81f3c0 4c8d9c24a0000000 lea     r11,[rsp+0A0h]

 

BUGCHECK_STR:  0x7E

 

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

 

LAST_CONTROL_TRANSFER:  from fffff8000354aada to fffff80003284153

 

STACK_TEXT:  

fffff880`037cb258 fffff800`0354aada : fffff6fb`7e2002a8 ffffffff`ffffffff fffff880`0abc32f0 0000007f`ffffffff : nt!memcpy+0x223

fffff880`037cb260 fffff800`0354a974 : 00000000`00000004 fffff8a0`048905d0 fffff880`0abc33f0 00000000`00000000 : nt!RtlpQueryRegistryDirect+0x4a

fffff880`037cb290 fffff800`0354a78e : fffff880`0abc3390 00000000`c0000034 fffff880`037cb410 00000000`00000000 : nt!RtlpCallQueryRegistryRoutine+0xc0

fffff880`037cb310 fffff880`0a81f3c0 : fffff880`0abc33f0 00000000`00000001 00000000`00000000 00000000`00000000 : nt!RtlQueryRegistryValues+0x242

fffff880`037cb3e0 fffff880`0aa3f8f4 : fffffa80`08f7f010 00000000`90170112 00000000`90170112 00000000`00000000 : RTKVHD64+0x153c0

fffff880`037cb490 fffff880`0aa15670 : 00000000`ffc00000 fffffa80`090de818 fffff880`00000000 00000000`00000000 : RTKVHD64+0x2358f4

fffff880`037cb760 fffff880`0a80c1af : fffffa80`077a86b0 00000000`39e0e610 fffffa80`0365c98c fffffa80`0365c000 : RTKVHD64+0x20b670

fffff880`037cba30 fffff880`0aa0bc97 : fffffa80`00000000 fffffa80`0938e0d0 fffffa80`0938e0d0 fffff880`00000623 : RTKVHD64+0x21af

fffff880`037cbb80 fffff880`0615616c : 00000000`00000001 fffffa80`08d7f060 fffffa80`08d7f1b0 fffffa80`08f65010 : RTKVHD64+0x201c97

fffff880`037cbbf0 fffff880`06151fce : fffff8a0`03909010 fffff8a0`054aa880 fffff800`034352d8 00000000`00000000 : portcls!PnpStartDevice+0x7c

fffff880`037cbc50 fffff800`035863d3 : 00000000`00000001 00000000`00000001 fffffa80`077a8bf0 fffffa80`03561660 : portcls!EnqueuedIoWorkItemCallback+0x26

fffff880`037cbc80 fffff800`032965b9 : fffff800`03435200 fffff800`03586301 fffffa80`03561600 fffffa80`03561660 : nt!IopProcessWorkItem+0x23

fffff880`037cbcb0 fffff800`0352bd6a : ffffffff`ffffffff fffffa80`03561660 00000000`00000080 fffffa80`0354a5a0 : nt!ExpWorkerThread+0x111

fffff880`037cbd40 fffff800`0327e266 : fffff880`035d3180 fffffa80`03561660 fffff880`035ddfc0 00000000`00000001 : nt!PspSystemThreadStartup+0x5a

fffff880`037cbd80 00000000`00000000 : fffff880`037cc000 fffff880`037c6000 fffff880`037c9de0 00000000`00000000 : nt!KxStartSystemThread+0x16

 

 

SYMBOL_STACK_INDEX:  4

 

SYMBOL_NAME:  RTKVHD64+153c0

 

FOLLOWUP_NAME:  MachineOwner

 

MODULE_NAME: RTKVHD64

 

IMAGE_NAME:  RTKVHD64.sys

 

DEBUG_FLR_IMAGE_TIMESTAMP:  5368e03d

 

STACK_COMMAND:  .cxr 0xfffff880037ca870 ; kb

 

FAILURE_BUCKET_ID:  X64_0x7E_RTKVHD64+153c0

 

BUCKET_ID:  X64_0x7E_RTKVHD64+153c0

 

Followup: MachineOwner

---------

 

---------------------------------------------------------------------------------

[ricktendo64]

R275 has officially been released, lets hope the issue is finally fixed (please confirm)