saha96 Опубликовано 22 ноября, 2016 Автор Опубликовано 22 ноября, 2016 Удалил более ненужную прогу от Cisco, очистил Temp и удалил файл драйвера. Теперь наблюдаем. 1
SQ Опубликовано 23 ноября, 2016 Опубликовано 23 ноября, 2016 Всё-таки продолжаются бсоды Прикрепите ссылку на новый дамп пожалуйста.
saha96 Опубликовано 24 ноября, 2016 Автор Опубликовано 24 ноября, 2016 https://drive.google.com/open?id=0B4bCYSEdP3lLWG1qb0NVR0lyLUU Это уже другое устройство, но тоже упал в синий экран Всё-таки приходится думать на каспера...
SQ Опубликовано 24 ноября, 2016 Опубликовано 24 ноября, 2016 Вот анализ приложенного Вами дампа, тут предположительно какие-то проблемы с видео-памятью: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10E, {a, ffffde8f6651e300, 0, 0} *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 000000000000000a, Invalid use of pinned allocation. Arg2: ffffde8f6651e300 Arg3: 0000000000000000 Arg4: 0000000000000000 Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_EPROCESS *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPCR *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KTHREAD *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 14393.447.amd64fre.rs1_release_inmarket.161102-0100 SYSTEM_MANUFACTURER: LENOVO SYSTEM_PRODUCT_NAME: 80MH SYSTEM_SKU: LENOVO_MT_80MH_BU_idea_FM_Lenovo ideapad 100-14IBY SYSTEM_VERSION: Lenovo ideapad 100-14IBY BIOS_VENDOR: LENOVO BIOS_VERSION: CCCN19WW(V2.05) BIOS_DATE: 01/12/2016 BASEBOARD_MANUFACTURER: LENOVO BASEBOARD_PRODUCT: Lenovo ideapad 1 BASEBOARD_VERSION: No DPK ADDITIONAL_DEBUG_TEXT: You can run '.symfix; .reload' to try to fix the symbol path and load symbols. WRONG_SYMBOLS_TIMESTAMP: 5819bd1f WRONG_SYMBOLS_SIZE: 820000 FAULTING_MODULE: fffff8016401d000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 5819bd1f DUMP_TYPE: 1 BUGCHECK_P1: a BUGCHECK_P2: ffffde8f6651e300 BUGCHECK_P3: 0 BUGCHECK_P4: 0 CPU_COUNT: 2 CPU_MHZ: 877 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 37 CPU_STEPPING: 8 CPU_MICROCODE: 0,0,0,0 (F,M,S,R) SIG: 831'00000000 (cache) 0'00000000 (init) CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: SQ-PC ANALYSIS_SESSION_TIME: 11-24-2016 20:45:56.0674 ANALYSIS_VERSION: 10.0.14321.1024 amd64fre LAST_CONTROL_TRANSFER: from fffff80887cd34ae to fffff80164167510 STACK_TEXT: ffffb580`2ce27878 fffff808`87cd34ae : 00000000`0000010e 00000000`0000000a ffffde8f`6651e300 00000000`00000000 : nt!KeBugCheckEx ffffb580`2ce27880 fffff808`8a983468 : ffffde8f`6651e300 ffffb580`2ce2798c 00000000`01000010 00000000`00000246 : watchdog+0x34ae ffffb580`2ce278c0 fffff808`87403a9e : ffffde8f`627dcc50 ffffde8f`69faee50 ffffb580`2ce27da0 ffffde8f`69faee50 : dxgmms1+0x53468 ffffb580`2ce278f0 fffff808`8738d720 : ffffb580`2ce28ab0 ffffb580`2ce28b28 ffffb580`2ce28ab0 ffffb580`2ce28b28 : dxgkrnl+0x113a9e ffffb580`2ce27c30 fffff808`87389d33 : ffffa482`f31136b0 ffffde8f`627dcc50 ffffde8f`62cae602 ffffde8f`62cae600 : dxgkrnl+0x9d720 ffffb580`2ce27f80 fffff808`873b0580 : ffffde8f`62cae600 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl+0x99d33 ffffb580`2ce28a00 fffff801`64172193 : 000000eb`e4d9a140 ffffde8f`6d9224a0 ffffde8f`00000000 0000026f`395ecb58 : dxgkrnl+0xc0580 ffffb580`2ce28c40 00007ffe`89d54e04 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!setjmpex+0x3a53 000000eb`e4d9a0e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`89d54e04 STACK_COMMAND: kb THREAD_SHA1_HASH_MOD_FUNC: 7e15364e73b1dcf955f4566769ebffdb7947f12b THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 59d47a805e1fc3fa96c5f2f8b1424e7098d7e2b7 THREAD_SHA1_HASH_MOD: 43856989496274c577252394d8dd48f984c0e9d7 FOLLOWUP_IP: dxgmms1+53468 fffff808`8a983468 90 nop FAULT_INSTR_CODE: 89ffe990 SYMBOL_STACK_INDEX: 2 FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: 10.0.14393.351 BUGCHECK_STR: 5819BD1F EXCEPTION_CODE: (NTSTATUS) 0x5819bd1f - <Unable to get error code text> EXCEPTION_CODE_STR: 5819BD1F EXCEPTION_STR: WRONG_SYMBOLS PROCESS_NAME: ntoskrnl.wrong.symbols.exe IMAGE_NAME: ntoskrnl.wrong.symbols.exe MODULE_NAME: nt_wrong_symbols SYMBOL_NAME: nt_wrong_symbols!5819BD1F820000 BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703 DEFAULT_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703 PRIMARY_PROBLEM_CLASS: WRONG_SYMBOLS FAILURE_BUCKET_ID: WRONG_SYMBOLS_X64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_TIMESTAMP_161102-101703_5819BD1F_nt_wrong_symbols!5819BD1F820000 TARGET_TIME: 2016-11-24T13:31:44.000Z OSBUILD: 14393 OSSERVICEPACK: 0 SERVICEPACK_NUMBER: 0 OS_REVISION: 0 SUITE_MASK: 272 PRODUCT_TYPE: 1 OSPLATFORM_TYPE: x64 OSNAME: Windows 10 OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS OS_LOCALE: USER_LCID: 0 OSBUILD_TIMESTAMP: 2016-11-02 12:17:03 BUILDDATESTAMP_STR: 161102-0100 BUILDLAB_STR: rs1_release_inmarket BUILDOSVER_STR: 10.0.14393.447.amd64fre.rs1_release_inmarket.161102-0100 ANALYSIS_SESSION_ELAPSED_TIME: 588a ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:wrong_symbols_x64_14393.447.amd64fre.rs1_release_inmarket.161102-0100_timestamp_161102-101703_5819bd1f_nt_wrong_symbols!5819bd1f820000 FAILURE_ID_HASH: {d82425fb-28f9-fe3c-99c4-cbc6653270b1} Followup: MachineOwner ---------
ska79 Опубликовано 24 ноября, 2016 Опубликовано 24 ноября, 2016 Если знакомы с английским то возможно здесь дан ответ https://social.technet.microsoft.com/Forums/en-US/26f5f26a-3cb6-485d-8ba9-b9dcacf4de72/bsod-please-help-ntoskrnlexe?forum=w7itprogeneral Я пытался перевести через гугл, но ничего не понятно
SQ Опубликовано 24 ноября, 2016 Опубликовано 24 ноября, 2016 Тут больше подходит следующая ссылка https://msdn.microsoft.com/en-us/library/windows/hardware/ff557238%28v=vs.85%29.aspx CauseThis bug check is usually caused by a video driver behaving improperly. ResolutionIf the problem persists, check Windows Update for an updated video driver. Как вариант попробуйте обновить драйвера видеокарты на ноутбук Lenovo. 1 1
Рекомендуемые сообщения
Пожалуйста, войдите, чтобы комментировать
Вы сможете оставить комментарий после входа в
Войти