Som do Pc travando (xiando e travando,parando e travando) ajuda pf !

[Adson Gomes]

Ola.Meu pc está com este problema a muito tempo o som dele para do nada e ai o pc trava, ou o som fica com muito chiado e o pc trava,isso acontece quando estou jogando,acessando a internet,ouvindo musica já aconteceu até antes de entrar no usuário,eu levei no técnico esses dias e ele me disse que não tinha nada de anormal no pc estava 100 % mas ele não abriu disse que só fez verificações por programas e que não encontrou nada de errado,ele também deixou umas 5 horas ligado tocando musica para testar e não travou mas o problema é que ele as vezes trava e as vezes não,as vezes passa 1,2 dias sem travar nenhuma vez,as vezes passa 2,3 dias só travando,nesse dia quando trouxe o computador para casa ele realmente não travou,mas no dia seguinte já começou a travar.Então queria a ajuda de vocês para isso e muito obrigado.

 

Ja tentei o metodo /sfc scannow  não funcionou

Já formatei e não resolveu 

[WETON]

Favor informar toda configuração de seu computador com marca e modelo das peças!

[Hqxriven]

Poste tb um minidump C:\windows\Minidump (faça o upload para algum lugar)

 

No minidump geralmente tem o registro do que ocorreu no momento da falha.

[Adson Gomes]

Favor informar toda configuração de seu computador com marca e modelo das peças!

 

 

Poste tb um minidump C:\windows\Minidump (faça o upload para algum lugar)

 

No minidump geralmente tem o registro do que ocorreu no momento da falha.

 ele é um

AOC All-in-one M92E evo

AMD Atlhon Neo x2 Dual-Core Processor L325 1.5 GHz

2,00 GB de Ram

320 GB de memoria

Placa de Video uma AMD Raedon HD 3200 Graphics (895 Mb de memoria grafica disponivel)

 

aqui está um link do manual da propria aoc : http://aoc.com.br/media/anexo/699FT_.PDF

 

aqui mais um site com especificações: http://www.qualitech.info/produto/15042/computador-aoc-evo-9223ps-all-in-one-m92e-amd-athlon-neo-x2-l325-15ghz--2gb--320gb--dvd-rw--web--185--wind7-starter/

 

Abaixo estão os minidumps.

 

http://www.4shared.com/rar/s6jbcTyeba/MD_online.html

 

Obrigado pela  ajuda

[Hqxriven]

você tem vários problemas diferentes, vou analisar os que mais me chamaram a atenção.

 

 

 

Loading Dump File [D:\Downloads\Firefox\MD\MD\091714-25896-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available



*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {c07cf6f8, 0, 0, 8307c136}

*** WARNING: Unable to verify timestamp for Bhbase.sys
*** ERROR: Module load completed but symbols could not be loaded for Bhbase.sys
Probably caused by : Bhbase.sys ( Bhbase+32ac )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: c07cf6f8, memory referenced
Arg2: 00000000, IRQL
Arg3: 00000000, 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: 8307c136, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 831a7718
Unable to read MiSystemVaType memory at 83187160
 c07cf6f8

CURRENT_IRQL:  0

FAULTING_IP:
nt!MiLockProtoPoolPage+19
8307c136 8b1f            mov     ebx,dword ptr [edi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  qubnfe.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  a900fadc -- (.trap 0xffffffffa900fadc)
ErrCode = 00000000
eax=00000012 ebx=9d6b6010 ecx=00000022 edx=0000001d esi=9dac2e98 edi=9a396e70
eip=832376ca esp=a900fb50 ebp=a900fb5c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
nt!RtlpHashStringToAtom+0xa5:
832376ca 0fb6460b        movzx   eax,byte ptr [esi+0Bh]     ds:0023:9dac2ea3=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8307c136 to 8308581b

STACK_TEXT:  
a900f934 8307c136 badb0d00 00000002 87d36d48 nt!KiTrap0E+0x2cf
a900f9cc 830cf9da a900fa2c 87d36d48 83173300 nt!MiLockProtoPoolPage+0x19
a900fa38 830c5e5e 9dac2ea3 00000000 83173300 nt!MiDispatchFault+0x5b2
a900fac4 83085628 00000000 9dac2ea3 00000000 nt!MmAccessFault+0x157c
a900fac4 832376ca 00000000 9dac2ea3 00000000 nt!KiTrap0E+0xdc
a900fb5c 8322ff6c 0000000d 7675fb80 00000000 nt!RtlpHashStringToAtom+0xa5
a900fba4 826b1d9c 9d6b6010 7675fb80 a900fbb8 nt!RtlLookupAtomInAtomTable+0x78
a900fbbc 826a8c61 7675fb80 2b829a2a 00000000 win32k!UserFindAtom+0x1d
a900fc00 826a8e8d 00000000 00000000 7675fb80 win32k!_FindWindowEx+0x28
a900fc54 888432ac 00000000 00000000 0012d6c0 win32k!NtUserFindWindowEx+0xeb
WARNING: Stack unwind information not available. Following frames may be wrong.
a900fd34 77d16344 badb0d00 0012d698 00000000 Bhbase+0x32ac
a900fd38 badb0d00 0012d698 00000000 00000000 0x77d16344
a900fd3c 0012d698 00000000 00000000 00000000 0xbadb0d00
a900fd40 00000000 00000000 00000000 00000000 0x12d698


STACK_COMMAND:  kb

FOLLOWUP_IP:
Bhbase+32ac
888432ac ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  Bhbase+32ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Bhbase

IMAGE_NAME:  Bhbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  531e74c3

FAILURE_BUCKET_ID:  0xA_Bhbase+32ac

BUCKET_ID:  0xA_Bhbase+32ac

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa_bhbase+32ac

FAILURE_ID_HASH:  {3ce1a5a9-6cb6-8b14-100c-d62f5e128f1f}

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

Você está com o Baidu PC Faster (ou Antivírus) instalado e ele está provocando travamentos. Desinstale o mesmo, dê um boot e passe o Adwcleaner e depois delete o arquivo C:\Windows\System32\DRIVERS\bhbase.sys

 

--

 

Loading Dump File [D:\Downloads\Firefox\MD\MD\091414-26644-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
 

 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 81fa196d, 913d8438, 0}

*** WARNING: Unable to verify timestamp for RTKVHDA.sys
*** ERROR: Module load completed but symbols could not be loaded for RTKVHDA.sys
*** WARNING: Unable to verify timestamp for Bhbase.sys
*** ERROR: Module load completed but symbols could not be loaded for Bhbase.sys
 

Probably caused by : RTKVHDA.sys ( RTKVHDA+19096d )

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

0: kd> !analyze -v
 

 

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 81fa196d, The address that the exception occurred at
Arg3: 913d8438, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru  o no 0x%08lx fez refer ncia   mem ria no 0x%08lx. A mem ria n o p de ser %s.

FAULTING_IP:
RTKVHDA+19096d
81fa196d ??              ???

TRAP_FRAME:  913d8438 -- (.trap 0xffffffff913d8438)
ErrCode = 00000000
eax=00000000 ebx=871f1008 ecx=00000000 edx=871ee928 esi=871eee50 edi=86b9e3b0
eip=81fa196d esp=913d84ac ebp=913d8504 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
RTKVHDA+0x19096d:
81fa196d ??              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  RtHDVCpl.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 830c3472 to 830e2dfc

STACK_TEXT:  
913d7fa4 830c3472 0000008e c0000005 81fa196d nt!KeBugCheckEx+0x1e
913d83c8 8304a026 913d83e4 00000000 913d8438 nt!KiDispatchException+0x1ac
913d8430 83049fda 913d8504 81fa196d badb0d00 nt!CommonDispatchException+0x4a
913d8438 81fa196d badb0d00 871ee928 00000000 nt!Kei386EoiHelper+0x192
WARNING: Stack unwind information not available. Following frames may be wrong.
913d8504 81f7ed7b 871eee50 00000002 00000000 RTKVHDA+0x19096d
913d8774 81f7f3e4 8544b3a0 873dc008 8656ba20 RTKVHDA+0x16dd7b
913d899c 955de5a2 8544b3a0 aab94568 88399008 RTKVHDA+0x16e3e4
913d89b4 955de438 88399008 8656ba20 9b693a80 portcls!PcDispatchProperty+0x146
913d89dc 929cf1d2 00000008 aab94568 aab94560 portcls!PropertyItemPropertyHandler+0x2b
913d8a2c 929d8177 88399008 00000014 9b693a80 ks!KspPropertyHandler+0x67c
913d8a50 955de2e5 88399008 00000016 9b693a58 ks!KsPropertyHandler+0x19
913d8a68 955ee784 00399008 00000016 9b693a58 portcls!PcHandlePropertyWithTable+0x49
913d8ab0 955de060 8656ba08 86b98030 88399008 portcls!CPortFilterWaveRT::DeviceIoControl+0xcf
913d8ad0 929ce789 86b980e8 88399008 913d8af8 portcls!DispatchDeviceIoControl+0x5b
913d8ae0 955e4001 86b98030 88399008 88399008 ks!KsDispatchIrp+0xb0
913d8af8 955e4cc8 86b98030 88399008 913d8b24 portcls!KsoDispatchIrp+0x43
913d8b08 81f8d858 86b98030 88399008 8542bf80 portcls!PcDispatchIrp+0x2d
913d8b24 830424ac 86b98030 c0000001 88399008 RTKVHDA+0x17c858
913d8b3c 832443be 8542bf80 88399008 8839909c nt!IofCallDriver+0x63
913d8b5c 832611af 86b98030 8542bf80 00000000 nt!IopSynchronousServiceTail+0x1f8
913d8bf8 8326398a 86b98030 88399008 00000000 nt!IopXxxControlFile+0x6aa
913d8c2c 8889dc74 00000420 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
913d8d34 77726344 badb0d00 0012fa30 00000000 Bhbase+0x1c74
913d8d38 badb0d00 0012fa30 00000000 00000000 0x77726344
913d8d3c 0012fa30 00000000 00000000 00000000 0xbadb0d00
913d8d40 00000000 00000000 00000000 00000000 0x12fa30


STACK_COMMAND:  kb

FOLLOWUP_IP:
RTKVHDA+19096d
81fa196d ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RTKVHDA+19096d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHDA

IMAGE_NAME:  RTKVHDA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5278d8aa

FAILURE_BUCKET_ID:  0x8E_RTKVHDA+19096d

BUCKET_ID:  0x8E_RTKVHDA+19096d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_rtkvhda+19096d

FAILURE_ID_HASH:  {6b72f0a4-a169-0d1c-f1da-6716e93a220f}

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

Mas antes tente apenas remover o Baidu no passo que passei acima e veja isso corrige, caso não corrija faça esse passo pro driver realtek

 

 

você possui problemas com o comportamento do driver de audio Realtek tente atualizar o driver e veja se corrige.

Se possível passe um AdwCleaner (vai ter que refazer o profile do Firefox porque ele buga o mesmo)

 

 

Até a próxima!

[Adson Gomes]

você tem vários problemas diferentes, vou analisar os que mais me chamaram a atenção.

 

 

 

Loading Dump File [D:\Downloads\Firefox\MD\MD\091714-25896-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {c07cf6f8, 0, 0, 8307c136}

*** WARNING: Unable to verify timestamp for Bhbase.sys

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

Probably caused by : Bhbase.sys ( Bhbase+32ac )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

*                                                                             *

*                        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: c07cf6f8, memory referenced

Arg2: 00000000, IRQL

Arg3: 00000000, 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: 8307c136, address which referenced memory

Debugging Details:

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

READ_ADDRESS: GetPointerFromAddress: unable to read from 831a7718

Unable to read MiSystemVaType memory at 83187160

 c07cf6f8

CURRENT_IRQL:  0

FAULTING_IP:

nt!MiLockProtoPoolPage+19

8307c136 8b1f            mov     ebx,dword ptr [edi]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  qubnfe.exe

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  a900fadc -- (.trap 0xffffffffa900fadc)

ErrCode = 00000000

eax=00000012 ebx=9d6b6010 ecx=00000022 edx=0000001d esi=9dac2e98 edi=9a396e70

eip=832376ca esp=a900fb50 ebp=a900fb5c iopl=0         nv up ei ng nz na po nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282

nt!RtlpHashStringToAtom+0xa5:

832376ca 0fb6460b        movzx   eax,byte ptr [esi+0Bh]     ds:0023:9dac2ea3=??

Resetting default scope

LAST_CONTROL_TRANSFER:  from 8307c136 to 8308581b

STACK_TEXT:  

a900f934 8307c136 badb0d00 00000002 87d36d48 nt!KiTrap0E+0x2cf

a900f9cc 830cf9da a900fa2c 87d36d48 83173300 nt!MiLockProtoPoolPage+0x19

a900fa38 830c5e5e 9dac2ea3 00000000 83173300 nt!MiDispatchFault+0x5b2

a900fac4 83085628 00000000 9dac2ea3 00000000 nt!MmAccessFault+0x157c

a900fac4 832376ca 00000000 9dac2ea3 00000000 nt!KiTrap0E+0xdc

a900fb5c 8322ff6c 0000000d 7675fb80 00000000 nt!RtlpHashStringToAtom+0xa5

a900fba4 826b1d9c 9d6b6010 7675fb80 a900fbb8 nt!RtlLookupAtomInAtomTable+0x78

a900fbbc 826a8c61 7675fb80 2b829a2a 00000000 win32k!UserFindAtom+0x1d

a900fc00 826a8e8d 00000000 00000000 7675fb80 win32k!_FindWindowEx+0x28

a900fc54 888432ac 00000000 00000000 0012d6c0 win32k!NtUserFindWindowEx+0xeb

WARNING: Stack unwind information not available. Following frames may be wrong.

a900fd34 77d16344 badb0d00 0012d698 00000000 Bhbase+0x32ac

a900fd38 badb0d00 0012d698 00000000 00000000 0x77d16344

a900fd3c 0012d698 00000000 00000000 00000000 0xbadb0d00

a900fd40 00000000 00000000 00000000 00000000 0x12d698

STACK_COMMAND:  kb

FOLLOWUP_IP:

Bhbase+32ac

888432ac ??              ???

SYMBOL_STACK_INDEX:  a

SYMBOL_NAME:  Bhbase+32ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Bhbase

IMAGE_NAME:  Bhbase.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  531e74c3

FAILURE_BUCKET_ID:  0xA_Bhbase+32ac

BUCKET_ID:  0xA_Bhbase+32ac

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0xa_bhbase+32ac

FAILURE_ID_HASH:  {3ce1a5a9-6cb6-8b14-100c-d62f5e128f1f}

Followup: MachineOwner

---------

 

Você está com o Baidu PC Faster (ou Antivírus) instalado e ele está provocando travamentos. Desinstale o mesmo, dê um boot e passe o Adwcleaner e depois delete o arquivo C:\Windows\System32\DRIVERS\bhbase.sys

 

--

 

Loading Dump File [D:\Downloads\Firefox\MD\MD\091414-26644-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

 

 

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 81fa196d, 913d8438, 0}

*** WARNING: Unable to verify timestamp for RTKVHDA.sys

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

*** WARNING: Unable to verify timestamp for Bhbase.sys

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

 

Probably caused by : RTKVHDA.sys ( RTKVHDA+19096d )

Followup: MachineOwner

---------

0: kd> !analyze -v

 

 

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

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)

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.

Some common problems are exception code 0x80000003.  This means a hard

coded breakpoint or assertion was hit, but this system was booted

/NODEBUG.  This is not supposed to happen as developers should never have

hardcoded breakpoints in retail code, but ...

If this happens, make sure a debugger gets connected, and the

system is booted /DEBUG.  This will let us see why this breakpoint is

happening.

Arguments:

Arg1: c0000005, The exception code that was not handled

Arg2: 81fa196d, The address that the exception occurred at

Arg3: 913d8438, Trap Frame

Arg4: 00000000

Debugging Details:

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

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - A instru  o no 0x%08lx fez refer ncia   mem ria no 0x%08lx. A mem ria n o p de ser %s.

FAULTING_IP:

RTKVHDA+19096d

81fa196d ??              ???

TRAP_FRAME:  913d8438 -- (.trap 0xffffffff913d8438)

ErrCode = 00000000

eax=00000000 ebx=871f1008 ecx=00000000 edx=871ee928 esi=871eee50 edi=86b9e3b0

eip=81fa196d esp=913d84ac ebp=913d8504 iopl=0         nv up ei pl zr na pe nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246

RTKVHDA+0x19096d:

81fa196d ??              ???

Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  RtHDVCpl.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from 830c3472 to 830e2dfc

STACK_TEXT:  

913d7fa4 830c3472 0000008e c0000005 81fa196d nt!KeBugCheckEx+0x1e

913d83c8 8304a026 913d83e4 00000000 913d8438 nt!KiDispatchException+0x1ac

913d8430 83049fda 913d8504 81fa196d badb0d00 nt!CommonDispatchException+0x4a

913d8438 81fa196d badb0d00 871ee928 00000000 nt!Kei386EoiHelper+0x192

WARNING: Stack unwind information not available. Following frames may be wrong.

913d8504 81f7ed7b 871eee50 00000002 00000000 RTKVHDA+0x19096d

913d8774 81f7f3e4 8544b3a0 873dc008 8656ba20 RTKVHDA+0x16dd7b

913d899c 955de5a2 8544b3a0 aab94568 88399008 RTKVHDA+0x16e3e4

913d89b4 955de438 88399008 8656ba20 9b693a80 portcls!PcDispatchProperty+0x146

913d89dc 929cf1d2 00000008 aab94568 aab94560 portcls!PropertyItemPropertyHandler+0x2b

913d8a2c 929d8177 88399008 00000014 9b693a80 ks!KspPropertyHandler+0x67c

913d8a50 955de2e5 88399008 00000016 9b693a58 ks!KsPropertyHandler+0x19

913d8a68 955ee784 00399008 00000016 9b693a58 portcls!PcHandlePropertyWithTable+0x49

913d8ab0 955de060 8656ba08 86b98030 88399008 portcls!CPortFilterWaveRT::DeviceIoControl+0xcf

913d8ad0 929ce789 86b980e8 88399008 913d8af8 portcls!DispatchDeviceIoControl+0x5b

913d8ae0 955e4001 86b98030 88399008 88399008 ks!KsDispatchIrp+0xb0

913d8af8 955e4cc8 86b98030 88399008 913d8b24 portcls!KsoDispatchIrp+0x43

913d8b08 81f8d858 86b98030 88399008 8542bf80 portcls!PcDispatchIrp+0x2d

913d8b24 830424ac 86b98030 c0000001 88399008 RTKVHDA+0x17c858

913d8b3c 832443be 8542bf80 88399008 8839909c nt!IofCallDriver+0x63

913d8b5c 832611af 86b98030 8542bf80 00000000 nt!IopSynchronousServiceTail+0x1f8

913d8bf8 8326398a 86b98030 88399008 00000000 nt!IopXxxControlFile+0x6aa

913d8c2c 8889dc74 00000420 00000000 00000000 nt!NtDeviceIoControlFile+0x2a

913d8d34 77726344 badb0d00 0012fa30 00000000 Bhbase+0x1c74

913d8d38 badb0d00 0012fa30 00000000 00000000 0x77726344

913d8d3c 0012fa30 00000000 00000000 00000000 0xbadb0d00

913d8d40 00000000 00000000 00000000 00000000 0x12fa30

STACK_COMMAND:  kb

FOLLOWUP_IP:

RTKVHDA+19096d

81fa196d ??              ???

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RTKVHDA+19096d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RTKVHDA

IMAGE_NAME:  RTKVHDA.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5278d8aa

FAILURE_BUCKET_ID:  0x8E_RTKVHDA+19096d

BUCKET_ID:  0x8E_RTKVHDA+19096d

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x8e_rtkvhda+19096d

FAILURE_ID_HASH:  {6b72f0a4-a169-0d1c-f1da-6716e93a220f}

Followup: MachineOwner

---------

 

Mas antes tente apenas remover o Baidu no passo que passei acima e veja isso corrige, caso não corrija faça esse passo pro driver realtek

 

 

você possui problemas com o comportamento do driver de audio Realtek tente atualizar o driver e veja se corrige.

Se possível passe um AdwCleaner (vai ter que refazer o profile do Firefox porque ele buga o mesmo)

 

 

Até a próxima!

Ok irei fazer os testes daqui 2 dias postarei o resultado.

[Adson Gomes]

Ok irei fazer os testes daqui 2 dias postarei o resultado.

Não funcionou continua travando vou tentar formatar ele pro windows 8.1,mas tem alguma ideia do que possa ser o problema?

[Hqxriven]

você atualizou o realtek e passou o adwcleaner?