Computer takes very long to power off after shutdown.

T

THROW_ME_AWAY

Active member
Joined
Dec 16, 2019
Posts
35
Hi, My PC takes a very long time to power off after I shut it down.
The screen turns off after the shutdown animation, but the Fans, RGB etc. stay on for very long afterwards.
This only happens o windows, not on an ubuntu install I have on another disk, so I can safely exclude any hardware issues.

I found it's not really safe to power it off by suffocating it with the power button, because that led to a broken EFI partition which I had to repair.
Luckily that's working again after rebuilding the EFI with an installation media and a system restore.

How can I safely diagnose what program or driver is causing the long wait before shutdown?
I tried booting in safe mode, but the problem persists there (sometimes?).
I'm not really sure how to proceed with this.
I'm worried that if I leave it like this, it might cause more system corruption in the future, so I want to solve the problem before it gets worse.

Is there a tool which I can use to see which drivers are still running after shutdown?
Maybe some sort of virtual driver whose job is to log which other drivers are still running after shutdown and then exits after like 5-10 minutes so it itself does not block shutdown?


Other things I tried:
chkdsk C: -> Windows has scanned the file system and found no problems.
sfc /SCANNOW -> Found corrupt files and repaired them. Running it again found no integrity violations
DISM /online /Cleanup-Image /ScanHealth -> No component store corruption detected.
Reinstall/update all drivers I could find (NVIDIA, Sound Card, Mouse) -> No Change

If you could help me with this, I would very much appreciate it!
Thanks in advance!
 
No need for apologies :-)

Open an elevated command prompt. Hit Start, type cmd, then CTRL + SHIFT + ENTER.

An elevated command prompt should open after you answer the prompt.

In this prompt, type powercfg.exe /hibernate off

Hit enter and reboot.

If you want to turn Hibernate back on, just simply repeat but replace off with on. This will reset it and remove any corruption that may be causing issues.

Sometimes the file (hiberfil.sys) that hibernation uses gets corrupt and can cause your symptoms. It can also get quite large.

What is Hibernate?
 
ok, have executed the collection app.
Output is attached.

  • A brief description of your problem (but you can also include the steps you tried)
    See Above.
  • System Manufacturer?
    Self-built.
    AMD Threadripper 1950x
    ASUS x399 A-PRIME
    2x NVIDIA GTX 1080
    G-SKILL Trident Z 32GB @ 3000MHz
  • Laptop or Desktop?
    Desktop
  • Exact model number (if laptop, check label on bottom)
    N/A
  • OS ? (Windows 10, 8.1, 8, 7, Vista)
    Windows 10
  • x86 (32bit) or x64 (64bit)?
    x64
  • (Only for xp, vista, 7) Service pack?
    N/A
  • What was original installed OS on system?
    N/A
  • Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
    No
  • Age of system? (hardware)
    Varying, mostly about 1-3 Years
  • Age of OS installation?
    ~1 Year since last Re-install
  • Have you re-installed the OS?
    Repeatedly, but not recently.
    But for unrelated reasons (e.g. Windows Store/Windows Update not working).
    None of these Issues have been present since last Re-install.
  • CPU
    AMD Threadripper 1950x 16C/32T @3.6 GHz
  • RAM (brand, EXACT model, what slots are you using?)
    G-SKILL Trident Z 32GB @ 3000MHz
  • Video Card
    2x NVIDIA GTX 1080
  • MotherBoard - (if NOT a laptop)
    ASUS x399 A-PRIME
  • Power Supply - brand & wattage (if laptop, skip this one)
    Corsair RM 850x (850W), wall power draw is never more than 700W, even at full load (checked using socket meter).
  • Is driver verifier enabled or disabled?
    I don't know what that is, and I didn't enable it, so it's probably not enabled.
  • What security software are you using? (Firewall, antivirus, antimalware, antispyware, and so forth)
    Just Windows Security (Windows Defender? What's it called nowadays?).
  • Are you using proxy, vpn, ipfilters or similar software?
    no
  • Are you using Disk Image tools? (like daemon tools, alcohol 52% or 120%, virtual CloneDrive, roxio software)
    no
  • Are you currently under/overclocking? Are there overclocking software installed on your system?
    CPU and RAM are mildly overclocked, but have been that way and stable for years.
    CPU from 3.4 to 3.6 GHz all-core.
    RAM at 3000MHz, rated for XMP 3200.
    Temps are fine.
    No overclocking Software installed. OC in BIOS.
 

Attachments

Please enter the following command in an elevated Command Prompt and then attach the file which will saved to your Desktop.

Code: 
powercfg /sleepstudy /output %userprofile%\Desktop\SleepStudyReport.xml /XML
 
That's weird because my system language is English, but it might have to do with local date/time formats, which are german
I'll look into it later.
I attached the sleep study report.
 

Attachments

Fine, I'll return the RAM to stock.
However, the BSOD was after forceful shutdown which caused a broken EFI partition.
That has since been repaired.
So I don't think BSOD it was a RAM speed issue, but I'll disable it just to exclude it as an error source.
 
Do you have hosted links to those BAT files without having to register somewhere?
I hate having to create thousands of accounts.
Anyway, I'll do it for now, but consider hosting them on sysnative as well if you use them often.
 
Code: 
###########################################################
# The following commands will be run in sequence.         #
# The first 5 will take quite a while to run, be patient. #
###########################################################

sfc /scannow
dism /online /cleanup-image /scanhealth
dism /online /cleanup-image /restorehealth
sfc /scannow

chkdsk /scan

wmic recoveros get autoreboot
wmic recoveros set autoreboot = false
wmic recoveros get autoreboot
wmic recoveros get DebugInfoType
wmic recoveros set DebugInfoType = 7
wmic recoveros get DebugInfoType

wmic pagefile list /format:list
wmic Computersystem where name="PYRESTONE-HOST" get AutomaticManagedPagefile
wmic Computersystem where name="PYRESTONE-HOST" set AutomaticManagedPagefile=True
wmic Computersystem where name="PYRESTONE-HOST" get AutomaticManagedPagefile

bcdedit /enum {badmemory}


C:\windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19041.746

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

C:\windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.19041.746

Image Version: 10.0.19041.746

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is SABRENT_ROCKET.

Stage 1: Examining basic file system structure ...
  1350400 file records processed.
File verification completed.
 Phase duration (File record verification): 10.66 seconds.
  18389 large file records processed.
 Phase duration (Orphan file record recovery): 0.00 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.46 milliseconds.

Stage 2: Examining file name linkage ...
  53261 reparse records processed.
  1645296 index entries processed.
Index verification completed.
 Phase duration (Index verification): 28.35 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 7.32 seconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 1.22 milliseconds.
  53261 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 144.00 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 69.75 milliseconds.
  147449 data files processed.
 Phase duration (Data attribute verification): 0.47 milliseconds.
CHKDSK is verifying Usn Journal...
  36671056 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 107.92 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

1952419836 KB total disk space.
 563816388 KB in 1141382 files.
    543976 KB in 147450 indexes.
         0 KB in bad sectors.
   1517592 KB in use by the system.
     65536 KB occupied by the log file.
1386541880 KB available on disk.

      4096 bytes in each allocation unit.
 488104959 total allocation units on disk.
 346635470 allocation units available on disk.
Total duration: 46.68 seconds (46686 ms).

C:\windows\system32>wmic recoveros get autoreboot
AutoReboot
TRUE


C:\windows\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\PYRESTONE-HOST\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\windows\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\windows\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\PYRESTONE-HOST\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\windows|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\windows\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\windows\system32>wmic pagefile list /format:list


AllocatedBaseSize=32000
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20200912083408.620422+120
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE


AllocatedBaseSize=64000
CurrentUsage=0
Description=G:\pagefile.sys
InstallDate=20210131001558.572436+060
Name=G:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\windows\system32>wmic Computersystem where name="PYRESTONE-HOST" get AutomaticManagedPagefile
AutomaticManagedPagefile
FALSE


C:\windows\system32>wmic Computersystem where name="PYRESTONE-HOST" set AutomaticManagedPagefile=True
Updating property(s) of '\\PYRESTONE-HOST\ROOT\CIMV2:Win32_ComputerSystem.Name="PYRESTONE-HOST"'
Property(s) update successful.

C:\windows\system32>wmic Computersystem where name="PYRESTONE-HOST" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\windows\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}
Press any key to continue . . .

LOGS.zip is Here: LINK
Powercfg_info is attached
 

Attachments

Hm. Now it doesn't turn off at all.
Previously it would usually turn off after about 5-10 minutes of black screen, but it's been way longer now and it's still not off.

I think one of those bat files messed with the pagefile configuration, but that shouldn't be the reason it takes forever now.

Usually, the behavior is idle for approx. 5min, then heavy fan noise for several seconds, then turn off.

Now it's been several minutes of heavy fan noise, but no sign of turning off.
Should I suffocate it manually?
 
It is still not fully powered off.
Should I force power off by holding power button?
The fans are still running heavily and it's drawing ~300W from the wall.

Also what is ACP? Admin CMD?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top