This Content Component encountered an error
This Content Component encountered an error
This Content Component encountered an error

To paraphrase Strother Martin in the movie Cool Hand Luke, "What we have here is a failure to hibernate." Here's...

what to do if you get the "insufficient system resources" warning while trying to hibernate your PC. I prefer to hibernate my desktop machine rather than shut it down completely. Since most computers come up out of hibernation much faster than they can reboot, my system is set to sleep after one hour of inactivity, then hibernate after two hours.

I've noticed that sometimes—not always, but often enough to be a problem—when I try to send the computer into hibernation it doesn't work. Instead of the hibernation screen, I get dumped back to the Desktop with a warning balloon popping up from the System Tray that reads: Insufficient system resources exist to complete the API.

Should you upgrade to Windows 7 or 8?

Windows XP shops don't have to migrate to Windows 7 anymore, but there are several pros and cons to weigh before deciding on a Windows 8 upgrade.

Bewildered, I set out to find out what it might mean. As it turns out, Microsoft has documented this failure to hibernate as a known bug. It turns up under the following circumstances:

  1. You're running Windows XP Service Pack 2, Windows XP Tablet PC Edition 2005, or Windows XP Media Center Edition 2005.
  2. Your computer has more than 1GB of physical memory.
  3. The system's memory is currently fragmented—meaning that applications have staked out enough physical memory that a large enough contiguous block of free memory to start the hibernation process can't be reserved. The more memory you have in the system to begin with, the bigger a block of free memory is needed.

Evidently the memory fragmentation issue is the key; many times, hibernation failed after I'd already run a number of other programs. Sometimes I was able to get hibernation to work again after logging off (i.e., after freeing up some of the memory in use), but that didn't always work either.

Microsoft has a fix for this, ostensibly set to go into the next Service Pack for Windows XP, but if you want to address it now you can call Product Support Services and ask for a free hotfix as referenced in the above article (909095). There's no charge for this call.

Note: Vista does not suffer from this issue.

About the author: Serdar Yegulalp is editor of the  Windows Insight, (formerly the Windows Power Users Newsletter), a blog site devoted to hints, tips, tricks and news for users and administrators of Windows NT, Windows 2000, Windows XP, Windows Server 2003 and Vista. He has more than 12 years of Windows experience under his belt, and contributes regularly to and

More information on this topic:

This was last published in April 2007
This Content Component encountered an error



Find more PRO+ content and other member only offers, here.

This Content Component encountered an error