Windows 10

When I enable my TV it only switches the default audio output device if it was set to be the default when it was disabled (which isn't always the case as sometimes I just turn the TV off but leave it enabled and disable it later when I get annoyed with my cursor disappearing).

I guess if I unplugged and plugged the TV in though it would change the default audio device to the TV. I would consider that expected behaviour.
 
Happens even without any Creative devices in the mix - put a new sound device in and/or drivers change and it picks whichever one initialised last regardless of what is set as default - it is basically Windows 10 "trying" to be helpful but even an idiot should be able to see the issues with it.

There are 100s of people asking how to solve it - but every reply seems to be people who just trigger on key words (especially the MS official helpers) and explain how to change the default sound device - it is hilarious and tragic.

It's not. It doesn't happen with Realtek, anytime I use Creative cards it forgets the settings on Windows 7, 8 and 10.
 
It's not. It doesn't happen with Realtek, anytime I use Creative cards it forgets the settings on Windows 7, 8 and 10.

Never had that problem with my Creative cards on 7. This is definitely a Windows 10 problem loads of people complain about it with or without Creative and I've played about with a couple of different setups and still happens without any Creative hardware in the mix.
 
Just had Teams crash with this message "Windows successfully diagnosed a low virtual memory condition"

I haven't touched virtual memory, no idea what windows 10 is doing.. :confused:
 
I'd want to know it was Teams gobbling up memory before i blamed teams for the crash.

Actually, I just closed a few Chrome windows and Teams now works again.... very odd. Might increase the page file size a little.

You shouldnt ever need to do anything other than let windows manage the pagefile size. It could well be a problem with teams, but it could also be something entirely unrelated.
 
I'd want to know it was Teams gobbling up memory before i blamed teams for the crash.

You shouldnt ever need to do anything other than let windows manage the pagefile size. It could well be a problem with teams, but it could also be something entirely unrelated.

Happened again today.... .

This popped on event viewer before Teams crashed.

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Unarchiver.exe (13576) consumed 2473984000 bytes, chrome.exe (5128) consumed 482959360 bytes, and Teams.exe (5708) consumed 380076032 bytes.
 
Last edited:
ahhh.jpg


Everytime I try to update to this above, I get a BSOD and a System Repair upon restart :mad:
 
Windows Resource Protection found corrupt files and successfully repaired them.

Cheers guys will try again, I haven't had any Windows issues per-say, so I wonder if a previous update broke them?
 
Back
Top Bottom