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

Computer very slow; could it be a virus?


  • Please log in to reply

#31
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,006 posts
  • MVP

Looks like the network adapter is having problems.  If you have the latest driver for it then perhaps an older one might work better,  OR just go into device manager and right click on the network adapter and Uninstall then reboot.

 

 

Also

 

Copy the next two lines:

dir  /a  C:\WINDOWS\system32\SRU  >  \junk.txt
notepad  \junk.txt
Open an Elevated Command Prompt:
Win 7: Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator
 
Right click and Paste (or Edit then Paste) and the copied lines should appear.
Hit Enter if notepad does not open.  Copy and paste the text from notepad into a reply. 

 


  • 0

Advertisements


#32
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

I'm not sure I understand about the drivers. I have 2 of them (their names are attached). Do I delete the newer one, or do I download a newer version of one of them and then delete the others? 

Attached Thumbnails

  • network drivers.JPG

Edited by frogg25, 27 August 2017 - 12:12 PM.

  • 0

#33
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,006 posts
  • MVP

One is wireless, one is wired.  Uninstall the one you use.  The AC 3165 is the wireless one so that's the one.  Just right click on it and Uninstall.

 

If you right click on it and hit properties then Driver then Roll Back Driver or Update driver. you might get a different driver.  


  • 0

#34
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

And I'll still be connected with the other one?


  • 0

#35
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,006 posts
  • MVP

The other one should not be connected.  When you reboot after uninstalling Windows will reinstall it.


  • 0

#36
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

Driver...done. It reconnected, but also added 8 "WAN Miniport" adapters. Is that what I want?

 

Here is the other info:

 

 Volume in drive C is Windows
 Volume Serial Number is F0D8-7B53
 
 Directory of C:\WINDOWS\system32\SRU
 
08/28/2017  01:37 PM    <DIR>          .
08/28/2017  01:37 PM    <DIR>          ..
08/28/2017  02:10 PM             8,192 SRU.chk
08/28/2017  02:10 PM            65,536 SRU.log
08/28/2017  01:34 PM            65,536 SRU00499.log
08/28/2017  01:37 PM            65,536 SRU0049A.log
08/28/2017  01:37 PM            65,536 SRU0049B.log
08/28/2017  02:10 PM        27,525,120 SRUDB.dat
08/28/2017  02:10 PM            16,384 SRUDB.jfm
08/11/2017  04:39 AM            65,536 SRUres00001.jrs
08/11/2017  04:39 AM            65,536 SRUres00002.jrs
08/28/2017  01:31 PM            65,536 SRUtmp.log
              10 File(s)     28,008,448 bytes
               2 Dir(s)  891,603,640,320 bytes free

  • 0

#37
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,006 posts
  • MVP

They are normal but you only see the miniports when you tell it to View, Show Hidden Devices.  

 

Search for

 

device manager

 

hit Enter

 

Find your Network Adapter then right click on it and disable.  (We will reenable it when we finish)

 

Then copy the next 2 lines:

del /q  C:\WINDOWS\system32\SRU\*.*
for /F "tokens=*" %1 in ('wevtutil.exe el') DO wevtutil.exe cl "%1"
Open an Elevated Command Prompt:
Win 7: Start, All Programs, Accessories then right click on Command Prompt and Run as Administrator
(Make sure you have a prompt C:\Windows\System32>  This is the default for an elevated command prompt))
 
Right click and Paste (or Edit then Paste) and the copied lines should appear.
Hit Enter.
 
Reenable the network adapter.    Reboot then run VEW again as before.

  • 0

#38
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

VEW System output:

 

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 04/09/2017 12:59:26 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • 0

#39
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

Disregard the one above. I forgot to reboot.


  • 0

#40
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 04/09/2017 1:10:02 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 04/09/2017 5:04:39 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The CldFlt service failed to start due to the following error:  The request is not supported.
 
Log: 'System' Date/Time: 04/09/2017 5:04:22 PM
Type: Error Category: 0
Event: 17 Source: BTHUSB
The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.
 
Log: 'System' Date/Time: 04/09/2017 5:03:40 PM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {D7FD466D-F6CF-4C8E-86DD-12E9B0FDAE48} did not register with DCOM within the required timeout.
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 04/09/2017 5:05:27 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 25 seconds since the last report.
 
Log: 'System' Date/Time: 04/09/2017 5:04:48 PM
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode.  The minimum required supported state mask is 0x491f7fffff, got 0x1fffffff.  Low Energy peripheral role functionality will not be available.
 
Log: 'System' Date/Time: 04/09/2017 5:04:22 PM
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode.  The minimum required supported state mask is 0x491f7fffff, got 0x1fffffff.  Low Energy peripheral role functionality will not be available.
 
Log: 'System' Date/Time: 04/09/2017 5:04:17 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device HID\Vid_8086&Pid_0001\6&f65e38f&0&0000.
 
Log: 'System' Date/Time: 04/09/2017 5:04:17 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device HID\Vid_8086&Pid_0001\6&221f9434&0&0000.
 
Log: 'System' Date/Time: 04/09/2017 5:04:17 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WudfRd failed to load for the device HID\Vid_8086&Pid_0001\6&34d944d9&0&0000.
 
Log: 'System' Date/Time: 04/09/2017 5:04:16 PM
Type: Warning Category: 0
Event: 1 Source: ISH
Intel® ISH Interface is being reset.
 
Log: 'System' Date/Time: 04/09/2017 5:04:16 PM
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\WUDFRd failed to load for the device ACPI\INT3400\2&daba3ff&1.
 
Log: 'System' Date/Time: 04/09/2017 5:03:04 PM
Type: Warning Category: 0
Event: 1073 Source: User32
The attempt by user NMS-HPLAPTOP\msnancy to restart/shutdown computer NMS-HPLAPTOP failed

  • 0

Advertisements


#41
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 04/09/2017 1:12:22 PM
 
Note: All dates below are in the format dd/mm/yyyy
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 04/09/2017 5:10:48 PM
Type: Error Category: 0
Event: 1008 Source: Microsoft-Windows-Perflib
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
 
Log: 'Application' Date/Time: 04/09/2017 5:07:49 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: PowerDVD14Agent.exe, version: 14.0.3.6129, time stamp: 0x56aad9cd Faulting module name: EvoParser.dll_unloaded, version: 1.2.0.8201, time stamp: 0x560cd3be Exception code: 0xc0000005 Fault offset: 0x00022d39 Faulting process id: 0x2cc4 Faulting application start time: 0x01d325a04062d36a Faulting application path: C:\Program Files (x86)\Cyberlink\PowerDVD14\PowerDVD14Agent.exe Faulting module path: EvoParser.dll Report Id: 0b7a81d3-061e-47a9-8dc0-16f785df53b2 Faulting package full name:  Faulting package-relative application ID: 
 
Log: 'Application' Date/Time: 04/09/2017 5:04:42 PM
Type: Error Category: 1
Event: 256 Source: DPTF
Intel® Dynamic Platform and Thermal Framework : ESIF(8.1.10605.221) TYPE: ERROR
 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\Sources\Manager\WIDomainPowerControlCapabilityChanged.cpp @ line 63
Executing Function:  WIDomainPowerControlCapabilityChanged::execute
Message:  Unhandled exception caught during execution of work item
Framework Event:  DomainPowerControlCapabilityChanged [19]
Participant:  TCPU [1]
Policy:  Passive Policy 2 [2]
Exception Function:  Policy::executeDomainPowerControlCapabilityChanged
Exception Text:  
Could not find client in directory.
 
 
Log: 'Application' Date/Time: 04/09/2017 5:04:42 PM
Type: Error Category: 1
Event: 256 Source: DPTF
Intel® Dynamic Platform and Thermal Framework : ESIF(8.1.10605.221) TYPE: ERROR
 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\Sources\Manager\WIDomainPerformanceControlCapabilityChanged.cpp @ line 63
Executing Function:  WIDomainPerformanceControlCapabilityChanged::execute
Message:  Unhandled exception caught during execution of work item
Framework Event:  DomainPerformanceControlCapabilityChanged [17]
Participant:  TCPU [1]
Policy:  Passive Policy 2 [2]
Exception Function:  Policy::executeDomainPerformanceControlCapabilityChanged
Exception Text:  
Could not find client in directory.
 
 
Log: 'Application' Date/Time: 04/09/2017 5:04:42 PM
Type: Error Category: 1
Event: 256 Source: DPTF
Intel® Dynamic Platform and Thermal Framework : ESIF(8.1.10605.221) TYPE: ERROR
 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\Sources\Manager\WIDomainPerformanceControlCapabilityChanged.cpp @ line 63
Executing Function:  WIDomainPerformanceControlCapabilityChanged::execute
Message:  Unhandled exception caught during execution of work item
Framework Event:  DomainPerformanceControlCapabilityChanged [17]
Participant:  TCPU [1]
Policy:  Passive Policy 2 [2]
Exception Function:  Policy::executeDomainPerformanceControlCapabilityChanged
Exception Text:  
Could not find client in directory.
 
 
Log: 'Application' Date/Time: 04/09/2017 5:04:42 PM
Type: Error Category: 1
Event: 256 Source: DPTF
Intel® Dynamic Platform and Thermal Framework : ESIF(8.1.10605.221) TYPE: ERROR
 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\..\Sources\Policies\PolicyLib\PolicyBase.cpp @ line 673
Executing Function:  PolicyBase::takeControlOfOsc
Message:  Failed to acquire OSC: Failure during execution of _OSC: 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\Sources\Manager\EsifServices.cpp @ line 473
Executing Function:  EsifServices::primitiveExecuteSet
Message:  Error returned from ESIF services interface function call
Participant:  NoParticipant
Domain:  NoDomain
ESIF Primitive:  SET_OPERATING_SYSTEM_CAPABILITIES [93]
ESIF Instance:  255
ESIF Return Code:  ESIF_E_UNSUPPORTED_ACTION_TYPE [1202]
 
 
Policy:  Passive Policy 2 [2]
 
 
Log: 'Application' Date/Time: 04/09/2017 5:04:42 PM
Type: Error Category: 1
Event: 256 Source: DPTF
Intel® Dynamic Platform and Thermal Framework : ESIF(8.1.10605.221) TYPE: ERROR
 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\..\Sources\Policies\PolicyLib\PolicyBase.cpp @ line 673
Executing Function:  PolicyBase::takeControlOfOsc
Message:  Failed to acquire OSC: Failure during execution of _OSC: 
DPTF Build Version:  8.1.10605.221
DPTF Build Date:  Oct 23 2015 12:24:15
Source File:  ..\..\..\Sources\Manager\EsifServices.cpp @ line 473
Executing Function:  EsifServices::primitiveExecuteSet
Message:  Error returned from ESIF services interface function call
Participant:  NoParticipant
Domain:  NoDomain
ESIF Primitive:  SET_OPERATING_SYSTEM_CAPABILITIES [93]
ESIF Instance:  255
ESIF Return Code:  ESIF_E_UNSUPPORTED_ACTION_TYPE [1202]
 
 
Policy:  Critical Policy [1]
 
 
Log: 'Application' Date/Time: 04/09/2017 4:56:26 PM
Type: Error Category: 0
Event: 2011 Source: Microsoft Office 16
Office Subscription licensing exception: Error Code: 0x803D0010; CorrelationId: {62B0265A-20E5-4DF5-B1B9-BE59986F058B}
 
Log: 'Application' Date/Time: 04/09/2017 4:56:26 PM
Type: Error Category: 0
Event: 2011 Source: Microsoft Office 16
Office Subscription licensing exception: Error Code: 0x803D0010; CorrelationId: {62B0265A-20E5-4DF5-B1B9-BE59986F058B}
 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  • 0

#42
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,006 posts
  • MVP

Check with HP and see if they have a new version of

 

Intel® Dynamic Platform and Thermal Framework

 

I think intel claims the program is the responsibility of the PC Maker

 

 

 

Do you have a wireless keyboard or mouse or perhaps headphones?  If not I would go into Device Manager and disable the Bluetooth driver as it seems to be unhappy.


  • 0

#43
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

I can't figure out if there is a new one or not. It seems to only distinguish by the model type and it doesn't pull mine up. I use a wireless mouse. Should I try to find an update for that too?


  • 0

#44
RKinner

RKinner

    Malware Expert

  • Expert
  • 20,006 posts
  • MVP

IF the wireless mouse uses bluetooth then it may need an update.

 

Give me the make and model number again and I will look for a new Intel® Dynamic Platform and Thermal Framework


  • 0

#45
frogg25

frogg25

    Member

  • Topic Starter
  • Member
  • PipPip
  • 33 posts

I'll check on the mouse update.

 

It's a Pavilion x360 Convertible. Thank you!


  • 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