Jump to content

Recommended Posts

debugging: 

2017-09-05 19:35:12.755 DEBUG [3028] [MainUI::buttonCleanClicked@316] [i] Clean button clicked (-31986)
2017-09-05 19:35:13.734 DEBUG [3028] [MainUI::buttonCleanClicked@338] [+] Retrieve results...
2017-09-05 19:35:13.811 DEBUG [3028] [MainUI::buttonCleanClicked@516] [+] Results retrieved - cleaning...
2017-09-05 19:35:13.818 DEBUG [2800] [AdwCleanerSDK::KillProcesses@168] [!] Killing processes.
2017-09-05 19:35:13.819 DEBUG [2800] [AdwCleanerSDK::KillProcesses@176] [!] Got enough permissions.
2017-09-05 19:35:13.822 DEBUG [2800] [AdwCleanerSDK::KillProcesses@237] [!] OpenProcess - [System Process] 87
2017-09-05 19:35:13.824 DEBUG [2800] [AdwCleanerSDK::KillProcesses@237] [!] OpenProcess - System 5
2017-09-05 19:35:13.825 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - smss.exe
2017-09-05 19:35:13.826 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - csrss.exe
2017-09-05 19:35:13.826 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - csrss.exe
2017-09-05 19:35:13.828 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - wininit.exe
2017-09-05 19:35:13.830 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - winlogon.exe
2017-09-05 19:35:13.832 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - services.exe
2017-09-05 19:35:13.833 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - lsass.exe
2017-09-05 19:35:13.834 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - lsm.exe
2017-09-05 19:35:13.836 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.838 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.839 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.842 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.844 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.846 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.849 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.851 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.853 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.854 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - MBAMService.exe
2017-09-05 19:35:13.855 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - svchost.exe
2017-09-05 19:35:13.856 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - explorer.exe
2017-09-05 19:35:13.856 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - ctfmon.exe
2017-09-05 19:35:13.857 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - mbamtray.exe
2017-09-05 19:35:13.857 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - explorer.exe
2017-09-05 19:35:13.857 DEBUG [2800] [AdwCleanerSDK::KillProcesses@248] [!] Process whitelisted - UnlockerAssistant.exe
2017-09-05 19:35:13.860 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.864 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.869 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.872 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.876 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.879 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.882 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing opera.exe
2017-09-05 19:35:13.886 DEBUG [2800] [AdwCleanerSDK::KillProcesses@241] [!] Killing dllhost.exe
2017-09-05 19:35:13.886 DEBUG [2800] [MainUI::Entry@1681] [!] Got enough permissions.
2017-09-05 19:35:13.886 DEBUG [2800] [MainUI::Entry@1692] [+] Cleaning services.
2017-09-05 19:35:13.886 DEBUG [2800] [MainUI::Entry@1699] [+] Cleaning folders.
2017-09-05 19:35:13.901 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@70] [!] It's not a directory! C:/ProgramData/Microsoft/Windows/Start Menu/Programs/mipony
2017-09-05 19:35:13.901 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@70] [!] It's not a directory! C:/Program Files/mipony
2017-09-05 19:35:13.901 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@74] [!] Removing C:\Users\JJBreaker\AppData\Roaming\mipony
2017-09-05 19:35:13.901 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@115] [!] Correctly changed permissions
2017-09-05 19:35:13.917 DEBUG [2800] [AdwCleanerSDK::Quarantine::Add@137] [+] Adding C:/Users/JJBreaker/AppData/Roaming/mipony to quarantine.
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Quarantine::Add@173] Quarantine index recreation...
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Quarantine::Add@178] 0
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Quarantine::Add@203] [!] Success.
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@126] 1
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@74] [!] Removing C:\Users\JJBreaker\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\mipony
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@115] [!] Correctly changed permissions
2017-09-05 19:35:14.042 DEBUG [2800] [AdwCleanerSDK::Quarantine::Add@137] [+] Adding C:/Users/JJBreaker/AppData/Roaming/Microsoft/Windows/Start Menu/Programs/mipony to quarantine.
2017-09-05 19:35:14.057 DEBUG [2800] [AdwCleanerSDK::Quarantine::Add@203] [!] Success.
2017-09-05 19:35:14.057 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@126] 1
2017-09-05 19:35:14.057 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@74] [!] Removing C:\ProgramData\Microsoft\Windows\Start Menu\Programs\ytd video downloader
2017-09-05 19:35:14.073 DEBUG [2800] [AdwCleanerSDK::Folders::CleanFolder@115] [!] Correctly changed permissions
2017-09-05 19:35:17.536 DEBUG [3028] [MainUI::menuLogsClicked@778] [i] Logs menu clicked (-31996)
2017-09-05 19:35:17.536 DEBUG [3028] [MainUI::menuLogsClicked@779] [+] Opening log manager.

 

Link to post
Share on other sites

Let's try looking at these 2 sets of reports:

Report Set #1)  Please run this report collecting tool (even though you may not be experiencing BSOD's) so that we can provide a complete analysis: (from the pinned topic at the top of the forum)  



If you have problems with it running it, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

Report Set #2)  Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

While waiting for a reply, please monitor your temps with this free utility: 

SpeedFan v. 4.5.1 and later (free from here:  http://www.almico.com/sfdownload.php ) can log temperatures in a CSV file:
You may not need to log temps - if uncertain, please ask.

To make it work (log the temps to a file) you have to do BOTH of the below:

1. Enable logging in general: Configure...Log...check "Enabled" then click on OK to save.

2. Enable logging for specific checks: Configure...Temperatures..left click on each sensor, then click on "Logged" at the bottom of the Window (for our purposes we want them all) then once you've selected "Logged" for all sensors, then click on OK to save.

The log will be located at C:\Program Files (x86)\SpeedFan

Naming: log files are named SFLogYYYYMMDD.csv, where YYYY is the year (four digits), MM is the month (2 digits, zero padded) and DD is the day (2 digits, zero padded). If a file already exists by that name, the file that already exists is renamed according to the following naming scheme: SFLogYYYYMMDD-CCCC.csv, where CCCC is a increasing number. The new file is then created with the standard file name scheme.

Notes: whenever you change the options related with logging, SpeedFan starts a new log file.

NOTE:You may want to turn logging off when we're done - as I don't know it's impact on performance or on the system.


 

Link to post
Share on other sites

Please generate the other report (Report Set #2)

Then, please generate these reports, zip them up, and upload them with your next post:

Quote

MSINFO32:
Please go to Start and type in "msinfo32.exe" (without the quotes) and press Enter
Save the report as an .nfo file, then zip up the .nfo file and upload/attach the .zip file with your next post.
Also, save a copy as a .txt file and include it also (it's much more difficult to read, but we have greater success in getting the info from it).

If you're having difficulties with the format, please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "msinfo32 /nfo %USERPROFILE%\Desktop\TEST.NFO" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the TEST.NFO file.  If you have difficulties with making this work, please post back.  Then zip up the .nfo file and upload/attach the .zip file with your next post.

systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the syteminfo.txt file.  If you have difficulties with making this work, please post back.  Then zip up the .txt file and upload/attach the .zip file with your next post.
NOTE:    Will not work with Windows XP

 

Link to post
Share on other sites

I cannot open the report that you uploaded, please try again.
I can get some information from it by opening it in Notepad - so this may be due to the different languages that we use (and is something we can't easily fix)

I still need the other reports also.  Please upload them.
This is what I need:

 


systeminfo:
Please open an elevated (Run as administrator) Command Prompt and type (or copy/paste) "systeminfo.exe >%USERPROFILE%\Desktop\systeminfo.txt" (without the quotes) and press Enter.  Then navigate to Desktop to retrieve the syteminfo.txt file.  If you have difficulties with making this work, please post back.  Then zip up the .txt file and upload/attach the .zip file with your next post.
NOTE:    Will not work with Windows XP

 

 

Report Set #2)  Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

Link to post
Share on other sites

There's a lot of problems with this copy of the OS.  In particular, this seems to be a pirated copy of Windows.
I suggest that the easiest route here would be to do a "Clean" install of Windows.
If the problems remain after the clean install - then the problem is most likely a hardware issue.
If the problems go away, then you've fixed it.  When installing software after this, do it slowly so you can see if anything in particular causes the problem.
 

Backup, Wipe, and "Clean Install" of Windows

For testing purposes, it's best to install Windows "clean".


  This is, basically, installing it the way that Microsoft intended (using drivers from Windows Update).
  This procedure is for Vista/7/8/10

 You will need your installation/recovery DVD(s) before you start.  Once you wipe the hard drive there's no going back!!!

 1.  Backup all your data. 
  This will wipe everything off of your hard drive, so anything that you want to keep will need to be saved elsewhere.

 NOTE: If this is due to an infection, remember to scan the data with another system's current antivirus in order to locate and remove any malware.
  NOTE: Disconnect any additional hard drives (internal and external) that you may have installed.  This may break any multi-boot setups that you have, so be prepared to conduct recovery operations on them once you're done.  Don't forget that, if this is due to an infection, the additional hard drives may be infected also.

 2.  Connect the system to the internet (if the system says disconnect from the Internet, then do so).

 3.  Make sure that you've run hardware diagnostics on the system, as installing Windows on "borked" hardware isn't a real good idea.
  Free diagnostics here:  http://www.carrona.org/hwdiag.html
  At a minimum, you must have run these bootable diagnostics (they work outside of Windows, so Windows doesn't have to be working):  http://www.carrona.org/initdiag.html

 4.  Use one of these free utilities to wipe the hard drive clean:
  KillDisk ( http://www.killdisk.com/downloadfree.htm ). 
  DBAN ( http://www.dban.org/download )
  This will also delete any recovery partitions on the system - so the installation/recovery DVD's are essential!!!

 5  Remove any add-on hardware that didn't come with the system (or hardware that isn't essential for running the system). This'll help to rule out any incompatibilities with that hardware.

 6.  Install Windows by booting from the installation/recovery DVD - DO NOT tweak any settings!!!

NOTE:  The installation from recovery media is a 2 step process if errors remain.  In order to rule out the recovery media as a source of the problem, you'll have to try again with a different set of recovery media (to rule out a bad copy).

 7.  Visit Windows Update and get all updates

 8.  Check Device Manager for any unknown/disabled devices - if there are unknown/disabled devices, fix them with the latest drivers from the device manufacturer's website (not the PC Manufacturer)

 9.  Visit Windows Update and get the Service Packs for your system. (usually under Important Updates). 
  Windows 10:  Please ensure that you get the 1511 update (build 10586).  Run "winver" (without the quotes) from a Command Prompt
  Windows 8.1:  Please get the Win8.1 update and the Win8.1 Update 1 update.
  Windows 7 SP1http://windows.microsoft.com/en-US/windows7/install-windows-7-service-pack-1 and  http://support.microsoft.com/kb/2505743
  Vista SP1http://windows.microsoft.com/en-US/windows-vista/Learn-how-to-install-Windows-Vista-Service-Pack-1-SP1 Once this is completed, please go to the next line and install  Vista SP2.
  Vista SP2http://windows.microsoft.com/en-US/windows-vista/Learn-how-to-install-Windows-Vista-Service-Pack-2-SP2
  Search Google/Bing for installing other OS's Service Packs.

 10.  Visit Windows Update and get ALL available updates.  Make repeated trips there until is shows that there are no updates left to install (it's OK to skip the Bing Desktop update as long as it's not installed on your system).

 11.  Download, install, and update a free antivirus so you don't get infected while testing ( http://www.carrona.org/freeav.html ).
       For Windows 8 and above, use Windows Defender and the Windows Firewall.

  12.  Test to see if the problem remains.
  If the problems persist, then the problem is most likely with your hardware.
  If the problems are gone, then proceed with installing the latest version of your favorite programs, testing after each one for errors.

 If you choose to continue setting up the system, these are the next steps:
  Step 13 - download and install all available updates from the system manufacturer (or motherboard manufacturer if it's a custom build)
  Step 14 - download and install all available updates for any additional hardware that's installed (from the manufacturer's website).
  Step 15 - download and install all available updates for any software that you have installed.

 CAVEAT:  If you have an Asus motherboard, check the date on the C:\Windows\System32\driver\ASACPI.sys file.  2004/2005 is a problem, 2009/2010 is OK.  Updates are available at the Asus support website.

 CAVEAT:  If you have a Sony system, make sure that you DO NOT have the 2007 (or earlier) version of the Sony Firmware Extension Parser (SFEP.sys).  Update this driver immediately!!!


 

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.