dudrick
Apr 29 2005, 11:11 AM
I would greatly appreciate getting advice on how to correct the system errors that pop up on my Dell desktop with the above operating system.
An example, "The application could not be handled by the operating system" When I contacted Dell, they told me that the OS is corrupt and I have to reformat and reinstall the system.
Is there a utility that could repair the OS? Or is there any other solution?
Thank you,
Jack Dudrick
LittlBUGer
Apr 29 2005, 11:20 AM
I've never seen such an error in Windows and I've seen just about every error imaginable. Are you asking for a tool on the UBCD4Win that could possibly help you, or just any tool in general? If it's for a tool on the UBCD4Win, then you've posted to the right section of the forums, but I'm not sure which tool may help, other than some of the Disk Checkup tools or a chkdsk /r command in a dos prompt. If you are looking for any tool not related to the project, then please, next time post in the correct forums section. Thanks.

LarrySmith
Apr 29 2005, 01:56 PM
Its been my experience that the majority of operating system problems has been a corrupted registry, and in the log run, simpler to save the data and reinstall.
dudrick
May 3 2005, 08:59 AM
Thank you for your responses.
I mistakenly typed the incorrect error messages and really did not give enough details.
I hope that the following messages clarify the situation for you.
The first one that I get is " NotifyAlert.exe - Common Language Runtime Debugging Services as the header. Then "Application has generated an exception that could not be handled. Process id=0xd80(3456), Thread id=0xd88 (3464) Click OK to terminate the application. Click cancel to debug.
The second one is an mg.exe error. "Application has generated an exception that could not be handled. Process id=0xc28 (3112), Thread id=0x540 (1344).
When I click OK ithe computer works fairly well except for MSWord which hangs up sometimes. When I click on Cancel the error message "Registered JIT debugger not available. A command resulted in an error code 0x2 (2). Please check cordbg.exe la 0xd58.
I hope this clarifies the problem a bit more.
Thanks again for your help.
Sincerely,
Jack Dudrick
Arctic Wolf
May 3 2005, 09:44 AM
Ok - a couple things for you to try that aren't really related to UBCD4WIN.
1.) Download http://www.ultimatebootcd.com and burn to CD. You'll want to run 2 tests. DFT (Drive Fitness Test) and Memtest86+. When running the DFT select the Advanced test. Memtest will just run. Make sure it completes at least one full pass.
This will verify that you don't have any hardware related issues going on. (Failing hard drive or memory.)
2.) Find your Windows XP cd. Reboot to CD and select the Recovery option. You'll eventually boot to a DOS prompt. Type in CHKDSK /R to begin running a scan of your system.
3.) If all else fails, backup and restore system.
Good luck - FYI doing all of this would probably take the better part of a day.
LittlBUGer
May 3 2005, 10:25 AM
Well, those two applications, NotifyAlert.exe and mg.exe, I am not familiar with at all and I'm assuming they don't come in a vanilla XP install. Thus, they probably came with your Dell computer and may not even be needed. Have you done a system search for those two files? Have you checked to see if they automatically start up with the system either by the Startup folder or by being a service? It just seems strange to me. If you get errors like that with all kinds of programs and not just those two, then disregard what I said and try Arctic Wolf's advice.

Arctic Wolf
May 3 2005, 10:30 AM
Sometimes reading the WHOLE message might be a nice change for me.
NotifyAlert.exe is a Dell application.
Maybe try running MSCONFIG and disabling NotifyAlert and MG.exe from the startup tab might be a solution.
LittlBUGer
May 3 2005, 10:38 AM
NOOO, msconfig is a TERRIBLE thing to use. You can either just remove the entry from the startup folder under the Programs folder in your Start Menu (if it's there), or run services.msc to view your services and see if it's starting up that way and disabled that service, or run regedit and go into your registry, browse to the Run location, and delete it from there. Doing it from the msconfig way is not good and it's never complete and sometimes doesn't even work (trust me, it's happened to me before and I've seen many experts say the same thing).

If you need help browsing the registry or finding the files, please just post back.

dudrick
May 5 2005, 09:59 AM
Thank you very much for your suggestions!
I will do the suggested processes and let you know what happens.
Sincerely,
Jack Dudrick
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.