thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Problem z wifi TP Link
TP-Link używa chipsetu na bazie Atheros'a. Najpierw spróbuj odczytać co to za chipset tam siedzi i wejść na stronę atheros.cz pobierając odpowiedni sterownik. Testowo wyłączyłbym także oprogramowanie AV/IS.
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp8\MINIDUMP\111111-25942-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c56670
Debug session time: Sat Nov 12 00: 32: 41.815 2011 (UTC + 1: 00)
System Uptime: 0 days 0: 01: 29.110
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff80000007f8e, 8, fffff80000007f8e, 0}
Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
Could not read faulting driver name
Probably caused by : athurx.sys ( athurx+9bf7b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80000007f8e, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80000007f8e, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc0100
fffff80000007f8e
FAULTING_IP:
+5fca2faf03b6ddf0
fffff800`00007f8e ? ?
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800819ea30 -- (.trap 0xfffff8800819ea30)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000003700000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000007f8e rsp=fffff8800819ebc0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000f44 r10=fffff80002a11000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
fffff800`00007f8e ? ?
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a399fc to fffff80002a8dc40
STACK_TEXT:
fffff880`0819e8c8 fffff800`02a399fc : 00000000`00000050 fffff800`00007f8e 00000000`00000008 fffff880`0819ea30 : nt!KeBugCheckEx
fffff880`0819e8d0 fffff800`02a8bd6e : 00000000`00000008 fffff800`00007f8e 00000000`00000000 00000000`00000000 : nt! ? : FNODOBFM: `string'+0x4611f
fffff880`0819ea30 fffff800`00007f8e : fffffa80`404f0089 fffff880`05e9ff7b fffffa80`00000000 80000000`00004048 : nt!KiPageFault+0x16e
fffff880`0819ebc0 fffffa80`404f0089 : fffff880`05e9ff7b fffffa80`00000000 80000000`00004048 fffff800`00000000 : 0xfffff800`00007f8e
fffff880`0819ebc8 fffff880`05e9ff7b : fffffa80`00000000 80000000`00004048 fffff800`00000000 00000000`00000000 : 0xfffffa80`404f0089
fffff880`0819ebd0 fffffa80`00000000 : 80000000`00004048 fffff800`00000000 00000000`00000000 00000000`00000000 : athurx+0x9bf7b
fffff880`0819ebd8 80000000`00004048 : fffff800`00000000 00000000`00000000 00000000`00000000 fffffa80`0534b030 : 0xfffffa80`00000000
fffff880`0819ebe0 fffff800`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0534b030 00000000`00000001 : 0x80000000`00004048
fffff880`0819ebe8 00000000`00000000 : 00000000`00000000 fffffa80`0534b030 00000000`00000001 fffffa80`039d4040 : 0xfffff800`00000000
STACK_COMMAND: kb
FOLLOWUP_IP:
athurx+9bf7b
fffff880`05e9ff7b ? ?
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: athurx+9bf7b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athurx
IMAGE_NAME: athurx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b42b0a4
FAILURE_BUCKET_ID: X64_0x50_athurx+9bf7b
BUCKET_ID: X64_0x50_athurx+9bf7b
Followup: MachineOwner
---------
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
(Ten post był ostatnio modyfikowany: 16.11.2011 00:21 przez thermalfake.)
16.11.2011 00:13
|
Post: #7
