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

Iastor.sys BSOD


  • This topic is locked This topic is locked
14 replies to this topic

#1 Kallisto1

Kallisto1

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 12:22 PM

Hello, it's been a while since I have needed your help, but I seem to have a new intermittent problem. Iastor.sys gives me a BSOD, usually everytime I try to log on to Steam. This problem first occured after a system restore and virus scan. This problem does not occur at other times and I have since download updated RAID drivers from intel. What is the cause of this issue?

P.S. I have included the results of the latest MalwareBytes scan in case you ask me for it later

Attached Files



BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


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

Posted 12 September 2011 - 12:23 PM

Can you update Malwarebytes?

#3 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:51 PM

Posted 12 September 2011 - 12:23 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply

#4 Kallisto1

Kallisto1
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 12:47 PM

My malwarebytes is updated....

Here is the report

Attached Files



#5 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:51 PM

Posted 12 September 2011 - 01:02 PM

Download BlueScreenView:
http://www.nirsoft.net/utils/blue_screen_view.html
unzip downloaded file and double click on BlueScreenView.exe to run the program.
when scanning is done, go to EDIT - Select All
Go to FILE - SAVE Selected Items, and save the report as BSOD.txt
Open BSOD.txt in Notepad, copy all of the content, and paste it into your next reply



#6 Kallisto1

Kallisto1
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 01:28 PM

==================================================
Dump File : Mini091211-01.dmp
Crash Time : 12/09/2011 9:49:42 AM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x82250f19
Parameter 3 : 0x8cbeb77c
Parameter 4 : 0x00000000
Caused By Driver : iastor.sys
Caused By Address : iastor.sys+43f19
File Description : Intel Rapid Storage Technology driver - x86
Product Name : Intel Rapid Storage Technology driver
Company : Intel Corporation
File Version : 10.6.0.1002
Processor : 32-bit
Crash Address : iastor.sys+43f19
Stack Address 1 : ntkrnlpa.exe+44976
Stack Address 2 : MpFilter.sys+bc7
Stack Address 3 : MpFilter.sys+ddfd
Computer Name :
Full Path : C:\Windows\Minidump\Mini091211-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,392
==================================================

==================================================
Dump File : Mini091111-04.dmp
Crash Time : 11/09/2011 5:52:14 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8224b4e8
Parameter 3 : 0x9f01777c
Parameter 4 : 0x00000000
Caused By Driver : iastor.sys
Caused By Address : iastor.sys+414e8
File Description : Intel Rapid Storage Technology driver - x86
Product Name : Intel Rapid Storage Technology driver
Company : Intel Corporation
File Version : 10.6.0.1002
Processor : 32-bit
Crash Address : iastor.sys+414e8
Stack Address 1 : ntkrnlpa.exe+44976
Stack Address 2 : MpFilter.sys+bc7
Stack Address 3 : MpFilter.sys+ddfd
Computer Name :
Full Path : C:\Windows\Minidump\Mini091111-04.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,728
==================================================

==================================================
Dump File : Mini091111-03.dmp
Crash Time : 11/09/2011 5:36:01 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x822474e8
Parameter 3 : 0xaf77377c
Parameter 4 : 0x00000000
Caused By Driver : iastor.sys
Caused By Address : iastor.sys+414e8
File Description : Intel Rapid Storage Technology driver - x86
Product Name : Intel Rapid Storage Technology driver
Company : Intel Corporation
File Version : 10.6.0.1002
Processor : 32-bit
Crash Address : iastor.sys+414e8
Stack Address 1 : ntkrnlpa.exe+44976
Stack Address 2 : MpFilter.sys+bc7
Stack Address 3 : MpFilter.sys+ddfd
Computer Name :
Full Path : C:\Windows\Minidump\Mini091111-03.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,392
==================================================

==================================================
Dump File : Mini091111-02.dmp
Crash Time : 11/09/2011 5:25:04 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x81e53dd1
Parameter 3 : 0x8afc791c
Parameter 4 : 0x00000000
Caused By Driver : ntkrnlpa.exe
Caused By Address : ntkrnlpa.exe+23add1
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.18484 (vistasp2_gdr.110617-0336)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+23add1
Stack Address 1 : ntkrnlpa.exe+23aec5
Stack Address 2 : ntkrnlpa.exe+2124ce
Stack Address 3 : ntkrnlpa.exe+23064e
Computer Name :
Full Path : C:\Windows\Minidump\Mini091111-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,640
==================================================

==================================================
Dump File : Mini091111-01.dmp
Crash Time : 11/09/2011 4:58:38 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x8224f4e8
Parameter 3 : 0xab1ff77c
Parameter 4 : 0x00000000
Caused By Driver : iastor.sys
Caused By Address : iastor.sys+414e8
File Description : Intel Rapid Storage Technology driver - x86
Product Name : Intel Rapid Storage Technology driver
Company : Intel Corporation
File Version : 10.6.0.1002
Processor : 32-bit
Crash Address : iastor.sys+414e8
Stack Address 1 : ntkrnlpa.exe+44976
Stack Address 2 : MpFilter.sys+bf1
Stack Address 3 : MpFilter.sys+dd73
Computer Name :
Full Path : C:\Windows\Minidump\Mini091111-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,712
==================================================

==================================================
Dump File : Mini090811-02.dmp
Crash Time : 08/09/2011 2:59:12 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x822454e8
Parameter 3 : 0x9c48e77c
Parameter 4 : 0x00000000
Caused By Driver : iastor.sys
Caused By Address : iastor.sys+414e8
File Description : Intel Rapid Storage Technology driver - x86
Product Name : Intel Rapid Storage Technology driver
Company : Intel Corporation
File Version : 10.6.0.1002
Processor : 32-bit
Crash Address : iastor.sys+414e8
Stack Address 1 : ntkrnlpa.exe+44976
Stack Address 2 : MpFilter.sys+bf1
Stack Address 3 : MpFilter.sys+dd73
Computer Name :
Full Path : C:\Windows\Minidump\Mini090811-02.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,640
==================================================

==================================================
Dump File : Mini090811-01.dmp
Crash Time : 08/09/2011 1:17:19 PM
Bug Check String : KERNEL_MODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000008e
Parameter 1 : 0xc0000005
Parameter 2 : 0x822424e8
Parameter 3 : 0xa360a77c
Parameter 4 : 0x00000000
Caused By Driver : iastor.sys
Caused By Address : iastor.sys+414e8
File Description : Intel Rapid Storage Technology driver - x86
Product Name : Intel Rapid Storage Technology driver
Company : Intel Corporation
File Version : 10.6.0.1002
Processor : 32-bit
Crash Address : iastor.sys+414e8
Stack Address 1 : ntkrnlpa.exe+44976
Stack Address 2 : MpFilter.sys+bf1
Stack Address 3 : MpFilter.sys+dd73
Computer Name :
Full Path : C:\Windows\Minidump\Mini090811-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6002
Dump File Size : 151,392
==================================================

==================================================
Dump File : Mini121610-01.dmp
Crash Time : 16/12/2010 3:10:55 PM
Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x000000d1
Parameter 1 : 0x40020014
Parameter 2 : 0x00000002
Parameter 3 : 0x00000000
Parameter 4 : 0x89eca9d0
Caused By Driver : tcpip.sys
Caused By Address : tcpip.sys+6cfe6
File Description : TCP/IP Driver
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 6.0.6002.22662 (vistasp2_ldr.110617-0336)
Processor : 32-bit
Crash Address : ntkrnlpa.exe+5ad84
Stack Address 1 : ndis.sys+c09d0
Stack Address 2 : ndis.sys+c0b40
Stack Address 3 : ndis.sys+c0835
Computer Name :
Full Path : C:\Windows\Minidump\Mini121610-01.dmp
Processors Count : 4
Major Version : 15
Minor Version : 6001
Dump File Size : 157,776
==================================================

#7 cryptodan

cryptodan

    Bleepin Madman


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

Posted 12 September 2011 - 01:29 PM

My malwarebytes is updated....

Here is the report



Your mbam log reflects a date from December:

15/12/2010 3:26:31 PM

Your version is 1.5, the current version is 1.51.1.1800.

Please update.

#8 Allan

Allan

  • BC Advisor
  • 8,589 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey
  • Local time:09:51 PM

Posted 12 September 2011 - 01:40 PM

It is not unlikely that drivers from Intel could cause this problem. Can you roll back to the previous driver?

#9 Kallisto1

Kallisto1
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 01:50 PM

I may have simply sent in an older virus report by accident, they are not as well organized in this list as one would hope....

Trust me, it is fully up to date

To answer the other question, which drivers in specific should I trying to roll back?

Edited by Kallisto1, 12 September 2011 - 01:51 PM.


#10 cryptodan

cryptodan

    Bleepin Madman


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

Posted 12 September 2011 - 02:00 PM

Before the driver updates are done lets perform 2 more scans with 2 more tools:

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 unchecked (leave all others checked):
    • Ignore files larger then 4mb
    • Ignore non-executable files

    Now Perform the 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.[list]
    • 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.

SAS Portable
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

GMER does not work in 64bit Mode!!!!!!

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 Full 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
.


All scans above should be performed in regular boot mode, and if that is not possible then I will post instructions in a follow up reply on how to get into Safe Mode to perform the scans. Also all scans should be COMPLETE and not quick unless specifically instructed to do so.

iastor.sys is often a target for rootkits.

#11 Kallisto1

Kallisto1
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 05:37 PM

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

Generated 09/12/2011 at 03:11 PM

Application Version : 5.0.1118

Core Rules Database Version : 7675
Trace Rules Database Version: 5487

Scan type : Complete Scan
Total Scan Time : 00:36:09

Operating System Information
Windows Vista Home Premium 32-bit, Service Pack 2 (Build 6.00.6002)
UAC Off - Administrator

Memory items scanned : 634
Memory threats detected : 0
Registry items scanned : 36815
Registry threats detected : 0
File items scanned : 44116
File threats detected : 0

GMER Report will be added soon...

#12 Kallisto1

Kallisto1
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 05:56 PM

GMER 1.0.15.15641 - http://www.gmer.net
Rootkit scan 2011-09-12 15:55:01
Windows 6.0.6002 Service Pack 2 Harddisk0\DR0 -> \Device\Ide\iaStor0 WDC_WD32 rev.12.0
Running: 4ix90z9y.exe; Driver: C:\Users\Richard\AppData\Local\Temp\uxliqfow.sys


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

SSDT \??\C:\Program Files\SUPERAntiSpyware\SASKUTIL.SYS ZwTerminateProcess [0x8A7D7640]

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

.text ntkrnlpa.exe!KeSetEvent + 621 81CF2DA4 4 Bytes [40, 76, 7D, 8A]
.text C:\Program Files\CyberLink\PowerDVD10\NavFilter\000.fcl section is writeable [0x8256B000, 0x2892, 0xE8000020]
.vmp2 C:\Program Files\CyberLink\PowerDVD10\NavFilter\000.fcl entry point in ".vmp2" section [0x8258E050]

---- User code sections - GMER 1.0.15 ----

.text C:\Windows\Explorer.EXE[668] ntdll.dll!NtProtectVirtualMemory 77DC4B84 5 Bytes JMP 0041000A
.text C:\Windows\Explorer.EXE[668] ntdll.dll!NtWriteVirtualMemory 77DC54C4 5 Bytes JMP 0193000A
.text C:\Windows\Explorer.EXE[668] ntdll.dll!KiUserExceptionDispatcher 77DC5BF8 5 Bytes JMP 0040000A
.text C:\Windows\system32\svchost.exe[1304] ntdll.dll!NtProtectVirtualMemory 77DC4B84 5 Bytes JMP 0010000A
.text C:\Windows\system32\svchost.exe[1304] ntdll.dll!NtWriteVirtualMemory 77DC54C4 5 Bytes JMP 002F000A
.text C:\Windows\system32\svchost.exe[1304] ntdll.dll!KiUserExceptionDispatcher 77DC5BF8 5 Bytes JMP 000F000A
.text C:\Program Files\Real\RealPlayer\Update\realsched.exe[2404] kernel32.dll!SetUnhandledExceptionFilter 77BCA8C5 5 Bytes [33, C0, C2, 04, 00] {XOR EAX, EAX; RET 0x4}
.text C:\Windows\system32\wuauclt.exe[4040] ntdll.dll!NtProtectVirtualMemory 77DC4B84 5 Bytes JMP 0067000A
.text C:\Windows\system32\wuauclt.exe[4040] ntdll.dll!NtWriteVirtualMemory 77DC54C4 5 Bytes JMP 0068000A
.text C:\Windows\system32\wuauclt.exe[4040] ntdll.dll!KiUserExceptionDispatcher 77DC5BF8 5 Bytes JMP 0066000A

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

IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdiplusShutdown] [74B07817] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCloneImage] [74B5A86D] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipDrawImageRectI] [74B0BB22] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipSetInterpolationMode] [74AFF695] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdiplusStartup] [74B075E9] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCreateFromHDC] [74AFE7CA] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCreateBitmapFromStreamICM] [74B38395] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipCreateBitmapFromStream] [74B0DA60] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipGetImageHeight] [74AFFFFA] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipGetImageWidth] [74AFFF61] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipDisposeImage] [74AF71CF] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipLoadImageFromFileICM] [74B8CAE2] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipLoadImageFromFile] [74B2C8D8] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipDeleteGraphics] [74AFD968] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipFree] [74AF6853] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipAlloc] [74AF687E] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)
IAT C:\Windows\Explorer.EXE[668] @ C:\Windows\Explorer.EXE [gdiplus.dll!GdipSetCompositingMode] [74B02AD1] C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.6002.18342_none_9e54f8aaca13c773\gdiplus.dll (Microsoft GDI+/Microsoft Corporation)

---- Disk sectors - GMER 1.0.15 ----

Disk \Device\Harddisk0\DR0 TDL4@MBR code has been found <-- ROOTKIT !!!
Disk \Device\Harddisk0\DR0 sector 00: rootkit-like behavior

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


GMER found something. Obviously I will clean it....

#13 cryptodan

cryptodan

    Bleepin Madman


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

Posted 12 September 2011 - 06:26 PM

Please follow the instructions in ==>Malware Removal and Log Section Preparation Guide<==.

Once the proper logs are created, then make a NEW TOPIC and post it ==>HERE<== Please include the link to this topic in your new topic and a description of your computer issues and what you have done to resolve them.

If you can produce at least some of the logs, then please create the new topic and explain what happens when you try to create the log(s) that you couldn't get. If you cannot produce any of the logs, then still post the topic and explain that you followed the Prep. Guide, were unable to create the logs, and describe what happens when you try to create the logs.

Once you have created the new topic, please reply back here with a link to the new topic.

Most importantly please be patient till you get a reply to your topic.

#14 Kallisto1

Kallisto1
  • Topic Starter

  • Members
  • 21 posts
  • OFFLINE
  •  
  • Local time:08:51 PM

Posted 12 September 2011 - 07:01 PM

New thread

http://www.bleepingcomputer.com/forums/topic418722.html

#15 Orange Blossom

Orange Blossom

    OBleepin Investigator


  • Moderator
  • 36,947 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Bloomington, IN
  • Local time:09:51 PM

Posted 12 September 2011 - 11:20 PM

Hello,

Now for the hard and frustrating part: waiting.

Now that you have posted in the Virus, Trojan, Spyware, and Malware Removal Logs forum, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a MRT Team member, nor should you ask for help elsewhere. Doing so can result in system changes which may not show in the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the MRT Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the MRT Team members are EXTREMELY busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the MRT Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MRT Team member is already assisting you and not open the thread to respond.

Please be patient. It may take several days to get a response but your log will be reviewed and answered as soon as possible. I advise checking your topic once a day for responses as the e-mail notification system is unreliable.

If HelpBot replies to your topic, PLEASE follow Step One so it will report your topic to the team members.

To avoid confusion, I am closing this topic. Good luck with your log.

Orange Blossom :cherry:
Help us help you. If HelpBot replies, you MUST follow step 1 in its reply so we know you need help.

Orange Blossom

An ounce of prevention is worth a pound of cure

SpywareBlaster, WinPatrol Plus, ESET Smart Security, Malwarebytes' Anti-Malware, NoScript Firefox ext., Norton noscript




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users