Excessively long shut-down times

Soldato
Joined
3 Feb 2012
Posts
14,643
Location
Peterborough
Evening,

When rebooting Windows 7 I am getting really long shut down times (around 2-3 minutes).

I've tried disabling all processes in the taskbar and all services except Microsoft ones and the issue is still there.

I've Google'd and not found anything yet so hoping someone here has some knowledge. I wondered if it could possibly be hardware related. I have only just done a new build and re-install of Windows so there's next to no gloat on here.

Additionally, the same set of programs were installed before the rebuild without any issues then.

The hardware changes was a new motherboard and an additional graphics card. Nothing else has changed. Wondered if it was perhaps a motherboard setting or something else...
 
Do you have any peripherals other than mouse/keyboard/speakers connected (gaming controller, webcam etc)?

Have you tried booting in safe mode and see if it's the same shutting down?

Try changing the WaitToKillServiceTimeout registry key to 2000 and see if that changes anything?

Otherwise, do as many virus/malware/adware scans as you can, or use CCleaner to clean the registry, although as a fresh install this shouldn't find much.
 
Do you have any peripherals other than mouse/keyboard/speakers connected (gaming controller, webcam etc)?

Have you tried booting in safe mode and see if it's the same shutting down?

Try changing the WaitToKillServiceTimeout registry key to 2000 and see if that changes anything?

Otherwise, do as many virus/malware/adware scans as you can, or use CCleaner to clean the registry, although as a fresh install this shouldn't find much.

Mouse and Keyboard only, along with a DVI cable into the graphics card and headphones into the motherboard. Will try a safe boot one now. I wish I could remember when it started taking so long as it definitely wasn't taking this long all the time!
 
Mouse and keyboard (obviously) won't be the cause, nor will headphones/DVI, if none of the above work, try changing ClearPageFile at Shutdown to 0, or open Event Viewer and navigate to Applications and Services Logs>Microsoft>Windows>Diagnostics-Performance>Operational and check any critical/warning events in the 200 (shutdown) series, although many have been known to slip through Event Viewer.
 
It's instant in safe mode.

Checked the logs and getting a load of entries:

Windows has shutdown:
Shutdown Duration : 5256ms
IsDegradation : false
Incident Time (UTC) : ‎2012‎-‎07‎-‎30T19:14:34.805300900Z


- System

- Provider

[ Name] Microsoft-Windows-Diagnostics-Performance

EventID 200

Version 1

Level 3

Task 4007

Opcode 40

Keywords 0x8000000000010000

- TimeCreated

[ SystemTime] 2012-07-30T19:19:46.876568500Z

EventRecordID 61

- Correlation

[ ActivityID] {030C8A40-F800-0000-8743-0904886ECD01}

- Execution

[ ProcessID] 1612
[ ThreadID] 2952

Channel Microsoft-Windows-Diagnostics-Performance/Operational

Computer Jason-PC

- Security

[ UserID] S-1-5-19


- EventData

ShutdownTsVersion 1
ShutdownStartTime 2012-07-30T19:14:34.805300900Z
ShutdownEndTime 2012-07-30T19:14:40.062143200Z
ShutdownTime 5256
ShutdownUserSessionTime 2494
ShutdownUserPolicyTime 0
ShutdownUserProfilesTime 0
ShutdownSystemSessionsTime 2075
ShutdownPreShutdownNotificationsTime 539
ShutdownServicesTime 1076
ShutdownKernelTime 686
ShutdownRootCauseStepImprovementBits 0
ShutdownRootCauseGradualImprovementBits 0
ShutdownRootCauseStepDegradationBits 0
ShutdownRootCauseGradualDegradationBits 0
ShutdownIsDegradation false
ShutdownTimeChange 0
 
ClearPageFile has already been set to 0. I got that tip by having a dig myself - didn't resolve it.

How do I interpret this event thingy then?
 
If I overclock mine it does it, and on waking up from sleep mode. I'm looking to set up an RMA over it as it is just getting plan old annoying now.
 
Ah you know, funny you should say that. I have just removed my overclock from the CPU as I can't remember it taking so long before that (moment of inspiration) and it rebooted instantly.

Why is the overclock causing it to get stuck rebooting? Doesn't look like an RMA will solve the problem if it's common.

What BIOS are you on?
 
The others cause my computer to crash, this is the first one that has been relatively stable for me.

Edit. I have posted in the customer support section of OcUK, I will wait until they get back to me before going to Gigabyte.
 
Last edited:
The others cause my computer to crash, this is the first one that has been relatively stable for me.

Cool. Well I'm happy I at least know what it is. To be fair, it doesn't bother me that much because I won't restart - I'll put on the PC and then turn it off. Still irritating if you do though.

Ah well, I'll wait to see what Gigabyte say when they come back.
 
While the long shut down timers are very annoying, I'm more fussed with the overclocking issues and the crashes. But it is nice to know that I'm not the only one having similar problems. Just a though have you tried using / updating the other BIOS on the board as it possible to switch between the two.
 
it "shouldn't" be the overclock, if it's fine in safe mode it points to a service/application/driver problem really. Are all drivers up to date, try updating BIOS as suggested, definitely weird that you're both having the problem on the same board
 
it "shouldn't" be the overclock, if it's fine in safe mode it points to a service/application/driver problem really. Are all drivers up to date, try updating BIOS as suggested, definitely weird that you're both having the problem on the same board

I wouldn't have thought so either. It seems very odd. If I leave everything unchanged the problem occurs. If I run the same scenario without the overclock, it's fine.

Odd but points to a BIOS problem. As mentioned, I've just done a rebuild so everything is the latest. F11 is the latest revision for the board.

Edit: What I was going to do is take a screenshot of the task manager showing all the process ID's for the services and then reboot with the overclock on and match the process ID from the event reporting error log to the one from the task manager. I notice they change process ID each time you load them which isn't helpful :(
 
Back
Top Bottom