none
BSOD RRS feed

  • Вопрос

  • Помогите что вызывает BSOD

    Show DivPrimary Analysis

    Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
    Online Crash Dump Analysis Service
    See http://www.osronline.com for more information
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 9600.18821.amd64fre.winblue_ltsb.170914-0600
    Machine Name:
    Kernel base = 0xfffff803`ec414000 PsLoadedModuleList = 0xfffff803`ec6e6650
    Debug session time: Fri Dec 15 04:26:38.317 2017 (UTC - 5:00)
    System Uptime: 1 days 21:53:30.730
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    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.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff803ec4ab939, The address that the exception occurred at
    Arg3: fffff803ec768a00, Parameter 0 of the exception
    Arg4: 0000000000000000, Parameter 1 of the exception

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

    TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

    FAULTING_IP:
    nt!PpmUpdatePerformanceFeedback+c9
    fffff803`ec4ab939 f0480fba2b00    lock bts qword ptr [rbx],0

    EXCEPTION_PARAMETER1:  fffff803ec768a00

    EXCEPTION_PARAMETER2:  0000000000000000

    ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

    BUGCHECK_STR:  0x1e_c000001d

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from fffff803ec5edb2a to fffff803ec561ba0

    FAILED_INSTRUCTION_ADDRESS:
    nt!PpmUpdatePerformanceFeedback+c9
    fffff803`ec4ab939 f0480fba2b00    lock bts qword ptr [rbx],0

    CONTEXT:  24acb60f000efb08 -- (.cxr 0x24acb60f000efb08)
    Unable to read context, Win32 error 0n30

    STACK_TEXT:  
    fffff803`ed8df6f8 fffff803`ec5edb2a : 00000000`0000001e ffffffff`c000001d fffff803`ec4ab939 fffff803`ec768a00 : nt!KeBugCheckEx
    fffff803`ed8df700 fffff803`ec5690ed : fffff803`ed8dfe70 00000000`00000000 fffff803`ed8e0668 fffff803`ed8df870 : nt!KiFatalExceptionHandler+0x22
    fffff803`ed8df740 fffff803`ec4db69d : 00000000`00000001 fffff803`ec414000 fffff803`ed8e0600 ffffe000`00000000 : nt!RtlpExecuteHandlerForException+0xd
    fffff803`ed8df770 fffff803`ec511b2c : fffff803`ed8e0668 fffff803`ed8e0370 fffff803`ed8e0668 fffff803`ed8e0668 : nt!RtlDispatchException+0x1a5
    fffff803`ed8dfe40 fffff803`ec56d7ce : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe000`19a46000 : nt!KiDispatchException+0x190
    fffff803`ed8e0530 fffff803`ec56b547 : 00000000`00000000 fffff803`ed8e07e0 00000000`00000002 fffff800`16c5d7ac : nt!KiExceptionDispatch+0xce
    fffff803`ed8e0710 fffff803`ec4ab939 : 00000000`00007b2b fffff803`ec7155c0 fffff803`ed8e08f8 fffff803`ec710180 : nt!KiInvalidOpcodeFault+0x107
    fffff803`ed8e08a0 fffff803`ec4aad80 : fffff803`ec710180 fffff803`ed8e0a00 fffff803`ed8e0a20 0000007c`5416d8ea : nt!PpmUpdatePerformanceFeedback+0xc9
    fffff803`ed8e0920 fffff803`ec4aa836 : fffff803`ec710180 fffff803`ed8e0b4c fffff803`ed8e0c10 00000000`00000002 : nt!PpmIdleExecuteTransition+0x390
    fffff803`ed8e0b10 fffff803`ec5656bc : fffff803`ec710180 fffff803`ec710180 fffff803`ec768a00 00000000`00602a53 : nt!PoIdle+0x2f6
    fffff803`ed8e0c60 00000000`00000000 : fffff803`ed8e1000 fffff803`ed8db000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x2c


    FOLLOWUP_IP:
    nt!PpmUpdatePerformanceFeedback+c9
    fffff803`ec4ab939 f0480fba2b00    lock bts qword ptr [rbx],0

    SYMBOL_STACK_INDEX:  7

    SYMBOL_NAME:  nt!PpmUpdatePerformanceFeedback+c9

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  59ba8548

    STACK_COMMAND:  .cxr 0x24acb60f000efb08 ; kb

    FAILURE_BUCKET_ID:  X64_0x1e_c000001d_BAD_IP_nt!PpmUpdatePerformanceFeedback+c9

    BUCKET_ID:  X64_0x1e_c000001d_BAD_IP_nt!PpmUpdatePerformanceFeedback+c9

    Followup: MachineOwner

    Заранее благодарен.

    28 декабря 2017 г. 10:21

Ответы

  • Привет,

    Можете сказать примерно после чего началась проблема?

    Попробуйте обновить все драйвера на сервере, так как я вижу из предоставленного, проблема заключается в одном из драйверов


    Мнения, высказанные здесь, являются отражением моих личных взглядов, а не позиции корпорации Microsoft. Вся информация предоставляется "как есть" без каких-либо гарантий. Не забывайте помечать сообщения как ответы и полезные, если они Вам помогли.

    29 декабря 2017 г. 7:01
    Модератор