Hello.
I'm facing an issue of stopping after finishing audio and crashing my audio player: an application connects Windows Media Player to play mp3 and wav audio file.
I guess that the issue is caused by an error occuring Windows Media Player under a specific environment because of my crash dumps and founding similar issue report on web, but it may have some mistakes.
Does anyone know something below about the issue or similar issue.
I've installed the audio player to some computers, but it doesn't occur on a specific computer with `OS: Windows 10 IoT Enterprise LTSC`, but it occurs 1 ~ 2 times per almost 1 month on other computers.
According to the audio player log files, I seem application stopping after completing the ALL tasks including playing audio and server-client communication 2 times.
[Program Flowchart on the issue](https://i.sstatic.net/oTXaeGOA.png)
On Application Crash Report, `Exception Code: 0xc0000409` indicates `stack buffer overrun`, but it may not to indicate it.
[STATUS_STACK_BUFFER_OVERRUN doesn’t mean that there was a stack buffer overrun](https://devblogs.microsoft.com/oldnewthing/20190108-00/?p=100655)
I found that the same error code reported on Web below.
[Windows Media player Crashing](https://pchelpforum.net/t/windows-media-player-crashing.76024/)
On Crash Dump of this issue, I found **calling wmp.dll MANY TIMES**, so I guess that it is caused by `stack buffer overrun`.
For other reasons, we have not updated the Windows version and use deprecated library: WMPLib.dll.
If you mean that the Windows version is relevant, please point this out.
MediaPlayer class on WMPLib uses COM and RPC connection, so the Crash Dump indicates that the issue is occured at collaboration between COM and Windows Media Player.
According to the report on web, `wmplayer.exe` has occured similar error on `Windows 10 Home`.
I guess that it occurs by using a program **using Windows Media Player with `MediaPlayer` class on `WMPLib` on `Windows 10 Pro` or `Home`**.
I'm facing an issue of stopping after finishing audio and crashing my audio player: an application connects Windows Media Player to play mp3 and wav audio file.
I guess that the issue is caused by an error occuring Windows Media Player under a specific environment because of my crash dumps and founding similar issue report on web, but it may have some mistakes.
Does anyone know something below about the issue or similar issue.
- Ever seen similar issue
- Cause details on this or similar issue
Details of Issue
The audio player is scheduled to play audio after launching per almost 15 seconds as child process by other application. 2 or above audio players do not work on a same time.I've installed the audio player to some computers, but it doesn't occur on a specific computer with `OS: Windows 10 IoT Enterprise LTSC`, but it occurs 1 ~ 2 times per almost 1 month on other computers.
According to the audio player log files, I seem application stopping after completing the ALL tasks including playing audio and server-client communication 2 times.
[Program Flowchart on the issue](https://i.sstatic.net/oTXaeGOA.png)
On Application Crash Report, `Exception Code: 0xc0000409` indicates `stack buffer overrun`, but it may not to indicate it.
[STATUS_STACK_BUFFER_OVERRUN doesn’t mean that there was a stack buffer overrun](https://devblogs.microsoft.com/oldnewthing/20190108-00/?p=100655)
I found that the same error code reported on Web below.
[Windows Media player Crashing](https://pchelpforum.net/t/windows-media-player-crashing.76024/)
On Crash Dump of this issue, I found **calling wmp.dll MANY TIMES**, so I guess that it is caused by `stack buffer overrun`.
Environment
| OS | Windows 10 Pro |
| Windows 10 ProProcessor | Intel® Core™ i5-11500 @2.7Ghz-4.6GHz |
| RAM | 16GB |
| System | 64bit Operating System, x64 base processor |
| Windows Version | 21H2 19044.1706 |
| Library | WMPLib.dll |
If you mean that the Windows version is relevant, please point this out.
Application Crash Report
| Fault Module Name | ucrtbase.dll |
| Fault Module Version | 10.0.19041.789 |
| Fault Module Timestamp | 0x82dc99a2 |
| Exception Code | 0xc0000409 |
| Exception Offset | 0x0009eddb |
Crash Dump
05d1e624 770ae77d 770ae760 7708189f 93d3a3dc ucrtbase!abort+0x4b
05d1e664 7708189f 93d3a3dc 00920dc8 6ee6e940 ucrtbase!_purecall+0x1d
05d1e664 6ef7969d 00920dc8 00920dcc 00000004 ucrtbase!__crt_state_management::wrapped_invoke<int (__cdecl*)(void),int>+0x9f
WARNING: Stack unwind information not available. Following frames may be wrong.
05d1e678 6ed50bd5 00920dcc 00000000 00000113 wmp!Ordinal3002+0x5f0ed
05d1e690 6ed5097d 00000004 05d1e6c8 771b0fcb wmp+0x140bd5
05d1e69c 771b0fcb 69aa03d8 00000113 00000004 wmp+0x14097d
05d1e6c8 771a3c02 6ed50970 69aa03d8 00000113 user32!_InternalCallWinProc+0x2b
05d1e794 771a5db3 6ed50970 00000000 00000113 user32!UserCallWinProc+0x143
05d1e800 771a5ac0 ae310000 05d1e850 6eda8f83 user32!DispatchMessageWorker+0x2e3
05d1e80c 6eda8f83 05d1e824 6f3deec8 05def858 user32!DispatchMessageW+0x10
05d1e850 6eda8cc5 6eda8cb0 05d1e878 6eda89aa wmp+0x198f83
...(SO MANY calling wmp about 20 TIMES!!!)
05d1ec74 75f31bf5 05d56930 05d1ecf0 05d1ed0c wmp+0x1f5f90
05d1ec98 75e92901 3a9385ec 05d1ecf0 05d1ed0c combase!<lambda_59f7b8acab183cdd0bcc7c9cde5da55a>:perator()+0xab
05d1ecd4 75e928d3 05d9fca8 05d9fca8 05d56930 combase!ObjectMethodExceptionHandlingAction<<lambda_59f7b8acab183cdd0bcc7c9cde5da55a> >+0x1b
05d1ed34 75f31748 00000001 00000040 008868a0 combase!CStdIdentity::ReleaseCtrlUnk+0x77
05d1ed78 75eee40a 00000001 05d1ee00 00000000 combase!CStdMarshal:
05d1edac 75eec7c1 00000001 05d1eee4 05d1f11c combase!CStdMarshal:
05d1eecc 75f14715 00000001 05e04e98 00000001 combase!CRemoteUnknown::RemReleaseWorker+0x7e1
05d1eee0 75630ba8 008fdcd8 00000001 05e04e98 combase!CRemoteUnknown::RemRelease+0x15
05d1ef00 755f4de2 75f14700 05d1f120 00000003 rpcrt4!Invoke+0x34
05d1f33c 75e73cd2 00903bb0 008ca2c0 00913624 rpcrt4!NdrStubCall2+0x392
05d1f384 75e73ac3 00903bb0 00913624 008ca2c0 combase!CStdStubBuffer_Invoke+0x92
05d1f3d8 75e73576 00903bb0 00913624 008ca2c0 combase!ObjectMethodExceptionHandlingAction<<lambda_ee1df801181086a03fa4f8f75bd5617f> >+0x6f
05d1f4bc 75ef5921 008ca2c0 00903bb0 05d1f7bc combase!DefaultStubInvoke+0x2b6
05d1f708 75e7b74a 00913624 00903bb0 008ca2c0 combase!ServerCall::ContextInvoke+0x471
05d1f744 75ef81ad 00913624 00000001 00000000 combase!ReentrantSTAInvokeInApartment+0x16a
05d1f9cc 75eabe62 05d1f9eb 00000400 1a6903e8 combase!ComInvokeWithLockAndIPID+0x191d
05d1fa64 771b0fcb 1a6903e8 00000400 0000babe combase!ThreadWndProc+0x452
05d1fa90 771a7f9a 75eaba10 1a6903e8 00000400 user32!_InternalCallWinProc+0x2b
05d1fb74 771a5cfa 75eaba10 00000000 00000400 user32!UserCallWinProcCheckWow+0x33a
05d1fbe8 771a5ac0 00000300 05d1fc30 75e6b1f0 user32!DispatchMessageWorker+0x22a
05d1fbf4 75e6b1f0 05d1fc14 00000000 008868a0 user32!DispatchMessageW+0x10
05d1fc30 75e6b127 75e6b060 00903a70 00000000 combase!CDllHost::STAWorkerLoop+0x86
05d1fc50 75e6b06e 75e6b060 05d1fc88 75ea038e combase!CDllHost::WorkerThread+0xb4
05d1fc5c 75ea038e 7602fe18 00903a70 75f1abf0 combase!DLLHostThreadEntry+0xe
05d1fc88 75f1ac0f 75f1abf0 75f1abf0 05d1fca8 combase!CRpcThread::WorkerLoop+0x198
05d1fc98 76c8fa29 00903a70 76c8fa10 05d1fd04 combase!CRpcThreadCache::RpcWorkerThreadEntry+0x1f
05d1fca8 776d7a7e 00903a70 ebec9ed1 00000000 kernel32!BaseThreadInitThunk+0x19
05d1fd04 776d7a4e ffffffff 776f89fd 00000000 ntdll!__RtlUserThreadStart+0x2f
05d1fd14 00000000 00000000 00000000 00000000 ntdll!_RtlUserThreadStart+0x1b
Expected Causes
According to Crash Dump, `stack buffer overrun` occurs on RPC thread.MediaPlayer class on WMPLib uses COM and RPC connection, so the Crash Dump indicates that the issue is occured at collaboration between COM and Windows Media Player.
According to the report on web, `wmplayer.exe` has occured similar error on `Windows 10 Home`.
I guess that it occurs by using a program **using Windows Media Player with `MediaPlayer` class on `WMPLib` on `Windows 10 Pro` or `Home`**.
