Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by Bersaglio

  1. Да, я только после установки заметил, что есть более новая версия. Уже переустановил, буду наблюдать дальше. Спасибо. Drru Я так понимаю, что эта утилита включит в отчёт кучу личных данных с моего компьютера, поэтому данную информацию в открытую публиковать не стоит? В случае повторения проблемы с новой версией, я сделаю такой отчёт. Не подскажете, куда его надо будет отправить? Спасибо. P.S. Уже сам нашёл. Видимо, сюда: https://my.kaspersky.com/ru
  2. Есть ли какой-нибудь способ избавиться от этих бесконечных BSOD`ов? Пару дней назад поставил триальную версию KAV 2016 (, лечу в BSOD уже пятый раз. До это стоял Microsoft Security Essentials 4.4 - никаких BSOD`ов не было никогда... Нужна помощь! Вот логи последнего BSOD: Microsoft ® Windows Debugger Version 6.11.0001.404 X86 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [D:\TEMP\Dump\Mini052616-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp3_qfe.160331-0610 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Thu May 26 23:00:07.936 2016 (GMT+3) System Uptime: 0 days 4:10:19.552 Loading Kernel Symbols ............................................................... ................................................................ ................... Loading User Symbols Loading unloaded module list .......................... Unable to load image kltdf.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for kltdf.sys *** ERROR: Module load completed but symbols could not be loaded for kltdf.sys ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {d, 0, 0, 0} *** WARNING: Unable to verify timestamp for klif.sys *** ERROR: Module load completed but symbols could not be loaded for klif.sys *** WARNING: Unable to verify timestamp for klhk.sys *** ERROR: Module load completed but symbols could not be loaded for klhk.sys Probably caused by : kltdf.sys ( kltdf+4c62 ) Followup: MachineOwner --------- 4: kd> kd: Reading initial command '!analyze -v; q' ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: System LAST_CONTROL_TRANSFER: from b40864b0 to b4086c62 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. b8537aec b40864b0 86edbb10 008f3ba0 86edbb98 kltdf+0x4c62 b8537b04 b408640a 86edbb10 c0000241 865dd450 kltdf+0x44b0 b8537b28 b408abda 86edbb10 c0000241 86de7b20 kltdf+0x440a b8537b44 b4088d3a 88ba0500 865dd450 88baf830 kltdf+0x8bda b8537b58 804ef1f9 88ba0500 865dd450 865dd450 kltdf+0x6d3a b8537b68 8058398b 86de7b08 000000a8 8acfa900 nt!IopfCallDriver+0x31 b8537b98 805bca82 8ad1f660 88ba0500 0012019f nt!IopCloseFile+0x26b b8537bcc 805bc3ab 8ad1f660 00000001 8acfa900 nt!ObpDecrementHandleCount+0xd8 b8537bf4 805bc449 e1000ea8 86de7b20 0000329c nt!ObpCloseHandleTableEntry+0x14d b8537c3c 805bc581 0000329c 00000000 00000000 nt!ObpCloseHandle+0x87 b8537c50 b42dcfaf 8000329c b8537cb8 00000000 nt!NtClose+0x1d b8537c64 b430f40a 8000329c 88c33ce0 88c33d08 klif+0x8ffaf b8537c78 b4310474 b42dcf88 b8537cb4 00000004 klhk+0x140a b8537c94 b430f3cf 88c33ce0 b8537cb4 b8537ca8 klhk+0x2474 b8537cac 805417e8 8000329c b8537d3c 804fff8d klhk+0x13cf b8537cac 804fff8d 8000329c b8537d3c 804fff8d nt!KiSystemServicePostCall b8537d28 b403bbff 8000329c 86fc46a8 b4038cb6 nt!ZwClose+0x11 b8537d3c b403bbbc 86fc46a8 b403a7a8 b8537d68 afd!AfdFreeConnectionResources+0x28 b8537d4c b403886a 86fc4720 88b1e528 88b224e0 afd!AfdFreeConnection+0x5c b8537d68 80576af3 88b224e0 00000000 8056485c afd!AfdDoWork+0x51 b8537d7c 80538923 88b1e528 00000000 8ad1c620 nt!IopProcessWorkItem+0x13 b8537dac 805cffee 88b1e528 00000000 00000000 nt!ExpWorkerThread+0xef b8537ddc 8054620e 80538834 00000001 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: kltdf+4c62 b4086c62 cd29 int 29h SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: kltdf+4c62 FOLLOWUP_NAME: MachineOwner MODULE_NAME: kltdf IMAGE_NAME: kltdf.sys DEBUG_FLR_IMAGE_TIMESTAMP: 556da696 FAILURE_BUCKET_ID: 0x7f_d_kltdf+4c62 BUCKET_ID: 0x7f_d_kltdf+4c62 Followup: MachineOwner --------- quit:
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.