[SnyderXC]

Hey all,
I'm new here, so thanks in advance for your help. I am using SetPower Free to hibernate my computer and resume my computer depending whether I am typically home at a time or not. While I am not sure whether my problem is directly related, I figure I should also mention that I recently installed a stick of 1GB DDR RAM on this computer. Now, within minutes of SetPower Free resuming my machine, it crashes and produces a BSOD. There have been various drivers that have been noted as the problem. Most recently, I have received several "ntfs.sys" related crashes.

SetPower Free Runs my system on the following schedules:

• Resumes at 7 AM (Sat, Sun)
• Hibernates (After 20 Minutes of non-use) at 10 PM (Sat, Sun)
• Resumes at 6 AM (Mon, Tue, Wen, Thur, Fri)
• Hibernates (After 20 Minutes of non-use) at 7 AM (Mon, Tue, Wen, Thur, Fri)
• Resumes at 2:35 PM (Mon, Tue, Wen, Thur, Fri)
• Hibernates (After 20 Minutes of non-use) at 10 PM (Mon, Tue, Wen, Thur, Fri)

I have also run CPU-Z

Both the CPU-Z Report and the minidumps are attached.

[CJS23]

Were you able to Hibernate / resume successfully before installing this Application?

[SnyderXC]

I was able to, I think that this is probably related to my RAM, except for the NTFS.sys error.

[CJS23]

If you were able to do this before then uninstall your new app and try again.

If you can Hibernate / Resume successfully, then the problem must lie with the software.

I'm no expert on power saving but most BIOSs are set to S3 settings where S1 seem to be more successful.

Worth a look.

[SnyderXC]

Thanks for the response, I will first try manually hibernating it to see if SetPower is the problem (Temporarily Disable scheduled power setting changes and such). If that doesn't work, I will resort to standby, although, I like the fact that Hibernate (S3) doesn't rely on having a constant power source while standby (S1) does.) Am I missing something about the S3 vs S1 thing? Or do I have it correct? Thanks again!
SnyderXC

[CJS23]

Aha - this is where the confusion may lie.

When you hibernate the ENTIRE contents of your RAM are written to a file called hiberfile.sys .

After Hibernation, the PC shuts down and you can safely unplug it / remove laptop battery.

When PC boots it simply "recreates" where you were based on hiberfile.sys

Basically, the following options normally work for me

1. Set to S1 in BIOS
2. Hibernate from Start Menu

That's it - lol

on a small point, are you removing any USB devices after Hibernation? I heard of a case where someone used to Hibernate and then remove a flash pen. When the system restarted it used to freak out (BSOD) when it discovered no flash pen was present.

[SnyderXC]

Thanks!

Good news today, I manually hibernated and resumed my computer with no problems. Maybe the program is causing the problems. I'll see about reporting it.

In theory, should that still work if I set to S1 and the computer automatically hibernates? (Based on idle time) And no, I'm not using a flash drive or anything. Although, I will remember that for future reference.

[CJS23]

Try setting to S1 and installing your program again. Or read FAQ's of Program. Do they ask you to disable Windows Hibernate?

[SnyderXC]

Thanks for all your help! I'll just do it manually for now I guess, and I'll report the problem to the creators. Hopefully, they can give figure out why exactly it is happening. I neglected to mention that I also have a scheduled task on computer lock to open "C:\Windows\System32\tsdiscon.exe" which takes the computer to the switch user/disconnect screen. I disabled that and it was fine, that is, until I tried to log on. I put in my password and, BOOM, BSOD. It seems to be something with accessing files after hibernate. My Win7 RC Installation is on my slave drive "D:/" do I need to do something to make sure Windows powers all my drives? I did find hiberfil.sys on both drives, so I don't think that's the issue.

[Rollin' Rog]

Be advised "NTFS" errors being file system issues are frequently the result of bad blocks, sectors, or corrupt files on the disk.

In your case, this may even include some system files.

You should run chkdsk on the drive and also check the Event Viewer > (run eventvwr.msc) > System Log for NTFS errors that might indicate bad blocks.

After running chkdsk, it might also be a good idea to run

sfc /scannow which will check for corrupt system files. It may complete without any prompts if it doesn't need your help in finding anything. It still may replace corrupt files.

The log for chkdsk will be available in the Event Viewer > Applications log > Wininit entry after chkdsk completes and reboots.

You can examine and copy/paste that log here.

[SnyderXC]

Check disk didn't find any errors.

sfc /scannow produced the following:

D:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

The system file repair changes will take effect after the next reboot.

I have also stopped the computer from turning off my hard disks, so hopefully that will work! Thanks!

[Rollin' Rog]

See what it fixed and what it couldn't; typically the the can't fixes, relate to add-ons and widgets and are not critical.

Also keep in mind that when you hibernate, as opposed to "sleep" you are storing the entire contents of system memory on the hard disk, do you really need to do this? -- the amount of power saved is probably minimal.

And file fragmentation can cause additional delays and problems in resume -- so if you are going to use it, you should probably defrag the disk more often.

[CJS23]

Originally Posted by SnyderXC

Check disk didn't find any errors.

sfc /scannow produced the following:

D:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of th
em.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

The system file repair changes will take effect after the next reboot.

I have also stopped the computer from turning off my hard disks, so hopefully that will work! Thanks!

I had the exact same problem ( http://forums.techguy.org/windows-vi...d-control.html ) and it turned out to be a dodgy RAM chip.

Download Memtest 4.00 and leave it running for at least an hour.

http://www.memtest.org/

[SnyderXC]

Alright, I'll run Memtest, but things seem to be good now! After disabling the Hard Disk shutdown thing, it hasn't crashed! Yay!

[SnyderXC]

Memtest Turned up no errors! Yay! (got to over 1500%)