Sleep issues (never powers off)

chief7 · 04 Aug 2011

I'm having an issue with my sleep/restart/shut down functions.

-if I choose to restart the computer shuts down
-if I choose to shut down or sleep the screen goes black, the fan runs and the keyboard is not responsive (caps lock doesn't register when clicked)

i haved tried the following with no luck:

-hardware diagnostics
-enabled turning off of wireless network adapter
-updated video drivers (nvidia)
-disabled hibernate sleep

If I attempt to shutdown from safe mode the screen locks on the "Shutting down ..." screen.

Any help would be most appreciated.

usasma · 05 Aug 2011

Update chipset and storage drivers
If that doesn't help, please provide this info (even though you're not seeing BSOD's): https://www.sevenforums.com/crashes-d...tructions.html

chief7 · 05 Aug 2011

All drivers are up to date.

Is Windows 7 Ultimate x64
- the original installed OS - OEM Win 7 Home Premium x64
- What is the age of system (hardware)? - 2 weeks old
- What is the age of OS installation (have you re-installed the OS?) 1 week

usasma · 06 Aug 2011

The upload isn't complete. Please re-run the procedure again and let it run to completion (it may appear like it's frozen/not working - but it's still doing stuff!).

I did get one memory dump and the dxdiag report, so here's what I suggest so far:

Get all available Windows Updates. I don't know if any are missing, but many problems are solved by getting updates. Do this after updating/replacing the storage and chipset drivers.

Uninstall Daemon Tools/Alcohol 120% (only 1 indication that this is installed) - the sptd.sys driver that they use is known to cause BSOD's in Win7 systems. Once it's uninstalled, please use this free tool to ensure that the offending sptd.sys driver has been completely removed from your system: DuplexSecure - FAQ - Remove 64 bit sptd.sys

Interestingly, I've never seen this error before. Here's a link to what little info I have on it: BSOD Index
This seems to relate to a boot volume without enough free space to handle a Virtual Hard Drive
Yet you have more than enough free space on all 3 of your drives (according to the dxdiag report) - the boot volume has 61 gB free. But the NTStatus message c000007f means that the system has returned the message that the disk is full.

Were you trying to mount a Virtual Hard Drive? If so, what size was it supposed to be once it was mounted?
The memory dump shows at a VHD Miniport Driver (vhdmp.sys) is loaded when the crash occurred.
I wonder if the system is trying to store the VHD in the pagefile (wild speculation on my part) and it's too large for that (although the pagefile isn't a drive).

Is the BSOD/freeze/lockup on shutdown nearly 100% predictable? If so, we may want to use Process Monitor to see what's happening at shutdown.
EDIT: I haven't found much on using Process Monitor for this, but have found this: http://www.windowsitpro.com/article/...-with-xbootmgr

As above, update chipset and storage drivers (remove them first, if possible). This includes any disk protection devices containing an accelerometer (Disk Class Filter Driver for Accelerometer by ST MicroElectronics). I'm pretty much convinced that this is a disk sub-system issue - but am uncertain as to exactly what component is causing problems. The remainder of the report(s) requested above may help us to find the offending component.

Finally, I'd test with different Virtual Machines to see if it's just one that does it - or if it's all of them.
I'd also suggest removing the Virtual Machine program and then reinstalling a fresh copy (and then testing it again).

OLDER DRIVERS PRESENT IN THE DUMP FILES
- Create a System Restore Point prior to doing any of this. DO NOT mess with the drivers themselves - leave the Windows\System32\drivers directory alone unless we specifically direct you to it!
- Please update these drivers from the device manufacturer's website - or uninstall them from your system. Reference links are included below.
- DO NOT use Windows Update or the Update Drivers function of Device Manager.
- Please feel free to post back about any drivers that you are having difficulty locating.
- Windows Update exceptions may be noted below for Windows drivers:

Code:


amdxata.sys   Fri Mar 19 12:18:18 2010 (4BA3A3CA)
vhdmp.sys     Sat Nov 20 05:35:36 2010 (4CE7A478)
FLTMGR.SYS    Sat Nov 20 04:19:24 2010 (4CE7929C)
FSDEPENDS.SYS Mon Jul 13 19:26:13 2009 (4A5BC295)
stdcfltn.sys  Fri Aug 20 14:05:01 2010 (4C6EC3CD)

http://www.carrona.org/dvrref.html#amdxata.sys
http://www.carrona.org/dvrref.html#vhdmp.sys
http://www.carrona.org/dvrref.html#FLTMGR.SYS
http://www.carrona.org/dvrref.html#FSDEPENDS.SYS
http://www.carrona.org/dvrref.html#stdcfltn.sys

BSOD BUGCHECK SUMMARY

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\080211-17830-01.dmp]
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Debug session time: Tue Aug  2 06:38:46.903 2011 (UTC - 4:00)
System Uptime: 0 days 0:00:12.778
Probably caused by : FSDEPENDS.SYS ( FSDEPENDS!DepFSAutochkWaitWorker+3d2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x136
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x136_FSDEPENDS!DepFSAutochkWaitWorker+3d2
Bugcheck code 00000136
Arguments 00000000`00000000 ffffffff`c000007f 00000000`00000000 00000000`00000000
CPUID:        "Intel(R) Core(TM) i5-2410M CPU @ 2.30GHz"
MaxSpeed:     2300
CurrentSpeed: 2294
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

usasma · 06 Aug 2011

PS - don't forget to submit the report in the Action Center to Microsoft - it may come back with some useful information.

chief7 · 06 Aug 2011

I tried to submit the report in the Action Center but it said it needed more information which I confirmed and then it failed due to some error.

I'm up-to-date on all windows updates.

Its not Daemon Tools because I have a second bootable partition without any software installed and it has the same issue.

Now the VHD error may be the issue. I was testing bootable VHDs and at one point had a VHD that was giving a similiar error. I have since fixed that issue and can now boot into that VHD. Do you think we should rebuild the boot configuration?

I downloaded the xperf tool and can run it if you like. Im just not sure which parameters/flags to use.

chief7 · 06 Aug 2011

i figured out what happened, i ran the app from a folder other than my docs. so the results were split between the my docs folder and the folder i ran it from. the missing half is attached.

usasma · 06 Aug 2011

Daemon Tools drivers are resident in memory - so when the system crashes we can't tell if it's Daemon Tools drivers or not. Please remove the program (and the sptd.sys driver) while we're troubleshooting. Feel free to reinstall the latest compatible version once we're done.

I'd run xperf exactly as the article describes. That's the only experience that I have with it - and haven't had the opportunity to run it on my own system.

I don't think that it'd hurt to rebuild the BCD - but am not sure if that would pertain to this. The problem is that the OS is saying the hard drive is full when it's not. IMO this could either be an issue with the boot OS, or it could be an issue with how the virtual OS communicates with the boot OS.

How did you fix the issue in the VHD? Rebuilding the BCD? Have you tested to see if it's a single VM that does this - or if all of your VM's do this?

I noted that you have a partitioning utility installed on your system. Have you been changing things that involved the boot partition?

chief7 · 06 Aug 2011

Okay, I uninstalled Daemon Tools and verified it was uninstalled.

I ran xperf and funny enough the laptop shutdown appropriately (no hang at the black screen) during the test. At first I thought, uninstalle Daemon must have fixed it but I shutdown again and had the same issue. I have attached the xperf results.

I fixed the VHD by resizing the VHD. I had made a copy of the main partition/OS with disk2vhd which creates an exact copy of the disk including sizes. When I tried to boot from this VHD it said there wasn't enough disk space to load it. So I resized with "VHD Resizer" and then it worked. I am running my main OS from disk and have a couple VHD i boot to occasionally. I have a second OS on disk as well. All 4 (2 on disk, 2 vhd) have the shutdown/sleep issue.

The main OS runs on a partition of the main disk. I created the partiion before installing the OS.

usasma · 07 Aug 2011

I first suspect something in disk2vhd or VHD Resizer. I tried disk2vhd once and it gave me fits, so I didn't try it again.
It could be that the disk2vhd program doesn't mark things correctly - and the VHD Resizer fixes just enough (but not all) to make it work.

But, since it occurs on all VHD's, this would only hold true if you used disk2vhd on all virtual machines.

BUT, you have the issue on 2 OS's also - so that makes me wonder about hardware, compatibility, or boot sector issues

Could you delete the xperf log file and run it again. What I'm looking for is one that we know is a trace of the bad shutdown - without any possible influence from a previous good shutdown. This is because I don't notice anything wrong in the xperf shutdown trace - at least nothing that would indicate a serious problem.

Just a guess, but have you run Windows 7 Startup Repair in the volumes? Run it at least 3 times, rebooting between each try.

I have the black screen on Sleep issue occasionally on my system (I always use Sleep) and couldn't fix it even with a new mobo and fresh OS installation. I attribute it to disk problems, but can't even figure out where they are coming from (I removed my RAID card and installed Win7 "by the book")

I have no idea if this'll give us any more info, but try running the system and VHD's while using Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Special Pool" and "Low Resource Simulation" and click "Next"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users