Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

ACER E5-771G Series Laptop


  • Please log in to reply

#1
moondog830

moondog830

    Member

  • Member
  • PipPipPip
  • 626 posts

I would like to know if it's possible to Add a SSDrive into my Laptop I would like to be able to run/start up my World of Tanks game faster. Thanks  in advance to anyone who takes the time to  answer me :)

 

moondog


  • 0

Advertisements


#2
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP

It's not hard to install an SSD into any laptop.  Problem is loading the software.  Usually you need the original Windows disk as a clone will not be happy on an SSD.


  • 0

#3
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

not sure if you understand for sure what I'm asking ... I want to keep the current HD ... and add (physically) an SSD ... want to use the SSD simply for my games to launch from.

 

I'm guessing that it  isn't possible to ADD another drive into a LAPTOP ... 


  • 0

#4
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP

No room in the laptop for that sort of thing.  Best you can do is stick it on a USB to SATA adapter.


  • 0

#5
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

That's what I feared ... but you're saying ...

 

I could get a SSD and connect it 'externally' to my laptop and use it that way? just have my games loaded on it and then connect it up and run them?

 

dog


  • 0

#6
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP

It's not ideal.  You may have a bottleneck in the usb connection but I see your laptop comes with USB 3.0 so it won't be that bad.  I run programs all the time on an external drive connected via a USB 2.0 and they work OK but I'm not a gamer so can't tell you if that will be an improvement over your internal drive.  

 

Another alternative might be to upgrade your hard drive.  Can't tell from the specs which drive you have.  If it doesn't have a 64 MB cache and run at 7200 RPM you might see some improvement if you replace the drive.  (Stay away from Seagate.  Western Digital Blacks are the best)

 

Do you have the maximum memory in your laptop?  

 

Let's check your laptop for problems that might slow it down:

 

Get the free version of Speccy:
 
http://www.filehippo...download_speccy (Look in the upper right for the Download
Latest Version button  - Do NOT press the large Start Download button on the upper left!)  
Download, Save and Install it.  Tell it you do not need CCLEANER.    Run Speccy.  When it finishes (the little icon in the bottom left will stop moving), 
File, Save as Text File,  (to your desktop) note the name it gives. OK.  Open the file in notepad and delete the line that gives the serial number of your Operating System.  
(It will be near the top about 10 lines down.) Save the file.  Attach the file to your next post.  (More Reply Options, Choose File, Open, Attach This File)
 

 

Get Process Explorer
 
Save it to your desktop then run it (Vista or Win7 - right click and Run As Administrator).  
 
View, Select Column, check Verified Signer, OK
Options, Verify Image Signatures
 
 
Click twice on the CPU column header  to sort things by CPU usage with the big hitters at the top.  
 
Wait a full minute then:
 
File, Save As, Save.  Note the file name.   Open the file  on your desktop and copy and paste the text to a reply.

  • 0

#7
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

Having a problem with the speccy file ... keep getting message when I try to post it HERE that the file is too long ... I noticed there are a ton of messages concerning updates to 8.1 ... and I mean a TON.


  • 0

#8
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP

It won't attach?

 

Perhaps if you zip it up first?  (If you need a program to zip with 7-zip is good and free and doesn't come with any adware.  http://www.7-zip.org/


  • 0

#9
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

I thought you needed it in text form ON the page so that others can readily read it. I use WinRar ... hope that is okay.

 

moondog

 

 

Attached Files


  • 0

#10
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP

Looks like you could use another 8 GB of memory.  Newegg.com has a sale on

 

Crucial 16GB (2 x 8G) 204-Pin DDR3 SO-DIMM DDR3L 1600 (PC3L 12800) Laptop Memory Model CT2KIT102464BF160B

 

$79.99  (EMCFGFH35 will give you another $5 off if you are on their mailing list)

 

That would give you the maximum that your laptop & operating system can use.  Too bad you didn't use the free Win 10 upgrade before it expired.  I think it's an improvement over the Win 8.1

 

Also you have gotten any updates since 2015.  Have you got Windows Updates turned off?

 

You have three old Java versions showing:

 

Java Runtime Environment
Path C:\Program Files (x86)\Java\jre1.8.0_91\bin\java.exe
Version 8.0
Update 91
Build 14
Java Runtime Environment
Path C:\Program Files\Java\jdk1.8.0_51\bin\java.exe
Version 8.0
Update 51
Build 16
Java Runtime Environment
Path C:\Program Files\Java\jre1.8.0_91\bin\java.exe
Version 8.0
Update 91
Build 14
 

 

Clear the Java Cache by following the instructions on
 
Then uninstall all of the old versions.
 
Java has been very vulnerable to infection so unless you absolutely need it you should not reinstall it.
 
If you feel you must have Java:
Get the latest Java at:
 
Save it to your PC then close all browsers and install it.  Do not let it install the yahoo toolbar or other foistware.
Once installed, go into Control Panel, Java, Security and set the slider to the Highest then OK.
 
(If you also want the 64 bit version then use the 64 bit version of IE to get it.)
 
I would uninstall SuperAntiSpyware.  I am not a fan.
 
Process Explorer looks pretty good.
 
Let's look at your errors:
 
 
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:
 
* System
4. Under 'Select type to list', select:
* Error
* Warning
 
 
Then use the 'Number of events' as follows:
 
 
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
 
 
Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)
 
 

  • 0

Advertisements


#11
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

It will take me a few days to get on this, caught the flu and spent 2 days changing places between bed and bathroom ... 

 

dog


  • 0

#12
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP

No hurry.  Hope you fell better soon.


  • 0

#13
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

Got better and then got busy with work, Christmas and then other stuff ... I'm back now though

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 31/12/2016 1:36:31 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 25/12/2016 8:20:44 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 20/12/2016 4:09:54 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 19/12/2016 4:43:23 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 18/12/2016 8:10:57 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 03/12/2016 12:44:19 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 01/12/2016 12:21:00 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 17/11/2016 5:02:14 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 04/11/2016 1:25:33 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 24/10/2016 4:47:52 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 20/10/2016 5:25:07 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 06/10/2016 12:09:45 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 02/10/2016 10:55:26 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 28/09/2016 12:49:33 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 20/09/2016 3:57:24 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 08/09/2016 2:41:30 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 19/08/2016 5:21:23 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 08/08/2016 5:55:29 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 30/06/2016 2:37:03 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 14/06/2016 5:22:22 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 18/04/2016 1:44:01 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/12/2016 12:26:21 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 31/12/2016 12:21:19 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 31/12/2016 12:20:49 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 27/12/2016 1:57:13 AM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.
 
Log: 'System' Date/Time: 25/12/2016 9:41:53 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 25/12/2016 9:41:23 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 25/12/2016 8:20:41 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
 
Log: 'System' Date/Time: 25/12/2016 8:20:59 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 5:46:55 AM on ?12/?24/?2016 was unexpected.
 
Log: 'System' Date/Time: 23/12/2016 4:14:10 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 23/12/2016 3:23:26 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 23/12/2016 3:22:56 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 23/12/2016 3:17:50 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 23/12/2016 3:17:20 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 20/12/2016 11:09:10 PM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.
 
Log: 'System' Date/Time: 20/12/2016 7:06:22 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 20/12/2016 5:45:36 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 20/12/2016 5:45:06 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 20/12/2016 4:09:46 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
 
Log: 'System' Date/Time: 20/12/2016 4:10:23 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 6:39:39 PM on ?12/?19/?2016 was unexpected.
 
Log: 'System' Date/Time: 19/12/2016 4:43:20 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 31/12/2016 6:26:30 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name g1.symcb.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 31/12/2016 5:28:07 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x7f8162c7 for Disk 3 (PDO name: \Device\00000085) was retried.
 
Log: 'System' Date/Time: 31/12/2016 5:20:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:21 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:21 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:21 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:21 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:21 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:17 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:11 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:11 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (This device does not exist.)
 
Log: 'System' Date/Time: 31/12/2016 5:20:11 PM
Type: Warning Category: 0
Event: 51 Source: disk
An error was detected on device \Device\Harddisk1\DR5 during a paging operation.
 
Log: 'System' Date/Time: 31/12/2016 4:50:50 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 31/12/2016 9:36:57 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 31/12/2016 6:36:32 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.msftncsi.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 31/12/2016 5:01:57 AM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 108859 seconds since the last report.

  • 0

#14
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,799 posts
  • MVP
Log: 'System' Date/Time: 31/12/2016 5:28:07 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x7f8162c7 for Disk 3 (PDO name: \Device\00000085) was retried.
 
Log: 'System' Date/Time: 31/12/2016 5:20:22 PM
Type: Warning Category: 0
Event: 140 Source: Microsoft-Windows-Ntfs
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: D:, DeviceName: \Device\HarddiskVolume10. (A device which does not exist was specified.)

 

 

Perhaps a disk check would help:

http://www.thewindow...cking-windows-8

 

You also have a lot of unexplained shutdowns apparently caused by the system not responding.

 

Probably a good idea to run DISM to make sure things are OK.

 

Open an elevated command prompt:
 
If you open an elevated command prompt it will by default open in c:\Windows\system32
 
Once you have an elevated command prompt:
 
Type(with an Enter after the line):
 
 
DISM  /Online  /Cleanup-Image  /RestoreHealth
 
 (I use two spaces so you can be sure to see where one space goes.)
This will take a while to complete.  Once the prompt returns:
 
Reboot.  Open an elevated Command Prompt again and type (with an Enter after the line):
 
sfc  /scannow
 
 
 
This will also take a few minutes.  
 
When it finishes it will say one of the following:
 
Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)
 
If you get the last result then type:
 
findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  \junk.txt 
Hit Enter.  Then type::
 
notepad  \junk.txt 
Hit Enter. 
 
 Copy the text from notepad and paste it into a reply.
 
 
After you finish SFC, regardless of the result:
 
 
 
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:
 
* System
4. Under 'Select type to list', select:
* Error
* Warning
 
 
Then use the 'Number of events' as follows:
 
 
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
 
 
Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)

  • 0

#15
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

Windows did not find any integrity violations

 

output log

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 10/01/2017 4:36:08 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 07/01/2017 10:25:54 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 25/12/2016 8:20:44 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 20/12/2016 4:09:54 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 19/12/2016 4:43:23 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 18/12/2016 8:10:57 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 03/12/2016 12:44:19 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 01/12/2016 12:21:00 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 17/11/2016 5:02:14 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 04/11/2016 1:25:33 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 24/10/2016 4:47:52 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 20/10/2016 5:25:07 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 06/10/2016 12:09:45 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 02/10/2016 10:55:26 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 28/09/2016 12:49:33 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 20/09/2016 3:57:24 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 08/09/2016 2:41:30 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 19/08/2016 5:21:23 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 08/08/2016 5:55:29 AM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 30/06/2016 2:37:03 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
Log: 'System' Date/Time: 14/06/2016 5:22:22 PM
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/01/2017 6:01:48 PM
Type: Error Category: 0
Event: 11 Source: disk
The driver detected a controller error on \Device\Harddisk2\DR2.
 
Log: 'System' Date/Time: 10/01/2017 5:57:27 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 10/01/2017 5:56:57 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 09/01/2017 5:59:45 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 09/01/2017 5:59:15 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 3:14:11 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 3:13:41 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 3:09:04 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 3:08:34 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 1:45:35 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 1:45:05 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 08/01/2017 1:26:55 PM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.
 
Log: 'System' Date/Time: 08/01/2017 1:36:59 AM
Type: Error Category: 0
Event: 11 Source: disk
The driver detected a controller error on \Device\Harddisk1\DR1.
 
Log: 'System' Date/Time: 07/01/2017 11:10:31 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 07/01/2017 11:10:01 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 07/01/2017 10:28:07 PM
Type: Error Category: 0
Event: 36887 Source: Schannel
A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 20.
 
Log: 'System' Date/Time: 07/01/2017 10:25:51 PM
Type: Error Category: 0
Event: 13 Source: Microsoft-Windows-HAL
The system watchdog timer was triggered.
 
Log: 'System' Date/Time: 07/01/2017 10:27:02 PM
Type: Error Category: 0
Event: 6008 Source: EventLog
The previous system shutdown at 2:37:40 AM on ?1/?7/?2017 was unexpected.
 
Log: 'System' Date/Time: 06/01/2017 7:29:34 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {1B1F472E-3221-4826-97DB-2C2324D389AE} did not register with DCOM within the required timeout.
 
Log: 'System' Date/Time: 06/01/2017 7:29:03 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 10/01/2017 6:45:04 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name beacons4.gvt2.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 6:12:56 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name w.apprep.smartscreen.microsoft.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 5:42:54 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 0 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
 
Log: 'System' Date/Time: 10/01/2017 5:42:54 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 3 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
 
Log: 'System' Date/Time: 10/01/2017 5:42:54 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 2 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
 
Log: 'System' Date/Time: 10/01/2017 5:42:54 PM
Type: Warning Category: 7
Event: 37 Source: Microsoft-Windows-Kernel-Processor-Power
The speed of processor 1 in group 0 is being limited by system firmware. The processor has been in this reduced performance state for 71 seconds since the last report.
 
Log: 'System' Date/Time: 10/01/2017 5:42:27 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name pxd-c1700.cloud.acer.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 5:42:26 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{0bbf93e6-c55e-11e6-8341-806e6f6e6963}#0000000000100000.
 
Log: 'System' Date/Time: 10/01/2017 5:42:26 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{95b9c301-cadf-11e6-8345-c45444b61c2d}#0000000000007E00.
 
Log: 'System' Date/Time: 10/01/2017 5:42:26 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device SWD\WPDBUSENUM\{95b9bd3d-cadf-11e6-8345-c45444b61c2d}#0000000006500000.
 
Log: 'System' Date/Time: 10/01/2017 4:46:23 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name mtalk.google.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:46:18 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name s1.stun.gamestream.nvidia.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:46:16 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www-c1700.cloud.acer.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:43:40 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name settings-win.data.microsoft.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:43:28 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name s1.stun.gamestream.nvidia.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:43:25 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name www.msftncsi.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:43:24 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ans-c1700.cloud.acer.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:42:43 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name ans-c1700.cloud.acer.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 4:39:57 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 10/01/2017 5:04:12 AM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
 
(sorry for the delay)

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP