I Keep on Getting NTMARTA.DLL is not a valid windows image.
Ok so i keep on getting NTMARTA.DLL is not a valid windows image everytime on startup here is a screenshot.http://i55.tinypic.com/10gjp52.jpgAlso I cant even acess my networks and my whole layout has changed any help?1 person needs an answerI do too
December 14th, 2010 6:55pm

Hi Bmanny5,· Did you make any software or hardware changes on your machine prior to this issue?· Are you getting the pop up error message only while using Debut Video Capture software or at other instances?Let’s follow these methods & check if it helps.Method 1You may reregister the 'NTMARTA.DLL' file & check if the issue persists.a. Type ‘cmd’ in the Start > Run Box, right-click on Command Prompt > click Run as Administrator. b. Type Regsvr32 <space> NTMARTA.DLL.c. Click the OK button.Method 2If you get the pop up error message only while using Debut Video Capture software, you may reintall the application & check if the issue persists.Hope the information helps. Please post back and let us know.RegardsDebleena SMicrosoft Answers Support EngineerVisit our Microsoft Answers Feedback Forum and let us know what you think.
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2010 6:52am

Ok - Look in the top of the error message box and notice who is complaining about the Bad Image file.It is not XP that is complaining, but it is your McAfee Security Scanner Scheduler (SSScheduler.exe), so the problem could be with McAfee, but you can replace the ntmarta.dll file easily enough and see if that straightens things out.Somebody is just not happy with the ntmarta.dll file that is in your c:\windows\system32 folder.If your c:\windows\system32\ntmarta.dll file is afflicted, and your Windows File Protection is working, let XP replace the suspicious file for you.Windows File Protection looks after 3498 XP files and if any of them come up missing, it will replace them for you from backup copies.Navigate to c:\windows\system32 and rename the suspicious ntmarta.dll file to something you can remember - like ntmarta.oldIf Windows FIle Protection is working as it should, WFP will quickly and silently replace the now "missing" ntmarta.dll file from a backup copy and put an event like this in the Event Viewer System Log:Event Type: InformationEvent Source: Windows File ProtectionEvent Category: NoneEvent ID: 64002Description:File replacement was attempted on the protected system file c:\windows\system32\ntmarta.dll. This file was restored to the original version to maintain system stability. The file version of the system file is 5.1.2600.5512.If you press F5 to refresh the c:\windows\system32 folder display, you should see that the ntmarta.dll file has been replaced. If it has not been replaced, you have another problem.Reboot and see how things look now. If things are worse, put the old ntmarta.dll file back if you want, but the error message is coming from McAfee Security Scanner Scheduler, so you may need to start looking at that if the problem persists after ntmarta.dll has been replaced.FYE: ntmarta = NT Multiple Access RouTing AuthorityYou cannot register the ntmarta.dll file with regsvr32 , but you can sure try.Do, or do not. There is no try.I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!
December 15th, 2010 11:32am

Look in the top of the error message box and see who is complaining about the Bad Image file.It is not XP that is complaining, but it is your McAfee Security Scanner Scheduler (SSScheduler.exe), so the problem could be with McAfee, but you can replace the ntmarta.dll file easily enough and see if that straightens things out.Somebody is just not happy with the ntmarta.dll file that is in your c:\windows\system32 folder.If your c:\windows\system32\ntmarta.dll file is afflicted, and your Windows File Protection is working, let XP replace the suspicious file for you.Windows File Protection looks after 3498 XP files and if any of them come up missing, it will replace them for you from backup copies.Navigate to c:\windows\system32 and rename the suspicious ntmarta.dll file to something you can remember - like ntmarta.oldIf Windows FIle Protection is working as it should, WFP will quickly and silently replace the now "missing" ntmarta.dll file from a backup copy and put an event like this in the Event Viewer System Log:Event Type: InformationEvent Source: Windows File ProtectionEvent Category: NoneEvent ID: 64002Description:File replacement was attempted on the protected system file c:\windows\system32\ntmarta.dll. This file was restored to the original version to maintain system stability. The file version of the system file is 5.1.2600.5512.If you press F5 to refresh the c:\windows\system32 folder display, you should see that the ntmarta.dll file has been replaced. If it has not been replaced, you have another problem.Reboot and see how things look now. If things are worse, put the old ntmarta.dll file back if you want, but the error message is coming from McAfee Security Scanner Scheduler, so you may need to start looking at that if the problem persists after ntmarta.dll has been replaced.FYE: ntmarta = NT Multiple Access RouTing AuthorityYou cannot register the ntmarta.dll file with regsvr32 , but you can sure try.Do, or do not. There is no try.I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!
Free Windows Admin Tool Kit Click here and download it now
December 15th, 2010 11:33am

Ok - Look in the top of the error message box and notice who is complaining about the Bad Image file.It is not XP that is complaining, but it is your McAfee Security Scanner Scheduler (SSScheduler.exe), so the problem could be with McAfee, but you can replace the ntmarta.dll file easily enough and see if that straightens things out.Somebody is just not happy with the ntmarta.dll file that is in your c:\windows\system32 folder.If your c:\windows\system32\ntmarta.dll file is afflicted, and your Windows File Protection is working, let XP replace the suspicious file for you.Windows File Protection looks after 3498 XP files and if any of them come up missing, it will replace them for you from backup copies.Navigate to c:\windows\system32 and rename the suspicious ntmarta.dll file to something you can remember - like ntmarta.oldIf Windows FIle Protection is working as it should, WFP will quickly and silently replace the now "missing" ntmarta.dll file from a backup copy and put an event like this in the Event Viewer System Log:Event Type: InformationEvent Source: Windows File ProtectionEvent Category: NoneEvent ID: 64002Description:File replacement was attempted on the protected system file c:\windows\system32\ntmarta.dll. This file was restored to the original version to maintain system stability. The file version of the system file is 5.1.2600.5512.If you press F5 to refresh the c:\windows\system32 folder display, you should see that the ntmarta.dll file has been replaced. If it has not been replaced, you have another problem.Reboot and see how things look now. If things are worse, put the old ntmarta.dll file back if you want, but the error message is coming from McAfee Security Scanner Scheduler, so you may need to start looking at that if the problem persists after ntmarta.dll has been replaced.You can delete the renamed file later when things are running smoothly again.FYE: ntmarta = NT Multiple Access RouTing AuthorityYou cannot register the ntmarta.dll file with regsvr32 , but you can sure try.Do, or do not. There is no try.I need YOUR votes and points for helpful replies and Propose as Answers. I am saving up for a pony!
December 15th, 2010 11:33am

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

Other recent topics Other recent topics