D
D. Hendriks (Dennis)
Usually, hibernation (which is set as my default shutdown option in the Start
Menu), takes less than a minute. Sometimes however, it takes very long. It
can get up to, or even more than, 10 minutes!
I accessed the Event Viewer -> Applications and Services logs -> Microsoft
-> Windows -> Diagnostics-Performance -> Operational, and filtered for Event
ID 300. There are several 'Error' and 'Critical' Level events, where the
'Critical' ones account for all of the problematic hibernations.
Typical entry ('Error' level):
Windows has resumed from standby:
Standby Duration : 49564ms
Standby Incident Time (UTC) : 8-11-2009 15:07:20
Resume Duration : 21076ms
Resume Incident Time (UTC) : 8-11-2009 20:30:12
IsDegradation : false
Problematic entry ('Critical' level):
Windows has resumed from standby:
Standby Duration : 506217ms
Standby Incident Time (UTC) : 8-11-2009 0:40:23
Resume Duration : 24673ms
Resume Incident Time (UTC) : 8-11-2009 10:18:22
IsDegradation : false
On the 'details' tab, for the second on (the 506 seconds), I see:
StandbySuspendTotal 506217
StandbySuspendHibernateWrite 487203
StandbyResumeHibernateRead 24150
So, I'm thinking that it takes 487 seconds to write the memory contents to
hiberfil.sys. I checked, and the fiile is not fragmented at all. Does anyone
have an idea as to why it takes so long to write the memory contents to file?
And why does it take long sometimes, while it usually goes much faster? Any
help would be greatly appreciated.
Some system details:
- Windows Vista Business 64-bit English SP2 with all the latest updates.
4GB internal memory.
- QuadCore Intel Core 2 Quad Q9550, 2833 MHz (8.5 x 333)
- Asus P5Q Deluxe (2 PCI, 2 PCI-E x1, 3 PCI-E x16, 4 DDR2 DIMM, Audio,
Dual Gigabit LAN, IEEE-1394)
- 4096 MB (DDR2-800 DDR2 SDRAM), 2x2GB
- NVIDIA GeForce GTX 275 (896 MB)
- ST3500320AS ATA Device (500 GB, 7200 RPM, SATA-II)
Menu), takes less than a minute. Sometimes however, it takes very long. It
can get up to, or even more than, 10 minutes!
I accessed the Event Viewer -> Applications and Services logs -> Microsoft
-> Windows -> Diagnostics-Performance -> Operational, and filtered for Event
ID 300. There are several 'Error' and 'Critical' Level events, where the
'Critical' ones account for all of the problematic hibernations.
Typical entry ('Error' level):
Windows has resumed from standby:
Standby Duration : 49564ms
Standby Incident Time (UTC) : 8-11-2009 15:07:20
Resume Duration : 21076ms
Resume Incident Time (UTC) : 8-11-2009 20:30:12
IsDegradation : false
Problematic entry ('Critical' level):
Windows has resumed from standby:
Standby Duration : 506217ms
Standby Incident Time (UTC) : 8-11-2009 0:40:23
Resume Duration : 24673ms
Resume Incident Time (UTC) : 8-11-2009 10:18:22
IsDegradation : false
On the 'details' tab, for the second on (the 506 seconds), I see:
StandbySuspendTotal 506217
StandbySuspendHibernateWrite 487203
StandbyResumeHibernateRead 24150
So, I'm thinking that it takes 487 seconds to write the memory contents to
hiberfil.sys. I checked, and the fiile is not fragmented at all. Does anyone
have an idea as to why it takes so long to write the memory contents to file?
And why does it take long sometimes, while it usually goes much faster? Any
help would be greatly appreciated.
Some system details:
- Windows Vista Business 64-bit English SP2 with all the latest updates.
4GB internal memory.
- QuadCore Intel Core 2 Quad Q9550, 2833 MHz (8.5 x 333)
- Asus P5Q Deluxe (2 PCI, 2 PCI-E x1, 3 PCI-E x16, 4 DDR2 DIMM, Audio,
Dual Gigabit LAN, IEEE-1394)
- 4096 MB (DDR2-800 DDR2 SDRAM), 2x2GB
- NVIDIA GeForce GTX 275 (896 MB)
- ST3500320AS ATA Device (500 GB, 7200 RPM, SATA-II)