Hi all,
I'm new here so forgive me if this question has already been asked, I did look for it but could find anything like the problem I'm having. So.......................
When the W10 upgrade was released, I upgraded from W8.1. Before the upgrade, my "project" (to my TV) feature, was working fine. Now, it will connect and stream to my TV, but after a while (anywhere from 5 mins to an hour or so), the TV picture freezes. In the "connect" box on the laptop, there is no change everything looks as it should. When I try to disconnect, the TV goes back to normal, but the laptop just keeps saying "disconnecting" and never actually disconnects.
When I look at the event log, it tells me that there has been a critical event (ID:10111) and that there has been a user mode driver crash. If I try to do anything much, it all sort of freezes up and I have to restart.
I don't know which driver is causing the problem. It could be the "Miracast display port driver V2". It has a driver date of 21.06.2006, I can't find anything online more recent than that. I have uninstalled it and reinstalled it many times to no avail. It could be the Realtek wifi adapter which I have updated and backdated and outdated however I could, again that has made no difference. It could be something else completely different, I have no clue now. I've been at it for days, searching and searching and nothing I can find seems to help.
I was just wondering if anyone else has a similar problem or is it just me?
It would also be great if someone who knows much more than me, might have some insight into what I could try next.
I think somewhere amongst the searching I did read something about there being an incompatibility with W10, and miracast (just to clear, I'm only using the laptop "connect/project" feature that was introduced in W8.1, I don't have a miracast dongle or any other hardware).
Thanks a lot in advance and if I can upload anything or give more details, then please let me know what you need to know.
Mark
It is a known issue. No time frame to fix. You may want to keep up on the Insider Blog. Windows Insider Program | Blogging Windows Gabe Aul is in charge of the Windows 10 Insider program. You can find him at Gabriel Aul (@GabeAul) | Twitter
Also keep the LOL and other stuff out of the post. It tends to make your posts passed over by others. Also a lot of the Miracast stuff is behind the times. Miracast has been on its deathbed since 2013, because of slow adoption by the industry.
Hi bro64,
Thanks a lot for the info, I will have a look. It makes me feel better to know it's a known issue. I'm assuming it's still without a fix, but at least I know it's probably not anything I did wrong. I will keep the posts more matter of fact in future and less chatty.
Thanks again
A bit more info about my system
Interface name: Wi-Fi
Driver : Realtek RTL8723BE 802.11 bgn Wi-Fi Adapter
Vendor : Realtek Semiconductor Corp.
Provider : Realtek Semiconductor Corp.
Date : 21/07/2015
Version : 2023.15.701.2015
INF file : C:WINDOWSINFoem3.inf
Files : 2 total
C:WINDOWSsystem32DRIVERS twlane.sys
C:WINDOWSsystem32DRIVERSvwifibus.sys
Type : Native Wi-Fi Driver
Radio types supported : 802.11n 802.11g 802.11b
FIPS 140-2 mode supported : Yes
802.11w Management Frame Protection supported : Yes
Hosted network supported : No
Authentication and cipher supported in infrastructure mode:
Open None
WPA2-Personal CCMP
Open WEP-40bit
Open WEP-104bit
Open WEP
WPA-Enterprise TKIP
WPA-Personal TKIP
WPA2-Enterprise TKIP
WPA2-Personal TKIP
WPA-Enterprise CCMP
WPA-Personal CCMP
WPA2-Enterprise CCMP
Vendor defined TKIP
Vendor defined CCMP
Vendor defined Vendor defined
Vendor defined Vendor defined
WPA2-Enterprise Vendor defined
WPA2-Enterprise Vendor defined
Vendor defined Vendor defined
Vendor defined Vendor defined
IHV service present : Yes
IHV adapter OUI : [00 e0 4c], type: [00]
IHV extensibility DLL path: C:WINDOWSsystem32Rtlihvs.dll
IHV UI extensibility ClSID: {6c2a8cca-b2a2-4d81-a3b2-4e15f445c312}
IHV diagnostics CLSID : {00000000-0000-0000-0000-000000000000}
Wireless Display Supported: Yes (Graphics Driver: Yes, Wi-Fi Driver: Yes)
A quick question for bro64 (or anyone who might be interested) If it's a known issue, why isn't everyone experiencing it, is it just a few cases that have the issue? I assume that there must be millions of people who used the feature in W8.1 and have also upgraded like me, so do all of them now have the same problem, or only a few? My wifi adapter is about as common as it could be, so I don't have some rare hardware, and my system is only a few months old, it came with W8 or 8.1 (don't remember now) but when I was searching for solutions, I really didn't find that many people complaining of the same thing.
