[mikhot]

Alright, PM sent.

[MagicAndre1981]

Ok, the cause is the resume of the devices:

- <device start="714224072" duration="118183136" name="ACPI_HAL\PNP0C08\0">
  <driver start="714224076" duration="118183128" name="\Driver\ACPI" /> 
  <driver start="832407205" duration="1" name="\Driver\ACPI_HAL" /> 
  </device>

in your case the ACPI device. Have you install the latest ATI/AMD drivers for your mainboard?

[mikhot]

Thanks for the feedback! Yes, I recently installed the newest northbridge driver from ASRock's website. Tried to browse AMD's site for chipset drivers but it seems it's best to use the ones from the manufacturer. idk..probably an updated acpi driver could solve the problem.

[mikhot]

Just to make sure, is the xbootmgr -trace hibernate -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP -command supposed to hibernate AND reboot the computer by itself? Because that's the way I understood it. I let it be for 30 mins or so and when it hadn't woken up by then, I turned it on myself. The resuming from hibernate to desktop then took about 3-4 mins.

[MagicAndre1981]

yes, the tool wakes up the again. Which ASRock board do you have?

[mikhot]

I have the ASRock M3A790GXH/128M.

[MagicAndre1981]

are you using the latest BIOS? Write a mail to the support if you have the latest BIOS version

[Kraxxis1]

I've recently reinstalled Windows 7 and it's taking a long time to shutdown.
I've ran a trace and here is where the file is available and the file passworld is
1344.
My link
It someone could look at this I would appreciate it very much.

Thanks. Charlie

[MagicAndre1981]

I can't extract the trace file. Is the password correct? upload it again without password

[Kraxxis1]

Sorry about that. The password is 1334.

thanks.

[MagicAndre1981]

Hi, you have the same issue like the user supjack.

  <interval name="ZeroHiberFile" startTime="17352" endTime="140686" duration="123333" /> 

I don't know why Windows overrides the hibernation file with 0. This takes some time (123 seconds) for your 4GB hibernation file.

[MagicAndre1981]

Hi Kraxxis1,

you should contact the Microsoft Support about this issue. This looks like a bug.

[supjack]

I'll be calling and paying for MS support to look this into today. One thing I did notice about this is that the issue creeps up after adding the PC to the domain. However once you add the PC to the domain MS will not help resolve anything without agreeing to pay a per incident fee or having an business support contract, free installation support is available for the OS as long as the OS has not been setup as a member of a domain.

[MagicAndre1981]

ok, can you post the result of the investigations here? I would also like to know the cause of it.

[supjack]

Will do, am filling out the request for MS support web form on the support.microsoft.com now.

[supjack]

MS paid support will not help fix until we upgrade the domain controller. They went through everything I did all over again to confirm that the issue is after adding the PC to the domain. Its not third party software or user tweaks after the install. Something with the add of the PC to the domain makes a change in the PC so that it now looks for a hybernation.sys file which does not exist so it just sits and spins. The over all feeling that I got as a result of the time spent with MS support was that once they had a BAILOUT they took it. I my gut tells me that an upper level tech more or less told the person I was working directly with that its a $$ loser support call due to the need to get deeper into things and to just dump it and move on over to another support request in the queue.........being that Win 2000 is no longer supported thats the BAILOUT. I doubt its an issue with Win 2000 because we have a couple of physical and virtual Win 7's working on the domain.

[MagicAndre1981]

so you use a Win2000 DC and included Windows 7 in it?

[supjack]

Yes for now we have a Win 2000 domain. We have a couple of Win 7 boxes running without this problem. Trying to move to Win 2008 SBS but we have issues with the changes MS made with how things work with Unix. Were not using a sophisticated file sharing setup here, or a sophisticated active directory. It used to be that we could just use simple mapping via the services for Unix application to allow a couple of accounts on the Unix system to put files out on the shared drives. MS has changed things in that it now requires a more detailed and in depth server configuration and network setup to play nice with Unix. I'm going to try and just muck with the system on my own today to see if I can figure out why after adding to the domain that the system changes with regards to hibernation. I'm thinking that I may use a sysinternals utility to watch what gets changed on the machine when added to the domain. I have confirmed that I can remove it from the domain and the shut down issue goes away, and then comes back again after again adding it.

This post has been edited by supjack: 23 August 2010 - 06:57 AM

[MagicAndre1981]

ok, the boot trace includes the Domain Info, the shutdown trace not. So I was not able to see this.

[Prodeje79]

MagicAndre1981, on 10 August 2010 - 09:56 AM, said:

temporarily disable SSDP and UPnP and check if everything works fie

ok trace4, same password.
disabling didn't seem to make it any faster nor take away the issue.
http://cid-5f415a3ae...asPC/Trace4.rar

Basically the PC has to fall asleep after a full restart, then it starts working OK.