ArsenyM
Для ознакомления
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff80002edf066, Address of the instruction which caused the bugcheck
Arg3: fffff8800774bc00, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
Parameter 2 contains the referenced virtual address.
Arg2: 00000000000000c8
Arg3: 0000000000000000
Arg4: 0000000000000000
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: 0000000000000003, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, 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: fffff80002e89142, address which referenced memory
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa80065ff8f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
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: ffffffff8b493a5b, 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: fffff80002e9043e, address which referenced memory
fffff880`0774b4b8 fffff800`02f036cd nt!RtlpExecuteHandlerForException+0xd
fffff880`0774b4c0 fffff880`03297350*** WARNING: Unable to verify timestamp for klif.sys Касперский
*** ERROR: Module load completed but symbols could not be loaded for klif.sys
klif+0x6f350
fffff880`0774b4c8 fffff880`03283f24 klif+0x5bf24
fffff880`0774b4d0 fffff880`03228000 klif
fffff880`0323f000 fffff880`03250000 _572f484b_455f_44b0_9d6a_da3ad2071365_Gw64 (deferred) Вот такое странное имя модуля
Image path: \SystemRoot\system32\drivers\{572f484b-455f-44b0-9d6a-da3ad2071365}Gw64.sys Это имя драйвера
Image name: {572f484b-455f-44b0-9d6a-da3ad2071365}Gw64.sys
Timestamp: Fri Jan 31 03:45:30 2014 (52EAF22A)
CheckSum: 00018C79
ImageSize: 00011000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
В основном все дампы связаны с нарушением памяти, такое часто бывает из-за антивируса. Код 124 указывает на виновность процеесора, но дело в том что одно из ядер находилось длительное время в ожидании, какой-то пользовательский процесс долгое время обрабатывался.
1.
Скачайте программу по удалению антивируса Касперского и удалите его
2.
Обратитесь за оказанием помощи по лечению http://forum.oszone.net/forum-87.html
Gw64.sys Fri Jan 31 03:45:30 2014
Reported to be infectious (adware) Вы можете поискать в поиковике
Жду Ваших результатов
