244
We might see Microsoft adding ads to BSOD
(feddit.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jul 2024
244 points (92.7% liked)
Showerthoughts
29525 readers
943 users here now
A "Showerthought" is a simple term used to describe the thoughts that pop into your head while you're doing everyday things like taking a shower, driving, or just daydreaming. A showerthought should offer a unique perspective on an ordinary part of life.
Rules
- All posts must be showerthoughts
- The entire showerthought must be in the title
- Avoid politics
- 3.1) NEW RULE as of 5 Nov 2024, trying it out
- 3.2) Political posts often end up being circle jerks (not offering unique perspective) or enflaming (too much work for mods).
- 3.3) Try c/politicaldiscussion, volunteer as a mod here, or start your own community.
- Posts must be original/unique
- Adhere to Lemmy's Code of Conduct
founded 1 year ago
MODERATORS
Too bad bluescreened computers likely won't report back viewership stats
(It's a joke, I know that the very existence of a bluescreen literally means that the processor has not hung but it has been detected that proceeding to run userspace code might result in undefined behavior; the network stack might remain functional throughout)
Microsoft would do anything to keep the statcounting service running more stable than the kernel itself
Ring -1 proprietary telemetry! Yay!
*Microsoft pushes UEFI-level telemetry as part of the Secure Boot requirements for Windows 12*
dear user.
thank you for your report.
please be assured that even in the event of a bsod, windows will still report metrics back to microsoft so long as the system drive is operational for use as temporary storage of that data until the next successful windows boot.
new OOB ad metrics reporting will also be added to intel ime and amd psp in future processors in order to further address your concern.
-microsoft support
It's a joke, I know that the very existence of a bluescreen literally means that the processor has not hung but it has been detected that proceeding to run userspace code might result in undefined behavior. The hard drive remains in use but this relies on a subsequent successful Windows boot (good luck). In case of bootlooping kiosks, the company's IT crew will probably just pull useful data off the drive and revert it to the known good installation.
If the BSOD happens on a running PC, networking will probably continue working. With a bootloop, it depends on whether the network stack initialization has progressed far enough before the crash.
I dunno. Kernels can dump the memory pages and whatnot, surely they could throw in which ad got served at the time too. I’m sure someone up at Microsoft is smart enough to figure it out.
I would imagine stats could be somehow stored and sent off once the problem is resolved