PC-HELP.CZ

Dobrý den,

s novým notebookem nemám skoro žádně problémy kromě dvou her a tou jsou Starcraft 2 a Mass Effect 3 - Multyplayer

BSOD nenaskočí hned, první mi zazní chyba, že spadl nějaký program ale pokud pokračuji v hraní tak spadne většina programů, počítač se sekne a BSOD naskočí.

U Starcraftu sem myslel, že ej to teplotou ale u Mass Effectu nic, singleplayer sem jel 42 hodin a nic se nestalo, teď dvě hodinky multy a je konec.

Notebok je MSI GT780DXR

Tady kopíruji zprávu z dumpu. Nejsem sem si jistý jestli sem to udělal správně tak raději přiložím odkazy souboru na stahnutí.


Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Neith Coldspark\Desktop\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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0345d000 PsLoadedModuleList = 0xfffff800`036a1650
Debug session time: Sun Mar 18 23:32:29.685 2012 (UTC + 1:00)
System Uptime: 1 days 4:05:10.606
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd4018). Type ".hh dbgerr001" for details
Loading unloaded module list
.........................
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff960002f0da7, fffff8800df89ea0, 0}

Page 1ea3f2 not present in the dump file. Type ".hh dbgerr004" for details
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::SetShape+157 )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff960002f0da7, Address of the instruction which caused the bugcheck
Arg3: fffff8800df89ea0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

FAULTING_IP:
win32k!SFMLOGICALSURFACE::SetShape+157
fffff960`002f0da7 488b5508 mov rdx,qword ptr [rbp+8]

CONTEXT: fffff8800df89ea0 -- (.cxr 0xfffff8800df89ea0)
rax=fffff8800df8a8c8 rbx=0000000000000000 rcx=fffff900c06aa010
rdx=fffff900c00c0010 rsi=0000000000000000 rdi=fffff900c06aa010
rip=fffff960002f0da7 rsp=fffff8800df8a880 rbp=0000000000000018
r8=000000001e12e18c r9=000000000000f4ac r10=000000000002de04
r11=fffff8800df8a8b0 r12=0000000000000001 r13=fffff900c00c0010
r14=fffff900c00c0010 r15=8000000000001000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
win32k!SFMLOGICALSURFACE::SetShape+0x157:
fffff960`002f0da7 488b5508 mov rdx,qword ptr [rbp+8] ss:0018:00000000`00000020=????????????????
Resetting default scope

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: dwm.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff96000247dec to fffff960002f0da7

STACK_TEXT:
fffff880`0df8a880 fffff960`00247dec : 00000000`00000000 00000000`00000001 fffff900`c32773d0 fffff900`c43fe9f0 : win32k!SFMLOGICALSURFACE::SetShape+0x157
fffff880`0df8a8d0 fffff960`001c3212 : fffff880`00000001 fffff800`00000001 00000000`000000c8 00000000`000000c8 : win32k!GreTransferSpriteStateToDwmState+0x1d0
fffff880`0df8a9e0 fffff960`001c3c47 : 00000000`00000000 fffff880`0df8ab60 00000000`c0000001 fffff880`0df8ab60 : win32k!zzzComposeDesktop+0x52
fffff880`0df8aa80 fffff960`0015822b : 00000000`00000000 00000000`ff61a3b0 00000000`001f0000 00000000`00000000 : win32k!zzzDwmStartRedirection+0xbf
fffff880`0df8aab0 fffff800`034d8fd3 : fffffa80`0a4c2b60 fffff880`0df8ab60 fffffa80`0d814740 00000000`00000000 : win32k!NtUserDwmStartRedirection+0x6b
fffff880`0df8aae0 00000000`774e5f7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`023bfa08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x774e5f7a


FOLLOWUP_IP:
win32k!SFMLOGICALSURFACE::SetShape+157
fffff960`002f0da7 488b5508 mov rdx,qword ptr [rbp+8]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: win32k!SFMLOGICALSURFACE::SetShape+157

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4f2b63bd

STACK_COMMAND: .cxr 0xfffff8800df89ea0 ; kb

FAILURE_BUCKET_ID: X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157

BUCKET_ID: X64_0x3B_win32k!SFMLOGICALSURFACE::SetShape+157

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

http://uloz.to/x238sw2/031812-16536-01-dmp
http://uloz.to/xzYPvwA/memory-dmp

No jedná se o chybu přístupu do paměti, vzniklé v GDI službě.
1) Zkusil bych předešlý grafický ovladač
2) Mohl by to mít na svědoní ovladač filtru (MpFilter.sys) Microsoft Malware Protection
3) Spusť Verifier a zkus si zahrát jednu z těch problémových her:

Spustit->napište "verifier"->OK->Vytvořit uživatelské nastavení->Vybrat individuální nastavení z úplného seznamu->mimo "Simulace nedostatku prostředků" zatrhněte vše->vybrat ovladače ze seznamu->vyberte vše, co není od Microsoftu->Dokončit->restartujte PC

Pokud verifier narazí na nějaký problém, objeví se BSOD a dojde k restartu počítače. Ve složce Windows\Minidump by se měl vytvořit nový výpis paměti, který mi upněte.
Pokud by k BSOD docházelo už při startu OS a nedařilo se i po několika restartech zavést systém,
spusťte nouzový režim (mačkání F8 při startu PC)
Tam spusťte Verifier a zvolte "Odstranit existující nastavení->Dokončit->restart PC.
Detekce chyby může trvat několik hodin i dní

Tak jsem tedy zkusil tu cestu přes verifier a systém už pak nenaskočil takže jsem to podle instrukcí vrátil zpátky a tady je nový výpis z dumpu + přiložím raději zase odkazy kdybych to zkopíroval špatně.



Microsoft (R) Windows Debugger Version 6.2.8229.0 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Neith Coldspark\Desktop\dump\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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`0341e000 PsLoadedModuleList = 0xfffff800`03662650
Debug session time: Tue Mar 20 17:43:21.089 2012 (UTC + 1:00)
System Uptime: 0 days 0:00:14.026
Loading Kernel Symbols
...............................................................
.......................................................
Loading User Symbols

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\user.ini, error 2
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C9, {23e, fffff88001c01300, fffff9800b6e0ee0, 0}

*** ERROR: Module load completed but symbols could not be loaded for dtsoftbus01.sys
TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
Probably caused by : dtsoftbus01.sys ( dtsoftbus01+1300 )

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

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

DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
The IO manager has caught a misbehaving driver.
Arguments:
Arg1: 000000000000023e, A driver has marked an IRP pending but didn't return STATUS_PENDING.
Arg2: fffff88001c01300, The address in the driver's code where the error was detected.
Arg3: fffff9800b6e0ee0, IRP address.
Arg4: 0000000000000000, Status code.

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

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

BUGCHECK_STR: 0xc9_23e

DRIVER_VERIFIER_IO_VIOLATION_TYPE: 23e

FAULTING_IP:
dtsoftbus01+1300
fffff880`01c01300 4053 push rbx

FOLLOWUP_IP:
dtsoftbus01+1300
fffff880`01c01300 4053 push rbx

IRP_ADDRESS: fffff9800b6e0ee0

DEVICE_OBJECT: fffffa800c179a30

DRIVER_OBJECT: fffffa8008be7c70

IMAGE_NAME: dtsoftbus01.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e9c1bae

MODULE_NAME: dtsoftbus01

FAULTING_MODULE: fffff88001c00000 dtsoftbus01

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LOCK_ADDRESS: fffff80003698b60 -- (!locks fffff80003698b60)

Resource @ nt!PiEngineLock (0xfffff80003698b60) Exclusively owned
Contention Count = 1
NumberOfExclusiveWaiters = 1
Threads: fffffa8006d53b60-01<*>
Threads Waiting On Exclusive Access:
fffffa8006d53680

1 total locks, 1 locks currently held

PNP_TRIAGE:
Lock address : 0xfffff80003698b60
Thread Count : 1
Thread address: 0xfffffa8006d53b60
Thread wait : 0x383

LAST_CONTROL_TRANSFER: from fffff800039233dc to fffff8000349ad40

STACK_TEXT:
fffff880`0395a868 fffff800`039233dc : 00000000`000000c9 00000000`0000023e fffff880`01c01300 fffff980`0b6e0ee0 : nt!KeBugCheckEx
fffff880`0395a870 fffff800`0392d47a : fffff800`039219f0 fffff880`01c01300 fffff980`0b6e0ee0 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0x3c
fffff880`0395a8b0 fffff800`0392e34e : 00000000`0000023e 00000000`00000000 fffff980`0b6e0ee0 00000000`ffffffff : nt!ViErrorFinishReport+0xda
fffff880`0395a900 fffff800`0393971f : fffffa80`0c9d8100 fffffa80`08b57f40 fffffa80`08b57ff8 fffff880`01c0507c : nt!VfErrorReport6+0x6e
fffff880`0395a9d0 fffff800`03939b63 : fffffa80`08b57f40 00000000`00000002 fffffa80`0c179a30 fffff880`01c013d0 : nt!IovpCallDriver2+0x13f
fffff880`0395aa30 fffff800`0393fc2e : fffff980`0b6e0ee0 fffff980`0b6e0ee0 00000000`00000002 fffffa80`0c179a30 : nt!VfAfterCallDriver+0x353
fffff880`0395aa80 fffff880`00e630c2 : fffff880`00edc7c0 fffffa80`0c97bdf0 00000000`00000025 fffffa80`08b57f40 : nt!IovCallDriver+0x57e
fffff880`0395aae0 fffff880`00e7859f : fffffa80`0cc15a40 00000000`00000000 fffff880`00000000 fffff880`046185d5 : Wdf01000!FxIoTarget::SubmitSync+0x24a
fffff880`0395ab90 fffff880`0462ce95 : fffffa80`00000020 fffffa80`0cc15a40 fffffa80`0c97bdf0 00000000`00000001 : Wdf01000!imp_WdfRequestSend+0x24b
fffff880`0395abe0 fffff880`0462d2f4 : 00000000`00000000 00000000`00000024 00000000`00000001 fffff880`0395ada0 : cdrom!DeviceSendRequestSynchronously+0xc9
fffff880`0395ac40 fffff880`0462bf04 : 0000057f`f3ceb7e8 fffff880`0395ada0 fffffa80`0c9f6640 00000000`00000024 : cdrom!DeviceSendSrbSynchronously+0x3ec
fffff880`0395ad70 fffff880`0462a825 : fffffa80`00000002 fffffa80`0c314b80 fffff880`046223b8 0000057f`f3ceb7e8 : cdrom!DeviceCacheDeviceInquiryData+0xbc
fffff880`0395ae40 fffff880`00ecd9d4 : 00000000`00000000 fffff880`00000010 00000000`0000000c fffff880`00ed6620 : cdrom!DeviceEvtSelfManagedIoInit+0x105
fffff880`0395ae80 fffff880`00ecd94e : fffffa80`0c3f99f0 00000000`0000000c fffff880`00ed6620 fffff880`00ed6600 : Wdf01000!FxSelfManagedIoMachine::Init+0x34
fffff880`0395aeb0 fffff880`00ec1b9b : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00ed6620 : Wdf01000!FxSelfManagedIoMachine::ProcessEvent+0x14a
fffff880`0395af20 fffff880`00ec16eb : 00000000`00000312 00000000`00000000 fffff880`00ed6600 fffff6fc`c0058c00 : Wdf01000!FxPkgPnp::PowerD0StartingStartSelfManagedIo+0x2f
fffff880`0395af50 fffff880`00ec138e : fffffa80`0c3f9b60 00000000`00000040 fffff880`00ed63e0 00000000`00000040 : Wdf01000!FxPkgPnp::PowerEnterNewState+0x1db
fffff880`0395b080 fffff880`00ec106c : 00000000`00000000 00000000`00000040 00000000`00000501 fffffa80`0c3f9b60 : Wdf01000!FxPkgPnp::PowerProcessEventInner+0x13e
fffff880`0395b0f0 fffff880`00eceb5e : 00000000`00000000 00000000`00000501 00000000`00000000 00000000`00000501 : Wdf01000!FxPkgPnp::PowerProcessEvent+0x1d4
fffff880`0395b180 fffff880`00eceabb : 00000000`00000501 00000000`00000000 00000000`00000500 fffff800`0393e5ec : Wdf01000!FxPkgPnp::NotPowerPolOwnerStarting+0xe
fffff880`0395b1b0 fffff880`00eca950 : fffffa80`0c3f9b60 00000000`00000001 00000000`00000000 fffff880`00ed2ff0 : Wdf01000!FxPkgPnp::NotPowerPolicyOwnerEnterNewState+0x1c7
fffff880`0395b230 fffff880`00eca372 : 00000000`00000000 00000000`00000001 00000000`00000000 fffffa80`0c3fcc70 : Wdf01000!FxPkgPnp::PowerPolicyProcessEventInner+0x3f8
fffff880`0395b2a0 fffff880`00ec6a45 : 00000000`00000000 fffffa80`0c3fcc70 00000000`00000108 00000000`00000000 : Wdf01000!FxPkgPnp::PowerPolicyProcessEvent+0x1e2
fffff880`0395b330 fffff880`00ec6841 : 00000000`00000101 00000000`00000108 00000000`00000108 fffff800`00000078 : Wdf01000!FxPkgPnp::PnpEventHardwareAvailable+0x111
fffff880`0395b370 fffff880`00ec64fe : fffffa80`0c3f9b60 fffff880`0395b4a0 00000000`00000004 fffff880`00ed5390 : Wdf01000!FxPkgPnp::PnpEnterNewState+0x1a5
fffff880`0395b3e0 fffff880`00ec6201 : 00000000`00000000 00000000`00000002 00000000`00000000 fffffa80`0c3f9b60 : Wdf01000!FxPkgPnp::PnpProcessEventInner+0x122
fffff880`0395b450 fffff880`00ebdd9c : 00000000`00000000 fffffa80`0c3f9b60 00000000`00000002 00000000`00000000 : Wdf01000!FxPkgPnp::PnpProcessEvent+0x1b1
fffff880`0395b4e0 fffff880`00ebcdd6 : fffffa80`08bf3e70 00000000`00000002 00000000`00000000 fffffa80`0c3f9b60 : Wdf01000!FxPkgPnp::_PnpStartDevice+0x20
fffff880`0395b510 fffff880`00e8c245 : fffff980`0b11ee50 fffff980`0b11ee50 fffffa80`0c3fcc70 00000000`00000000 : Wdf01000!FxPkgPnp::Dispatch+0x1b2
fffff880`0395b580 fffff880`00e8c14b : fffff880`0395b668 fffff980`0b11ee50 00000000`00000002 fffffa80`0c3fcc70 : Wdf01000!FxDevice::Dispatch+0xa9
fffff880`0395b5b0 fffff800`0393fc16 : fffff980`0b11ee50 00000000`00000002 fffffa80`0c3fcc70 fffffa80`0c3fcc70 : Wdf01000!FxDevice::DispatchWithLock+0x93
fffff880`0395b5f0 fffff800`03852f5e : fffff980`0b11ee50 fffffa80`0cae2f10 fffffa80`0c3fcc70 fffffa80`08b90b60 : nt!IovCallDriver+0x566
fffff880`0395b650 fffff800`0358afad : fffffa80`0c179a30 fffffa80`0cae2f10 fffff800`035946d0 00000000`00000000 : nt!PnpAsynchronousCall+0xce
fffff880`0395b690 fffff800`038622a6 : fffff800`03698920 fffffa80`0c3f2890 fffffa80`0cae2f10 fffffa80`0c3f2a38 : nt!PnpStartDevice+0x11d
fffff880`0395b750 fffff800`03862544 : fffffa80`0c3f2890 fffffa80`06d8002a fffffa80`06d81b80 00000000`00000001 : nt!PnpStartDeviceNode+0x156
fffff880`0395b7e0 fffff800`03885c76 : fffffa80`0c3f2890 fffffa80`06d81b80 00000000`00000002 00000000`00000000 : nt!PipProcessStartPhase1+0x74
fffff880`0395b810 fffff800`0388612c : fffff800`03696400 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x296
fffff880`0395ba80 fffff800`03596ff2 : 00000001`00000003 00000000`00000000 00000000`32706e50 00000000`00000084 : nt!PiProcessStartSystemDevices+0x7c
fffff880`0395bad0 fffff800`034a4471 : fffff800`03596cf0 fffff800`03790701 fffffa80`06d53b00 fffffa80`0000055a : nt!PnpDeviceActionWorker+0x302
fffff880`0395bb70 fffff800`03734f7a : 00000000`00000000 fffffa80`06d53b60 00000000`00000080 fffffa80`06cb5890 : nt!ExpWorkerThread+0x111
fffff880`0395bc00 fffff800`0348b9c6 : fffff880`0376d180 fffffa80`06d53b60 fffff880`037780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0395bc40 00000000`00000000 : fffff880`0395c000 fffff880`03956000 fffff880`0395aad0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb

SYMBOL_NAME: dtsoftbus01+1300

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1300

BUCKET_ID: X64_0xc9_23e_VRF_dtsoftbus01+1300

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


http://uloz.to/xXLUEQG/032012-18626-01-dmp
http://uloz.to/xZnVZcv/memory-dmp

Verifier zachytil chybu v ovladači dtsoftbus01.sys (Daemon Tools) Jedna jeho rutina nastavuje chybnou stavovou hodnotu, při zpracovávání IRP paketu.
Odinstaluj to včetně sptd.sys, znovu zapni verifier a jdi si zahrát. Sptd.sys odinstaluješ pomocí jeho instalátoru.
Mimochodem asi před týdnem jsem řešil obdobnou situaci, kde to pravděpodobně shazoval právě ovladač virtuální sběrnice dtsoftbus01.sys od Daemon Tools. Je to zparchantělý software, který si autor stále nedokáže opravit (nalezeny chyby již v několika předcházejících verzích)
Ten výpis z debuggeru sem nedávej, jen to znepřehledňuješ. Také stačí upnout pouze minidump. O kompletní výpis paměti jádra si kdyžtak řeknu sám.

Odinstalováno a tentokrát systém naskočil bez problému, takže du zkusit zahrát. Dám vedět.

OK

Dvě hodinky sem hrál a jelo to bez problému, ještě jsem nechal puštěný počítač přes noc a ráno vypl. A dnes když jsem prišel domů a chtěl zapnout počítač tak naběhlo BSOD poprvé a po druhé už to naskočilo normálně. Příkládám odkaz na mini dump tedy.

http://uloz.to/xXrHW7B/032212-21028-01-dmp

Tak tady máme další chybu a to v ovladači MBfilt64.sys (Creative Audio Driver) - Fri Jul 31 05:40:32 2009
Aktualizuj ho a ještě chvíli ověřuj.

To nevím jak, protože já žádný Creative audio samostatně nemám a nevím čeho je součástí o zvuk se mi stará Realtek audio a thx.

Máš pravdu, je to od Realteku. Nainstaluj tuto verzi, mbfilt64.sys je tam novější.

Na ten Váš odkaz je přístupé jméno a heslo takže sem si našel na stránkách výrobce tuto verzi http://cz.msi.com/service/download/nbdriver-17283.html je to ono?

Není. Je třeba High Definition Audio Codecs verze R2.67 zde.
Před instalací raději původní soft odinstaluj v Programy a funkce.