This quote above is a snip from the original post. I was hoping replying to my own post this would be seen by all that have contributed. I believe all were helpful. At this point I'm watching, it seems to be acting more normal. I worked all your suggestions and added of myself, I mentioned above, to disabling all the Task Schedules that were triggered by "When Idle" ... as it was happening when idling only. I hope this is the best fix and do want to thank you all. I trust I hit everyones LIKE icon. Let me know if I missed. Thank you for hanging in there with me. ":-Dx
On my two Dell laptops, one new, one a decade old the settings for adaptive brightness are in the graphics drivers own App. If set to 'on' the brightness is all over the place in normal usage on battery.
Worth a look to see what graphics your Toshiba uses and if there is some control panel for it. It may even be in the old Windows Control Panel which is still available in W11.
Tbh I thought Toshiba exited the PC market years ago... have a friend with a Satellite laptop and that must be around 12+ yrs old now but it runs W10 OK.
, I mentioned above, to disabling all the Task Schedules that were triggered by "When Idle" ... as it was happening when idling only. I hope this is the best fix and do want to thank you all. I trust I hit everyones LIKE icon. Let me know if I missed. Thank you for hanging in there with me. ":-Dx
Really? Well I don't know which one specifically worked is that okay? I'd try one and then the other, and another and somehow it all seems to be equalling out it's behaving better but no specific one jumped out as the magic bullet. I can do no better than that. Apologies. ":-\\
Really? Well I don't know which one specifically worked is that okay? I'd try one and then the other, and another and somehow it all seems to be equalling out it's behaving better but no specific one jumped out as the magic bullet. I can do no better than that. Apologies. ":-\\
If I were to guess what did the trick I'd say I saw the best progress when I disabled the Scheduled Tasks that ran "when idle" ... so I guess I was the answer. But I wasn't willing to take the credit as I believed all the suggestions tossed in there to the end effect.
On my two Dell laptops, one new, one a decade old the settings for adaptive brightness are in the graphics drivers own App. If set to 'on' the brightness is all over the place in normal usage on battery.
Truth be told this is an older Toshiba Satellite, I guess they are out of the picture these days. I've had 3 satellites since about 1995 and this one was a rescue. I'd say this was state of the art when Win 10 was just new. But with the hack that everyone is aware of it's running win 11 just fine. I use it for slow sessions and jump on one of the others when I need more power faster. Thanks for your suggestions I will look for those things you pointed out! Thanks!
Same goes for the options from Intel's GCC - as recommended by Mooly?
Also, open a random folder and copy the following in address bar:
Control Panel\Hardware and Sound\Power Options
And...
Also, especially if you have SSD - in search bar copy paste Services and Disable SysMain.
Above 2 settings can cause all kinds of issues - despite of being intended to improve performance. Your system is actually performing better (overall) and more stable/secure - if both settings are disabled.
Putting the PC to Sleep & Turning Off the Display - is more than enough for power saving. After all - the CPU alone has 75 Power Management settings - where the majority are meant for power throttling/saving.
Something I noticed over a few years was that both my PC's had the same issue when I disabled Fast Start and that was that the clock stops synchronising. It has done that through various versions of W10/11 and tbh my reason for turning it off originally was because of Night Light scheduling issues (which turning off Fast Start fixed).
Just something to be aware, it may not happen all hardware configurations but both my Dell laptops exhibited the same behaviour.
Something I noticed over a few years was that both my PC's had the same issue when I disabled Fast Start and that was that the clock stops synchronising. It has done that through various versions of W10/11 and tbh my reason for turning it off originally was because of Night Light scheduling issues (which turning off Fast Start fixed).
Just something to be aware, it may not happen all hardware configurations but both my Dell laptops exhibited the same behaviour.
That shouldn't be possible if you have internet access and Set time automatically and Set time zone automatically are On. Unless you're using the computer offline - and has a bad battery (since then it would be synced with BIOS time).
The thing about Fast Startup - it's basically a hibernation feature - so your system never truly/properly shutdowns. That's why/how it starts so fast. But that can cause all kinds of problems - even serious ones - if the stored settings get corrupted (an endless loop where the system keeps shunting down - while accessing the hibernation file/stored settings). The system is simply more prone to getting unstable. Yet, if disabled - those settings are flushed (same way it happens with a Restart - also why sometimes - a restart is all it takes to solve issues caused by a corrupted setting/file which gets flushed away) - and the system starts anew every time.
For a similar reason i recommenced Fast Boot - to be disabled as well. Fast boot enabled - basically skips the basic functionality test ran by BIOS, so - if there's a issue with the system (such as failing hardware) - the system might still be able to boot (and then fail the Windows test - and trigger a BSOD) - which increases the chances of more serious damage.
That shouldn't be possible if you have internet access and Set time automatically and Set time zone automatically are On. Unless you're using the computer offline - and has a bad battery (since then it would be synced with BIOS time).
I noticed the clock was about 20 seconds in error today and on checking the 'last synced' date was surprised to see 01/01/22 Clicking sync now worked correctly and it re-synced. The date seems odd, more than just coincidence that it should be 01/01. If I look at 'date and time' in control panel...
www.elevenforum.com
This jumps in halfway through that thread but it was totally conclusive:
I noticed the clock was about 20 seconds in error today and on checking the 'last synced' date was surprised to see 01/01/22 Clicking sync now worked correctly and it re-synced. The date seems odd, more than just coincidence that it should be 01/01. If I look at 'date and time' in control panel...
www.elevenforum.com
Both laptops are now running with Fast Start enabled since the Night Light issues seemed to get resolved and the clocks on both sync as they should.
I noticed the clock was about 20 seconds in error today and on checking the 'last synced' date was surprised to see 01/01/22 Clicking sync now worked correctly and it re-synced. The date seems odd, more than just coincidence that it should be 01/01. If I look at 'date and time' in control panel...
www.elevenforum.com
This jumps in halfway through that thread but it was totally conclusive:
I noticed the clock was about 20 seconds in error today and on checking the 'last synced' date was surprised to see 01/01/22 Clicking sync now worked correctly and it re-synced. The date seems odd, more than just coincidence that it should be 01/01. If I look at 'date and time' in control panel...
www.elevenforum.com
Both laptops are now running with Fast Start enabled since the Night Light issues seemed to get resolved and the clocks on both sync as they should.
That sounds like Dell being Dell - if their systems have to be kept On all the time (even if an hibernation state) - to be able to display the time correctly in 2023... almost 2024. Most issues that you'll ever encounter on a Dell system - are usually caused by Dell devs. It's like - they've been trying hard to self-sabotage for past decade or so (there was a time when Dell meant something, i mean - still pricey - but more reliable compared to other competitive brands).
I noticed the clock was about 20 seconds in error today and on checking the 'last synced' date was surprised to see 01/01/22 Clicking sync now worked correctly and it re-synced. The date seems odd, more than just coincidence that it should be 01/01. If I look at 'date and time' in control panel...
www.elevenforum.com
This jumps in halfway through that thread but it was totally conclusive:
I noticed the clock was about 20 seconds in error today and on checking the 'last synced' date was surprised to see 01/01/22 Clicking sync now worked correctly and it re-synced. The date seems odd, more than just coincidence that it should be 01/01. If I look at 'date and time' in control panel...
www.elevenforum.com
Both laptops are now running with Fast Start enabled since the Night Light issues seemed to get resolved and the clocks on both sync as they should.
Just remembered - there this App which seems to be made particularly for Dell machines (and others alike). As in: Update Time v1.3 ^^
PS. 526th reason to avoid Dell systems like the plague: almost 2024 and Dell can't even sync time correctly (the most basic feature in the tech industry) - without keeping the system partially (hibernation) open all the time.
AT the moment and with no issues needing Fast Start disabling to correct them (its always been the Night Light scheduler that causes problems) all is good. That's interesting though, thanks.
I wanted to get back to any of you that might be following this issue(s) I've had with the laptop on/off even from shutdown, etc. I seemed to have found a fix. In the BIOS I decided to click on Defaults. I found one that said "Critical Battery Alarm" turned that setting off and it's been a normal laptop for about 72 hours now, no auto startups etc.
It's been quite awhile since I posted. This issue persists even though I bought an new AC Module. I've just learned to work around it. It's not #1 pc anyway. Thanks for all your help in the past. I think I gave and LIKES to everyone. I meant to. To better days to you all! jack
