|a trawl out there in www-land will bring up a hit or two that detail how to add hibernate to the shutdown menu... While they're for XP... possibly it may be possible to modify/apply it for ME?|
A very long shot; and don't be too kwik to dismiss it... Consider RAM...; possibly one or more sticks has a failing section...
When a system hibernates and then re-awakens... data to RAM is written afresh. If per chance RAM is dubious,failing. duff etc... - and typically if intermittent... re-applying data (which effectively is a voltage input...) can often resolve an issue sed RAM may produce (but not always) - including a rodent's behaviour (drivers...). Similarly if it takes a couple of reboots to get a system booted up properly... RAM is often a viable chief suspect/issue there (but not always...).
Perhaps substitute all RAM and see what happens; if problem persists then likely not RAM. But if after a typical interlude for the problems to appear -- no problems appear..., then not unreasonable to suspect one or more of the RAM sticks originally installed? If two or more installed - try with only one installed (minimum of 16Meg I think is the preferred for ME - but whatever you can manage/get away with otherwise?); testing each stick in turn. And again allow for a typical interval for the problem to appear?
RAM often fails slowly; seems to perform OK for a while, then not so (thus intermittently...
Memtester utils are aplenty; and personally I have limited faith in them. Generally find a straight substitution test (if practical/possible etc.) more effective and faster too... But if only (by today's standards) a small amount of RAM installed - and 64Meg is small these days... then perhaps run a memtest if substitution not practical?
Incidentally this site seems to suggest the option to "trigger/activate" hibernate is within the shutdown menu (by default); and may not work if a driver or two require updates..?