Author Topic: Repair 2 9 26 : new issues after repair  (Read 11063 times)

0 Members and 1 Guest are viewing this topic.

Offline darth2602

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 9
  • Karma: 0
    • View Profile
Repair 2 9 26 : new issues after repair
« on: March 26, 2017, 01:36:22 am »
hello

i have several pc (with Windows 7 32 integral)  two has freeze problem : system random freeze... well... i started repair (3 9 26) in safe mode to solve this (disk ok, sfc ok, no malware, memory ok)

the problem has been solved on both but repair added new same issues on both  1) a service loading problem (timeout), impossible to manually load them 2) at my computer>properties  i can read :

processor= not available
memory =   not available


3) when i want to optimize service with  the Smart (the windows club)  i have a message : there was an error retrieving service

4) when i whant to start mawarebyte i have now a "unable to connect the service" message (the malwarebyte service setting is "manual" malwarebyte can not load it, i tested : uninstall with revo uninstaller the re install > same issue 

there are the same issues on both computer ....then i think it's a repair bug  could you help me to solve the problem (it's may be a "services permissions reset or "service restauration"  issue ? )

ALL was ok before  Repair except a rare random windows freeze

in advance thanks

best regards



P.S. sorry for my strange English language, i'm french
 
« Last Edit: March 26, 2017, 04:22:10 am by darth2602 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #1 on: March 26, 2017, 04:37:25 am »
Can you open Event Viewer to see what that reports - you'll need to translate as I don't speak or read French.

You can revert the repairs by using Option 5 in the program, using the Registry Restore option.

When you get that window, click on the Restore Registry tab then use the dropdown to select the back up and then Restore Now.

Offline darth2602

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 9
  • Karma: 0
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #2 on: March 26, 2017, 04:59:50 am »
SYSTEM

a lot of  "The timeout (30000 milliseconds) was reached when the Windows Management Infrastructure service connection was logged."

an few

"458/5000
Application-specific authorization settings do not grant Local Run permissions for the COM server application with the CLSID
{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}
  And APPID
{344ED43D-D086-4961-86A6-1106F4ACAD9B}
  To the SID AUTHORITY NT \ System User (S-1-5-18) from the LocalHost address (using LRPC). This security permission can be changed by using the Component Services administrative tool."


Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #3 on: March 26, 2017, 05:35:05 am »
You can usually ignore those DCOM 10016 errors - I do.

Use the registry restore function to take you back to before the repairs and if/when the freeze occurs, go back into Event Viewer to see what it reports.

Offline darth2602

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 9
  • Karma: 0
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #4 on: March 26, 2017, 06:56:33 am »
well....done

wmi seem too be corrected but i have 2 new issues

1)  "Error: Windows Explorer has stopped working"

Name of the failing module: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Error offset: 0x0588f6b0
Failed process ID: 0xb30
Start time of the application failing: 0x01d2a63fe4cad22e
Path of the failed application: C: \ Windows \ explorer.exe
Path of the failing module: unknown
Report ID: 305e1d74-122b-11e7-b8e3-0021910b7cca


2) Nvidia Display Driver Stopped Responding and has Recovered


Log Name: System
Source: Display
Date: 26/03/2017 16:10:22
Event ID: 4101
Task category: None
Level: Warning
Keywords: Classical
User: N / A
Computer: ANAKIN
Description:
The nvlddmkm display driver no longer responded.
XML of the event:
<Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event">
   <System>
     <Provider Name = "Display" />
     <EventID Qualifiers = "0"> 4101 </ EventID>
     <Level> 3 </ Level>
     <Task> 0 </ Task>
     <Keywords> 0x80000000000000 </ Keywords>
     <TimeCreated SystemTime = "2017-03-26T14: 10: 22.000000000Z" />
     <EventRecordID> 307877 </ EventRecordID>
     <Channel> System </ Channel>
     <Computer> ANAKIN </ Computer>
     <Security />
   </ System>
   <EventData>
     <Data> nvlddmkm </ Data>
     <Data>
     </ Data>
   </ EventData>
</ Event>

« Last Edit: March 26, 2017, 07:14:01 am by darth2602 »

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #5 on: March 26, 2017, 09:03:40 am »
It's probably the Nvidia that's causing the freezes.

See if disabling hardware acceleration resolves the freezes, otherwise update or reinstall the graphics driver.

http://www.thewindowsclub.com/hardware-acceleration-windows-7

If you are using an OEM machine then go to the computer support site to see if any updated drivers are available.

Alternatively, go into Device Manager by going Start - type devmgmt.msc and press enter.

Expand Display adapter - right click on the Nvidia and select Update Driver Software and for it to search online.

If that returns that you already have the latest driver, OK out of that and right click again on it and select Update Driver Software - Browse my computer - Let me pick... then click on the Nvidia driver and then on Next to reinstall it.

It may be responsible for taking out Windows Explorer but you need to see if you still get the freezes after performing those steps and it's still snagged in Event Viewer.

Offline darth2602

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 9
  • Karma: 0
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #6 on: March 29, 2017, 12:42:45 am »
> i restaured the registry


t's probably the Nvidia that's causing the freezes.

See if disabling hardware acceleration resolves the freezes, otherwise update or reinstall the graphics driver.
> impossible, the button is "grey"

http://www.thewindowsclub.com/hardware-acceleration-windows-7

If you are using an OEM machine then go to the computer support site to see if any updated drivers are available.

> No assembled machine


Alternatively, go into Device Manager by going Start - type devmgmt.msc and press enter.

Expand Display adapter - right click on the Nvidia and select Update Driver Software and for it to search online.

If that returns that you already have the latest driver, OK out of that and right click again on it and select Update Driver Software - Browse my computer - Let me pick... then click on the Nvidia driver and then on Next to reinstall it.

> i cleaned the drivers with DDU an installed the latetest Nvidia drivers
> result no more freeze, but always  "driver crashes an recovery" and alway "Explorer exe has stopped working "

It may be responsible for taking out Windows Explorer but you need to see if you still get the freezes after performing those steps and it's still snagged in Event Viewer.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #7 on: March 29, 2017, 05:40:12 am »
As I understand it, your system is now back to pre-Windows Repairs but with an updated graphics driver ?

Do you still get these problems when booting up in a clean boot or in Safe Mode with Networking or when you are doing something in particular ?

In Safe Mode you won't be using the Nvidia graphics but this will separate Windows Explorer from those.

To perform a clean boot, go Start type msconfig and press enter.

Under the Startup tab click on Disable all - Apply - OK then Restart.

If in that mode you still get the problems, then go back into msconfig and under the Services tab, check the box to Hide all Microsoft services then Disable all - Apply - OK - Restart to check again.

If that resolves the problems then you will need to re-enable some of the services at a time and see if any are responsible.

To restore from a clean boot, in msconfig check the Normal start up button, but you don't really need any items checked under the Startup tab.

These are general trouble shooting steps for WE stopped working, of which you have already done some.

https://support.microsoft.com/en-gb/help/2694911/error-windows-explorer-has-stopped-working


Offline darth2602

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 9
  • Karma: 0
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #8 on: March 30, 2017, 10:15:38 am »
    You may be using an outdated or corrupted video driver> no

    System files on your PC may be corrupt or mismatched with other files > no

    You may have a Virus or Malware infection on your PC  >no

    Some applications or services running on your PC may be causing Windows Explorer to stop working > maybe

Offline darth2602

  • Newbie
  • *
  • Join Date: May 2015
  • Posts: 9
  • Karma: 0
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #9 on: March 31, 2017, 06:39:39 am »
i have  unchecked "desktop composition" and other.... all but cleartype and theme,  and in firefox "material acceleration"

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: Repair 2 9 26 : new issues after repair
« Reply #10 on: April 01, 2017, 01:40:18 am »
Did you perform a clean boot as I described and are you doing anything in particular when WE stops working ?

Have you also checked to see if it still occurs in Safe Mode with Networking ?