BÄREN-Wiki · öffentliche Vorschau

Windows, Fehlercodes und Gerätewissen

Öffentlich sichtbar sind Fehlerquelle und Grundeinstufung. Vollständige Diagnosen, Hersteller- und Praxishinweise sowie Reparaturroutinen erhalten ausschließlich angemeldete Bären-EDV-Techniker.

Windows, Fehlercodes und Gerätewissen

NTSTATUS 0xC0360001 (STATUS_IPSEC_BAD_SPI): The SPI in the packet does not match a valid IPsec SA.

NTSTATUS 0xC0360002 (STATUS_IPSEC_SA_LIFETIME_EXPIRED): Packet was received on an IPsec SA whose lifetime has expired.

NTSTATUS 0xC0360003 (STATUS_IPSEC_WRONG_SA): Packet was received on an IPsec SA that does not match the packet characteristics.

NTSTATUS 0xC0360004 (STATUS_IPSEC_REPLAY_CHECK_FAILED): Packet sequence number replay check failed.

NTSTATUS 0xC0360005 (STATUS_IPSEC_INVALID_PACKET): IPsec header and/or trailer in the packet is invalid.

NTSTATUS 0xC0360006 (STATUS_IPSEC_INTEGRITY_CHECK_FAILED): IPsec integrity check failed.

NTSTATUS 0xC0360007 (STATUS_IPSEC_CLEAR_TEXT_DROP): IPsec dropped a clear text packet.

NTSTATUS 0xC0360008 (STATUS_IPSEC_AUTH_FIREWALL_DROP): IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.

NTSTATUS 0xC0360009 (STATUS_IPSEC_THROTTLE_DROP): IPsec dropped a packet due to DoS throttling.

NTSTATUS 0xC0368000 (STATUS_IPSEC_DOSP_BLOCK): IPsec DoS Protection matched an explicit block rule.

NTSTATUS 0xC0368001 (STATUS_IPSEC_DOSP_RECEIVED_MULTICAST): IPsec DoS Protection received an IPsec specific multicast packet which is not allowed.

NTSTATUS 0xC0368002 (STATUS_IPSEC_DOSP_INVALID_PACKET): IPsec DoS Protection received an incorrectly formatted packet.

NTSTATUS 0xC0368003 (STATUS_IPSEC_DOSP_STATE_LOOKUP_FAILED): IPsec DoS Protection failed to look up state.

NTSTATUS 0xC0368004 (STATUS_IPSEC_DOSP_MAX_ENTRIES): IPsec DoS Protection failed to create state because the maximum number of entries allowed by policy has been reached.

NTSTATUS 0xC0368005 (STATUS_IPSEC_DOSP_KEYMOD_NOT_ALLOWED): IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.

NTSTATUS 0xC0368006 (STATUS_IPSEC_DOSP_MAX_PER_IP_RATELIMIT_QUEUES): IPsec DoS Protection failed to create a per internal IP rate limit queue because the maximum number of queues allowed by policy has been reached.

NTSTATUS 0xC0370001 (STATUS_VID_DUPLICATE_HANDLER): The handler for the virtualization infrastructure driver is already registered. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370002 (STATUS_VID_TOO_MANY_HANDLERS): The number of registered handlers for the virtualization infrastructure driver exceeded the maximum. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370003 (STATUS_VID_QUEUE_FULL): The message queue for the virtualization infrastructure driver is full and cannot accept new messages. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370004 (STATUS_VID_HANDLER_NOT_PRESENT): No handler exists to handle the message for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370005 (STATUS_VID_INVALID_OBJECT_NAME): The name of the partition or message queue for the virtualization infrastructure driver is invalid. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370006 (STATUS_VID_PARTITION_NAME_TOO_LONG): The partition name of the virtualization infrastructure driver exceeds the maximum.

NTSTATUS 0xC0370007 (STATUS_VID_MESSAGE_QUEUE_NAME_TOO_LONG): The message queue name of the virtualization infrastructure driver exceeds the maximum.

NTSTATUS 0xC0370008 (STATUS_VID_PARTITION_ALREADY_EXISTS): Cannot create the partition for the virtualization infrastructure driver because another partition with the same name already exists.

NTSTATUS 0xC0370009 (STATUS_VID_PARTITION_DOES_NOT_EXIST): The virtualization infrastructure driver has encountered an error. The requested partition does not exist. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC037000A (STATUS_VID_PARTITION_NAME_NOT_FOUND): The virtualization infrastructure driver has encountered an error. Could not find the requested partition. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC037000B (STATUS_VID_MESSAGE_QUEUE_ALREADY_EXISTS): A message queue with the same name already exists for the virtualization infrastructure driver.

NTSTATUS 0xC037000D (STATUS_VID_MB_STILL_REFERENCED): The memory block for the virtualization infrastructure driver is still being used and cannot be destroyed.

NTSTATUS 0xC037000F (STATUS_VID_INVALID_NUMA_SETTINGS): The non-uniform memory access (NUMA) node settings do not match the system NUMA topology. In order to start the virtual machine, you will need to modify the NUMA configuration.

NTSTATUS 0xC0370010 (STATUS_VID_INVALID_NUMA_NODE_INDEX): The non-uniform memory access (NUMA) node index does not match a valid index in the system NUMA topology.

NTSTATUS 0xC0370011 (STATUS_VID_NOTIFICATION_QUEUE_ALREADY_ASSOCIATED): The memory block for the virtualization infrastructure driver is already associated with a message queue.

NTSTATUS 0xC0370012 (STATUS_VID_INVALID_MEMORY_BLOCK_HANDLE): The handle is not a valid memory block handle for the virtualization infrastructure driver.

NTSTATUS 0xC0370013 (STATUS_VID_PAGE_RANGE_OVERFLOW): The request exceeded the memory block page limit for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370014 (STATUS_VID_INVALID_MESSAGE_QUEUE_HANDLE): The handle is not a valid message queue handle for the virtualization infrastructure driver.

NTSTATUS 0xC0370015 (STATUS_VID_INVALID_GPA_RANGE_HANDLE): The handle is not a valid page range handle for the virtualization infrastructure driver.

NTSTATUS 0xC0370016 (STATUS_VID_NO_MEMORY_BLOCK_NOTIFICATION_QUEUE): Cannot install client notifications because no message queue for the virtualization infrastructure driver is associated with the memory block.

NTSTATUS 0xC0370018 (STATUS_VID_INVALID_PPM_HANDLE): The handle is not a valid parent partition mapping handle for the virtualization infrastructure driver.

NTSTATUS 0xC0370019 (STATUS_VID_MBPS_ARE_LOCKED): Notifications cannot be created on the memory block because it is use.

NTSTATUS 0xC037001A (STATUS_VID_MESSAGE_QUEUE_CLOSED): The message queue for the virtualization infrastructure driver has been closed. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC037001B (STATUS_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED): Cannot add a virtual processor to the partition because the maximum has been reached.

NTSTATUS 0xC037001C (STATUS_VID_STOP_PENDING): Cannot stop the virtual processor immediately because of a pending intercept.

NTSTATUS 0xC037001D (STATUS_VID_INVALID_PROCESSOR_STATE): Invalid state for the virtual processor. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC037001E (STATUS_VID_EXCEEDED_KM_CONTEXT_COUNT_LIMIT): The maximum number of kernel mode clients for the virtualization infrastructure driver has been reached. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC037001F (STATUS_VID_KM_INTERFACE_ALREADY_INITIALIZED): This kernel mode interface for the virtualization infrastructure driver has already been initialized. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.

NTSTATUS 0xC0370020 (STATUS_VID_MB_PROPERTY_ALREADY_SET_RESET): Cannot set or reset the memory block property more than once for the virtualization infrastructure driver. Restarting the virtual machine may fix the problem. If the problem persists, try restarting the physical computer.