Restoration Data Processing Win 7?

seamorton

Member
Feb 11, 2016
102
4
81
OS is Win 7 64 Bit ... System does/will not shutdown/poweroff. Following is what appears on screen. Status - 0x0000411 - Fatal error occurred processing restoration data - File: \hiberfill. sys.

What/how do I need to do to shutdown or turn off my PC. When it is shutdown the system will restart itself? Any an all assistance that you can give this SC would very much be appreciated. Thank you for taking the time to help. SM
 

VirtualLarry

No Lifer
Aug 25, 2001
56,571
10,207
126
Well, "hiberfil.sys" is used for Hibernation, not Shutdown. (AFAIK, it was Windows 8.1 or 10, that implemented "Fast Startup", along with "Hybrid Sleep", so that when you shut down, the contents of RAM were written to the hiberfil.sys, and then it went into a really low-power shutdown state, so that when you pressed the power button, it would restore back to running state quickly, and if power was ever fully removed, then it would restore from the hiberfil.sys instead.)

AFAIK, with Windows 7, this was never implemented, so I'm a little confused as to why you're getting errors writing to hiberfil.sys upon Shutdown in Windows 7, unless you explicitly chose Hibernate.

Anyways, I would do a disk check, and a surface scan, you may have disk errors, or your drive may be failing. You may want to back up your important data first, before doing that, as a disk-check can really screw up potential recovery, if you run it with the "/F" (fix) flag, with a failing drive with bad sectors.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,571
10,207
126
When it is shutdown the system will restart itself?
That could be:
1) Bad ACPI info, recorded by the OS, when it was installed.
2) Bad CMOS battery. (Replace it.)
3) Bad PSU. (Replace it, with a test PSU that is known-good first, then permanently if it turns out that fixes it.)
4) Bad drive. (BSOD during shutdown, triggers re-start during unfinished shutdown.)
5) Bad mobo. (Besides CMOS battery low, this is probably the second-most reason for causing this.)

I guess, I would start, by using a bootable RAM test (Win7/8.1/10 boot media can do this, I think.)
Then, do a surface-scan on the drive. If it turns up any bad sectors, then that's probably the reason.
Then I would check and/or replace the CMOS battery. (Checking it requires a DVM (meter), to check the voltage. Replacing it may just be easier.)
 

seamorton

Member
Feb 11, 2016
102
4
81
Well, "hiberfil.sys" is used for Hibernation, not Shutdown. (AFAIK, it was Windows 8.1 or 10, that implemented "Fast Startup", along with "Hybrid Sleep", so that when you shut down, the contents of RAM were written to the hiberfil.sys, and then it went into a really low-power shutdown state, so that when you pressed the power button, it would restore back to running state quickly, and if power was ever fully removed, then it would restore from the hiberfil.sys instead.)

AFAIK, with Windows 7, this was never implemented, so I'm a little confused as to why you're getting errors writing to hiberfil.sys upon Shutdown in Windows 7, unless you explicitly chose Hibernate.

I stand corrected. I received the message, as posted when I started/turned on the PC. Also, initally when I installed win 7 it was working quite satisfactorily - powering off and then starting up when needed. That was about 3 mos ago I installed the OS an about a week to two weeks ago this has started to occur. Now I have to switch off the PS to shut it down and to restart Win 7. Not the best approach. I've been updating updates as received.

I just replaced the battery but have not figured out how to scan or the HD for errors as when I try I get an message that the HD is running and to restart pc to scan??? There must be a better way as this does not work. Thank you! PM USAF 62-66
 
Last edited:

VirtualLarry

No Lifer
Aug 25, 2001
56,571
10,207
126
Well, if you open "Computer"/"My Computer", right-click on the C-colon drive on the right hand side, select Properties, then click on the tab labeled Tools, then click "Disk Check". It should prompt you to schedule a disk check the next time you reboot.

But if you're having trouble rebooting, that might be an issue.

Hmm. I would backup anything important, and consider wiping and re-installing Windows.

Is this a HDD or SSD? How old / used is it?

Edit: Maybe before reformatting and re-installing, trying disabling hibernate, and re-enabling it, or just leave it disabled.

From an Admin Command Prompt, type "powercfg -h off".
 
Last edited:

seamorton

Member
Feb 11, 2016
102
4
81
Thanks very much. I'll see what I can do? I've noticed that this problem comes up a lot more than we realize and not an easy one to resolve? Will try to keep you posted. PM
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
How out-of-date is the copy of Windows 7? Was this a system restore, full system reset, or Windows install only? If you only have Windows but haven't installed all the drivers, and/or are running Windows in pre-SP1 mode, that could be causing some of your problems.

Assuming all drivers are installed and Windows SP1 has all current updates, try this from an elevated command prompt and see if it helps:

powercfg.exe /hibernate off
https://appuals.com/enable-disable-hibernation-windows-7/
 

BarkingGhostar

Diamond Member
Nov 20, 2009
8,410
1,617
136
Well, "hiberfil.sys" is used for Hibernation, not Shutdown. (AFAIK, it was Windows 8.1 or 10, that implemented "Fast Startup", along with "Hybrid Sleep", so that when you shut down, the contents of RAM were written to the hiberfil.sys, and then it went into a really low-power shutdown state, so that when you pressed the power button, it would restore back to running state quickly, and if power was ever fully removed, then it would restore from the hiberfil.sys instead.)

AFAIK, with Windows 7, this was never implemented, so I'm a little confused as to why you're getting errors writing to hiberfil.sys upon Shutdown in Windows 7, unless you explicitly chose Hibernate.

Anyways, I would do a disk check, and a surface scan, you may have disk errors, or your drive may be failing. You may want to back up your important data first, before doing that, as a disk-check can really screw up potential recovery, if you run it with the "/F" (fix) flag, with a failing drive with bad sectors.
Not true. It is implemented, but it may be version-specific in Windows 7. For instance, on my copies of Windows 7 Pro 4-bit it is enabled by default, but as I migrated to an SSD boot drive I manually and permanently disabled it. I would find and disable hybernation and then try to power down. I would think disabled the 'thing' that is causing the problem would be ... interesting.
 

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
That's not what he is saying. Versions of Windows up to 7 used hiberfil.sys for the hibernate function only. Starting with Windows 8, the file was also used for Fast Startup.
 

BarkingGhostar

Diamond Member
Nov 20, 2009
8,410
1,617
136
I get that, but since he is using Windows 7 then it is presumably optional, and thence can be manually handled. Has it been tried? I'm not suggesting it permanently be terminated, but rather just to clear this buggy incident.
 

mikeymikec

Lifer
May 19, 2011
20,385
15,082
136
That's not what he is saying. Versions of Windows up to 7 used hiberfil.sys for the hibernate function only. Starting with Windows 8, the file was also used for Fast Startup.

One small modification: Hibernation and hybrid sleep (the latter is enabled by default, so therefore the former has to be as well if only for the hybrid sleep feature).

Hybrid sleep is a failsafe feature for sleep/standby mode: when the computer is put into sleep the contents of RAM are written to disk. This means that if the computer was to lose power while in sleep mode, the Windows session can be resurrected from disk.