Being that it is an error message saying that the file can't be found, it is not a matter of finding the file, it is more a matter of locating the reference to the file. Most likely, the file in question was quarantined by antivirus software. I don't generally trust things with a .rom extension that are trying to be executed. .rom files on a PC are typically archives IIRC, and there is no reason that it should be getting an execution call. Especially since it is being loaded by the RunDLL system. Since this is happening at startup, most of the profiling utilities may not find the file since they will load after the rest of the system (and thus, possibly after the call to winmul).

First, I would check the antivirus log to see if the file was in fact quarantined. If it was, the log should indicate what threat was found, and you may be able to find additional cleaning steps to resolve the infection. You can also check Windows Defender, which is now a component of Windows Vista. There is a utility in that program that will show all processes that are part of the system startup. You may be able to find the call through there. You can also check the system configuration utility (type msconfig in the search box at the bottom of your start menu) startup tab for an entry.

Note that the file is being treated as a DLL. In many cases, DLLs are called by other applications. This could be a problem with another service or application that is trying to load but the library is corrupt or missing. In that case, you may need to check the Event Viewer (in your control panel) to find the source of the issue. You can also try booting into Safe Mode, to see if the use problem occurs, or use a selective startup to narrow down possible sources of the error. Once you identify the software that is triggering the problem, you can contact the maker for guidance.

__________________
The best way to learn anything, is to question everything.