Arma 3 unable to init dxgi ошибка - Решение и исправление самых разных ошибок на TopOshibok.ru

if any of you are wondering its not a hardware issue or anything wrong with your computer. unless tens of thousands of computers across the planet are having the same horrible hardware problem at the same exact time.

this bug really makes me regret my purchase of arma 3 and i want to stress that in the harshest possible terms.

its been years now and its still in the game. every time i ask for help even if i post a full log with every detail imaginable i get ignored along with pretty much everyone else who posts about it.

it makes the game totally unplayable and beyond that it can cause your video driver to crash and never recover. then you have to restart your computer by holding the power button down. hope you werent working on anything important.

this doesnt happen in any other game ive ever played in literally my entire life on the planet earth. so its safe to say that arma 3 is the cause of it and not some dust mite sitting on circuitboard.

like someone else in this topic said: they have the time to cook up DLC that people dont even want to buy, but they dont have the time to fix the incredible number of game-breaking bugs already in the game.

at this point i’ve completely given up all hope that they will ever fix it or even acknowledge that it exists. might as well go back to playing operation arrowhead.

maybe in arma 4 they will fix it?

Источник

A screenshot of an Unusual process exit message

1.42

An “Unusual process exit” message is displayed by Arma 3 Launcher whenever it detects that the game was not closed correctly. That may mean that the Operating System (OS) was unable to start the game or that the game has crashed.

The exit code in the message is a number provided by the OS and it may be ambiguous. However, it still may provide a clue about what the issue is and how to solve it.

ⓘ

If you need to, you can copy the message by pressing Ctrl + C while it is displayed, and then paste it to the Feedback Tracker or another channel by pressing Ctrl + V.

Common exit codes

Here’s a short list of common exit codes:

0xC0000022 — STATUS_ACCESS_DENIED

This code means the OS doesn’t have access to some files required to run the game.
Possible solution:

Run the game or Steam as administrator.

0xC0000135 — STATUS_DLL_NOT_FOUND

The OS is unable to load a file that is required to run the game. A missing DLL may belong to the game, the OS or one of the required components (DirectX e.g.).
Possible solutions:

Verify the integrity of the game cache using Steam.
Re-install DirectX.
Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).
Run the Windows System File Check tool to repair corrupted system files.
To identify the precise DLL that is causing an issue.
- Download a 64-bit version of the Microsoft Dependency Walker and open arma3_x64.exe with it. The libraries with a red icon are the corrupted ones.
- Download a 32-bit version of the Microsoft Dependency Walker and open arma3.exe with it. The libraries with a red icon are the corrupted ones.

0x00000035 — ERROR_BAD_NETPATH

One of the possible reasons for this message is running Steam as an administrator and starting Launcher as a regular user. If this situation occurs, Launcher may display a «Updates unavailable — Steam is not running» message in its status.

Possible solutions:

Run the game from Steam client by clicking on the Play button (not from a shortcut nor directly from an executable).
Exit Steam and run as a regular user (instead of running it as an administrator).
Run the game or the Launcher from a shortcut or from an executable as an administrator.
Restart Steam.
Restart the computer.

0x406D1388 — MS_VC_EXCEPTION

This error may be caused by a registry override (a hack) that forces Arma 3 to utilize Large-Page memory. This type of hack was previously used by Fred41’s custom allocator, but it may cause issues on some computers.
Possible solution:
In the Windows registry, locate the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\arma3.exe and check the value of attribute UseLargePages. If the value is 1 then set it to 0 or remove it entirely.

0xC0000005 — ACCESS_VIOLATION

Can also be STATUS_ACCESS_VIOLATION.

This error is very generic. It may be caused by many issues, such as a hardware malfunction, a virus in the computer, but also an error in the game itself.
Possible solutions:

Try changing the Memory Allocator you are using (default: «tbb4malloc_bi» — try «system» on Windows 7 and later)
Try joining another server, then rejoin the previous one.
Update the graphics card drivers to a newer version.
Rollback the graphics card drivers to an older version.
Check the temperature of your GPUs and CPUs.
Verify the integrity of the game cache using Steam.
Re-install DirectX.
Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).
Run a Windows System File Check tool to repair corrupted system files.

0x00000001 – UNABLE_TO_INIT_DXGI

The game is unable to initialize a graphical subsystem. One of possible reasons is ALT TABbing while the game is launching.
Possible solutions:

Update the graphics card drivers to a newer version.
Rollback the graphics card drivers to an older version.
Check the temperature of your GPUs and CPUs.
Disable the Steam Overlay.

0xC000007B — STATUS_INVALID_IMAGE_FORMAT

These errors are usually raised when some DLLs are corrupted or missing or when they are replaced with an incompatible version. It may also happen that you placed a DLL file in the game folder that is loaded instead of the genuine one.
Possible solutions:

Verify the integrity of the game cache using Steam.
Re-install DirectX.
Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).
Run the Windows System File Check tool to repair corrupted system files.
If you are using post-processing tools like Reshade or SweetFX or utilities like RadeonPro remove them.
Re-install the game; remove all files from the game installation folder and then verify the integrity of the game cache using Steam.
To identify the precise DLL that is causing an issue.
- Download a 64-bit version of the Microsoft Dependency Walker and open arma3_x64.exe with it. The libraries with a red icon are the corrupted ones.
- Download a 32-bit version of the Microsoft Dependency Walker and open arma3.exe with it. The libraries with a red icon are the corrupted ones.

0xC0000139 — STATUS_ENTRYPOINT_NOT_FOUND

See #0xC000007B — STATUS_INVALID_IMAGE_FORMAT

0xC000007A — STATUS_PROCEDURE_NOT_FOUND

See #0xC000007B — STATUS_INVALID_IMAGE_FORMAT

0xC000012F — STATUS_INVALID_IMAGE_NOT_MZ

These errors are raised when the EXE or DLLs, either in the game folder or in the system folders, are corrupted.
Possible solutions:

Verify the integrity of the game cache using Steam.
Re-install DirectX.
Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).
Run the Windows System File Check tool to repair corrupted system files.
To identify the precise DLL that is causing an issue.
- Download a 64-bit version of the Microsoft Dependency Walker and open arma3_x64.exe with it. The libraries with a red icon are the corrupted ones.
- Download a 32-bit version of the Microsoft Dependency Walker and open arma3.exe with it. The libraries with a red icon are the corrupted ones.

0xCFFFFFFF — APPLICATION_HUNG

The application became unresponsive and was terminated by the OS.

0xC000009A — STATUS_INSUFFICIENT_RESOURCES

This error may occur when you have an obsolete version of the BattlEye anti-cheat software or after an upgrade to Windows 10.

Possible solution:

Read a section dedicated to this error on BattlEye FAQ page.
Update the BattlEye anti-cheat software or contact BattlEye support.
If you encountered this problem after the upgrade to Windows 10, some system or shared files might get lost in the upgrade.
- Re-install DirectX.
- Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).

0xC06D007E — ERROR_MOD_NOT_FOUND

The specified module could not be found in loaded dynamic library. The reason that the DLL could not be loaded is most often that it needs to load other DLL’s it depends on to do its work. (note: this has nothing to do with game mods, MOD in this case means module).

Possible solutions:

Upgrade your Intel Graphics Driver: https://downloadcenter.intel.com/ or NVidia Drivers (an issue in the older versions the driver was identified as a root cause for this error in Arma 3 1.68).
Verify the integrity of the game cache using Steam.
Re-install DirectX.
Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again using this version (do not use the Repair function).
Run the Windows System File Check tool to repair corrupted system files.
Dependency Walker might give an insight, but unfortunately this issue mostly happens for libraries that are loaded dynamically, so they are not visible in Dependency Walker.

0xC000041D — STATUS_FATAL_USER_CALLBACK_EXCEPTION

There is a multiple reasons for this error:

3rd party programs interfering with the game and failing, crashing the game in the process.
See #0xC06D007E — ERROR_MOD_NOT_FOUND.

Possible solutions:

Close all unnecessary applications.
Un-install 3rd party applications that could interfere with the game (performance boosters, streaming apps, FPS indicators, overlays, graphics enhancers) or disable them.

Report the error to the Feedback Tracker

If you encounter an error that you cannot solve by yourself, please report it to our Feedback Tracker, or contact our support team. Together with the error code, please attach an error report. See this guide for more information on how to do so.

Источник

Во время использования компьютера пользователь может столкнуться с ошибкой с кодом 0x00000001, связанной с dxgi (DirectX Graphics Infrastructure). Эта ошибка может возникать в различных ситуациях, например, при запуске игр или приложений, использующих графические возможности компьютера. В данной статье мы рассмотрим несколько возможных решений этой проблемы.

Перезагрузка компьютера

Первым шагом в решении проблемы с ошибкой 0x00000001 может быть перезагрузка компьютера. Это может помочь в случае, если ошибка возникла в результате временной неисправности компьютера или приложения.

Обновление драйверов видеокарты

Если перезагрузка не помогла, следующим шагом может быть обновление драйверов видеокарты. Для этого можно использовать программу управления драйверами, которая обычно входит в комплект поставки видеокарты. Если у вас нет такой программы, вы можете скачать последнюю версию драйверов с официального сайта производителя вашей видеокарты.

Обновление DirectX

Если проблема не решилась после обновления драйверов, следующим шагом может быть обновление DirectX. Для этого можно воспользоваться официальным сайтом Microsoft и загрузить последнюю версию DirectX для вашей операционной системы.

Отключение антивирусного программного обеспечения

Иногда антивирусное программное обеспечение может приводить к ошибке 0x00000001. Для решения этой проблемы можно попробовать отключить антивирусное ПО или добавить приложение, вызывающее ошибку, в список исключений антивируса.

Изменение настроек компьютера

Некоторые пользователи сообщают, что ошибка 0x00000001 исчезает после изменения настроек компьютера. Например, вы можете попробовать отключить функцию глубокого сна, использовать один монитор вместо двух или изменить настройки разрешения экрана.

Переустановка приложения

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

Вывод

Ошибка 0x00000001 может быть вызвана различными причинами, но с помощью описанных выше методов вы сможете ее исправить. Если ни один из методов не помог, рекомендуется обратиться за помощью к профессионалам.

Источник

dxdiag would be nice as well to see if directX is corrupted or missing (even though I’m pretty sure its probably not, good to have anyways).

(in the start menu search bar type dxdiag then that’ll bring up the utility you can use to dump a log to the desktop (click Save All Information), then share it here.)

Im having the same issue, but only when trying to load any saves. heres my DxDiag for reference:

——————

System Information

——————

Time of this report: 3/3/2016, 23:54:15

Machine name: GRASSY-PC

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.160121-1718)

Language: English (Regional Setting: English)

System Manufacturer: MSI

System Model: MS-7918

BIOS: BIOS Date: 12/24/14 10:46:49 Ver: V2.6B0

Processor: Intel® Core i5-4460 CPU @ 3.20GHz (4 CPUs), ~3.2GHz

Memory: 8192MB RAM

Available OS Memory: 8144MB RAM

Page File: 3450MB used, 12835MB available

Windows Dir: C:Windows

DirectX Version: DirectX 11

DX Setup Parameters: Not found

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 64bit Unicode

————

DxDiag Notes

————

Display Tab 1: No problems found.

Display Tab 2: No problems found.

Display Tab 3: No problems found.

Display Tab 4: No problems found.

Sound Tab 1: No problems found.

Sound Tab 2: No problems found.

Sound Tab 3: No problems found.

Sound Tab 4: No problems found.

Input Tab: No problems found.

———————

DirectX Debug Levels

———————

Direct3D: 0/4 (retail)

DirectDraw: 0/4 (retail)

DirectInput: 0/5 (retail)

DirectMusic: 0/5 (retail)

DirectPlay: 0/9 (retail)

DirectSound: 0/5 (retail)

DirectShow: 0/6 (retail)

—————

Display Devices

—————

Card name: NVIDIA GeForce GTX 970

Manufacturer: NVIDIA

Chip type: GeForce GTX 970

DAC type: Integrated RAMDAC

Device Key: EnumPCIVEN_10DE&DEV_13C2&SUBSYS_39753842&REV_A1

Display Memory: 3727 MB

Dedicated Memory: 4007 MB

Shared Memory: 3815 MB

Current Mode: 1440 x 900 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: W1952

Monitor Id: GSM4B78

Native Mode: 1440 x 900(p) (59.887Hz)

Output Type: DVI

Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um

Driver File Version: 10.18.0013.6200 (English)

Driver Version: 10.18.13.6200

DDI Version: 11

Driver Model: WDDM 1.1

Driver Attributes: Final Retail

Driver Date/Size: 2/23/2016 17:58:18, 16995384 bytes

WHQL Logo’d: Yes

WHQL Date Stamp:

Device Identifier: {D7B71E3E-5082-11CF-CA43-78191CC2C735}

Vendor ID: 0x10DE

Device ID: 0x13C2

SubSys ID: 0x39753842

Revision ID: 0x00A1

Driver Strong Name: oem12.inf:NVIDIA_Devices.NTamd64.6.1:Section032:10.18.13.6200:pciven_10de&dev_13c2

Rank Of Driver: 00E62001

Video Accel:

Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=

D3D9 Overlay: Supported

DXVA-HD: Supported

DDraw Status: Enabled

D3D Status: Enabled

AGP Status: Enabled

Card name: NVIDIA GeForce GTX 970

Manufacturer: NVIDIA

Chip type: GeForce GTX 970

DAC type: Integrated RAMDAC

Device Key: EnumPCIVEN_10DE&DEV_13C2&SUBSYS_39753842&REV_A1

Display Memory: 3727 MB

Dedicated Memory: 4007 MB

Shared Memory: 3815 MB

Current Mode: 1920 x 1080 (32 bit) (60Hz)

Monitor Name: Generic PnP Monitor

Monitor Model: ELEFW328

Monitor Id: ELE0000

Native Mode: 1360 x 768(p) (60.015Hz)

Output Type: HDMI