As it is so quick to try I would suggest you turn off 'fast start up' as per here (option 1).
It may not be the culprit but it is an easy 'solution' to try. My last 2 PC's if I had 'fast start up' enabled gave me glitches and freezes so might be worth a shot (especially if a restart solves the...
One short beep is confirming that the checks have all been passed so is normal in my experience.
I have heard of the 1 long and 3 short beeps being linked to issues with the monitor turned off and the MOBO not being able to identify that the GPU is connected correctly. If the monitor is turned...
If the beeps are still occurring the same way then I wonder if the GPU is the issue. Has it been used in any other system so that you are sure it isn't faulty?
I'm assuming you are definitely connecting the cables to the GPU in the back of the PC in the right slots and not any that are for the...
If it is 1 beep followed by 3 short beeps then would seem to indicate no VGA detected as per here (section 2.3).
Are you sure the GPU has been seated correctly? Might be an idea re-seating it (and making sure you are connecting the cables to the GPU and not the Motherboard).
As per above a clean install of Windows would be an option but will remove all files from your PC.
It may be that a temporary folder like via System Restore is retaining the virus in some way and it is being reactivated after 'removal'. I would personally run a Malwarebytes or Microsoft Safety...
I had a few issues with an old build a while back with W10 and it was due to 'fast start-up'.
I think your issues sound different to mine but as it is a quick thing to do I would personally turn it off as per here just in case it helps.
I had this happen a few months ago, appears some form of update (only one I did around that time was Steam) corrupted my OS.
Unfortunately I had to completely reinstall the OS via a fresh install. Other than the time it took wasn't a massive issue for me as I have all personal files needed...
Many thanks for the reply. I've disabled most of the options regarding security and the 'Get tips' section but errors still appear.
I'll tinker about a bit more and see if I can get the errors to stop by changing some settings but if not as no performance issue I'll just ignore those errors.
In Windows Reliability Report I have all of a sudden started getting Runtime Broker errors almost every 10 minutes or so that is attached to Cortana.
I don't use Cortana and have a lot of my options disabled regarding privacy and nothing happened with my system or Windows updates to coincide...
If you post your full PCS spec including the make and model of the Motherboard I'm sure someone can decipher those beep codes for you.
Normally 1 long beep and 3 short is a GPU problem or a VGA issue. If nothing at all is displaying on the monitor you could try to connect the monitor via your...
Looking at each manual they do seem very similar so would have guessed the same BIOS basics but unfortunately neither manual (unlike some others) clarifies the BIOS beep codes. Hopefully OP is able to run the scenario via PCS or ASUS for clarification.
From what I have seen I don't think it is an issue to worry about but as a precaution would be worth speaking to PCS and logging it with them just to see what they say. Alternatively you could speak to Asus direct here.
I checked your MOBO Manual online but couldn't see beep codes listed anywhere in it.
In my experience the codes you are getting could indicate (for some ASUS MOBO's) a VGA error. Sometimes this can occur when the system boots up, realises no VGA is detected (assume you connect via DVI/HDMI)...
Might be worth connecting via ethernet just to make sure definitely a wireless only issue.
I would make sure all drivers are updated via Windows if on W10. If they are and no further updates are available I would check to see if there are any further manufacturer drivers for the wireless card...