- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am facing crash in encoder (while calling encoder->Init()) on my following environment:
OS: Windows 10 Enterprise 2016 LTSB, version 1607 (OS build 14393.2906)
Processor: Intel(R) Core(TM) i5-6402P CPU @ 2.80GHz
Graphics Card: Intel HD Graphics 510
Driver: 25.20.100.6323 (dated 18 Nov 2018)
SDK & Smaples: Intel(R) Media SDK 2018 R1 & Media Samples 8.3.26.352
This crash is reproducible through sample_encode exe too by using command:
sample_encode h264 -i input.rgb -w 1280 -h 720 -o out.h264
Crash is occurring when I try to encode a RGB file into h264 using system memory & HW accel. But it works fine if I use:
- HW accel with video memory (d3d or d3d11), or
- SW accel with system memory or video memory (d3d or d3d11).
I tried to upgrade my display driver using Intel Driver and Support Assistant, it shows an update available (dch_igcc_win64_26.20.100.6709) but this driver is not getting installed on system, error says "This installation package is not supported by this processor type".
Further, I did rollback my display driver and it reverted to 20.19.15.4501 and on this version there is no crash in any scenario, all case is working fine.
So it seems issue with only a specific driver version. Can you please suggest what can be done to fix this issue properly. I am afraid that as this driver is not getting updated too, so it may cause my product to crash in some of the customer's environment having same configuration.
- Tags:
- Development Tools
- Graphics
- Intel® Media SDK
- Intel® Media Server Studio
- Media Processing
- Optimization
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ramashankar,
The driver version reminds me other post recently, could you check if it is related?
https://software.intel.com/en-us/forums/intel-media-sdk/topic/804820
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Mark,
Yes it seems same issue, crash in encoder with same driver version (25.20.100.6323) on same OS (Win 10 LTSB 1607).
So as you mentioned there, fix may be available after a month approx?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, I am still trying to confirm it, will keep you updated.
Mark
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page