Tak jsem to zanalyzoval a vyšlo mi toto, takže zato nejpíš může Avast

3: 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: fffff87feefd5020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff800034deeb4, address which referenced memory

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


READ_ADDRESS: fffff87feefd5020

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiCommitThreadWait+34
fffff800`034deeb4 65488b3c2520000000 mov rdi,qword ptr gs:[20h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: AvastSvc.exe