[skrnn]

Yankee

Для ознакомления.

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

PROCESS_NAME: networx.exe В трех дампах, как указано, причина в драйвере networx.exe


0: kd> .trap fffff801`76cc0e70
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801751d920f rsp=ffffd00023bbeeb0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KiInterruptDispatchLBControl+0x11f:
fffff801`751d920f 488b642410 mov rsp,qword ptr [rsp+10h] ss:ffffd000`23bbeec0=???????????????? По этому адресу в памяти нет данных



BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 000000000000000d,
Arg2: ffffd00024d202b0
Arg3: 0000000047d2388a
Arg4: d3c23dbadd259d7e

PROCESS_NAME: AvastSvc.exe Здесь уже указан виновником антивирус

fffff8006d8e0c60: Unable to get special pool info
fffff8006d8e0c60: Unable to get special pool info
Pool page ffffd00024d202b0 region is unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
Unknown
*ffffd00024d20000 size: 610 previous size: 0 (Free ) *.... Process: 30015e083660
Owning component : Unknown (update pooltag.txt)

ffffd00024d20610 doesn't look like a valid small pool allocation, checking to see
if the entire page is actually part of a large page allocation...

GetUlongFromAddress: unable to read from fffff8006d8d3c78
ffffd00024d20610 is not a valid small pool allocation, checking large pool...
unable to get pool big page table - either wrong symbols or pool tagging is disabled
ffffd00024d20610 is freed (or corrupt) pool
Bad allocation size @ffffd00024d20610, zero is invalid

***
*** An error (or corruption) in the pool was detected;
*** Pool Region unknown (0xFFFFD00024D20610)
***
*** Use !poolval ffffd00024d20000 for more details.
***

Pool page ffffd00024d202b0 region is Unknown

Validating Pool headers for pool page: ffffd00024d202b0

Pool page [ ffffd00024d20000 ] is __inVALID.

Analyzing linked list...
[ ffffd00024d20000 --> ffffd00024d20420 (size = 0x420 bytes)]: Corrupt region

Scanning for single bit errors...
None found



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: fffff800da2f236a, The address that the exception occurred at
Arg3: ffffd0018512d618, Exception Record Address
Arg4: ffffd0018512ce20, Context Record Address

IMAGE_NAME: athwbx.sys А тут Qualcomm Atheros AR9485WB-EG Wireless Network Adapter

FAULTING_IP:
athwbx+20036a
fffff800`da2f236a 488b08 mov rcx,qword ptr [rax]

EXCEPTION_RECORD: ffffd0018512d618 -- (.exr 0xffffd0018512d618)
ExceptionAddress: fffff800da2f236a (athwbx+0x000000000020036a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

CONTEXT: ffffd0018512ce20 -- (.cxr 0xffffd0018512ce20)
rax=0000000000000000 rbx=ffffe000ef6e5cf0 rcx=0000000000000000
rdx=0000000000000000 rsi=ffffe000efe96050 rdi=fffff800d5d4e05c
rip=fffff800da2f236a rsp=ffffd0018512d850 rbp=0000000000000000
r8=fffff800da4834e0 r9=00000000000007ff r10=fffff8004dce6be0
r11=ffffe000ede03a20 r12=fffff8004dca3300 r13=0000000000000002
r14=ffffe000ef6e5cf0 r15=fffff8004dca3200
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
athwbx+0x20036a:
fffff800`da2f236a 488b08 mov rcx,qword ptr [rax] ds:002b:00000000`00000000=???????????????? Снова нарушены страницы памяти
Resetting default scope

1. Скачайте специальную программу для удаления антивируса Avast Ваша система имеет нормальную защиту и может обойтись без стороннего антивируса.
2. Попробуйте обновить драйверы TOSHIBA. Они явно устарели, хотя и не замечены виновниками появления BSOD.

Жду Ваших результатов.