New
#11
I did get a trace, and the machine sleeps (according to the trace) for less than one second - at 4.8 seconds into the trace, there's a sleep notification, and then at ~5.7 seconds there's wake activity. However, driver notification doesn't happen until about 56 seconds into the trace, and the CPUs are idle for that whole time (basically - a few ms at the beginning of activity on CPU 0, which is scheduling activity). I also see the last device slept before the long delay is the USB root bus driver, and Symantec's nsiproxy.sys driver. The machine does indeed wake due to this bus coming online:
"\Driver\umbus"
"\Driver\umbus"
"UMB\UMB\1&841921d&0&PrinterBusEnumerator"
"UMB\UMB\1&841921d&0&IPBusEnumRoot"
Note that the Symantec driver, even though the machine is totally "awake" at ~7 seconds into the trace, completely blocks all service activity until ~56seconds into the trace, so you might want to consider that as part of the problem (it is). Ultimately, however, the question really is, what do you have attached to the USB bus on this machine? This is actually possible to be a BIOS/hardware issue (Windows 7 is a lot more touchy about USB hardware, specifically, than XP or Vista was), but it could be a device plugged in as well.