DWWin.exe failed to initialise because Windows is shutting down

[rirusstek2]

..... and the "Shutdown" takes forever.

Windows XO Pro SP3 ...

I have tried looking in Event Manager and disabled Error reporting on Services and Disabled Dr. Watson through the Registry in AeDebug but the DWWin.exe failed to initialise because Windows is shutting down keeps popping up and the Shut Down takes an eternity.

Any suggestions?

Thanks.

 

[rirusstek2]

its Windows XP Pro


I've also done sfc /scannow

 

[rirusstek2]

Looking for an answer I found this page ...

http://www.aumha.org/win5/a/shtdwnxp.htm

Tried some of the suggestion but with no luck.

Still get that DWWin.exe failed to initialise because Windows is shutting down

 

[wahnula]

rirusstek2

Try reading through this thread to see if it's of any help. I didn't take the time to read through it, but there certainly are lots of responses.

Tony

Users helping Users...

 

[linney]

DWWIN.EXE
thread779-733966

I can't link to the above post because it is old and more to the point missing, so I have quoted the whole post for your perusal.


QUOTE.......

DWWIN.EXE
thread779-733966

Read
New Posts Reply To
This Thread
E-mail It
Print It Next
Thread
bellini (TechnicalUser) Dec 19, 2003
I'm running XP Pro and I'm getting the error-dwwin.exe could not be started because the windows station is shutting down.

I get this error every time I shut down the PC...it pops up just before the screen that says windows is saving settings, shutting down, etc.

Does anyone know how to fix this?


Thank bellini for this valuable post!


Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!




Start Your Own Tek-Tips Group! Click Here!
bcastner (IS/IT--Manageme) Dec 19, 2003
To turn off the Dr Watson debugger, apply the following Windows NT / Windows 2000 / Windows XP registry hack:

Hive: HKEY_LOCAL_MACHINE
Key: SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug
Name: Auto
Type: REG_DWORD
Value: 0 disable
Value: 1 enable

To re-enable Dr Watson, you can change Auto back to 1 or from the command line type drwtsn -i.

It is likely though that your system is trying to throw a stop error. Look in Control Panel, Event Viewer, in the System log entries to see if a critical stop error has been generated.



Thank bcastner for this valuable post!


Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!



linney (TechnicalUser) Dec 19, 2003
See if any of these help you.

http://www.abxzone.com/forums/showthread/t-24408.html

http://aumha.org/win5/a/shtdwnxp.htm

308029 - Resources to Help Troubleshoot Shutdown Problems in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us...

310353 - How to Perform a Clean Boot in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us...

316434 - HOW TO: Perform Advanced Clean-Boot Troubleshooting in Windows XP

http://support.microsoft.com/default.aspx?scid=kb;en-us...

Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!



bellini (TechnicalUser) Dec 19, 2003
My thanks to bcastner and linney for the advice. I found the problem to be caused by a program called, "Actual Title Buttons." It has been uninstalled and the problem went with it.


Thank bellini for this valuable post!


Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!



dickcu (TechnicalUser) Dec 23, 2003
I have had this problem for several months now. Some have cured the problem with Registry edits. With others this hasn't worked. I tried the edit that bcastner suggests and it didn't work for me. I would be more than welcome to try any other suggestions. I've spent many hours trying to solve it. While it doesn't do any harm it is an annoyance I'd like to eliminate.


Thank dickcu for this valuable post!


Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!



bcastner (IS/IT--Manageme) Dec 23, 2003
dickcu,

Control Panel, Event Viewer, check all the logs at the time of shutdown (or create a shutdown event) and post back as to what red marked events appear in the logs.



Thank bcastner for this valuable post!


Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!



dickcu (TechnicalUser) Dec 24, 2003
I get the following two similar system error messages in Event Viewer on reboot.

DCOM got error "The service database is locked. " attempting to start the service ccPwdSvc with arguments "" in order to run the server:
{DBA28A20-5CE1-4E8D-AD35-418B62269E54}


DCOM got error "The service database is locked. " attempting to start the service netman with arguments "" in order to run the server:
{BA126AE5-2166-11D1-B1D0-00805FC1270E}

After posting I did a clean boot and through the process of start-up elimination traced the DWWIN message at reboot ("DWWIN.EXE has failed to initialize because the windows station is shutting down.") to the application "iHatePopUps." I had done this before and found nothing. This time I was apparently more careful. So while I've eliminated the rebooting Dr. Watson error message I still have a queston. Is the Event Viewer error messages anything I should be concerned with?

I'm running Windows XP Pro on an Athlon 3200+ CPU.
Thanks again for your help!



Thank dickcu for this valuable post!


Inappropriate post?
If so, Red Flag it!


Check out the FAQ
area for this forum!



bcastner (IS/IT--Manageme) Dec 24, 2003
As per Microsoft: "These error messages are generated because another application, such as Microsoft Transaction Server, has already started the Dcom (the Distributed Component Object Model) Service. These messages do not indicate an actual problem and are benign."

See:

http://www.eventid.net/display.asp?eventid=10005&source...

Thank bcastner for this valuable post!

END QUOTE......