I'm having problems with crashing or exceptions during the logon process. Typically if the domain workstation cannot reach it's domain controller/DNS.May be due to a credential provider interaction.Because there is no user, it seems that WER doesn't want to create a dump.I wantto setup so thatdumps are produced,and/or someway to get a debugger on the exception.This is happeningin system from boot time. So I cannot use a technique that requires interactive setup.Dave.

HiThis might help you.http://support.microsoft.com/kb/244139/Johan

Hi , Thank you for your posts. This should be a kernel mode crash issue. To troubleshoot this kind of kernel crash issue, we need to debug the crashed system dump. Unfortunately, debugging is beyond what we can do in the forum. I'd like to recommend that you contact Microsoft Customer Support Service (CSS) for assistance so that this problem can be resolved efficiently. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. Having said that, I'd still like to provide the following suggestion to see if we can eliminate this problem: 1. Scan your system to make sure that the system is virus free. Temporarily disable your security software (Anti-virus software, firewall, etc.) to see if this problem is gone. 2. If you have recently installed any software, hardware or drivers, please remove them. 3. This issue can also be resulted by the factor that some third party software confliction. Please perform a clean-boot environment to narrow down this issue. Clean boot ================= 1) Click the Start Button type "msconfig" (without quotation marks) in the Search box, and then press Enter. Note: If prompted, please click Continue on the User Account Control (UAC) window. 2) Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray). 3) Click the "Startup" tab, click "Disable All" and click "OK".Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK. NOTE: we can go back to normal boot by running msconfig again and checking on Normal Startup in the General tab. In the Clean Boot Environment, the third party services and applications are disabled, please check if the issue reoccurs at this time. If the problem does not occur, it indicates that the problem is related to one application or service we have disabled. You may use the MSCONFIG tool again to re-enable the disabled item one by one to find out the culprit. If everything worked before, a quick solution is to restore the system back to the previous status when the issue didnt occur with System Restore. (Note: Performing a system restore may cause the loss of the current system settings; therefore, before doing this, please make sure that the system restore point is not too old and set a restore point for the current status.) However, if the issue still persists, please contact Microsoft Customer Support Service (CSS) for further troubleshooting. I hope the problem will be resolved soon. Thanks.Nicholas Li - MSFT

LogonUI.exe runs as a process, I think a child of Winlogon.exeThe problem is that the user's desktop and session contexthasn't been created yet.I have spent several days fussing with combinations of command line parameters for ntsd, along the lines of help file documentation and guides for Winlogon debugging to get a setup that seems to work. (I now also know several waysto fix a Vista registry on a screwed up system ;^} I'm trying to use remote debugging, but it seems to work without.The nature of the problem seems to be related toexceptions thrown by various components logonui is calling, because the RPC to the domain is not working. Most are handled. But some sometimes cause a hang. In particular wlanutil.dll seems to be the last called before an occasionalhang. I can now force a crash dump with ntsd, or I will also try the above trick on system that aren't instrumented with full debugging tools.I will take these dumps to my Premiere support, FWIW ...I can't debug logonui.exe but I am looking for hints that my code may/may not have contributed to it's confusion.Dave.