Search:

figured it out. i had to delete the partitions including the health recovery from the old windows install. then iw as able to reboot with secure boot mode on and then format and use the drive.

after adding an old sata hdd drive i had laying around to my asus strix b250 system for storage the system won't boot with windows 10 secure boot enabled. Is the only way to fix this to re-install...

Thought upgrading to windows 1809 version fixed my issue. But nope. Aura still crashes. Usually when playing bfv. Freezes and starts eating around 12-15% cpu until I end task. I give up.

Well after the latest windows feature update to 1809 and lates bfv update. My aura hasn't froze yet playing bfv. crossing fingers I no longer have issue will report back if I do.

1.07.36 Still the same issue as op since day 1. Its starting to really piss me off cause with each update the freezes happen more often. Masterasus said my system is faulty. But so many people...

same for me. usually when gaming in bfv. but on other occasions as well.

BIOS 1207 Strix b250f


none


none


yes

can't download version Version 1.05.38.

An error occurred while processing your request.
Reference #132.96c8d917.1546414577.2feed513

Interesting, cause I kept saying I wanted to go back...

I had a feeling lol.

spoke too soon. had it get stuck around 13-15% again. but still better then random hitches. was able to close and restart aura sync process. this is what I've always had to do so I guess just...

haven't had the issue. only thing I did was reinstall aura sync again after this time making sure power was cut by flipping psu switch for 10 minutes. Maybe that did it. Not sure if I changed...

The only thing causing it to not run right is aura sync, as I've confirmed. And it seems other users have the thing hog up 15% of cpu as well. In fact this was in issue since the original...

well thought I fixed it by uninstalling, unplugging pc for 10 mins. then reinstalling. But next thing you know my bfv started lagging, and sure enough I tabbed to task manager and lighting...

hmm maybe. I'll do some more testing. I will also unplug plower and hit psu switch again to see if any change. Also will use defaullt rainbow setting and see if any diff. I will report back.

Aura sync averages 1-3% normally when not spiking.
I don't do much on pc except game so when idle my total cpu is pretty much 0-3% I play titanfall 2, bfv, star wars battlefront 2, witcher 3. ...

strix b250f, latest windows 10 build, no rgb hardware except motherboard, latest bios 1207.

CPU usage sometimes spikes close to 15% causing massive slow downs when gaming. It would get stuck...

the fix is to disable fast startup. or do disable and enable graphics card in device manager.

has nothing to do with realtek drivers. seems to be an issue on z170, z370, b250 , maximus x and v,...

just seems like common sense to also disable it in bios. Same thing when setting pc to high performance you would also disable cstates in bios not just in windows to make sure its fully disabled.

Lateset audio driver did not fix the issue. Asus must think its a realtek problem but its not. Its most likely asus bios issue, but could also be windows or/and nvidia issue.

as the asus guy said the fix is to disable and enable the graphics card in device manager. Also turn off fast startup in windows and bios. I just wish nvida, windows, or asus bios would fix w/e...

yes this is the exactly the issue. but how to get them to fix it? lol.

add this to the list of threads on this issue http://www.tomshardware.com/forum/id-3561083/windows-audio-crackling.html

Definitely a windows and nvidia problem.

ya it did in my case I was using sennheiser gsx-1000. But I got rid of it since I felt the asus onboard sounded way better.

I think you mean you disabled fast boot? That will fix the issue people have when turning on the machine. But the issue comes back if using sleep mode. restarting will fix it since that is not...

latest audio drivers released this week didn't fix the issue. Still think its an nvidia drvier, or windows/bios problem.