| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 26 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 48:46:24 |
| Calls: | 632 |
| Files: | 1,187 |
| D/L today: |
3 files (4,227K bytes) |
| Messages: | 177,138 |
On Fri, 9/19/2025 4:53 PM, micky wrote:
I posted without running the usual tests because I thought there might
be some new famous cause of freezing that you guys would know off the
top of your head. But test results follow.
sfc /scannow Hey! Windows Resource Protection found corrupt files and
successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log.
cbs.log was 6 megabytes, didn't understand it.
Might there be a log entry somewhere of what went wrong?
Last December, Amazon had the same refurbished computer with win10 or
win11. Does that imply that win11 was an upgrade and not a fresh
install, and could that be a problem?
In alt.comp.os.windows-11, on Fri, 19 Sep 2025 16:41:04 -0400, micky
<NONONOmisc07@fmguy.com> wrote:
Windows 11 Freezes for no apparent reason.
Dell Latitude 5510, about 4 years old, bought refurbished from Amazon
last winter, 32gigs ram.
Five times now over the last 3 months. Not doing anything special. This >>> time I was clickilng on a tab in Firefox. Don't remember previous
times.
Cursor shows but will not move, external mouse does nothing, external
keyboard does nothing. Uncover the laptop's keyboard but it does
nothing, mousepad does nothing, only key that works is power key. Hhave >>> to hold down for 15 seconds and restart.
Thought maybe it was overheating, becasue I covered the keyboard to keep >>> it clean. Uncovered it for 15 minutes, no change,
Using far fewer resources than in pervious win10 computer when I often
went up to 100% CPU and 96% memory. Now I have 32Gigs instead of 8 and
after restarting all the same programs, I was only using 35% of memory
and about 9% of cpu.
Might there be an entry somewhere of what went wrong?
Even thought it's 4 years old, I'm constantly getting Dell updates,
including 10 updates to the BIOS during the summer. I thought BIOS
software was rarely updated and not at all after a year or two.
(Looked brand new when I got it except was supposed to be black and it's >>> silver with a wood-grain surface texture which immediately gets dirty
and won't just wipe off, although it was clean when when I got it.)
Go to Settings and enter "Relia" to see an entry for Reliability Monitor.
It shows major events and displays their Event Viewer information (eventvwr.msc).
Just be aware, there are freezes that generate no log whatsoever. After
a power cycle, the Reliability Monitor will level an accusation of a--- Synchronet 3.21a-Linux NewsLink 1.2
"dirty shutdown", as an interpretation of finding a dirty shutdown sideeffects.
But that's not the freeze log. If you're frozen, all I/O can easily stop
on a dime. All it takes is being frozen in a kernel call.
I had a kind of freeze, that resulted in a BSOD, and the claimed
event there was a "DPC watchdog timeout". That's where Delay Procedure Calls >associated with Interrupt servicing, are piling up and not getting serviced. >But in my example there, the freeze became "unfrozen" in time, to blow
the BSOD instead, and the BSOD got logged. The BSOD was just a side effect
of a freeze, where the system (eventually) got a chance to report "something". >Again, not getting to report the root cause, just report a late side effect of it.
I have seen some strange things in Windows like that, where there are
no comparable incidents on the Linux side. This doesn't mean anything >particularly, except that whatever the root cause is, is not
tickled on the Linux side. Like if it was a problem with my AMD processor, >you would think there would be some sort of equivalence on Linux.
Paul
Paul wrote:
On Fri, 9/19/2025 5:07 PM, Lynn McGuire wrote:Another, when it's not(hardware).
It is always a hardware error.a Except when it is not.
Lynn
Indeed. I just checked my Reliability Monitor.
Looks like my PC was partying on Thursday, and the
party stopped when a definition update for Windows Defender
came in.
[Picture]
https://i.postimg.cc/JncDHLys/reliability-report.gif
I haven't seen anything like that before.
Paul
<https://i.postimg.cc/c4dNgfwB/RM-01.jpg>
A failure to update definitions, not even worthy of investigation.
- it updated successfully, and automatically one minute later
