Windows 10: i have some bug while finding my pc's capability

well i guess i have some bug here , i want to upgrade my pc to the 64 bit version but it said i need to check if my pc is 64 bit capablewhen i tried with the command msinfo32 in Run , i got that my system is 86 bit base system , but when i went to about in system settings it says that my system is 64 bit capablehow can i know which one is real and how can i fix this bug ?screenshot 1 because i had some error while uploading photosscreenshot 2 for the same reasonthank you before

:)

 

Capability Access Manager

Hi Jelani Moonah，



Welcome to Microsoft Community.



Regarding the random behavior of the Capability Access Manager when recording audio, it's possible that there are underlying factors contributing to this inconsistency. Here are some potential reasons and suggestions to consider:

1. Resource Availability: The time taken for the Capability Access Manager to appear may be influenced by the availability of system resources. If your system is under heavy load, it could affect the time it takes for the manager to process and display the recorded audio.
   
   • Suggestion: Try monitoring your system's resource usage (CPU, memory, disk) during the audio recording process to see if there are any spikes or limitations that could be contributing to the delays.
     
2. Background Processes: Other background processes running on your computer could potentially impact the performance of the Capability Access Manager and its ability to handle and display the recorded audio in a timely manner.
   
   • Suggestion: Consider reviewing and minimizing other running applications and background processes while recording audio to see if it affects the appearance time of the Capability Access Manager.
     
3. Software or Driver Issues: It's possible that there may be software or driver-related issues affecting the Capability Access Manager's performance. Outdated or incompatible drivers, as well as software conflicts, could lead to unpredictable behavior.
   
   • Suggestion: Ensure that your audio drivers are up to date and compatible with your operating system. You may also want to consider reinstalling or updating the audio recording software you are using to see if it improves the consistency of the Capability Access Manager's appearance.
     
4. System Configuration: Certain system configurations or settings, such as power management settings, might impact the performance of audio recording and the appearance of the Capability Access Manager.
   
   • Suggestion: Check your power management settings and ensure that they are optimized for performance rather than power saving. You can also review other system settings related to audio recording to ensure they are properly configured.
     

Thank you for your patience and understanding, if you have any questions, please feel free to leave us a message.



Best regards

Brandon | Microsoft Community Support Specialist

 

Overclocking / Undervolting guide for Vega 56 or 64?

Here's a quick laundry list:

List of software to use for overclocking and testing
Examples:
Wattman (and how to find and use it, like an overview, including profiles)
Unigine Valley or Heaven (use this for quick testing while changing settings in Wattman and checking for stability / artifacts) ...just suggesting this
How to monitor cores / mem speeds and temps during testing (I've seen screen overlays, and others using GPUz)

Step-by step overclocking in Wattman
Fan speeds
Power limit
Temp limit
Voltages
Core speeds
Memory speeds

 

Projecting to this PC {we are still trying to determine the feature capabilities}

John Sarc,

I believe you are misunderstanding the question in this thread. The error message:

"we are still trying to determine the feature capabilities"

is appearing on the potential receiving Windows 10 PC - not a transmitting mobile device.

Additionally, please understand that this is not a "Continuum" question. This is a question regarding Windows 10 Miracast reception.

Also, part of the problem is that the error message is nonsensical. Someone with better English language skills needs to re-write the error message so that it provides an explanation of what error is occurring.

*************************************************************************************

Below are steps recommended by AirServer to de-bug Miracast problems on a Windows 10 PC. I would think Microsoft would have similar suggestions somewhere:

If you are unable to start Miracast services on a
compatible Windows 8.1 or Windows 10 computer:

• Try disabling the WiFi adapter and then re-enabling it again.
• If Cisco VPN client is installed on the PC, make sure that
  "stateful firewall" is turned off. Also ensure that "Deterministic Network Enhancer" which gets installed with Cisco VPN client is disabled.
• If VirtualBox is installed on the PC, disable the "VirtualBox Bridged Network Driver".

If the steps described above does not resolve the issue, follow these advance troubleshooting steps:

Warning: This procedure will delete all WiFi settings, including passwords remembered for known Wireless networks.

• Obtain the latest NDIS 6.4 WiFi driver/software for the WiFi adapter on your machine.
• Quit AirServer Universal.
• Open Device Manager and locate the WiFi adapter which can be found under Network Adapters.
• Right-click the WiFi adapter and choose Uninstall.
• When promoted to confirm, also enable "Delete the driver software for this device" and proceed.
• Restart your computer.
• Install the latest WiFi driver/software from Step 1.
• Launch AirServer Universal.