Installer Steam
Logg inn
|
språk
简体中文 (forenklet kinesisk)
繁體中文 (tradisjonell kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tsjekkisk)
Dansk (dansk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spania)
Español – Latinoamérica (spansk – Latin-Amerika)
Ελληνικά (gresk)
Français (fransk)
Italiano (italiensk)
Bahasa Indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (nederlandsk)
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasil)
Română (rumensk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (vietnamesisk)
Українська (ukrainsk)
Rapporter et problem med oversettelse



https://youtu.be/qrTfLfruYHo?si=TK3bjYoxLa9aZbUo
DDR5 that hasn't brought significant improvements over decent DDR4.
Strange implementations to make 11 run or crash better in the name of espionage. (Ah! no, security).
Anything is possible.
We're stuck in a false 64-bit environment, where only Linux (which would never have been a threat) is starting to bring real benefits to servers and now, given the demise of the solid 10, even to desktop expansion.
Event 41 - Windows stopped without expected shut down, meaning something else is the cause.
What's happening to the kernel?
Many people want competitive online games, and they're willing to cheat. To prevent this, programs are installed that compromise the kernel. How does the kernel respond? It crashes.
Few people are still using Windows 11 to avoid throwing millions of PCs into the landfill.
To avoid this, in the end, by surrender, it's being allowed to run on PCs that were initially excluded. Updates attempt to recover this hardware, and the compromises on the new one are most likely not a good thing.
Win 11 has been out for a few years, but it feels like it came out today, because it's only been used recently, on hardware that may not be the best.
When 11 is ready, we will already be talking about 12. But then we will all be using a Chinese OS on Chinese hardware and the problems will be solved. :)
sfc /scannow
dism /online /cleanup-image /restorehealth
And run memtest64
Most likely during a boot is trying to update a kb that fails and leaves it for the next boot.
If it was RAM, then the crashes would have to be like the lights on a Christmas tree unless the sector in question is kaput.
They're choosing poorly tested hardware that burns out.
You should look for hardware that has been tested by the masses without any problems, even if it's old. If you're not looking for crashes, this certainly helps a lot.
Now I'm banking on my two modern monsters, which I occasionally recommend and which work.
My Asrock Phantom AM4 came out of UEFI beta a few months ago. And we're talking beta on a still AM4 socket, I don't know if you understand.
I'm testing these two PCs with all the operating systems I can get my hands on, just to rule out any hardware-related issues.
All systems are installed via SSDs and not virtualized. Some SSDs are external and connected via USB. Windows, for example, is installed via WinToUsb.
The primary operating system remains the undefeated Pika OS.
This system has a history of transformations and redevelopment attempts.
Quick and customized installation.
Stable and responsive.
(The original Debian-based Steam OS could have been like this.)
Try throttling the Windows Updates via the advanced settings there and see if that helps for now. Could be a network adapter issue. It used to do that on one of our Laptops until I replaced the WiFi card inside. It had some issues like crashing to where the network adapter would reset at random when using 5 Ghz but it was generally fine on 2.4 Ghz
Booted up a linux USB, all is well, did an install of LMDE, all was stable. Reinstalled 25H2 fresh, all was back to normal.
I did have Win 10 for a long time, did all feature updates and even the win 11 upgrade on it's own for several years - just got lucky until now \_(._.)_/