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 slows down, almost freezes


  • Please log in to reply

#16
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

I don't see the error about the network adapter so that's a good thing. 

 

Do you have it using G: for the page file?  Might want to change it back to C: until you get the new drive.

 

Looking at the S.M.A.R.T. info in your Speccy log I don't see any sign of either the C: or the K: having problems so your program is probably not too far off.  Can't say I'm familiar with it tho.

 

If you post the problem in a new separate post I night not be the one who gets it unless you put "for rkinner" in the title.


  • 0

Advertisements


#17
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

RK: " Do you have it using G: for the page file?  Might want to change it back to C: until you get the new drive."

BF: I just checked the settings; the paging file is on C:\ only.

 

I am assuming that the case closed. Right?

==============================================================================

Here is the "bonus" problem.

 

External drives disconnect at random

 

This has been posted in February on several forums including geeks but nobody could provide a satisfactory explanation to the problem, much less a solution.

 

Last December, I bought a new machine, Dell with Win 10 Pro,

 

All data is stored on two external USB drives, named N: and T:.

 

From day one, drive N: would disconnect (or would be disconnected) from the computer for no reason, at random times. It has never once happened while it was connected to the old machine, a Gateway with Vista.

 

When this happens, I disconnect-reconnect the power supply to the drive and the computer recognizes it again.

 

Both drives are Seagate. N: is about 5 years old, T is 3 y.o

 

I spent a lot of time swapping USB ports, cables, etc. At one time, the N: drive was connected for 3-4 days in a row, then started dropping off again. At another time, the T: drive disconnected a couple times.

Both drive, when connected to the HP Win 7 machine (the mothership of the failed G: drive) were fine for several days, never being lost.

 

Incidentally, the Hard Disk Sentinel predicts about 280 days to N: and 1000 to T:.  I understand that N: will have to replaced, but it exhibits no issues when connected to another computer.

 

There is an article discussing problem between Seagate drives and Win 10. If interested, it's at https://windowsrepor...ive_windows_10/

 

As of this writing, the N:\ drive disconnects at least once a day, most likely every day (I am not keeping diary).

 

Any idea?

 

Thank you!


  • 0

#18
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

We're done with the Win 7.  I'll give you my standard cleanup instructions along with some recommendations first then address the Win 10 problem.

 

Time to clean up:
If we used FRST to clean your PC:

right click on FRST.exe or FRST64.exe (whichever you used) and rename it to uninstall.exe.  Then right click on uninstall.exe and Run as Admin.

 
If we installed Speccy it needs to be uninstalled.  Process Explorer, VEW, AdwCleaner, JRT  and their logs and Speccy's log can just be deleted.

Also make sure you have the latest versions of any adobe.com products you use like Shockwave, Flash or Acrobat.  Flash is now the most malware targeted program so it must be kept up to date.  Be careful with Adobe.  They are fond of offering optional downloads like yahoo or Ask toolbars or that worthless McAfee Security Scan.  Go slow and uncheck the optional stuff.

Whether you use adobe reader, acrobat or fox-it to read pdf files you need to disable Javascript in the program.  There is an exploit out there now that can use it to get on your PC.  For Adobe Reader:  Start, All Programs, Adobe Reader, Edit, Preferences, Click on Javascript in the left column and uncheck Enable Acrobat Javascript.  OK Close program.  It's the same for Foxit reader except you uncheck Enable Javascript Actions.


If you use Chrome/Firefox/Edge then get the Ublock Origin extension.  For IE go to adblockplus.org  and get the program.
If Chrome/Firefox is slow loading make sure it only has the current Java add-on.  Then download and run Speedy Fox.
http://www.crystalidea.com/speedyfox. Close Chrome/Firefox/Skpe. Hit Optimize.   You can run it any time that Chrome/Firefox seems slow starting..
(If it complains about Chrome still running you can stop it with Task Manager or go into Chrome then go to:

chrome://settings/

Hit Advanced at the bottom of the page then scroll down to near the bottom where it says System.

Change
Continue running background apps when Google Chrome is closed
to Off (slide the blue thing to the left and it turns brown)
Close Chrome.

You can run it any time that Chrome/Firefox seems slow starting.

If the browser is still slow then go in and disable all of your extensions, close the browser and Optimize with SpeedyFox then restart the browser.  If that helps then one or more of your extensions is at fault.  Go back in and turn them on one at a time and see if you can figure out which ones slow things down the most.


If you use Facebook you need FB Purity: http://www.fbpurity.com/

To prevent a relatively new phishing attack:  In Firefox, type:

https://www.xn--80ak6aa92e.com/

If the URL changes to https://www.apple.cominstead of the correct value
type:
about:config

in the URL box and hit Enter.  You should get a new page of options (if you get a notice about voiding the warranty just cancel the warning).  In the Search box put in

puny

You should only get 2 options:
"network.IDN_show_punycode"
We want it to say True but by default it is False so double click on it to toggle from False to True.


 "network.standard-url.punycode-host" Leave this one at default of False.
Close and restart firefox.

If you are a Facebook user get the FB Purity extension for your browser:
http://www.fbpurity.com/
This will stop all of the suggested pages and ads so that Facebook loads much quicker.


Be warned:  If you use Limewire, utorrent or any of the other P2P programs you will probably be coming back to the Malware Removal forum.  If you must use P2P then submit any files you get to http://virustotal.combeforeyou open them.

Due to a recent rise in the number of Crytolocker infections I am now recommending you install:

https://www.bleeping...somware/dl/306/
It's currently a free version.

If you have a router, log on to it today and change the default password!  If using a Wireless router you really should be using encryption on the link.  Use the strongest (newest) encryption method that your router and PC wireless adapter support especially if you own a business.  See http://www.king5.com...0637284.htmlandhttp://www.seattlepi...ted-1344185.php for why encryption is important.  If you don't know how, visit the router maker's website.  They all have detailed step by step instructions or a wizard you can download.

Special note on Java.  Old Java versions should be removed after first clearing the Java Cache by following the instructions in:
http://www.java.com/...lugin_cache.xml
Then remove the old versions by going to Control Panel, Programs and Features and Uninstall all Java programs which are not the latest.  If in doubt uninstall all.  These may call themselves: Java Runtime, Runtime Environment, Runtime, JRE, Java Virtual Machine, Virtual Machine, Java VM, JVM, VM, J2RE, J2SE.  Get the latest version from Java.com.  They will usually attempt to foist some garbage like the Ask toolbar, Yahoo toolbar or McAfee Security Scan on you as part of the download.  Just uncheck the garbage before the download (or install) starts.  If you use a 64-bit browser and want the 64-bit version of Java you need to use it to visit java.com.
Due to multiple security problems with Java we are now recommending that it not be installed unless you absolutely know you need it.  IF that is the case then go to Control Panel, Java, Security and slide it up to the highest level.  OK.


Recommended software: (I'm not saying you should download these just that if you have a need for a new program these are safe and work)  
Compression:  7-zip.  Avoid WinRar and WinZip as the free versions have adware.
Video Player:  VLC  Unlike Windows Medi Player it never seems to need extra files to work.
Photo organizer and editor:  Google's Picasa.  While it has been discontinued by Google you can still get it at:
http://techfilehippo...-free-download/
Office like free program:  Open Office: https://www.openoffice.org/download/
or
LibreOffice: https://www.libreoffice.org/
Free Anti-Virus:  Avast
Free Malware prevention:  MBAM: Free version at https://www.malwareb...m/mwb-download/
Can run with your anti-virus.
Paid Anti-Virus:  Kaspersky or BitDefender
Utilities:
Root Kit Detector:  MBAR: https://www.malwareb...om/antirootkit/
Process Explorer:  Show you what is running on the PC.  Like Task manager but better:  http://live.sysinter...com/procexp.exe
WhoCrashed: Why did your system crash?
http://www.resplendence.com/downloads
Then click on Download free home edition
where it says:
WhoCrashed 5.51
Comprehensible crash dump analysis tool
for Windows 10/8.1/8/7/Vista/XP/2012/2008/2003 (x86 and x64)
System Health:
Speccy:  
http://www.filehippo.com/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!)  Decline CCleaner if offered.  Pay attention to SMART info on your hard drives and to temps.  If in doubt about temps try:
SpeedFan:  Try speedfan
http://www.filehippo...nload_speedfan/
Download, save and Install it (Win 7 or Vista right click and Run As Admin.) then run it.
Download Flash and Video.  To save flash video.  Works with Firefox.  https://addons.mozil...lash-and-video/This allows you to start a recording and then switch to a different window and record another video.

With Win 10 only there is a new Game recorder program.  It's supposed to only work for games but it works nicely to record any video you watch.  Hit the Win key + Alt + r to start the recorder.  The first time it asks you if it is looking at a game.  Just tell it yes.  After that it starts recording whenever you bring it up.  Videos are saved to the Captures folder under Videos.  You can only record what you watch so limited to only one video at a time.  Best to go to full screen before starting the recorder.

Avoid:  
Advanced System Care
SuperAntiSpyware
HitmanPro
Spybot S&D
Any P2P software especially if it comes from Conduit.
Registry Cleaners
Driver updating software.
PC fixing or Speed up software.
Running more than one anti-virus.
Seagate hard drives.  If you have one it's going to fail on you so backup your data now!

 

Win 10 problem:

See if this helps:

Search for

 

disk management

 

hit enter.

 

Scroll down to Universal Serial Bus Controllers and hit the arrow in front to open it up.  Start at the bottom of the list of drivers.  Right click on each and select Properties then Power Management.  Uncheck

 

Allow the Computer to turn off this device to save power.

 

Some of them may not have the power management tab.  Just go thru and make sure that those that have it have the box unchecked.

 

You can also do the same to Storage Controllers and Disk Drives tho on my desktop they do not have the Power Management option.  I always do it to my Network Adapters.

 

Reboot when done.

 

In my opinion Seagate drives are not reliable so avoid when you replace yours.  Best drives are Western Digital Blacks but they tend to be a bit more.  That's all I use.


  • 0

#19
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

Thank you! This is some homework.  Will do, post findings if any.


  • 0

#20
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

While cleaning the PC, a few questions arose:

 

RK: "If we used FRST to clean your PC:
right click on FRST.exe or FRST64.exe (whichever you used) and rename it to uninstall.exe.  Then right click on uninstall.exe and Run as Admin."

 

BF: There are no references to FRST64.exe in the instructions you sent me. However, I found two copies of this program in my PC.   When I renamed it to uninstall.exe and R-clicked as admin, I got a dialog screen with [scan] [search files] [search registry ] and [fix] buttons. 

What am I supposed to do to what results please?

 

Next:

 

RK: "... You should only get 2 options:
"network.IDN_show_punycode"
We want it to say True but by default it is False so double click on it to toggle from False to True.

 

BF: done; 6/5/2019 9:28 PM

 "network.standard-url.punycode-host" Leave this one at default of False.
Close and restart firefox.

 

BF: the default value was set to True; changed to False. 6/5/2019 9:30 PM

 

Next

 

RK: "Due to a recent rise in the number of Crytolocker infections I am now recommending you install:

https://www.bleeping...somware/dl/306/
It's currently a free version.

 

BF: downloaded file mbarw-setup-consumer-0.9.18.807.exe

As soon as the app was downloaded and installed, a bubble flashed about a new version; I clicked on it it but the setup screens were different from the original so I aborted; the version offered was 3.6.1.2711.

 

Thank you!

 

To be continued...


  • 0

#21
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

We didn't run FRST so you probably have an old version.  You can just delete it.


  • 0

#22
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

Re Win 7.

Finished clean up.

 

Re Win 10.

Computer stopped working

 

Yesterday, when I came to it, It showed a login screen, i.e. the system had restarted on its own (I hate this design).

 

Upon login, the system informed about 2 critical and 2 less important updates.  I OK'ed all 4. During the update, a grey message screen lit up:

"WARNING! The system firmware is being updated. Keyboard is locked. DO NOT TURN THE POWER OFF!!!"

I snapped a screen shot with a phone when the message read "Write new nvram block..."

 

The entire update with the reboot took 22 min.

 

I am being anal with these descriptions because I don't know what info IS important and what NOT.

 

Upon login, I unchecked the Power Management Option where was possible, as per your advice,  and rebooted the  machine again .

 

The reboot process took 30 min.

 

Upon login, I discovered the was no mouse. So,  I navigated with the keyboard to the power options and selected Shut Down.

 

Nothing was happening for 30 min, then a blue screen of death appeared:

 

:(

Your PC ran into a problem... collecting error info ... will restart...

If you call support give them: Stop code: DRIVER_POWER_STATE_FAILURE

 

Now, 9 hrs later, the screen is still there.  The computer is VERY noisy, probably all fans working.

 

I just shut it down with the switch.

 

Otherwise things are fine.

 

Thank you!


Edited by BerDov, 09 June 2019 - 05:09 AM.

  • 0

#23
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

Windows does not normally write to NVRAM.  Sounds like your PC maker's software decided you needed a BIOS upgrade.  I've seen BIOS updates mess up the BIOS settings so try: Shut it down then start it up and try to get into the BIOS setup.  (Check your PC maker's website for how to do that)  Once you get in, there should be an option to set to Default options.  Do that and Save and Exit. Then see if it will boot


  • 0

#24
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

I turned the computer ON, but forgot to switch the keyboard and the mouse from HP to DELL (via KVM switch) so tapping F2 was useless.

 

However, the computer initialized in about a minute, I logged in, mouse worked.

 

I checked the USB Controller Power Management option, it was unchecked;  it appears that the changed setting were not lost.

 

Should I restart and try to go into BIOS now or should I wait till the computer acts up again?

 

When I opened the Win Explorer, the N: drive was lost. I unplugged it and plugged back in.

 

That's where we are right now.

 

Thanks.


  • 0

#25
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

Probably a good idea to go into the BIOS sometime just so you know how and then look through it to see how it is set but if it's working now then don't set it to Default.

 

If the USB Power Management was unchecked in all instances then please leave it unchecked.  Probably not the problem.

 

Let's run DISM & SFC to make sure Windows is happy with its files.

 

Open an elevated command prompt:

http://www.howtogeek...-in-windows-10/
http://www.eightforu...indows-8-a.html

(If you open an elevated Command Prompt properly it will say Administrator: Command Prompt in the margin at the top of the window)


Once you have an elevated command prompt:

Type:

 DISM  /Online  /Cleanup-Image  /RestoreHealth

 (I use two spaces so you can be sure to see where one space goes.)
Hit Enter.  This will take a while (10-20 minutes) 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  >  %UserProfile%\desktop\junk.txt


Hit Enter.  Then type::


notepad %UserProfile%\desktop\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
http://images.malwar...om/vino/VEW.exe
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.)
 

 

You might try USBLogView from Nirsoft:

https://www.nirsoft....b_log_view.html

 

Also USBDeview

 

https://www.nirsoft....vices_view.html


  • 0

Advertisements


#26
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

Here is what I did:

 

"Once you have an elevated command prompt: Type:
 DISM  /Online  /Cleanup-Image  /RestoreHealth
 

BF: took 1 min to run; "The restore operation completed successfully"

 

"Reboot. 

BF: It took almost 5 min to see the login screen; upon login, a totally blank desktop appeared (1st time ever!); it took one minute to display the icons;

also, the N:\ drive did not connect; most times it shows in the win explorer upon reboot;

 

"Open an elevated Command Prompt again and type (with an Enter after the line):

sfc  /scannow

 

BF: After about 3 min, my report was: " Windows Resource Protection found corrupt files and successfully repaired them"

 

BF: executed VEW.exe; reports are below:

===========

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 11/06/2019 2:43:37 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 09/06/2019 7:59:54 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/06/2019 6:34:42 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® Management and Security Application Local Management Service service failed to start due to the following error:  The system cannot find the file specified.

Log: 'System' Date/Time: 11/06/2019 6:34:40 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

Log: 'System' Date/Time: 11/06/2019 6:34:37 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The Windows Search service hung on starting.

Log: 'System' Date/Time: 11/06/2019 6:34:10 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

Log: 'System' Date/Time: 11/06/2019 6:33:40 PM
Type: Error Category: 0
Event: 7011 Source: Service Control Manager
A timeout (30000 milliseconds) was reached while waiting for a transaction response from the WSearch service.

Log: 'System' Date/Time: 11/06/2019 6:29:54 PM
Type: Error Category: 0
Event: 14 Source: nvlddmkm
The event description cannot be found.

Log: 'System' Date/Time: 11/06/2019 6:26:40 PM
Type: Error Category: 0
Event: 56 Source: Application Popup
The event description cannot be found.

Log: 'System' Date/Time: 09/06/2019 8:02:19 PM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® Management and Security Application Local Management Service service failed to start due to the following error:  The system cannot find the file specified.

Log: 'System' Date/Time: 09/06/2019 8:00:12 PM
Type: Error Category: 0
Event: 1001 Source: Microsoft-Windows-WER-SystemErrorReporting
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000009f (0x0000000000000004, 0x000000000000012c, 0xffffe30da870e040, 0xffffbd0d06a9f7e0). A dump was saved in: C:\WINDOWS\Minidump\060919-19921-01.dmp. Report Id: 0d05bdb1-b907-4c72-910b-5d65797f402d.

Log: 'System' Date/Time: 09/06/2019 8:00:08 PM
Type: Error Category: 0
Event: 14 Source: nvlddmkm
The event description cannot be found.

Log: 'System' Date/Time: 09/06/2019 7:59:54 PM
Type: Error Category: 0
Event: 161 Source: volmgr
Dump file creation failed due to error during dump creation.

Log: 'System' Date/Time: 09/06/2019 7:59:52 PM
Type: Error Category: 0
Event: 56 Source: Application Popup
The event description cannot be found.

Log: 'System' Date/Time: 09/06/2019 2:02:11 AM
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The Intel® Management and Security Application Local Management Service service failed to start due to the following error:  The system cannot find the file specified.

Log: 'System' Date/Time: 09/06/2019 2:00:02 AM
Type: Error Category: 0
Event: 14 Source: nvlddmkm
The event description cannot be found.

Log: 'System' Date/Time: 09/06/2019 1:50:33 AM
Type: Error Category: 0
Event: 56 Source: Application Popup
The event description cannot be found.

Log: 'System' Date/Time: 09/06/2019 1:30:46 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/06/2019 1:30:46 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/06/2019 1:30:46 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/06/2019 1:30:46 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/06/2019 1:30:46 AM
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {AB8902B4-09CA-4BB6-B78D-A8F59079A8D5} did not register with DCOM within the required timeout.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 11/06/2019 6:34:34 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:34:14 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:33:57 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:33:31 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:33:29 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:33:11 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:33:09 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:32:50 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:32:34 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:32:20 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:32:06 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.SecurityAppBroker  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 11/06/2019 6:32:06 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID  Windows.SecurityCenter.WscBrokerManager  and APPID  Unavailable  to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 11/06/2019 6:32:06 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:31:52 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:31:37 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:31:23 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:31:09 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:30:55 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:30:41 PM
Type: Warning Category: 0
Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

Log: 'System' Date/Time: 11/06/2019 6:30:30 PM
Type: Warning Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID  {C2F03A33-21F5-47FA-B4BB-156362A2F239}  and APPID  {316CDED5-E4AE-4B15-9113-7055D84DCC97}  to the user DELL\boris SID (S-1-5-21-4153292753-3333531167-3868062159-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.1_neutral_neutral_cw5n1h2txyewy SID (S-1-15-2-155514346-2573954481-755741238-1654018636-1233331829-3075935687-2861478708). This security permission can be modified using the Component Services administrative tool.

=====================================

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 11/06/2019 2:50:20 PM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 10/06/2019 10:03:24 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 17360 and the required size was 31752.

Log: 'Application' Date/Time: 09/06/2019 8:19:14 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 17392 and the required size was 31200.

Log: 'Application' Date/Time: 09/06/2019 2:03:31 AM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007045b, A system shutdown is in progress. .

Log: 'Application' Date/Time: 09/06/2019 2:03:31 AM
Type: Error Category: 0
Event: 13 Source: VSS
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress. ]

Log: 'Application' Date/Time: 09/06/2019 1:30:50 AM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007045b, A system shutdown is in progress. .

Log: 'Application' Date/Time: 09/06/2019 1:30:50 AM
Type: Error Category: 0
Event: 13 Source: VSS
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress. ]

Log: 'Application' Date/Time: 09/06/2019 12:31:50 AM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x8007045b, A system shutdown is in progress. .

Log: 'Application' Date/Time: 09/06/2019 12:31:50 AM
Type: Error Category: 0
Event: 13 Source: VSS
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress. ]

Log: 'Application' Date/Time: 09/06/2019 12:30:55 AM
Type: Error Category: 0
Event: 10007 Source: Microsoft-Windows-RestartManager
Application or service 'Intel® Management and Security Application Local Management Service' could not be restarted.

Log: 'Application' Date/Time: 09/06/2019 12:30:55 AM
Type: Error Category: 0
Event: 11920 Source: MsiInstaller
Product: Intel® Management Engine Components -- Error 1920. Service 'Intel® Dynamic Application Loader Host Interface Service' (jhi_service) failed to start.  Verify that you have sufficient privileges to start system services.

Log: 'Application' Date/Time: 09/06/2019 12:30:13 AM
Type: Error Category: 0
Event: 10007 Source: Microsoft-Windows-RestartManager
Application or service 'Intel® Dynamic Application Loader Host Interface Service' could not be restarted.

Log: 'Application' Date/Time: 08/06/2019 5:13:41 AM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 16152 and the required size was 34144.

Log: 'Application' Date/Time: 07/06/2019 3:39:25 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: ServiceShell.exe, version: 1.1.0.46, time stamp: 0x5be9f49a Faulting module name: KERNELBASE.dll, version: 10.0.18362.86, time stamp: 0xda9755c4 Exception code: 0xe0434352 Fault offset: 0x000000000003a839 Faulting process id: 0x33ac Faulting application start time: 0x01d51b2adceb3b85 Faulting application path: C:\Program Files (x86)\Dell\UpdateService\ServiceShell.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: 50592c72-6cbe-45b4-b4a1-b4ad4519b980 Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 07/06/2019 3:39:25 PM
Type: Error Category: 0
Event: 1026 Source: .NET Runtime
Application: ServiceShell.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.MissingMemberException
   at Dell.Asimov.UpdateTelemetry.Platinum.PlatinumProvider+<Send>d__10.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()



Log: 'Application' Date/Time: 06/06/2019 11:43:37 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 18296 and the required size was 34512.

Log: 'Application' Date/Time: 05/06/2019 11:43:36 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 19416 and the required size was 33224.

Log: 'Application' Date/Time: 04/06/2019 10:39:29 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 15632 and the required size was 34328.

Log: 'Application' Date/Time: 03/06/2019 10:09:27 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 13336 and the required size was 34880.

Log: 'Application' Date/Time: 02/06/2019 8:09:06 PM
Type: Error Category: 0
Event: 1020 Source: Microsoft-Windows-Perflib
The required buffer size is greater than the buffer size passed to the Collect function of the "C:\Windows\System32\perfts.dll" Extensible Counter DLL for the "LSM" service. The given buffer size was 14016 and the required size was 39112.

Log: 'Application' Date/Time: 02/06/2019 8:06:02 PM
Type: Error Category: 0
Event: 8193 Source: VSS
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance.  hr = 0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. .

Operation:
   Instantiating VSS server

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 11/06/2019 6:25:58 PM
Type: Warning Category: 1
Event: 2000 Source: Intel( R ) RMT
IRMT - CAudioManager::UnregisterMmClientCallbackEvent   Unable to unregister default audio device change notification callback, status=0x80070490

Log: 'Application' Date/Time: 11/06/2019 1:33:24 AM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 09/06/2019 2:03:31 AM
Type: Warning Category: 1
Event: 2000 Source: Intel( R ) RMT
IRMT - CAudioManager::UnregisterMmClientCallbackEvent   Unable to unregister default audio device change notification callback, status=0x80070490

Log: 'Application' Date/Time: 09/06/2019 1:30:50 AM
Type: Warning Category: 1
Event: 2000 Source: Intel( R ) RMT
IRMT - CAudioManager::UnregisterMmClientCallbackEvent   Unable to unregister default audio device change notification callback, status=0x80070490

Log: 'Application' Date/Time: 09/06/2019 12:31:50 AM
Type: Warning Category: 1
Event: 2000 Source: Intel( R ) RMT
IRMT - CAudioManager::UnregisterMmClientCallbackEvent   Unable to unregister default audio device change notification callback, status=0x80070490

Log: 'Application' Date/Time: 09/06/2019 12:30:24 AM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 09/06/2019 12:30:24 AM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 09/06/2019 12:30:24 AM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, IntelMEProv, has been registered in the Windows Management Instrumentation namespace root\Intel_ME to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

Log: 'Application' Date/Time: 09/06/2019 12:30:10 AM
Type: Warning Category: 3
Event: 2001 Source: LMS
The event description cannot be found.

Log: 'Application' Date/Time: 07/06/2019 1:13:39 AM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 07/06/2019 12:43:37 AM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 07/06/2019 12:13:37 AM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 06/06/2019 10:43:37 PM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 06/06/2019 10:13:37 PM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 06/06/2019 9:13:37 PM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 06/06/2019 7:43:37 PM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 06/06/2019 5:13:37 PM
Type: Warning Category: 0
Event: 2017 Source: Microsoft-Windows-PerfOS
Unable to collect NUMA physical memory utilization data. The first four bytes (DWORD) of the Data section contains the status code.

Log: 'Application' Date/Time: 04/06/2019 11:05:30 PM
Type: Warning Category: 1
Event: 2000 Source: Intel( R ) RMT
IRMT - CAudioManager::UnregisterMmClientCallbackEvent   Unable to unregister default audio device change notification callback, status=0x80070490

Log: 'Application' Date/Time: 02/06/2019 8:05:59 PM
Type: Warning Category: 14
Event: 4104 Source: Microsoft-Windows-MSDTC Client 2
Failed trying to get the state of the cluster node: DELL.The error code returned: 0x8007085A

Log: 'Application' Date/Time: 02/06/2019 8:05:02 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace ROOT\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

==============================

BF: Executed USBLogView from Nirsoft and USBDeview; could not interpret the results, sorry. Here they are, copied from txt(csv) file.

 

======================== LOGView =====================================

==================================================
Event Type        : Unplug
Event Time        : 6/11/2019 3:26:46 PM
Device Name       : Port_#0011.Hub_#0001
Description       : USB Composite Device
Device Type       : Unknown
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
==================================================

==================================================
Event Type        : Unplug
Event Time        : 6/11/2019 3:26:46 PM
Device Name       : 0000.0014.0000.011.000.000.000.000.000
Description       : Logitech USB Input Device
Device Type       : HID (Human Interface Device)
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 01
==================================================

==================================================
Event Type        : Unplug
Event Time        : 6/11/2019 3:26:46 PM
Device Name       : 0000.0014.0000.011.000.000.000.000.000
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 02
==================================================

==================================================
Event Type        : Unplug
Event Time        : 6/11/2019 3:26:46 PM
Device Name       : 0000.0014.0000.011.000.000.000.000.000
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 00
USB Protocol      : 00
==================================================

==================================================
Event Type        : Plug
Event Time        : 6/11/2019 3:27:01 PM
Device Name       : Port_#0011.Hub_#0001
Description       : USB Composite Device
Device Type       : Unknown
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
==================================================

==================================================
Event Type        : Plug
Event Time        : 6/11/2019 3:27:01 PM
Device Name       : 0000.0014.0000.011.000.000.000.000.000
Description       : Logitech USB Input Device
Device Type       : HID (Human Interface Device)
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 01
==================================================

==================================================
Event Type        : Plug
Event Time        : 6/11/2019 3:27:01 PM
Device Name       : 0000.0014.0000.011.000.000.000.000.000
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 02
==================================================

==================================================
Event Type        : Plug
Event Time        : 6/11/2019 3:27:01 PM
Device Name       : 0000.0014.0000.011.000.000.000.000.000
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Drive Letter      :
Serial Number     :
Vendor ID         : 046d
Product ID        : c52b
Vendor Name       : Logitech, Inc.
Product Name      : Unifying Receiver
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 00
USB Protocol      : 00
==================================================

============================== USBDeView =====================================

==================================================
Device Name       : Port_#0022.Hub_#0001
Description       : Unknown USB Device (Set Address Failed)
Device Type       : Unknown
Connected         : No
Safe To Unplug    : No
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/8/2019 9:50:34 PM
Last Plug/Unplug Date: 6/8/2019 9:50:33 PM
VendorID          : 0000
ProductID         : 0004
Firmware Revision : 0.00
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   :
Service Name      :
Service Description:
Driver Filename   :
Device Class      :
Device Mfg        : (Standard USB Host Controller)
Friendly Name     :
Power             :
USB Version       :
Driver Description: Unknown USB Device (Set Address Failed)
Driver Version    : 10.0.18362.1
Driver InfSection : BADDEVICE.Dev.NT
Driver InfPath    : usb.inf
Instance ID       : USB\VID_0000&PID_0004\5&1488a0d9&0&22
Capabilities      : Removable, SilentInstall, RawDeviceOK
==================================================

==================================================
Device Name       : Port_#0008.Hub_#0001
Description       : Qualcomm QCA9377 Bluetooth
Device Type       : Bluetooth Device
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 2:26:43 PM
Last Plug/Unplug Date: 6/2/2019 4:02:11 PM
VendorID          : 0cf3
ProductID         : e009
Firmware Revision : 0.01
USB Class         : e0
USB SubClass      : 01
USB Protocol      : 01
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 6&2403f536&0
Service Name      : BTHUSB
Service Description: @bth.inf,%BTHUSB.SvcDesc%;Bluetooth Radio USB Driver
Driver Filename   : BTHUSB.sys
Device Class      :
Device Mfg        : Qualcomm
Friendly Name     :
Power             : 100 mA
USB Version       : 2.01
Driver Description: Qualcomm QCA9377 Bluetooth
Driver Version    : 10.0.0.714
Driver InfSection : QCABTUSB
Driver InfPath    : oem21.inf
Instance ID       : USB\VID_0CF3&PID_E009\5&1488a0d9&0&8
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : Basic Optical Mouse
Description       : Microsoft Hardware USB Mouse
Device Type       : HID (Human Interface Device)
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 2:26:43 PM
Last Plug/Unplug Date: 6/9/2019 3:59:55 PM
VendorID          : 045e
ProductID         : 0084
Firmware Revision : 0.00
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 02
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 6&2ca2c2be&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : Microsoft
Friendly Name     :
Power             : 100 mA
USB Version       : 1.10
Driver Description: Microsoft Hardware USB Mouse
Driver Version    : 9.9.108.0
Driver InfSection : IPCdless_Install
Driver InfPath    : oem30.inf
Instance ID       : USB\VID_045E&PID_0084\5&1488a0d9&0&13
Capabilities      : Removable, SurpriseRemovalOK
==================================================

==================================================
Device Name       : USB Receiver
Description       : Logitech USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 3:27:01 PM
Last Plug/Unplug Date: 6/11/2019 3:27:01 PM
VendorID          : 046d
ProductID         : c52b
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 01
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 7&228d51bc&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : Logitech (x64)
Friendly Name     :
Power             : 98 mA
USB Version       : 2.00
Driver Description: Logitech USB Input Device
Driver Version    : 1.10.78.0
Driver InfSection : LogiLDA
Driver InfPath    : oem44.inf
Instance ID       : USB\VID_046D&PID_C52B&MI_00\6&1700755d&0&0000
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : USB Receiver
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 3:27:01 PM
Last Plug/Unplug Date: 6/11/2019 3:27:01 PM
VendorID          : 046d
ProductID         : c52b
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 02
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 7&149ec06&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : (Standard system devices)
Friendly Name     :
Power             : 98 mA
USB Version       : 2.00
Driver Description: USB Input Device
Driver Version    : 10.0.18362.1
Driver InfSection : HID_Inst.NT
Driver InfPath    : input.inf
Instance ID       : USB\VID_046D&PID_C52B&MI_01\6&1700755d&0&0001
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : USB Receiver
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 3:27:01 PM
Last Plug/Unplug Date: 6/11/2019 3:27:01 PM
VendorID          : 046d
ProductID         : c52b
Firmware Revision : 12.03
USB Class         : 03
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 7&252129c8&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : (Standard system devices)
Friendly Name     :
Power             : 98 mA
USB Version       : 2.00
Driver Description: USB Input Device
Driver Version    : 10.0.18362.1
Driver InfSection : HID_Inst.NT
Driver InfPath    : input.inf
Instance ID       : USB\VID_046D&PID_C52B&MI_02\6&1700755d&0&0002
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : 0002.0000.0000.003.000.000.000.000.000
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : No
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/3/2019 12:14:27 PM
Last Plug/Unplug Date: 6/3/2019 12:14:27 PM
VendorID          : 0e8f
ProductID         : 0020
Firmware Revision : 2.80
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 01
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 8&629e50e&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : (Standard system devices)
Friendly Name     :
Power             : 400 mA
USB Version       : 1.10
Driver Description: USB Input Device
Driver Version    : 10.0.18362.1
Driver InfSection : HID_Inst.NT
Driver InfPath    : input.inf
Instance ID       : USB\VID_0E8F&PID_0020&MI_00\7&1ba01871&0&0000
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : PS2toUSB Adapter
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 2:26:46 PM
Last Plug/Unplug Date: 6/11/2019 2:26:46 PM
VendorID          : 0e8f
ProductID         : 0020
Firmware Revision : 2.80
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 01
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 8&ff8fe1f&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : (Standard system devices)
Friendly Name     :
Power             : 400 mA
USB Version       : 1.10
Driver Description: USB Input Device
Driver Version    : 10.0.18362.1
Driver InfSection : HID_Inst.NT
Driver InfPath    : input.inf
Instance ID       : USB\VID_0E8F&PID_0020&MI_00\7&2ef75247&0&0000
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : 0002.0000.0000.003.000.000.000.000.000
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : No
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/3/2019 12:14:27 PM
Last Plug/Unplug Date: 6/3/2019 12:14:27 PM
VendorID          : 0e8f
ProductID         : 0020
Firmware Revision : 2.80
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 02
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 8&1ded7153&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : (Standard system devices)
Friendly Name     :
Power             : 400 mA
USB Version       : 1.10
Driver Description: USB Input Device
Driver Version    : 10.0.18362.1
Driver InfSection : HID_Inst.NT
Driver InfPath    : input.inf
Instance ID       : USB\VID_0E8F&PID_0020&MI_01\7&1ba01871&0&0001
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : PS2toUSB Adapter
Description       : USB Input Device
Device Type       : HID (Human Interface Device)
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 2:26:46 PM
Last Plug/Unplug Date: 6/11/2019 2:26:46 PM
VendorID          : 0e8f
ProductID         : 0020
Firmware Revision : 2.80
USB Class         : 03
USB SubClass      : 01
USB Protocol      : 02
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 8&13de3fa3&0
Service Name      : HidUsb
Service Description: @input.inf,%HID.SvcDesc%;Microsoft HID Class Driver
Driver Filename   : hidusb.sys
Device Class      :
Device Mfg        : (Standard system devices)
Friendly Name     :
Power             : 400 mA
USB Version       : 1.10
Driver Description: USB Input Device
Driver Version    : 10.0.18362.1
Driver InfSection : HID_Inst.NT
Driver InfPath    : input.inf
Instance ID       : USB\VID_0E8F&PID_0020&MI_01\7&2ef75247&0&0001
Capabilities      : SurpriseRemovalOK
==================================================

==================================================
Device Name       : Port_#0005.Hub_#0001
Description       : USB Attached SCSI (UAS) Mass Storage Device
Device Type       : Mass Storage
Connected         : Yes
Safe To Unplug    : No
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     : MSFT30NAA32DMQ
Created Date      : 6/2/2019 3:59:50 PM
Last Plug/Unplug Date: 6/2/2019 4:00:11 PM
VendorID          : 0bc2
ProductID         : 231a
Firmware Revision : 7.08
USB Class         : 08
USB SubClass      : 06
USB Protocol      : 62
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   :
Service Name      : UASPStor
Service Description: @uaspstor.inf,%UASPortName%;USB Attached SCSI (UAS) Driver
Driver Filename   : uaspstor.sys
Device Class      :
Device Mfg        : USB Attached SCSI (UAS) Compatible Device
Friendly Name     :
Power             :
USB Version       :
Driver Description: USB Attached SCSI (UAS) Mass Storage Device
Driver Version    : 10.0.18362.1
Driver InfSection : UASPort_Install_Control
Driver InfPath    : uaspstor.inf
Instance ID       : USB\VID_0BC2&PID_231A\MSFT30NAA32DMQ
Capabilities      : Removable, UniqueID
==================================================

==================================================
Device Name       : Port_#0006.Hub_#0001
Description       : USB Attached SCSI (UAS) Mass Storage Device
Device Type       : Mass Storage
Connected         : Yes
Safe To Unplug    : No
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     : MSFT30NA8ERJDF
Created Date      : 6/2/2019 3:59:50 PM
Last Plug/Unplug Date: 6/2/2019 4:00:11 PM
VendorID          : 0bc2
ProductID         : 331a
Firmware Revision : 9.09
USB Class         : 08
USB SubClass      : 06
USB Protocol      : 62
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 6&2eaf4ed&0
Service Name      : UASPStor
Service Description: @uaspstor.inf,%UASPortName%;USB Attached SCSI (UAS) Driver
Driver Filename   : uaspstor.sys
Device Class      :
Device Mfg        : USB Attached SCSI (UAS) Compatible Device
Friendly Name     :
Power             :
USB Version       :
Driver Description: USB Attached SCSI (UAS) Mass Storage Device
Driver Version    : 10.0.18362.1
Driver InfSection : UASPort_Install_Control
Driver InfPath    : uaspstor.inf
Instance ID       : USB\VID_0BC2&PID_331A\MSFT30NA8ERJDF
Capabilities      : Removable, UniqueID
==================================================

==================================================
Device Name       : Port_#0023.Hub_#0001
Description       : USB Attached SCSI (UAS) Mass Storage Device
Device Type       : Mass Storage
Connected         : Yes
Safe To Unplug    : No
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     : MSFT30NA8ERLKP
Created Date      : 6/2/2019 3:59:50 PM
Last Plug/Unplug Date: 6/2/2019 4:00:11 PM
VendorID          : 0bc2
ProductID         : 331a
Firmware Revision : 9.09
USB Class         : 08
USB SubClass      : 06
USB Protocol      : 62
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 6&fc912d2&0
Service Name      : UASPStor
Service Description: @uaspstor.inf,%UASPortName%;USB Attached SCSI (UAS) Driver
Driver Filename   : uaspstor.sys
Device Class      :
Device Mfg        : USB Attached SCSI (UAS) Compatible Device
Friendly Name     :
Power             :
USB Version       :
Driver Description: USB Attached SCSI (UAS) Mass Storage Device
Driver Version    : 10.0.18362.1
Driver InfSection : UASPort_Install_Control
Driver InfPath    : uaspstor.inf
Instance ID       : USB\VID_0BC2&PID_331A\MSFT30NA8ERLKP
Capabilities      : Removable, UniqueID
==================================================

==================================================
Device Name       : Port_#0022.Hub_#0001
Description       : USB Attached SCSI (UAS) Mass Storage Device
Device Type       : Mass Storage
Connected         : Yes
Safe To Unplug    : No
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     : MSFT30NA7E63C8
Created Date      : 6/2/2019 3:59:50 PM
Last Plug/Unplug Date: 6/2/2019 4:00:11 PM
VendorID          : 0bc2
ProductID         : ab34
Firmware Revision : 1.00
USB Class         : 08
USB SubClass      : 06
USB Protocol      : 62
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   :
Service Name      : UASPStor
Service Description: @uaspstor.inf,%UASPortName%;USB Attached SCSI (UAS) Driver
Driver Filename   : uaspstor.sys
Device Class      :
Device Mfg        : USB Attached SCSI (UAS) Compatible Device
Friendly Name     :
Power             :
USB Version       :
Driver Description: USB Attached SCSI (UAS) Mass Storage Device
Driver Version    : 10.0.18362.1
Driver InfSection : UASPort_Install_Control
Driver InfPath    : uaspstor.inf
Instance ID       : USB\VID_0BC2&PID_AB34\MSFT30NA7E63C8
Capabilities      : Removable, UniqueID
==================================================

==================================================
Device Name       : USB Receiver
Description       : USB Composite Device
Device Type       : Unknown
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/11/2019 3:27:01 PM
Last Plug/Unplug Date: 6/3/2019 12:14:27 PM
VendorID          : 046d
ProductID         : c52b
Firmware Revision : 12.03
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 6&1700755d&0
Service Name      : usbccgp
Service Description: @usb.inf,%GenericParent.SvcDesc%;Microsoft USB Generic Parent Driver
Driver Filename   : usbccgp.sys
Device Class      :
Device Mfg        : (Standard USB Host Controller)
Friendly Name     :
Power             : 98 mA
USB Version       : 2.00
Driver Description: USB Composite Device
Driver Version    : 10.0.18362.1
Driver InfSection : Composite.Dev.NT
Driver InfPath    : usb.inf
Instance ID       : USB\VID_046D&PID_C52B\5&1488a0d9&0&11
Capabilities      : Removable, SurpriseRemovalOK
==================================================

==================================================
Device Name       : PS2toUSB Adapter
Description       : USB Composite Device
Device Type       : Unknown
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     : 00000030
Created Date      : 6/11/2019 2:26:46 PM
Last Plug/Unplug Date: 6/2/2019 4:02:13 PM
VendorID          : 0e8f
ProductID         : 0020
Firmware Revision : 2.80
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 7&2ef75247&0
Service Name      : usbccgp
Service Description: @usb.inf,%GenericParent.SvcDesc%;Microsoft USB Generic Parent Driver
Driver Filename   : usbccgp.sys
Device Class      :
Device Mfg        : (Standard USB Host Controller)
Friendly Name     :
Power             : 400 mA
USB Version       : 1.10
Driver Description: USB Composite Device
Driver Version    : 10.0.18362.1
Driver InfSection : Composite.Dev.NT
Driver InfPath    : usb.inf
Instance ID       : USB\VID_0E8F&PID_0020\00000030
Capabilities      : Removable, UniqueID, SurpriseRemovalOK
==================================================

==================================================
Device Name       : Port_#0003.Hub_#0002
Description       : USB Composite Device
Device Type       : Unknown
Connected         : No
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     :
Created Date      : 6/2/2019 4:01:29 PM
Last Plug/Unplug Date: 6/2/2019 4:00:11 PM
VendorID          : 0e8f
ProductID         : 0020
Firmware Revision : 2.80
USB Class         : 00
USB SubClass      : 00
USB Protocol      : 00
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   : 7&1ba01871&0
Service Name      : usbccgp
Service Description: @usb.inf,%GenericParent.SvcDesc%;Microsoft USB Generic Parent Driver
Driver Filename   : usbccgp.sys
Device Class      :
Device Mfg        : (Standard USB Host Controller)
Friendly Name     :
Power             : 400 mA
USB Version       : 1.10
Driver Description: USB Composite Device
Driver Version    : 10.0.18362.1
Driver InfSection : Composite.Dev.NT
Driver InfPath    : usb.inf
Instance ID       : USB\VID_0E8F&PID_0020\6&18416120&0&3
Capabilities      : Removable, SurpriseRemovalOK
==================================================

==================================================
Device Name       : External USB 3.0
Description       : TOSHIBA External USB 3.0 USB Device
Device Type       : Mass Storage
Connected         : Yes
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      : S:
Serial Number     : DK3P8205006F
Created Date      : 6/11/2019 2:26:40 PM
Last Plug/Unplug Date: 6/2/2019 4:00:11 PM
VendorID          : 0480
ProductID         : d002
Firmware Revision : 0.00
USB Class         : 08
USB SubClass      : 06
USB Protocol      : 50
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   :
Service Name      : USBSTOR
Service Description: @usbstor.inf,%USBSTOR.SvcDesc%;USB Mass Storage Driver
Driver Filename   : USBSTOR.SYS
Device Class      :
Device Mfg        : Compatible USB storage device
Friendly Name     :
Power             : 0 mA
USB Version       : 3.00
Driver Description: USB Mass Storage Device
Driver Version    : 10.0.18362.1
Driver InfSection : USBSTOR_BULK.NT
Driver InfPath    : usbstor.inf
Instance ID       : USB\VID_0480&PID_D002\DK3P8205006F
Capabilities      : Removable, UniqueID, SurpriseRemovalOK
==================================================

==================================================
Device Name       : Port_#0013.Hub_#0001
Description       : SanDisk Cruzer Dial USB Device
Device Type       : Mass Storage
Connected         : No
Safe To Unplug    : Yes
Disabled          : No
USB Hub           : No
Drive Letter      :
Serial Number     : 4C530001280610108534
Created Date      : 6/5/2019 8:38:28 PM
Last Plug/Unplug Date: 6/3/2019 2:51:20 PM
VendorID          : 0781
ProductID         : 5599
Firmware Revision : 1.00
USB Class         : 08
USB SubClass      : 06
USB Protocol      : 50
Hub / Port        :
Computer Name     : DELL
Vendor Name       :
Product Name      :
ParentId Prefix   :
Service Name      : USBSTOR
Service Description: @usbstor.inf,%USBSTOR.SvcDesc%;USB Mass Storage Driver
Driver Filename   : USBSTOR.SYS
Device Class      :
Device Mfg        : Compatible USB storage device
Friendly Name     :
Power             :
USB Version       :
Driver Description: USB Mass Storage Device
Driver Version    : 10.0.18362.1
Driver InfSection : USBSTOR_BULK.NT
Driver InfPath    : usbstor.inf
Instance ID       : USB\VID_0781&PID_5599\4C530001280610108534
Capabilities      : Removable, UniqueID, SurpriseRemovalOK
==================================================

 


  • 0

#27
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

Something wrong here:
 

Event: 153 Source: disk
The IO operation at logical block address 0x800 for Disk 3 (PDO name: \Device\0000004c) was retried.

 

 

 

 

Copy the next line:

wmic path Win32_PnPSignedDriver where "pdo like '%0000004c'" get friendlyname

Open an elevated Command Prompt:

http://www.howtogeek...-in-windows-10/

Right click and Paste (or Edit then Paste) and the copied lines should appear.
Hit Enter.  It will take a minute or so then come back with something like:

 

FriendlyName
WDC WD10EZEX-08M2NA0

 

This is the Part number and serial number of the drive having a problem.  Speccy will tell us which drive that is:

Get the free version of Speccy:

http://www.filehippo...ownload_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,  10-20  lines down.) Save the file.  Attach the file to your next post.  Attaching the log is the best option as it is too big for the forum.  Attaching is a multi step process.

First click on More Reply Options
Then scroll down to where you see
Choose File and click on it.  Point it at the file and hit Open.
Now click on Attach this file.
 

Check the SMART section of the Speccy log.  See if it sees all of your drives.  Is one missing?

 

  Is this one of your USB connected drives? 


  • 0

#28
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

As I wrote in the previous report, " N:\ drive did not connect; most times it shows in the win explorer upon reboot"

 

I wanted to run VEW.exe first without, and the with the N: drive connected, so I repeated the test just now.

 

In both cases, with and without the drive connected, the same note appeared.

 

Next, the 'friendly name' command was executed.  The result was "No instance(s) available".

 

As I do not know the meaning or significance of this reply and the next steps that follow, I obtained the serial number of the N:\ drive (assuming that's that one referred to in the VEW report)  via Hard Disk Sentinel: W1E7YMS1.

 

Next, I ran Speccy.

 

It saw ALL drives.

 

All reports are attached rather than pasted here.

 

Thank you!

 

Boris

Attached Files


  • 0

#29
RKinner

RKinner

    Malware Expert

  • Expert
  • 21,708 posts
  • MVP

Do you have any programs from Acronis on this PC?  I don't see any in Speccy but I might not recognize them.

 

There are reports of it causing a problem on Win 10.

 

If you look at Speccy report for N:

 

It shows

 

Attribute name    Command Timeout
                                            Real value    12,885,229,576

 

The other drives all have 0 (one has 1).

 

Some people say this is unimportant on Seagates but Backblaze reports it as one of the key indicators of failure.

 

https://www.backblaz...drive-failures/

 

Also it is only running at SATA II speed vs SATA III even tho it says it should be able to do III. 

 

How long is the USB cable going to N: ?  I have seen reports that anything over 1 meter on a Seagate will result in problems.

 

Win 7 uses USBSTOR Win 10 uses UASPSTOR  to talk to the USB hard drives instead so there is a big difference between 7 and 10.  Apparently UASPSTOR is more sensitive to these errors.

 

 

 

Just a warning but the S: drive says it is running too hot at 52 C vs about 42 C for the others.  Can you improve airflow around the drive?


  • 0

#30
BerDov

BerDov

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 103 posts

Thank you, Ron!

RK: Do you have any programs from Acronis on this PC?  I don't see any in Speccy but I might not recognize them.

There are reports of it causing a problem on Win 10.

 

BF: Never heard of the company; do not see the name in the Control Panel list; did not see any familiar name in their list of products on Wiki.

 

If you look at Speccy report for N:

It shows

Attribute name    Command Timeout
                                            Real value    12,885,229,576

The other drives all have 0 (one has 1).

Some people say this is unimportant on Seagates but Backblaze reports it as one of the key indicators of failure.

https://www.backblaz...drive-failures/

Also it is only running at SATA II speed vs SATA III even tho it says it should be able to do III. 

 

BF: Ok, but I do not know how to deal with it. 

 

How long is the USB cable going to N: ?  I have seen reports that anything over 1 meter on a Seagate will result in problems.

 

 BF: It is 112cm between the connectors. Most likely, it's the cable that came with the drive. (BTW, the disk "successfully" disconnected itself since my last report at 10:30)

 

Win 7 uses USBSTOR Win 10 uses UASPSTOR  to talk to the USB hard drives instead so there is a big difference between 7 and 10.  Apparently UASPSTOR is more sensitive to these errors.

 

BF: i.e. nothing to be done about it, right?

 

 Just a warning but the S: drive says it is running too hot at 52 C vs about 42 C for the others.  Can you improve airflow around the drive?

BF: Yes, I know. The Sentinel program showed 53C just now. The disk is in the vertical orientation, at least 10cm from the nearest drive. Looking for an optimum operation temperature for a 6TB Toshiba drive, I just came across this discussion: https://forums.tomsh...issues.2561880/ Apparently, the issue is not unique to my drive. I agree with "the cooler the better" point, but nobody in that thread reported a fact of disk failure, just worries...

 

So... ?


Edited by BerDov, 15 June 2019 - 11:50 AM.

  • 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