Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Computer is slow


  • Please log in to reply

#61
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

Uninstall

Speccy

Latency Monitor

Why so slow (if it installed)

 

On your desktop create a new folder called Shortcuts.  (Right click on desktop, New, Folder) Drag all of your shortcuts over to the new folder and let go so that the desktop is cleared of as many icons as possible.  You can delete the folder called FRSTOlder and any log files that you have already posted.

 

Download BlueScreenView
http://www.nirsoft.n...creen_view.html

Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit, Select All.

Go File, Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

 

If the battery can be easily removed on your laptop, shut it down, remove the battery and boot it back up without the battery.  After things settle (about 5 minutes) create a Process Explorer log (remember to wait a full minute after starting the program) and post it.


  • 0

Advertisements


#62
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts
==================================================
Dump File         : 041020-32625-01.dmp
Crash Time        : 4/10/2020 2:31:11 PM
Bug Check String  : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code    : 0x1000007e
Parameter 1       : ffffffff`c0000005
Parameter 2       : fffff801`0cf4beee
Parameter 3       : ffffb688`b89af388
Parameter 4       : ffffb688`b89aebd0
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14beee
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+14beee
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\041020-32625-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 740,844
Dump File Time    : 4/10/2020 2:34:54 PM
==================================================
==================================================
Dump File         : 041020-32812-01.dmp
Crash Time        : 4/10/2020 8:49:47 AM
Bug Check String  : SYSTEM_SERVICE_EXCEPTION
Bug Check Code    : 0x0000003b
Parameter 1       : 00000000`c0000005
Parameter 2       : fffff805`0a54beee
Parameter 3       : ffffd78e`bc37f9a0
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+1c2380
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\041020-32812-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 831,332
Dump File Time    : 4/10/2020 8:54:27 AM
==================================================
==================================================
Dump File         : 040720-32859-01.dmp
Crash Time        : 4/7/2020 9:21:23 PM
Bug Check String  :
Bug Check Code    : 0x0000011d
Parameter 1       : 00000000`00000007
Parameter 2       : ffffdb0b`b3f8c000
Parameter 3       : 00000000`00010000
Parameter 4       : 00000000`00000000
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+1c2380
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+1c2380
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\040720-32859-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 742,012
Dump File Time    : 4/7/2020 10:47:41 PM
==================================================
==================================================
Dump File         : 032920-27187-01.dmp
Crash Time        : 3/29/2020 10:38:54 AM
Bug Check String  :
Bug Check Code    : 0x00000154
Parameter 1       : ffffd009`fef0e000
Parameter 2       : ffffca05`94b245f0
Parameter 3       : 00000000`00000001
Parameter 4       : 00000000`00000000
Caused By Driver  : hal.dll
Caused By Address : hal.dll+2476
File Description  :
Product Name      :
Company           :
File Version      :
Processor         : x64
Crash Address     : ntoskrnl.exe+1c2380
Stack Address 1   :
Stack Address 2   :
Stack Address 3   :
Computer Name     :
Full Path         : C:\WINDOWS\Minidump\032920-27187-01.dmp
Processors Count  : 2
Major Version     : 15
Minor Version     : 18362
Dump File Size    : 829,132
Dump File Time    : 3/29/2020 10:43:23 AM
==================================================

Attached Files


  • 0

#63
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

Apparently the battery is not causing a problem so you can shut down and reinstall it.

 

Assume you created the Shortcut folder and cleaned up the desktop a bit since we managed to get back 2 or 3 % in CPU from DWM.  Let's see if there is something wrong with the background picture.  Right click on the desktop and Personalize.  Under background change Picture to Solid Color then choose the Cool Blue.  Closing the window then run Process Explorer as before.

 

Blue screen view is only showing windows files but I suspect based on the value of Interrupts that a bad driver is causing the problem.  Most likely is the network adapter so search for

device manager

hit Enter.  Find the network adapter you are using and right click on it and disable.  Then create a process explorer log as before then enable and post it.


  • 0

#64
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts

I did make the shortcut folder and cleaned up the desktop. 

 

Here is the Process explorer after Making the desktop solid cool blue. 

 

 

Attached Files


  • 0

#65
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts

After disabling the network adaptor. There was a WiFi adapter that I did not disable.


  • 0

#66
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts

See the Registry attached. 

Attached Files


  • 0

#67
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

You can go back and put the original picture back if you like.  Difference was less than 1/2 %

 

I think the WiFI adapter is the one you are using so it should be the one disabled.  Please try again.


  • 0

#68
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts

Okay.  WiFi disabled.  I also attached a screenshot of "others" that were under the Network Adapter.  

Attached Thumbnails

  • Annotation 2020-04-10 214840.jpg

Attached Files


  • 0

#69
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

That one didn't help the Interrrupts so it's not the culprit.

 

Search for

msconfig

hit Enter

Click on Diagnostic Startup then OK.  Reboot.

 

Rerun Process Explorer.  What does Interrupts say now?

 

If Interrupts drop to something less than 1.5 % then go back into msconfig and

check Normal Startup then Apply.  Go to the Services tab and check Hide Microsoft services.  Uncheck all that remain.  OK Reboot and check Interrupts in Process Explorer.  If still low then one of the services is at fault.  Go back in and recheck about half of them OK and reboot.  Try to isolate it down to a bad service.

 

If it looked good in Diagnostic start but Services didn't help then it might be a Startup entry.  Unfortunately Win 10 doesn't make it easy to uncheck them.  You have to go into Task Manager and under the Startup tab there are all the startup items.  You have to select and DISABLE each item individually then reboot and check Interrupts.

 

If Diagnostic Startup didn't help then put it back to Normal OK and reboot.


  • 0

#70
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts
Ok. To avoid confusion - I did the Diagnostic start and Interrupts were 1.37. Started up normal, hid Microsoft, unchecked the rest. Now Interrupts are 3.72.

For the final step - I am not sure what you mean by if Diagnostic looked good. Is the 1.37 good?
  • 0

Advertisements


#71
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

1.37 is good.

 

After you hid microsoft and unchecked the remaining and OK or Apply did you reboot?  It only takes effect after a reboot.  If you did then the next step is to right click on the clock and select Task Manager then Startup.  Then you have to DISABLE each item.  Reboot and check again.


  • 0

#72
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts

Step 1: Click on Diagnostic Startup then OK.  Reboot. Rerun Process Explorer.  What does Interrupts say now?

 

Interrupts were 1.37

 

Step 2.:

A. If Interrupts drop to something less than 1.5 % then go back into msconfig and

check Normal Startup then Apply.  Go to the Services tab and check Hide Microsoft services.  Uncheck all that remain.  OK Reboot and check Interrupts in Process Explorer. 

 

Interrupts were 3.72

 

 B. If still low then one of the services is at fault.  Go back in and recheck about half of them OK and reboot.  Try to isolate it down to a bad service. DID NOT DO THIS STEP BECAUSE INTERRUPTS WERE NOT LOW

 

 

Step 3.  Per your last post, I did reboot.  So I went on to with your next instruction;

the next step is to right click on the clock and select Task Manager then Startup.  Then you have to DISABLE each item.  Reboot and check again.

 

Interrupts were 2.66

 

I'm putting things back to normal at least until your next post.  I'm not sure what I'm looking for to find which one is the problem. 


  • 0

#73
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

Right click on the clock and select Task Manager (or you can search for task manager and hit Enter).  More Details,

 

click on Performance.  At the bottom of the page, click on  Open Resource Monitor

 

Click on the Disk tab.  This should show what processes are using the hard drive.  If not sorted with the processes with the most total disk activity at the top click on the column header for Total (B/s) once or twice until the largest numbers are at the top.  Make a screen shot of the page and post it.

 


  • 0

#74
butterrice

butterrice

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 403 posts

See Attached

Attached Thumbnails

  • Annotation 1 2020-04-13 190847.jpg

  • 0

#75
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,624 posts
  • MVP

click on the column header for Total (B/s) once or twice until the largest numbers are at the top.  Make a screen shot of the page and post it.


  • 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