Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

dll file errors on boot up.


  • Please log in to reply
8 replies to this topic

#1 struckdumb1

struckdumb1

  • Members
  • 88 posts
  • OFFLINE
  •  
  • Local time:05:51 PM

Posted 01 September 2010 - 01:11 AM

A couple of days ago my antivirus Avira reported what looked like a virus associated with files emeyuruwokuqisal.dll and srcodb.dll.
It would not fix these problems but went into a cycle of reporting the files then scanning and then reporting them again.

Reading somewhere that Avira is known for not fixing some issues - on a recommendation I replaced Avira with Avast.
I scanned my system with Avast and MBAM and nothing untoward was reported.

However, since then, on boot up I get the following 4 error messages:
emeyuruwokuqisal.dll is not a valid windows image
srcodb.dll is not a valid windows image
error loading emeyuruwokuqisal.dll %1 is not a valid win32 application
error loading srcodb.dll %1 is not a valid win32 application

Can you help please?

Many thanks
Paul

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:51 PM

Posted 01 September 2010 - 04:43 PM

Download the following:

Malwarebytes Anti-Malware

Please download Malwarebytes Anti-Malware and save it to your desktop.Download Link 1
Download Link 2
MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.

  • Make sure you are connected to the Internet.
  • Double-click on mbam-setup.exe to install the application.
    For instructions with screenshots, please refer to the How to use Malwarebytes' Anti-Malware Guide.
  • When the installation begins, follow the prompts and do not make any changes to default settings.
  • When installation has finished, make sure you leave both of these checked:
    • Update Malwarebytes' Anti-Malware
    • Launch Malwarebytes' Anti-Malware
  • Then click Finish.
MBAM will automatically start and you will be asked to update the program before performing a scan.
  • If an update is found, the program will automatically update itself. Press the OK button to close that box and continue.
  • If you encounter any problems while downloading the definition updates, manually download them from http://mbam.malwarebytes.org/database/mbam-rules.exe" target="_blank" rel="nofollow">here and just double-click on mbam-rules.exe to install.
On the Scanner tab:
  • Make sure the "Perform Quick Scan" option is selected.
  • Then click on the Scan button.
  • If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
  • The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
  • When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
  • Click OK to close the message box and continue with the removal process.
Back at the main Scanner screen:
  • Click on the Show Results button to see a list of any malware that was found.
  • Make sure that everything is checked, and click Remove Selected.
  • When removal is completed, a log report will open in Notepad.
  • The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
  • Copy and paste the contents of that report in your next reply. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
  • Exit MBAM when done.
Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.


SUPERAntiSpyware:

Please download and scan with SUPERAntiSpyware Free

  • Double-click SUPERAntiSypware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If it will not start, go to Start > All Prgrams > SUPERAntiSpyware and click on Alternate Start.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the "General and Startup" tab, and under Start-up Options, make sure "Start SUPERAntiSpyware when Windows starts" box is unchecked.
  • Click the "Scanning Control" tab, and under Scanner Options, make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen and exit the program.
  • Do not run a scan just yet.
Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with SUPERAntiSpyware as follows:
  • Launch the program and back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan and click "Next".
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes" and reboot normally.
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.

Instructions:

Download and scan with SUPERAntiSpyware Free for Home Users
  • Double-click SUPERAntiSpyware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the Scanning Control tab.
  • Under Scanner Options make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen.
  • Back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan.
  • Click "Next" to start the scan. Please be patient while it scans your computer.
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes".
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.


Now GMER

Please download GMER from one of the following locations and save it to your desktop:

  • Main Mirror
    This version will download a randomly named file (Recommended)
  • Zipped Mirror
    This version will download a zip file you will need to extract first. If you use this mirror, please extract the zip file to your desktop.
  • Disconnect from the Internet and close all running programs.
  • Temporarily disable any real-time active protection so your security programs will not conflict with gmer's driver.
  • Double-click on the randomly named GMER file (i.e. n7gmo46c.exe) and allow the gmer.sys driver to load if asked.
  • Note: If you downloaded the zipped version, extract the file to its own folder such as C:\gmer and then double-click on gmer.exe.

    Posted Image
  • GMER will open to the Rootkit/Malware tab and perform an automatic quick scan when first run. (do not use the computer while the scan is in progress)
  • If you receive a WARNING!!! about rootkit activity and are asked to fully scan your system...click NO.
  • Now click the Scan button. If you see a rootkit warning window, click OK.
  • When the scan is finished, click the Save... button to save the scan results to your Desktop. Save the file as gmer.log.
  • Click the Copy button and paste the results into your next reply.
  • Exit GMER and be sure to re-enable your anti-virus, Firewall and any other security programs you had disabled.
-- If you encounter any problems, try running GMER in safe mode.
-- If GMER crashes or keeps resulting in a BSODs, uncheck Devices on the right side before scanning
.


Make sure you run full scans of MBAM and SAS, and make sure they are updated.

#3 struckdumb1

struckdumb1
  • Topic Starter

  • Members
  • 88 posts
  • OFFLINE
  •  
  • Local time:05:51 PM

Posted 02 September 2010 - 04:34 PM

Hi there,

Many thanks for your help.
I ran the scans as you asked.
First timer I ran SAS on safe mode - but it didn't save a log.
Ran again not on safe mode and log was saved.
Results are below for all three scans:


Malwarebytes' Anti-Malware 1.46
www.malwarebytes.org

Database version: 4528

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

02/09/2010 17:28:52
mbam-log-2010-09-02 (17-28-52).txt

Scan type: Full scan (C:\|D:\|)
Objects scanned: 306538
Time elapsed: 1 hour(s), 0 minute(s), 52 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)







SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 09/02/2010 at 05:50 PM

Application Version : 4.42.1000

Core Rules Database Version : 5444
Trace Rules Database Version: 3256

Scan type : Custom Scan
Total Scan Time : 00:19:48

Memory items scanned : 590
Memory threats detected : 0
Registry items scanned : 7660
Registry threats detected : 0
File items scanned : 35284
File threats detected : 26

Adware.Tracking Cookie
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@atdmt[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@invitemedia[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@yadro[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@www.nakedwines[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@media6degrees[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@at.atwola[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@revsci[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@statcounter[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@collective-media[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@www.googleadservices[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@server.iad.liveperson[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@www.googleadservices[4].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@liveperson[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@interclick[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@stats.paypal[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@www.googleadservices[3].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@chitika[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@www.googleadservices[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@nakedwines[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@adserver.adtechus[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@ads.bleepingcomputer[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@steelhousemedia[2].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@tacoda[1].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@CAWAQRO3.txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@www.googleadservices[5].txt
D:\Documents and Settings\Paul.049759620338.001\Cookies\paul@liveperson[3].txt








GMER 1.0.15.15281 - http://www.gmer.net
Rootkit scan 2010-09-02 21:48:57
Windows 5.1.2600 Service Pack 3
Running: pcl4moho.exe; Driver: D:\DOCUME~1\PAUL04~1.001\LOCALS~1\Temp\pxryrkob.sys


---- System - GMER 1.0.15 ----

SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwClose [0xAA127CD2]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwCreateKey [0xAA127B8E]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwDeleteKey [0xAA128142]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwDeleteValueKey [0xAA12806C]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwDuplicateObject [0xAA127764]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwOpenKey [0xAA127C68]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwOpenProcess [0xAA1276A4]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwOpenThread [0xAA127708]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwQueryValueKey [0xAA127D88]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwRenameKey [0xAA128210]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwRestoreKey [0xAA127D48]
SSDT \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwSetValueKey [0xAA127EC8]
SSDT \??\C:\Program Files\SUPERAntiSpyware\SASKUTIL.SYS (SASKUTIL.SYS/SUPERAdBlocker.com and SUPERAntiSpyware.com) ZwTerminateProcess [0xAA1EB620]

Code \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwCreateProcessEx [0xAA134B9C]
Code \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwCreateSection [0xAA1349C0]
Code \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ZwLoadDriver [0xAA134AFA]
Code \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) NtCreateSection
Code \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ObInsertObject
Code \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software) ObMakeTemporaryObject

---- Kernel code sections - GMER 1.0.15 ----

PAGE ntkrnlpa.exe!ZwLoadDriver 8058413A 7 Bytes JMP AA134AFE \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software)
PAGE ntkrnlpa.exe!NtCreateSection 805AB38E 7 Bytes JMP AA1349C4 \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software)
PAGE ntkrnlpa.exe!ObMakeTemporaryObject 805BC502 5 Bytes JMP AA1305B4 \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software)
PAGE ntkrnlpa.exe!ObInsertObject 805C2F86 5 Bytes JMP AA131F6C \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software)
PAGE ntkrnlpa.exe!ZwCreateProcessEx 805D1134 7 Bytes JMP AA134BA0 \SystemRoot\System32\Drivers\aswSP.SYS (avast! self protection module/ALWIL Software)
.text C:\WINDOWS\system32\DRIVERS\nv4_mini.sys section is writeable [0xB593E3A0, 0x59FFE5, 0xE8000020]

---- User IAT/EAT - GMER 1.0.15 ----

IAT C:\WINDOWS\system32\services.exe[788] @ C:\WINDOWS\system32\services.exe [ADVAPI32.dll!CreateProcessAsUserW] 00390002
IAT C:\WINDOWS\system32\services.exe[788] @ C:\WINDOWS\system32\services.exe [KERNEL32.dll!CreateProcessW] 00390000

---- Devices - GMER 1.0.15 ----

Device \FileSystem\Ntfs \Ntfs aswSP.SYS (avast! self protection module/ALWIL Software)

AttachedDevice \FileSystem\Ntfs \Ntfs aswMon2.SYS (avast! File System Filter Driver for Windows XP/ALWIL Software)
AttachedDevice \Driver\Tcpip \Device\Ip aswTdi.SYS (avast! TDI Filter Driver/ALWIL Software)
AttachedDevice \Driver\Kbdclass \Device\KeyboardClass0 ELkbd.sys (Intel Corporation)
AttachedDevice \Driver\Tcpip \Device\Tcp aswTdi.SYS (avast! TDI Filter Driver/ALWIL Software)
AttachedDevice \Driver\Tcpip \Device\Udp aswTdi.SYS (avast! TDI Filter Driver/ALWIL Software)
AttachedDevice \Driver\Tcpip \Device\RawIp aswTdi.SYS (avast! TDI Filter Driver/ALWIL Software)

Device \FileSystem\Fastfat \Fat A806AD20

AttachedDevice \FileSystem\Fastfat \Fat fltmgr.sys (Microsoft Filesystem Filter Manager/Microsoft Corporation)
AttachedDevice \FileSystem\Fastfat \Fat aswMon2.SYS (avast! File System Filter Driver for Windows XP/ALWIL Software)

---- EOF - GMER 1.0.15 ----

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:51 PM

Posted 02 September 2010 - 05:28 PM

On boot up what do you mean, do you get these errors prior to the actual windows login or after?

#5 struckdumb1

struckdumb1
  • Topic Starter

  • Members
  • 88 posts
  • OFFLINE
  •  
  • Local time:05:51 PM

Posted 03 September 2010 - 01:53 AM

Everything boots up ok.
Windows logs in.
But once complete the error messages appear - 4 of them.


The first says

rundll32.exe - Bad image
The application or DLL C:\WINDOWS\emeyuruwokuqisal.dll is not a valid windows image. Please check this against your installation diskette. [/indent]




The second is identical but for srcodb.dll




The third says

RUNDLL
Error loading C:\WINDOWS\emeyuruwokuqisal.dll
%1 is not a valid Win32 application




The fourth is identical but for srcodb.dll







I don't have a diskette.
Everything came preinstaled.

#6 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:51 PM

Posted 03 September 2010 - 01:55 AM

Can you load up msconfig via Start then Run and typing in msconfig and hit enter. Go to the Start Up tab and tell me what is starting up?

#7 struckdumb1

struckdumb1
  • Topic Starter

  • Members
  • 88 posts
  • OFFLINE
  •  
  • Local time:05:51 PM

Posted 03 September 2010 - 02:26 AM

Posted Image

Does this give what you need?

#8 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:09:51 PM

Posted 03 September 2010 - 02:52 AM

The following involves making changes to your registry:

Please download ERUNT to make a back up of your registry.

You will want to go to start then run and type in regedit hit enter.

You will want to hit F3 and search for srcodb and emeyuruwokuqisal and delete those values. They will be on the right hand side.

Reboot and see if you get those errors again.

#9 struckdumb1

struckdumb1
  • Topic Starter

  • Members
  • 88 posts
  • OFFLINE
  •  
  • Local time:05:51 PM

Posted 03 September 2010 - 03:19 AM

That seems to have done it.
They've gone. :thumbsup:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users