RDP to Vista causes reboot/ crash
OS: Vista Business 64 bit SP1 (clean install with no added software, fully updated)I am trying to RDP into this Vista Machine from Server 2008. On the server side it connects, then disconnects never establishing the connection, never asking me for log on credentials.On the client side, if there is a user logged into the machine when the server attempts to connect a dialog box opens up that says "Windows has encountered a critical problem and will restart automatically in one min. Please save your work now" and then reboots the machine. If there is no user logged on then after a min the machine just reboots.
May 7th, 2009 7:17pm

This is happening on another Vista box as well, this one with just Vista Businiess 64 bit SP1. It also occurs from Vista to Vista in either direction. Any suggestions?
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2009 3:29pm

Hi J-Will, thanks for the post. Based on the error message, I suggest you first try the solution in the following thread: "Windows has encountered a critical problem and will restart automatically in one minute." http://social.technet.microsoft.com/Forums/en-US/itprovistaannouncements/thread/2f78de4d-5927-4a8b-95a6-34b0330bfc5a If the issue still occurs, you can also try a Clean Boot to troubleshoot the issue: 1. Click Start, type "MSCONFIG" (without the quotations) in the Search Bar and Press "Enter" to start the System Configuration Utility. Note: Please click Continue if the "User Account Control" window pops up. 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". 4. Restart the computer and test the issue. Note: Clean Boot is a troubleshooting step. If some programs have been disabled, we can re-enable them later. If you see the System Configuration Utility, check the box of "Don't show this message" and then click "OK". Please test this issue in the Clean Boot environment. If the issue disappears, we can use a 50/50 approach to quickly narrow down which entry is causing the issue. Hope this helps!Sean Zhu - MSFT
May 11th, 2009 9:54am

Thank you very much for your reply. I tried a clean boot and recieved the same outcome on both of my Vista machines. Both are fresh installs with no software yet installed, just Remote Desktops enabled.
Free Windows Admin Tool Kit Click here and download it now
May 11th, 2009 5:13pm

Hi J-Will, thanks for the update. Does this occur if you connect to other clients on Windows Server 2008? Have you disabled GBP service in msconfig by performing a Clean Boot? Meanwhile, I suggest you go through the troubleshooting steps on the following link if the computer cannot connect to the Windows Vista computer: http://windowshelp.microsoft.com/Windows/en-US/help/5c4f7ad8-40b3-452d-81ec-3a63453f0ada1033.mspx#EI Sean Zhu - MSFT
May 12th, 2009 11:20am

Sean thanks again... sadly still no solution from that link.Other OSs connected to the Server 2008 domain work fine, I have 4 XPs and I've tried 2 machines using Win7 RC. Again, those allow the Remote Desktops connecting and I'm able to login and work just fine. All of the machines are identical, so I do not think hardware is an issue. Also like I said, there is no software installed (yet) other than the OS. I checked the logs and I'm just getting a fairly generic Event ID: 6008 under System log.At the same time I get an Application Error that might be a little bit more helpful: Event ID: 1000Faulting application lsass.exe, version 6.0.6001.18000, time stamp 0x479195b7, faulting module ncrypt.dll, version 6.0.6001.18000, time stamp 0x4791ad6a, exception code 0xc0000005, fault offset 0x0000000000010f7f, process id 0x28c, application start time 0x01c9d25b100e4f80.And then right after that there isEven ID: 1015, Source WininitA critical system process, C:\Window\system32\lsass.exe, failed with status code 255. The machine must now be restarted.
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2009 5:03pm

Thanks for the update with the event log which shows that the crash occurred due to an access violation exception generated in ncrypt.dll. Also, I'd like to inform you that this should be a disk based corruption of the dll. To fix the issue, we can replace the file with a good copy by following these steps: 1. At an elevated command prompt, type the following command, and then press ENTER: takeown /f c:\windows\system32\ncrypt.dll 2. Type the following command, and then press ENTER to grant administrators full access to the file: icacls c:\windows\system32\ncrypt.dll /grant administrators:F 3. Type the following command to replace the file with a known good copy of the file (from a retail build of windows): copy c:\temp\ncrypt.dll c:\windows\system32\ncrypt.dll Hope this helps! Sean Zhu - MSFT
May 14th, 2009 5:17am

What processes are tied to that dll? It will not let me overwrite that dll as it is in use. I copied the ncrypt.dll from the server 2008 machine since I am not having this issue with that one. As it seems, that dll is in use from login.
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2009 4:50pm

Any update on this? You can not replace ncrypt.dll file using the instructions provided.
May 15th, 2009 2:31am

Hi, if you receive the error "file is in use", please use Windows Vista DVD or OEM disc and boot into recovery console and replace the file. Then, let's see if the issue is resolved. Sean Zhu - MSFT
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2009 5:50am

Yes, that finally did work!!!! Thanks a lot Sean!I still do not understand why that was needed. The Vista installs were brand new, I installed the OS enabled Remote Desktops and tried it out only to get the error. And this happened on the 2 Vista machines. So unless them came off the Vista DVD that way, I just do not see why replacing that file wasthe issue.Anyway, it is fixed! Thanks again
May 15th, 2009 6:13pm

Hello, I am still a bit confused with this...so I am now in the recovery console it says x:\ What do I do after that? I went to the c: prompt and typed in takeown /f c:\windows\system32\ncrypt.dlland it says its invalidand why would I be copying the .dll from a temp folder?This is urgent, thanks
Free Windows Admin Tool Kit Click here and download it now
May 28th, 2009 7:43pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics