Home > Faulting Module > Faulting Module Ntdll.dll Version 5.2

Faulting Module Ntdll.dll Version 5.2

There isn't a restrict within the amount of RAM that the computer system could have if it is a 64-bit operating process, but usually 4GB memory is plenty of. Marked as answer by eryang Monday, May 02, 2011 3:45 AM Unmarked as answer by eryang Wednesday, June 01, 2011 12:53 AM Wednesday, April 20, 2011 6:28 AM Reply | Quote I realize on customer machine, running Windows 2003 Server R2, that after a few days or hours, my application crashs. You may want to switch out nic(s) with a new one to see if you get the same errors. 0 LVL 9 Overall: Level 9 Windows Server 2003 5 MS Source

The overview also provides basic troubleshooting procedures to follow in order to resolve typical causes of Faulting Module Ntdll.dll Version 5.2 error codes. Once I did that the errors went away. Automatic System Restore will begin and restart the device once it completes. Related Sites Visual Studio Visual Studio Integrate VSIP Program Microsoft .NET Microsoft Azure Connect Forums Blog Facebook LinkedIn Stack Overflow Twitter Visual Studio Events YouTube Developer Resources Code samples Documentation Downloads https://social.msdn.microsoft.com/Forums/vstudio/en-US/d9c99e41-ff25-451e-9b48-d1621b238275/faulting-module-ntdlldll?forum=clr

Easiest way to fix Faulting Module Ntdll.dll Version 5.2 errors Two methods for fixing Faulting Module Ntdll.dll Version 5.2 errors: Manual Method for Advanced Users Boot up your system and login Join & Ask a Question Need Help in Real-Time? Does not apply when logged in via ms-remote.

This can cause active VMDg resources in a VERITAS or Microsoft Cluster to fault and result in a cluster failover. You would still use DebugDiag to get an analysis and follow the threads that are using the CPU. Join Now For immediate help use Live now! In cases like thjis one, the askers NEED to work with the experts... 0 How does your email signature look on mobiles?

check some of this: http://www.codeproject.com/KB/dotnet/unhandledexceptions.aspx http://www.codeproject.com/KB/exception/UnhandledExceptionClass.aspx Friday, June 03, 2011 11:54 AM Reply | Quote 1 Sign in to vote I would capture a dump at the time of the high Nope. If errors continue or no update(s) or patch(es) are available, contact the software designer or distributor for assistance. get redirected here Solution The solution requires the restart of the Veritas Enterprise Administrator Service.

Very strange. I am just saying that the idea is to save answers. Supported Products A-Z Get support for your product, with downloads, knowledge base articles, documentation, and more. Try that simple task first to see if it fixes the error code problem.

Try these resources. find this Kindly adivse us to fix these, would be great.Thanks in advance.Edited by: Dharshan s on 24-Oct-2009 08:23 1367-254150-1414124 Back to top Paul gasdas Members #2 Paul gasdas 4 posts Posted 17 All Rights Reserved Privacy & Terms Privacy statement Dev Centers Windows Office More...

To activate it, click the "Start" button and enter "memory" in the "Run" field. this contact form Close Login Didn't find the article you were looking for? If you want, you can also use ProcDumpto capture the dump, and use the switches so that it dumps automatically when the CPU stays high for a certain period of time. I believe some points should be awarded for the suggestions.

What are Faulting Module Ntdll.dll Version 5.2 errors? First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. and no matter that I hate this, I cannot recomend acceptance Sometimes the question is clear and the solutions are solutions. have a peek here Most common examples include: 1) incomplete software installation; 2) incomplete software uninstallation; 3) improperly deleted hardware drivers, and 4) improperly deleted software applications.

Thank You! Regards Tuesday, May 31, 2011 9:25 AM Reply | Quote 0 Sign in to vote By any chance, could this problem being caused by Remote Desktop Access? Storage Software SBS Windows Server 2003 Windows Server 2008 Xpdf - PDFtoPNG - Command Line Utility to Convert a Multi-page PDF File into Separate PNG Files Video by: Joe In this

But, keep the points, delete the question, whatever you have to do.

Suggested Solutions Title # Comments Views Activity RDP up only between 8am-13.00 pm ? 11 61 46d How to customise Office 2016 font settings with a GPO 3 55 41d Inserting Below are instructions to detect bad memory. Were there any other solutions? 0 Message Expert Comment by:benthomas2008-07-18 Comment Utility Permalink(# a22036208) Anyone ever resolve this? 0 LVL 9 Overall: Level 9 Windows Server 2003 5 MS Many applications require installation of memory management programs.

HTH Monday, June 06, 2011 10:31 AM Reply | Quote 0 Sign in to vote Thanks everyone, I will try what Michael suggested. From a command line window, run "net stop vxob"Rename C:\Program Files\Veritas\Veritas Object Bus\alertlog\alertlog.log to alertlog.log.oldRename C:\Program Files\Veritas\Veritas Object Bus\tasklog\tasklog.log to tasklog.log.oldRun "net start vxob" Terms of use for this information are found in Legal Please re-enable javascript to access full functionality. Check This Out I have a timer application that will delay my application start and I garantee that when the application starts I'm not remotely connected.

Win7 SP1. I'm using try/catch in order to log all the errors, but I cannot detect any problem. See http://groups.google.com/group/microsoft.public.windows.server.sbs/msg/17fba053e482d2ea TechSoEasy 0 Featured Post How to improve team productivity Promoted by Quip, Inc Quip adds documents, spreadsheets, and tasklists to your Slack experience - Elevate ideas to Quip docs Noone knows what had gone wrong with the asker's OS.

Insufficient RAM. Tried uninstalling every printer and printerdriver does not help. And that sometimes the Askers never return and the questions CANNOT be answered... I'm logging to file when start and end every procedure and I don't detect no procedure that as a start without an end, so I believe there is no infinite loop

in a XP machine.