Dear Samuel (You can't see me, because I'm in or between meetings - don't tell my PA),
Believe it or not - this is fun.
Folk's spend big bucks on cable or movie tickets to watch detective or spy thrillers - where the focus hero or heroine track clues, leads, false trails, etc., etc; to try to find/catch the villain or villains ... when in fact all you need do is be good
enough to track the same through assorted computers.
Things that seem unrelated - are often the 'big break throughs' - that help crack cases.
The very long shut-down is just that.
Tells us a lot, and helps narrow-in.
I would like to know the type/size of your Hard Drive (SSD), as well as the amount of RAM that came with your DELL XPS 9500 laptop. There are several configurations. Just want to know a bit more of what we are dealing-with (not critical, but it helps).
The video was great. No one complained about the music, and mostly we were more interested in watching 'the show'.
Firstly. The Very High usage on the core MS system functions are potentially misleading, because those mostly run as (master) hosts (for other functions).
I've known from your first image/post the 'very high' was process 'hosting' - simply because it was not drawing significantly on other resources (memory/disk) - thus we need work-out who/what and how many programs are chewing your resources/taxing the CPU
... via the System, File Manager, Desktop Manager, Comm's Manager ... etc.
iCore7? No problems or lack there; however - if you do not already know - click the 'performance' tab - in task manager - then the cpu chart. let it settle (15 seconds), then take a screen shot - to post here.
Just want to see the cores, threads and CPU speed/draw numbers (MHz) ...
Why? Don't have Dells laptops handy (i7's); so we've looked at some HP Pavillion, Toshiba Satellites and Levono Legions (hi-spec); to test the sleep/shut down characteristics of i7 laptops running Windows 10.
Norm/mean is 30~45 seconds.
Next we decided to torture them a bit (make shut-down slower/harder) - to get out to the 30+ minute mark.
We also have an assortment of i7 workstations (hi spec desk tops), which - as a rule - start/stop faster than Laptops; which in turn can/do talk to some of the larger servers here (HP Dual Xeon's); which in turn do stuff for the BRASS development system
("Clover Array") - that is 'biggish', most simply described as four (4) large dual xeon systems on a lower layer, with a larger dual xeon = upper layer; which acts much the same as Windows "service" {it splits and feeds data to the bottom four, then feeds
out processed data to the firewall system, which then goes to the Comms/server - that gives access (portals)} to the folks/their desk/lap systems talking to and working on the project (BRASS).
BRASS is a new kind of all weather radar, originally designed to address airborne volcanic ash and 'black ice' events - following a couple of airliner crashes. It has evolved a bit (still has the original core purpose/function), because its range and accuracy
mean it will be the navigation system/control-tracking system of assorted space agencies, over the next three or four decades. Assorted governments/agencies already know this; however the rest is 'secret'.
Reason I/we cannot send pictures (probably have to take myself outside and execute myself ... if I did, laugh).
Point being, there is a range of seriously good computing stuff around here, that allows a broad range of testing/checking; plus - when it happens - unlike most folks/people, you just go down the stores and sign-out a new computer, after stuffing-up/blowing-up
the one you were using.
So - the fast high specification i5, i7 and i9 systems, do not hold a candle to the bigger (hard core) systems, however they are doing different things. More often than note the small systems - doing their thing - can go faster than the bigger systems.
Has to do with RISC (processing and language-set architecture).
None of the systems here - small, medium or big - take more that 3~5 minutes to shut-down (of those running Win 10x, as the interface OS).
Consensus (my thoughts, and the others asked about this = distraction is as good as a holiday {break from work}) is:
- Your CPU is working overtime and 2~3 times more than it should be;
- Cause is back ground activity;
- #2 is either:
3.1. Third party software - main offender being 'Rambox', in parallel to anti-virus/anti-malware, and other items;
3.2 System and Third party functions - like shadow drive, back-up, disk compression, disk de-fragmentation, archiving, etc.;
3.3 Damaged or compromised system files - Windows repair trying to restore/fix;
3.4 Hijacker code, or similar function within a game or media-share software - that is using your system/resources as a 'bot' (remote server).
3.5 Combination of element (some/all) @ 3.1 through 3.4.
Important thing is approaching this slowly - one step at a time.
- "Rambox", and potential that Windows recovery is trying to repair damaged files.
4.1 We all think you are better off to completely remove "Rambox" from your system. It is not good software, ultra resource-heavy, and likely doing far more 'bad', than any good.
Unless you absolutely need it, uninstall it completely - then reboot for the next stage.
If you feel it has some function/job you need ... tell us what that function/job is, then we will find software that does the same, without all the 'Rambox' potential negatives.
4.2 Following (after removing Rambox) reboot; go into the Windows start menu, find "Command Prompt", _Right Click_ on it and select "run as administrator".
When the Command prompt window comes up type:
sfc /scannow
{note. That is 'sfc' - space - '/scannow'}
Then hit 'enter' or 'return' ... and let it run (internet connected).
Once finished it will say what it has fixed (where/if needed), and give you a log address ... for review.
Reboot, go into Task manager and watch. Take note of any improvements. After 3~5 minutes, take note of what is chewing resources now (= next/second step ... following one at a time protocol).
Must run, because people are at the door waiting and I'm running slightly late {laugh}.
I was thinking of moving us/this thread up to HP Community (Paul Tikkanen - best in USA/North America) on this sort of think, because we do not have Dell's. I think - not sure - Dells are, or a branch of, HP. However we'll try to fix what we know we can
fix, and is Windows 10/OS related (potentially).
Cheers,
Rick.