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

#16
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,783 posts
  • MVP
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: 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.

 

 

 

 

You nrrd to do a disk check on each drive.  

 

 
1. Double-click My Computer, and then right-click the hard disk that you want to check. C:
2. Click Properties, and then click Tools.
3. Under Error-checking, click Check Now. A dialog box that shows the Check disk options is displayed,
4. Check both boxes and then click Start.
You will receive the following message:
The disk check could not be performed because the disk check utility needs exclusive access to some Windows files on the disk. These files can be accessed by restarting Windows. Do you want to schedule the disk check to occur the next time you restart the computer?
Click Yes to schedule the disk check,
 
 but don't restart yet.
 
Right click on (My) Computer and select Manage (Continue) Then the Event Viewer. Next select Windows Logs.  Right click on System and Clear Log, Clear. Repeat for Application.
 
Reboot. The disk check will run and will probably take an hour or more to finish.
 
Repeat the check for each drive or USB drive.  You may not have to reboot for any but C:
 
Run VEW again just for System
 
 

  • 0

Advertisements


#17
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 11/01/2017 1:21:52 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: 11/01/2017 5:38:52 PM
Type: Error Category: 0
Event: 55 Source: Ntfs
A corruption was discovered in the file system structure on volume H:.  The exact nature of the corruption is unknown.  The file system structures need to be scanned online. 
 
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.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/01/2017 6:15:44 PM
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name imi.sp1.convertro.com timed out after none of the configured DNS servers responded.
 
Log: 'System' Date/Time: 11/01/2017 6:04:48 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: 11/01/2017 6:04:48 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: 11/01/2017 6:04:48 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: 11/01/2017 6:04:48 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: 11/01/2017 6:04:23 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: 11/01/2017 6:04:23 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: 11/01/2017 6:04:23 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: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 132 Source: Ntfs
Too many repair events have occurred in a short period of time. Temporarily suspending posting of further repair events.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.
 
Log: 'System' Date/Time: 11/01/2017 5:38:52 PM
Type: Warning Category: 0
Event: 98 Source: Microsoft-Windows-Ntfs
Volume H: (\Device\HarddiskVolume11) requires an Online Scan.  An Online Scan will automatically run as part of the next scheduled maintenance task.  Alternatively you may run "CHKDSK /SCAN" locally via the command line, or run "REPAIR-VOLUME <drive:> -SCAN" locally or remotely via PowerShell.

  • 0

#18
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,783 posts
  • MVP
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 132 Source: Ntfs
Too many repair events have occurred in a short period of time. Temporarily suspending posting of further repair events.
 
Log: 'System' Date/Time: 11/01/2017 5:41:41 PM
Type: Warning Category: 0
Event: 130 Source: Ntfs
The file system structure on volume H: has now been repaired.

 

 

I think you are making progress but it may still have some problem with H:  I would do another diskcheck of H: just to make sure.


  • 0

#19
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

no errors found  on H: ... that's one of my externals that I've been shifting files/books and stuff around on

 

also at one time you mentioned that my logs showed a number of incorrect shutdowns ... many times I just close up my laptop as I moved from room to room in school or whatever

 

you also commented on my not updating Windows ... I have satellite internet and many times the updates were just more than I could handle so I stopped ... stupid I know, but did 

it anyway :(

 

dog


  • 0

#20
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,783 posts
  • MVP
also at one time you mentioned that my logs showed a number of incorrect shutdowns ... many times I just close up my laptop as I moved from room to room in school or whatever

 

 

Search for

power options

and hit Enter

 

This should open the Power Options control panel.  Click on Change Plan Setting then on Change Advanced Power Options then scroll down in the left until you find Power Buttons and Lid.  Make sure that closing the just puts the PC to sleep.  Of course if your battery is no good and you have to unplug it to move it then sleep isn't going to work.  I think you can change the Lid option to shutdown.  That will be a bit easier on your PC just give it a few seconds to shutdown before you unplug it.

 

I would take the laptop to a library or McDonalds or somewhere where they have free wifi and let it get caught up on its updates.


  • 0

#21
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

I also sent you a personal message if you could read it. I will try to get to the library in the next 3 or 4 days and get updated ... we've had 3 days of no school here in Michigan as the weather has not cooperated at all for me to go substitute teach ... or pretty much go anywhere else for the last 2 days.


  • 0

#22
RKinner

RKinner

    Malware Expert

  • Expert
  • 19,783 posts
  • MVP

The only thing we have done that might change things was remove the old versions of Java.  If you removed all of them then perhaps installing a new version would help.  Can you give me a link to a site that is not working?  (In a PM if you would rather not reveal it to the world.)


  • 0

#23
moondog830

moondog830

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 626 posts

they are now both up and running ... thanks


  • 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