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.


Possible x64 Rootkit infection

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

#1 Jerry22


  • Members
  • 1 posts
  • Local time:10:33 AM

Posted 29 June 2015 - 01:44 PM


Hello, thanks for taking the time to look at my problem... All help is appreciated!



  • Base OS: Windows 7 x64
    • VM1: Windows 7 x32
    • VM2: Debian 7 x32

The start: All problems started yesterday, I was coding something on my Windows 7 x32 VM, I was given a random BSOD, then after restarting, I was given another random shutdown.... My theme changed to windows basic, programs became inaccessible and I was shut down.


I proceeded to restart... I checked my event logs and minidump, NOTING... Nothing was there at all. I then tried to replicate the error with no luck whatsoever. 


At this point I had to just check if the system has any kind of infection, so I run GMER and there seems to be an issue with ntkrnlpa.exe:



Okay... At this point I'm thinking... what the hell is this. So I take a closer look with AntiSpy and it confirms there is some hooking:




I've proceeded to run:

  • Avast Anti-rootkit
  • BootkitRemover Bitdefender
  • Novirusthanks rootkit remover
  • Various AV boot CDs 

All found nothing.


Since I was worried I continued to monitor my processes and outbound connections closely. I found that Svchost was sending and receiving UDP data, with the local port "bootpc". This could be perfectly fine, just something I thought could be of use.  


Moving on

Just as I have started writing this, my main system has just been given a BSOD (Windows 7 x64). NOW I'M SERIOUSLY WORRIED...


I did however get a minidump:


062915-8158-01.dmp 29/06/2015 17:53:19 0x00000109 a3a039d8`9e14e54c b3b7465e`f093204a fffff800`0fcb6080 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\062915-8158-01.dmp 8 15 7601 293,640 29/06/2015 17:54:04
Ntoskrnl.exe appears to be the problem here...
Okayyy... So now I have repeated the same procedures as I did on the other system, only this time, GMER gives me an error: 
  • "C:\Windows\System32\config\system: The process cannot access the file because it is being used by another process."
  • "C:\Users\Root\ntuser.dat: The process cannot access the file because it is being used by another process."

Then produces this: 

  • INITKDBG  C:\Windows\system32\ntoskrnl.exe!ExDeleteNPagedLookasideList + 528
  • INITKDBG  C:\Windows\system32\ntoskrnl.exe!ExDeleteNPagedLookasideList + 588 


I've run:

  • TDSKiller
  • Avast Anti-Rootkit
  • Sophos Anti-Rootkit
  • Malware Bytes Anti-rootkit
  • Bitdefender Anti-rootkit (Finished instantly like it didn't even scan)
  • Novirusthanks - (Wouldn't work: Wouldn't access C:\)
  • Bootable AV CDs
    • Bitdefender
    • F-Secure
    • Avast
  • Rouge Killer

After all of this, nothing was found... 


Final Words

If anyone can shed some light on this I'd be VERY VERY pleased. I've not had 1 blue-screen in over a year, now 2 consecutive BSOD on 2 different systems (Virtual/Main) within the space of a day. 


Please get back to me as soon as possible. 


I'm extremely worried about the fact GMER produces that error on my main system, If you know anything about why this could be legitimately possible I'd much appreciate it if you can bring it to my attention please!









I am also unable to run "RootRepel":

  • Exception Code: 0xc0000005
  • Exception Address: 0x00429d13
  • Attempt to write to address: 0x1348000

EDIT: (22:08)


Just received another Blue Screen on my Main system, Windows 7 x64, it said something about modification of system files:


I was doing nothing when this happened. Just watching youtube.


Here is the log: 

  • 062915-8127-01.dmp 29/06/2015 22:03:56 0x00000109 a3a039d8`9dec9b8f b3b7465e`f06ad98d fffff880`02ff16c0 00000000`00000002 ntoskrnl.exe ntoskrnl.exe+75bc0 NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7601.18409 (win7sp1_gdr.140303-2144) x64 ntoskrnl.exe+75bc0 C:\Windows\Minidump\062915-8127-01.dmp 8 15 7601 293,592 29/06/2015 22:04:36

Edited by Jerry22, 29 June 2015 - 04:14 PM.
Moved from AII to MRL - Hamluis.

BC AdBot (Login to Remove)


#2 HelpBot


    Bleepin' Binary Bot

  • Bots
  • 12,760 posts
  • Gender:Male
  • Local time:05:33 AM

Posted 04 July 2015 - 01:45 PM

Hello and welcome to Bleeping Computer!

I am HelpBot: an automated program designed to help the Bleeping Computer Staff better assist you! This message contains very important information, so please read through all of it before doing anything.

We apologize for the delay in responding to your request for help. Here at Bleeping Computer we get overwhelmed at times, and we are trying our best to keep up. Please note that your topic was not intentionally overlooked. Our mission is to help everyone in need, but sometimes it takes just a little longer to get to every request for help. No one is ignored here.

To help Bleeping Computer better assist you please perform the following steps:


step1.gif In order to continue receiving help at BleepingComputer.com, YOU MUST tell me if you still need help or if your issue has already been resolved on your own or through another resource! To tell me this, please click on the following link and follow the instructions there.

CLICK THIS LINK >>> http://www.bleepingcomputer.com/logreply/581303 <<< CLICK THIS LINK

If you no longer need help, then all you needed to do was the previous instructions of telling me so. You can skip the rest of this post. If you do need help please continue with Step 2 below.


step2.gifIf you still need help, I would like you to post a Reply to this topic (click the "Add Reply" button in the lower right hand of this page). In that reply, please include the following information:

  • If you have not done so already, include a clear description of the problems you're having, along with any steps you may have performed so far.
  • A new FRST log. For your convenience, you will find the instructions for generating these logs repeated at the bottom of this post.
    • Please do this even if you have previously posted logs for us.
    • If you were unable to produce the logs originally please try once more.
    • If you are unable to create a log please provide detailed information about your installed Windows Operating System including the Version, Edition and if it is a 32bit or a 64bit system.
    • If you are unsure about any of these characteristics just post what you can and we will guide you.
  • Please tell us if you have your original Windows CD/DVD available.
  • Upon completing the above steps and posting a reply, another staff member will review your topic and do their best to resolve your issues.

Thank you for your patience, and again sorry for the delay.


We need to see some information about what is happening in your machine. Please perform the following scan again:

  • Download FRST by Farbar from the following link if you no longer have it available and save it to your destop.

    FRST Download Link

  • When you go to the above page, there will be 32-bit and 64-bit downloads available. Please click on the appropriate one for your version of Windows. If you are unsure as to whether your Windows is 32-bit or 64-bit, please see this tutorial.
  • Double click on the FRST icon and allow it to run.
  • Agree to the usage agreement and FRST will open. Do not make any changes and click on the Scan button.
  • Notepad will open with the results.
  • Post the new logs as explained in the prep guide.
  • Close the program window, and delete the program from your desktop.

As I am just a silly little program running on the BleepingComputer.com servers, please do not send me private messages as I do not know how to read and reply to them! Thanks!

#3 HelpBot


    Bleepin' Binary Bot

  • Bots
  • 12,760 posts
  • Gender:Male
  • Local time:05:33 AM

Posted 09 July 2015 - 01:45 PM

Hello again!

I haven't heard from you in 5 days. Therefore, I am going to assume that you no longer need our help, and close this topic.

If you do still need help, please send a Private Message to any Moderator within the next five days. Be sure to include a link to your topic in your Private Message.

Thank you for using Bleeping Computer, and have a great day!

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users