BSOD - 0x1000007e - athurx.sys
Zdravím,
přicházím se žádostí o pomoc.
Nedávno jsem koupil nové SSD Samsung 850 Evo 250 GB Basic, nainstaloval nový Windows atp. Avšak začaly se mi dít nepříjemnosti v podobě BSOD. Googlil jsem googlil jsem, ale stále nic nepomohlo.
BSOD:
Kód chyby: 0x1000007e
Minidumpy RaR: [odkaz, pro zobrazení se přihlaste] - Heslo: mini
Co jsem zkoušel:
- Memtest - paměti jsou v pořádku
- Stahovat aktualizační a opravné soubory od Microsoftu
- Aktualizovat system
- Aktualizovat ovladače síťového adaptéru
- Reinstalovat ovladač síťového adaptéru
PC komponenty:
viz podpis
Síťový USB adaptér TP-Link TL-WN722N
RAM paměti běží na frekvenci 1333 kvůli procesoru
Budu rád za jakoukoliv další pomoc.. Btw. při psaní tohoto tématu mě to nejdříve 2x "odpojilo" od internetu, přičemž jsem byl stále připojen, podle stavů internet běžel a IP adresy jsem měl všechny přidělené, a pak tedy hodilo další dvě modré smrti.
přicházím se žádostí o pomoc.
Nedávno jsem koupil nové SSD Samsung 850 Evo 250 GB Basic, nainstaloval nový Windows atp. Avšak začaly se mi dít nepříjemnosti v podobě BSOD. Googlil jsem googlil jsem, ale stále nic nepomohlo.
BSOD:
Kód chyby: 0x1000007e
Minidumpy RaR: [odkaz, pro zobrazení se přihlaste] - Heslo: mini
Co jsem zkoušel:
- Memtest - paměti jsou v pořádku
- Stahovat aktualizační a opravné soubory od Microsoftu
- Aktualizovat system
- Aktualizovat ovladače síťového adaptéru
- Reinstalovat ovladač síťového adaptéru
PC komponenty:
viz podpis
Síťový USB adaptér TP-Link TL-WN722N
RAM paměti běží na frekvenci 1333 kvůli procesoru
Budu rád za jakoukoliv další pomoc.. Btw. při psaní tohoto tématu mě to nejdříve 2x "odpojilo" od internetu, přičemž jsem byl stále připojen, podle stavů internet běžel a IP adresy jsem měl všechny přidělené, a pak tedy hodilo další dvě modré smrti.
Dělá to TP-Link TL-WN722N. Věnoval jsem dva dny rozcházení tohohle krámu u známého (na W8.1), vyzkoušel přes deset různých ovladačů a dospěl k závěru, že tento adaptér stabilně s plnou funkčností (byl požadován i režim AP) nelze zprovoznit. Řešením byla výměna za externí AP. Volba konkrétního modelu se odvíjí od požadovaných vlastností.
Analýza posledního minidumpu:
[CODE]
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Downloads\Minidump\122015-25194-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
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
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`03247730
Debug session time: Sun Dec 20 18:34:25.674 2015 (UTC + 1:00)
System Uptime: 0 days 7:37:58.531
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.............
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88006610e26, fffff88003385808, fffff88003385060}
Probably caused by : athurx.sys ( athurx+8e26 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006610e26, The address that the exception occurred at
Arg3: fffff88003385808, Exception Record Address
Arg4: fffff88003385060, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam
FAULTING_IP:
athurx+8e26
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h]
EXCEPTION_RECORD: fffff88003385808 -- (.exr 0xfffff88003385808)
ExceptionAddress: fffff88006610e26 (athurx+0x0000000000008e26)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000002698
Attempt to read from address 0000000000002698
CONTEXT: fffff88003385060 -- (.cxr 0xfffff88003385060;r)
rax=0000000000000000 rbx=fffffa800a06e050 rcx=fffffa800ac37030
rdx=0000000000000003 rsi=fffffa800670cb50 rdi=fffffa800ccff160
rip=fffff88006610e26 rsp=fffff88003385a40 rbp=fffff8000321e280
r8=0000000000000000 r9=0000000000000000 r10=000000000001041b
r11=0000000000000000 r12=fffffa800ccff160 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
athurx+0x8e26:
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800a06e050 rcx=fffffa800ac37030
rdx=0000000000000003 rsi=fffffa800670cb50 rdi=fffffa800ccff160
rip=fffff88006610e26 rsp=fffff88003385a40 rbp=fffff8000321e280
r8=0000000000000000 r9=0000000000000000 r10=000000000001041b
r11=0000000000000000 r12=fffffa800ccff160 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
athurx+0x8e26:
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000002698
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b1100
GetUlongFromAddress: unable to read from fffff800032b11c0
0000000000002698 Nonpaged pool
FOLLOWUP_IP:
athurx+8e26
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h]
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffffa800a06e050 to fffff88006610e26
STACK_TEXT:
fffff880`03385a40 fffffa80`0a06e050 : fffff880`06610dc5 fffff880`06754740 fffff880`067546f0 00000000`000015d7 : athurx+0x8e26
fffff880`03385a48 fffff880`06610dc5 : fffff880`06754740 fffff880`067546f0 00000000`000015d7 00000000`00000003 : 0xfffffa80`0a06e050
fffff880`03385a50 fffff880`06754740 : fffff880`067546f0 00000000`000015d7 00000000`00000003 00000000`00000000 : athurx+0x8dc5
fffff880`03385a58 fffff880`067546f0 : 00000000`000015d7 00000000`00000003 00000000`00000000 00000000`c0000184 : athurx+0x14c740
fffff880`03385a60 00000000`000015d7 : 00000000`00000003 00000000`00000000 00000000`c0000184 00000000`00000000 : athurx+0x14c6f0
fffff880`03385a68 00000000`00000003 : 00000000`00000000 00000000`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
fffff880`03385a70 00000000`00000000 : 00000000`c0000184 00000000`00000000 0000057f`00000000 fffffa80`0ac37af8 : 0x3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: athurx+8e26
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athurx
IMAGE_NAME: athurx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4daeb071
STACK_COMMAND: .cxr 0xfffff88003385060 ; kb
FAILURE_BUCKET_ID: X64_0x7E_athurx+8e26
BUCKET_ID: X64_0x7E_athurx+8e26
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_athurx+8e26
FAILURE_ID_HASH: {ef04386b-f0b2-3efa-b240-ded80b69a26b}
Followup: MachineOwner
---------
[/CODE]
athurx.sys = součást ovladače Atheros, což je čip použitý v onom USB donglu.
Analýza posledního minidumpu:
[CODE]
Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\Downloads\Minidump\122015-25194-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
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
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
Machine Name:
Kernel base = 0xfffff800`03000000 PsLoadedModuleList = 0xfffff800`03247730
Debug session time: Sun Dec 20 18:34:25.674 2015 (UTC + 1:00)
System Uptime: 0 days 7:37:58.531
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.............
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88006610e26, fffff88003385808, fffff88003385060}
Probably caused by : athurx.sys ( athurx+8e26 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88006610e26, The address that the exception occurred at
Arg3: fffff88003385808, Exception Record Address
Arg4: fffff88003385060, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam
FAULTING_IP:
athurx+8e26
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h]
EXCEPTION_RECORD: fffff88003385808 -- (.exr 0xfffff88003385808)
ExceptionAddress: fffff88006610e26 (athurx+0x0000000000008e26)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000002698
Attempt to read from address 0000000000002698
CONTEXT: fffff88003385060 -- (.cxr 0xfffff88003385060;r)
rax=0000000000000000 rbx=fffffa800a06e050 rcx=fffffa800ac37030
rdx=0000000000000003 rsi=fffffa800670cb50 rdi=fffffa800ccff160
rip=fffff88006610e26 rsp=fffff88003385a40 rbp=fffff8000321e280
r8=0000000000000000 r9=0000000000000000 r10=000000000001041b
r11=0000000000000000 r12=fffffa800ccff160 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
athurx+0x8e26:
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
Last set context:
rax=0000000000000000 rbx=fffffa800a06e050 rcx=fffffa800ac37030
rdx=0000000000000003 rsi=fffffa800670cb50 rdi=fffffa800ccff160
rip=fffff88006610e26 rsp=fffff88003385a40 rbp=fffff8000321e280
r8=0000000000000000 r9=0000000000000000 r10=000000000001041b
r11=0000000000000000 r12=fffffa800ccff160 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
athurx+0x8e26:
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h] ds:002b:00000000`00002698=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000002698
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b1100
GetUlongFromAddress: unable to read from fffff800032b11c0
0000000000002698 Nonpaged pool
FOLLOWUP_IP:
athurx+8e26
fffff880`06610e26 488b8098260000 mov rax,qword ptr [rax+2698h]
BUGCHECK_STR: 0x7E
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffffa800a06e050 to fffff88006610e26
STACK_TEXT:
fffff880`03385a40 fffffa80`0a06e050 : fffff880`06610dc5 fffff880`06754740 fffff880`067546f0 00000000`000015d7 : athurx+0x8e26
fffff880`03385a48 fffff880`06610dc5 : fffff880`06754740 fffff880`067546f0 00000000`000015d7 00000000`00000003 : 0xfffffa80`0a06e050
fffff880`03385a50 fffff880`06754740 : fffff880`067546f0 00000000`000015d7 00000000`00000003 00000000`00000000 : athurx+0x8dc5
fffff880`03385a58 fffff880`067546f0 : 00000000`000015d7 00000000`00000003 00000000`00000000 00000000`c0000184 : athurx+0x14c740
fffff880`03385a60 00000000`000015d7 : 00000000`00000003 00000000`00000000 00000000`c0000184 00000000`00000000 : athurx+0x14c6f0
fffff880`03385a68 00000000`00000003 : 00000000`00000000 00000000`c0000184 00000000`00000000 0000057f`00000000 : 0x15d7
fffff880`03385a70 00000000`00000000 : 00000000`c0000184 00000000`00000000 0000057f`00000000 fffffa80`0ac37af8 : 0x3
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: athurx+8e26
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: athurx
IMAGE_NAME: athurx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4daeb071
STACK_COMMAND: .cxr 0xfffff88003385060 ; kb
FAILURE_BUCKET_ID: X64_0x7E_athurx+8e26
BUCKET_ID: X64_0x7E_athurx+8e26
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0x7e_athurx+8e26
FAILURE_ID_HASH: {ef04386b-f0b2-3efa-b240-ded80b69a26b}
Followup: MachineOwner
---------
[/CODE]
athurx.sys = součást ovladače Atheros, což je čip použitý v onom USB donglu.
Podle informací, co jsem shromáždil jsem si myslel, že to dělá ten adaptér. Každopádně z toho plyne jednoduché řešení a to koupit nový adaptér, že? :)
Každopádně zkusím ještě pohledat. Našel jsem teď nějaké dva "prý funkční" drivery, které nejsou officiální od TP-Linku, ale prý by měly vyřešit problém.
Dám pak vědět, jak to dopadlo.
Každopádně zkusím ještě pohledat. Našel jsem teď nějaké dva "prý funkční" drivery, které nejsou officiální od TP-Linku, ale prý by měly vyřešit problém.
Dám pak vědět, jak to dopadlo.
