Ir ao conteúdo
  • Cadastre-se
sir emo

Tela Azul - AsRock x TP Link 4800 Wifi

Recommended Posts

Amigos, 

 

Estou precisando a ajuda de vocês, vou relatar os fatos bem rapidamente e os procedimentos tomados.

 

Montei um PC de performance para um amigo, optamos por um AMD FX X6 BE, 12 RAM, Fontre 650W 80 plus e GTX550Ti tudo isso numa Placa Mãe AM3+ 970 Pro3 R2.0 a e um cooler Akasa Venom  :cool:

 

beleza, instalei o Windows 7, Pro. (raramente uso o Ultimate) estava tudo certo, instalei os drive da placa mãe, placa de vídeo e deixei atualizando (foram 123 atualizações da MS)

porém quando eu instalei a Placa TP Link 4800 (Wireless 450Mbps) ai começou as "Telas Azuis"  na verdade eu demorei a perceber isso. pois o "Ruwindows" não me mostrava com clareza. Dps de um tempo baixei o programa "Crash ME" la ele me deu esse laudo:

 

System Information (local)
--------------------------------------------------------------------------------
 
computer name: BLADER-PC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
Hardware: ASRock, 970 Pro3 R2.0
CPU: AuthenticAMD AMD FX-6300 Six-Core Processor AMD586, level: 21
6 logical processors, active mask: 63
RAM: 12839538688 total
VM: 2147352576, free: 1962135552
 
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
On Mon 17/03/2014 17:48:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031714-36629-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880) 
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8000308B756, 0xD, 0xFFFFFA8015350B00)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
 
 
 
On Mon 17/03/2014 17:48:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8000308B756, 0xD, 0xFFFFFA8015350B00)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
 
 
 
On Sun 16/03/2014 23:39:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031614-58125-01.dmp
This was probably caused by the following module: athrx.sys (athrx+0x13AA0B) 
Bugcheck code: 0xD1 (0x206, 0xC, 0x8, 0x206)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\athrx.sys
product: Driver for Atheros CB42/CB43/MB42/MB43 Network Adapter
company: Atheros Communications, Inc.
description: Atheros Extensible Wireless LAN device driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.). 
Google query: Atheros Communications, Inc. DRIVER_IRQL_NOT_LESS_OR_EQUAL
 
 
 
On Sun 16/03/2014 23:25:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031614-89700-01.dmp
This was probably caused by the following module: usbhub.sys (usbhub+0x33300) 
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x3811CA, 0x8, 0x3811CA)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\usbhub.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Default Hub Driver for USB
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 
 
 
 
 
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
 
4 crash dumps have been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: 
 
athrx.sys (Atheros Extensible Wireless LAN device driver, Atheros Communications, Inc.)
 
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
 
 
Read the topic general suggestions for troubleshooting system crashes for more information. 
 
Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 
 
 
:confused: 
Pois é, dps de muita pesquisa fiz os seguinte procedimentos:
;)
 
  1. desinstalar o drive e baixar do site global da TP Link
  2. desinstalar o drive, tirar da mini pci, reiniciar e instalar tudo de novo
  3. procurar no Google

:mad: Todas deram em zero!

 

Agora instalei a mesma placa em outro PC, um AMD Phenon X4, blah blah numa MB Foxconn, Windows 7, 32bits. ta funcionando de boa, coloquei no torrent e no youtube 1080.  

 

o que faço?sera que a AsRock tem treta com a TPlink? a mini PCI é safada? ou o Windows ta "bugado" só pra variar.

 

:( Troco por uma PCI? UBS? ou tento a DLink?

 

Sugestões?

 

Até mais!

Sander B)  

 
 

Compartilhar este post


Link para o post
Compartilhar em outros sites

Crie uma conta ou entre para comentar

Você precisar ser um membro para fazer um comentário

Criar uma conta

Crie uma nova conta em nossa comunidade. É fácil!

Crie uma nova conta

Entrar

Já tem uma conta? Faça o login.

Entrar agora





Sobre o Clube do Hardware

No ar desde 1996, o Clube do Hardware é uma das maiores, mais antigas e mais respeitadas publicações sobre tecnologia do Brasil. Leia mais

Direitos autorais

Não permitimos a cópia ou reprodução do conteúdo do nosso site, fórum, newsletters e redes sociais, mesmo citando-se a fonte. Leia mais

×