|
Добрый день. вновь возникла ошибка «-2005270523» судя по описанию это проблема во взаимодействие с directx, но для решения проблемы я пробовал полностью переустановить как игру так и ОС в целом. Проверка и перезаливка клиента тоже не помогает.Удаление папок с шейдерами тоже не помогло. UPD. переустановкой винды вопрос не решился Последняя редакция: kotobuffer. Время: 30 дек. 2017 г., 22:00:55 Last bumped24 янв. 2018 г., 13:55:23 |
Сообщение
Цитировать это сообщение |
|
https://ibb.co/eQVxSG
Последняя редакция: kotobuffer. Время: 30 дек. 2017 г., 10:12:57 |
Сообщение
Цитировать это сообщение |
|
не, ну нормально,ответа нет ни здесь,ни от ТП на почте… худшей работы поддержки я еще не видел… |
Сообщение
Цитировать это сообщение |
так новый год, все пьют еще, отпуск и тд. |
Сообщение Цитировать это сообщение |
|
тем временем ответа от ТП так и нет.. а раньше я думал, что 4game саппорт «так себе».. *я никогда так не ошибался* |
Сообщение
Цитировать это сообщение |
Та же ошибка,такая ерунда началась около недели назад.Ждем и надеямся на патч..ибо хрен знает как фиксить эти «артефакты» Последняя редакция: Gordium666. Время: 11 янв. 2018 г., 15:33:55 |
Сообщение Цитировать это сообщение |
|
нашли решения проблемы? каждые 5 минут сегодня ошибку выдает |
Сообщение
Цитировать это сообщение |
|
как вариант временно играть на 9м.. но глюки все равно есть |
Сообщение
Цитировать это сообщение |
|
Тем временем техподдержка так и не ответила, судя по всему ее тупо нет, или они решают только вопросы из серии «я не могу заплатить вам бабла» проблема на dx11 сохраняется |
Сообщение
Цитировать это сообщение |
|
У меня та же проблема. Это пофиксить только разрабы могут, ошибка в коде игры походу. Скрытый текст
|
Сообщение Цитировать это сообщение |
Пожаловаться на запись форума
В игре Call of Duty: Ghosts у многих происходит зависание игрового процесса и вылет игры с ошибками:
Direct3DDevice::Present failed (DEVICE REMOVED): DXGI_ERROR_DEVICE_HUNG (-2005270523)
Происходит это из-за нехватки напряжения графического процессора GPU, т.к. заводские настройки низкие и видеокарта не справляется с игровыми нагрузками.
Лечится данная проблема с помощью программы MSI AfterBurner 2.3.1 Final.
Инструкция:
1. Открываете программу MSI AfterBurner.
2. Внизу интерфейса нажмите на кнопку дополнительных настроек «Settings».
3. В открывшемся окне поставьте галочки на пунктах:
«Разблокировать управление напряжением»
«Разблокировать мониторинг напряжения»
4. Нажмите «ОК» и перезапустите программу нажав «ДА».
5. В первом окне «Core Voltage (mV)» ползунком увеличьте напряжение на 12 единиц. Пример с видеокартой GeForce GTX 570 — с 1013mV до 1025mV. Можно и больше, но мне хватило. Если будете экспериментировать и прибавлять, то смотрите за температурой видеокарты.
6. Зафиксируйте настройки кнопкой «Apply».
7. Приятной игры без зависаний и вылетов на высоких настройках!
Для безопасности можно конечно опять заблокировать настройки, т.е. в дополнительных настройках «Settings», снять поставленные галки и нажать «ОК», но тогда со временем настройки возвращаются к дефолтным и начинаются опять вылеты. Не знаю почему это происходит, пару раз возвращал их обратно, а потом надоело и перестал их блокировать, играю нормально.
Подобные проблемы у меня были в играх: Far Cry 3, Assassin’s Creed IV: Black Flag, а особенно в Battlefield 3 и Battlefield 4. После данного лечения все нормализовалось, играю без вылетов.
Скачать программу MSI AfterBurner 2.3.1 Final (9Mb) можно по ссылке на источник.
Источник:
Сундук Пирата
The error code is actually -2005270523 (decimal) which is 0x887a0005 in Hexadecimal.
This is an error from the operating system. You can find the full list here
https://docs.microsoft.com/en-us/win…error-codes-10
It decodes to this error.
============================================
DXGI_ERROR_DEVICE_REMOVED
0x887A0005
The GPU device instance has been suspended.
============================================
So the video card has «disappeared». The most common reason for this is that the video card device driver crashed. You might find entries in the Windows Event log recording the crash.
You are also running a version of BurnInTest that is a couple of years old. So you should update to the latest patch release.
Lenovo are aware of this issue with their Laptop. They reported the issue to us a month ago. I don’t know what action they took (if any) to debug and fix it.
Some video card crashes are also related to memory leak issues (low available RAM causes a crash are a long period of heavy load, but the real bug is a memory leak in the driver).
Video card device driver problems like this are also common. If you Google 0x887A0005, you’ll get 1000s of people reporting this error with various software.
-
rujialiu
- Goblin
- Posts: 296
- Joined: Mon May 09, 2016 8:21 am
- x 35
[2.1] RenderingAPIException: Failed to create frame fence
-
Quote
-
login to like this post
Hi!
Our software is working on most of our customers’ computer, but some of them are receiving the RenderingAPIException: Failed to create frame fence. Most of them are Intel integrated graphics cards, which is below our minimum requirement. However, today a customer with GTX940M also failed. His laptop cannot open even the simplest scene we have. Here is the trimmed Ogre.log
Code: Select all
12:00:48: CPU Identifier & Features
12:00:48: -------------------------
12:00:48: * CPU ID: GenuineIntel: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
12:00:48: * Logical cores: 8
12:00:48: * SSE: yes
12:00:48: * SSE2: yes
12:00:48: * SSE3: yes
12:00:48: * MMX: yes
12:00:48: * MMXEXT: yes
12:00:48: * 3DNOW: no
12:00:48: * 3DNOWEXT: no
12:00:48: * CMOV: yes
12:00:48: * TSC: yes
12:00:48: * FPU: yes
12:00:48: * PRO: yes
12:00:48: * HT: no
12:00:48: -------------------------
12:00:48: D3D11 : Subsystem Initialising
12:00:48: ***************************************
12:00:48: *** D3D11 : Subsystem Initialized OK ***
12:00:48: ***************************************
...
12:00:48: RenderSystem capabilities
12:00:48: -------------------------
12:00:48: RenderSystem Name: Direct3D11 Rendering Subsystem
12:00:48: GPU Vendor: nvidia
12:00:48: Device Name: NVIDIA GeForce 940MX_0
12:00:48: Driver Version: 21.21.13.6937
12:00:48: * Fixed function pipeline: no
12:00:48: * Hardware generation of mipmaps: yes
12:00:48: * Texture blending: yes
12:00:48: * Anisotropic texture filtering: yes
12:00:48: * Dot product texture operation: yes
12:00:48: * Cube mapping: yes
12:00:48: * Hardware stencil buffer: yes
12:00:48: - Stencil depth: 8
12:00:48: - Two sided stencil support: yes
12:00:48: - Wrap stencil values: yes
12:00:48: * Hardware vertex / index buffers: yes
12:00:48: * 32-bit index buffers: yes
12:00:48: * Vertex programs: yes
12:00:48: * Number of floating-point constants for vertex programs: 512
12:00:48: * Number of integer constants for vertex programs: 16
12:00:48: * Number of boolean constants for vertex programs: 16
12:00:48: * Fragment programs: yes
12:00:48: * Number of floating-point constants for fragment programs: 512
12:00:48: * Number of integer constants for fragment programs: 16
12:00:48: * Number of boolean constants for fragment programs: 16
12:00:48: * Geometry programs: yes
12:00:48: * Number of floating-point constants for geometry programs: 512
12:00:48: * Number of integer constants for geometry programs: 16
12:00:48: * Number of boolean constants for geometry programs: 16
12:00:48: * Tessellation Hull programs: yes
12:00:48: * Number of floating-point constants for tessellation hull programs: 512
12:00:48: * Number of integer constants for tessellation hull programs: 16
12:00:48: * Number of boolean constants for tessellation hull programs: 16
12:00:48: * Tessellation Domain programs: yes
12:00:48: * Number of floating-point constants for tessellation domain programs: 512
12:00:48: * Number of integer constants for tessellation domain programs: 16
12:00:48: * Number of boolean constants for tessellation domain programs: 16
12:00:48: * Compute programs: yes
12:00:48: * Number of floating-point constants for compute programs: 512
12:00:48: * Number of integer constants for compute programs: 16
12:00:48: * Number of boolean constants for compute programs: 16
12:00:48: * Supported Shader Profiles: cs_4_0 cs_4_1 cs_5_0 ds_5_0 gs_4_0 gs_4_1 gs_5_0 hlsl hs_5_0 ps_4_0 ps_4_0_level_9_1 ps_4_0_level_9_3 ps_4_1 ps_5_0 vs_4_0 vs_4_0_level_9_1 vs_4_0_level_9_3 vs_4_1 vs_5_0
12:00:48: * Texture Compression: yes
12:00:48: - DXT: yes
12:00:48: - VTC: no
12:00:48: - PVRTC: no
12:00:48: - ATC: no
12:00:48: - ETC1: no
12:00:48: - ETC2: no
12:00:48: - BC4/BC5: yes
12:00:48: - BC6H/BC7: yes
12:00:48: - ASTC: no
12:00:48: * Hardware Occlusion Query: yes
12:00:48: * User clip planes: yes
12:00:48: * VET_UBYTE4 vertex element type: yes
12:00:48: * Infinite far plane projection: yes
12:00:48: * Hardware render-to-texture: yes
12:00:48: * Floating point textures: yes
12:00:48: * Non-power-of-two textures: yes
12:00:48: * 1d textures: yes
12:00:48: * Volume textures: yes
12:00:48: * Max Texture resolution (2D) 16384
12:00:48: * Max Texture resolution (3D) 2048
12:00:48: * Max Texture resolution (Cubemaps) 16384
12:00:48: * Multiple Render Targets: 8
12:00:48: - With different bit depths: yes
12:00:48: * Point Sprites: yes
12:00:48: * Extended point parameters: yes
12:00:48: * Max Point Size: 256
12:00:48: * Vertex texture fetch: yes
12:00:48: * Number of world matrices: 0
12:00:48: * Number of texture units: 16
12:00:48: * Stencil buffer depth: 8
12:00:48: * Number of vertex blend matrices: 0
12:00:48: - Max vertex textures: 4
12:00:48: - Vertex textures shared: no
12:00:48: * Render to Vertex Buffer : yes
12:00:48: * Hardware Atomic Counters: no
12:00:48: DefaultWorkQueue('Root') initialising on thread main.
...
12:00:53: OGRE EXCEPTION(3:RenderingAPIException): Failed to create frame fence.
Error code: -2005270523.
hr = 0x887A0005
in D3D11VaoManager::_update at C:ogremyguiOGRERenderSystemsDirect3D11srcVaoOgreD3D11VaoManager.cpp (line 1476)
12:00:53: OGRE EXCEPTION(3:RenderingAPIException): Failed to create frame fence.
Error code: -2005270523.
hr = 0x887A0005
in D3D11VaoManager::_update at C:ogremyguiOGRERenderSystemsDirect3D11srcVaoOgreD3D11VaoManager.cpp (line 1476)
12:00:53: OGRE EXCEPTION(3:RenderingAPIException): Failed to create frame fence.
Error code: -2005270523.
hr = 0x887A0005
in D3D11VaoManager::_update at C:ogremyguiOGRERenderSystemsDirect3D11srcVaoOgreD3D11VaoManager.cpp (line 1476)
Our released software is using Ogre 2.1 in June 2018 (with fake area lights). His GPU has 2048MB RAM (GPU-Z said)
Anyone has some thoughts or similar experience? Thanks!
-
dark_sylinc
- OGRE Team Member
- Posts: 5058
- Joined: Sat Jul 21, 2007 4:55 pm
- Location: Buenos Aires, Argentina
- x 1190
- Contact:
Re: [2.1] RenderingAPIException: Failed to create frame fence
-
Quote
-
login to like this post
Post
by dark_sylinc » Sat Sep 22, 2018 4:40 pm
Hi!
The error code 0x887A0005 is key.
It corresponds to DXGI_ERROR_DEVICE_REMOVED. We could enhance the error reporting to include what GetDeviceRemoved says.
In this case the most likely scenarios are:
- Missing Windows Update updates
- Needs DirectX update
- Needs a driver update (or sometimes… a downgrade). If it has multiple GPUs, make sure the customer upgrades both GPUs’ drivers. According to the internet, driver 21.21.13.6937 is from Feb 4 2017. It probably hasn’t had a driver update since it was bought.
- The system has two GPUs (e.g. Intel integrated + NVIDIA), and the Monitor is only hooked to the Intel card, which can cause trouble with the NV card if no monitor is hooked to it.
- The system is an Optimus laptop. This is the source of lots of problems. Perhaps your app needs to be whitelisted in NVIDIA’s control panel or the app must be run via Right Click -> Run with NVIDIA. Something that may help, export NvOptimusEnablement symbol in your application (I can’t remember if it should be exported in your app, or D3D11’s RenderSystem, or both).
- Third party applications interfering. Apps like MSI Afterburner, Plays.tv and Mumble hook onto D3D11 calls and modify them to «enhance» the experience.
- The monitor cable is loose
- The system is overclocked or overheating.
- The GPU is actually dying. Doubtful.
Hello guys,
Same problem for me, Just replaced my rx 380 with the RX 5700 XT OC…
As eloge2lafuite I did the normal procedure to install the graphic card , used DDU , install new drivers…
When I play at heroes of the storm the game is giving me a black screen, go back to Windows and few seconds after it goes back into the game…
After that I can get a blackscreen again and this time radeonsoftware crash and the game too…
I can’t play with this card.. I tryed the old drivers 19.8.1 8.2,… and it’s the same eachtime.
I tryed to install the old version without radeon software… I worked one day but with a small difference, I got only a small freeze. (The difference between the full crash and the small freeze is that the game recover the «screen».
GFX 16:07:37.528 DirectX call failed with error code -2005270523
GFX 16:07:37.528 PerfNotifier: [Render] [APIErrors] Occurrences [1] Peak [1.000000]
GFX 16:07:37.531 Attempting device reboot
GFX 16:07:42.038 Windows Timeout Detection and Recovery (TDR) detected!
GFX 16:07:43.768 Final device refCount is 0
GFX 16:07:43.768 Adapter «AMD Radeon RX 5700 XT» Vendor 0x4098 Device 0x4098
GFX 16:07:43.768 Adapter «Microsoft Basic Render Driver» Vendor 0x5140 Device 0x5140
GFX 16:07:43.768 Skipped adapter «Microsoft Basic Render Driver» because no outputs
GFX 16:07:43.768 Attempting D3D11 device creation on «AMD Radeon RX 5700 XT»
GFX 16:07:43.795 Device creation success.
GFX 16:07:43.795 Setting up swap chain.
GFX 16:07:43.795 Trying fullscreen
GFX 16:07:43.865 Found matching display mode width: 2560 height: 1440 RRN: 144 RRD: 1
GFX 16:07:43.866 Resizing D3D11 swap chain (2560×1440)
GFX 16:07:44.729 Windows Timeout Detection and Recovery (TDR) detected!
GFX 16:07:44.932 Device reboot successful
GFX 16:07:44.932 Setting up swap chain.
GFX 16:07:44.932 Trying fullscreen
GFX 16:07:44.936 Found matching display mode width: 2560 height: 1440 RRN: 144 RRD: 1
GFX 16:07:44.937 Resizing D3D11 swap chain (2560×1440)
GFX 16:07:48.664 PerfNotifier: [Render] [DeviceReboots] Occurrences [1] Peak [1.000000]
GFX 16:07:48.664 PerfNotifier: [ResourceCache] [Evicted] Occurrences [1] Peak [193.093750]
GFX 16:12:48.675 PerfNotifier: [ResourceCache] [Evicted] Occurrences [31] Peak [193.093750]
In my game logs I have this =>
GFX 21:14:09.292 Adapter «AMD Radeon RX 5700 XT» Vendor 0x4098 Device 0x4098
GFX 21:14:09.292 Adapter «Microsoft Basic Render Driver» Vendor 0x5140 Device 0x5140
GFX 21:14:09.292 Skipped adapter «Microsoft Basic Render Driver» because no outputs
GFX 21:14:09.292 Attempting D3D11 device creation on «AMD Radeon RX 5700 XT»
GFX 21:14:09.302 Device creation success.
GFX 21:14:09.302 Setting up swap chain.
GFX 21:14:09.302 Trying fullscreen
GFX 21:14:12.511 Windows Timeout Detection and Recovery (TDR) detected!
GFX 21:14:14.150 SetFullSceenState failed.
GFX 21:14:14.289 Found matching display mode width: 2560 height: 1440 RRN: 144 RRD: 1
GFX 21:14:14.305 Resizing D3D11 swap chain (2560×1440)
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523
GFX 21:14:14.318 DirectX call failed with error code -2005270523……. at the end.
GFX 21:14:15.114 Windows Timeout Detection and Recovery (TDR) detected!
After that I need to kill the game and the amd driver.
If I want to go in the driver configuration I have a white box….
If I put back my old graphic card it’s working perfectly…
What can we do?