Laptop shuts down when sleep is selected

Investigating the issue of my work laptop sometimes rebooting when I try to use Sleep for travelling it. This is because Windows took the "Hybernate" option away, however I learned that it is possible to manually call the hyberbnate function from a CMD window using "shutdown /h". The rebooting while sleeping seems most likely to be due to damage to the laptop's motherboard.

This is an article titled with the exact problem that I was trying to solve. It had pretty much the same solutions as a lot of other related pages, which were to fiddle with power settings most of which I couldn't touch due to the group policy settings on my laptop: https://www.guidingtech.com/fix-windows-10-shuts-down-instead-sleep-hibernating/

I was unable to get around the group policies to try to turn off "fast startup". Here are a few searches that I tried on the topic. The hints, while unsuccessful, were interesting and I'd like to learn more:

turn off fast startup from command prompt: https://www.bing.com/search?q=turn+off+fast+startup+from+command+prompt&qs=AS&pq=turn+off+fast+startup+from+c&sk=AS1&sc=2-28&cvid=7C0CE2BE4176472982CB018F0BAC4ACA&FORM=QBRE&sp=2&ghc=1

powercfg -h off unable to perform operationhttps://www.bing.com/search?q=powercfg+-h+off+unable+to+perform+operation&cvid=de3e7676a2b54113b4fc6159bdf1b712&FORM=ANAB01&PC=U531

Windows restart hangs on zombie process

Thanks to the indefensibly badly written drivers in QuickUSB, the workstation froze when I tried to reboot it. Here are the spoils of a half a day trying to find some solution. The short answer is that I was hosed without any recourse the moment the driver failed to get a response. All I have to console myself with is having learned a few things.

First off, taskman fails to kill the process that calls the QuickUSB libraries; the process just continues on.

The basic alternative tools available apparently do the same things that taskman would try, so they don't work either. Here's a few forums that pointed the start of this path.

This author suggested pskill, and the remainder of the post is frustrated users hurling insults at the author when it didn't work.

http://www.watchingthenet.com/how-to-kill-windows-processes-that-wont-die-or-terminat.html

This author suggested taskill, and the remainder of the post is frustrated users hurling insults at the author when it didn't work.

http://www.tech-recipes.com/rx/446/xp_kill_windows_process_command_line_taskkill/

pskill and taskkill are very nice utilities, however, and ship standard with XP pro. I tried using taskkill with parameters to operate on all processes for my userID and it still wouldn't kill the dead I/O processes; it killed everything except those. I eventually got taskman to launch, and used it's "run" function to get some IE's, cmd windows, and file explorers going even without a desktop! At some point the desktop just magically reappeared.

One of the commenters in the above threads suggested a fancy piece of freeware that has something like 16 kill methods, called apt for Advanced Process Termination. I tried it but it didn't work for me.

http://www.pendriveapps.com/advanced-process-termination-kill-running-processes/

Here is the best forum thread that I found on the topic, containing some actual signal. Some commenters futilely attempt to explain how a driver that's waiting on a response causes this problem (which matches what I'm dealing with) and exactly why normal process killing tools don't affect it. The thread is several dozen pages long and I was hoping that somebody somewhere would reveal a magic bullet for this kind of "zombie thread" but sadly nobody seems to have anything aside from cursing microsoft up and down.

http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/598fe2b4-844d-412d-b195-5fa53dc62661

Someone mentioned Process Explorer, which suspiciously somebody before me had already put in the downloads folder on this workstation. I tried it, it could find the zombie thread, but it couldn't terminate it. Hoever, Process Explorer sure is gorgeous.

http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/598fe2b4-844d-412d-b195-5fa53dc62661

Oh yeah, I also tried attaching debuggers to the processes, calling the debugger from a cmd window using the -p option but they said access denied.

Drive failing

The BSOD error provided by the XPS is STOP Error 0x0000006f Session3_initialization_failed. Here are the first two results from googling it:

http://forums.techarena.in/windows-xp-support/867056.htm
http://forums.techguy.org/windows-xp/764365-session3_initialization_failed-bsod.html

They suggested trying Safe Mode to search for removed drivers, but in fact the drive on the PC makes a sickening thudding sound when I started in Safe Mode, so the reason why it can't find the drivers is physical and it was unable to complete Safe Mode startup.

I'm planning on getting around this by buying a new drive and cloning my working XPS onto it. The existing drive is a Seagate ST3160023AS, which is a 160G 7200RPM SATA 8MB Cache drive. I could buy that one still (the WD3160318AS seems equivalent also), or buy the WD equivalent, which seems to be part number WD1600AAJS. The advantage of the WD drive is that I can download their clone tool, which worked great the last time I tried it in the W98 era:

http://support.wdc.com/product/downloaddetail.asp?swid=119

Not enough quota available to process this command

Presently unresolved thread for tracking a recurring error on one of the work XPS's.

The error is is not accessible. Not enough quota is available to process this command.

Once this is received, the only thing that can be done is close all programs and reboot the machine.

It is somewhat interesting that this is an XPS that has more memory than the others.
The hardware and software configuration is otherwise identical to the others, and no dissimilar programs are being run (Labview, Word, PDF Reader).

The interwub doesn't have a consensus to the problem, but the disparate postings and answers may all point to a common solution if I could just figure it out.

Nobody has fingered this as a virus issue.

First off is M$'s patronizing KB article:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/1495.mspx?mfr=true

Also here:
http://msdn.microsoft.com/en-us/library/ms820778.aspx

This thread:
http://74.125.95.132/search?q=cache:tBeocXxTxcEJ:forums.ni.com/ni/board/message%3Fboard.id%3D170%26thread.id%3D258595+Not+enough+quota+is+available+to+process+this+command&hl=en&ct=clnk&cd=7&gl=us

points to two interesting process monitoring options aside from good old Taskmon, including this one which seems well loved but looks useless:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

These guys trying to troubleshoot their software:
http://forum.sysinternals.com/forum_posts.asp?TID=4975

Have traced it to Access Control List problems? See these two:
http://groups.google.de/group/microsoft.public.win32.programmer.kernel/browse_thread/thread/a024fb3948d5943d/ba4e698efab83ada?lnk=st&q=%22Not+enough+quota+is+available+to+process+this+command%22&rnum=9&hl=de#ba4e698efab83ada
http://support.microsoft.com/kb/185292/en-us

These guys are trying to do simple file copies in Vista and having the problem, and traced it to something to do with offline file sync?
http://social.technet.microsoft.com/Forums/en-US/itprovistaapps/thread/c6c79225-dd97-41ce-aeb2-b3f46f235872/

Perhaps most promising for my configuration, this guy blamed it on Dell Control Utility:
http://discussions.virtualdr.com/archive/index.php/t-129176.html