Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Does this sound like a driver issue (if so, how to figure out which one?)
6 views
Skip to first unread message
arlen holder
Apr 15, 2019, 1:01:37β―PM4/15/19
to
Does this sound like a driver issue (if so, how to figure out which one?)
1. If I leave the spare desktop on Ubuntu, it stays alive no matter what.
2. If I leave it on Windows 10, it freezes solid, even when not used.
Normally I'm in Windows, but for the past month or so, the desktop, which
is mostly unused but which stays on to serve shares, freezes solid.
Nothing can be done when it freezes solid, except a reboot.
Even then, a reboot often comes up with a frozen screen in minutes.
Hmmmmm...
So I rebooted to Ubuntu 18.04 and let it sit for days.
It never froze.
Does this sound like a driver issue - or something else?
If so, how can I figure out _which_ driver is causing the problem?
1. If I leave the spare desktop on Ubuntu, it stays alive no matter what.
2. If I leave it on Windows 10, it freezes solid, even when not used.
Normally I'm in Windows, but for the past month or so, the desktop, which
is mostly unused but which stays on to serve shares, freezes solid.
Nothing can be done when it freezes solid, except a reboot.
Even then, a reboot often comes up with a frozen screen in minutes.
Hmmmmm...
So I rebooted to Ubuntu 18.04 and let it sit for days.
It never froze.
Does this sound like a driver issue - or something else?
If so, how can I figure out _which_ driver is causing the problem?
J.O. Aho
Apr 15, 2019, 4:08:50β―PM4/15/19
to
On 15/04/2019 19.01, arlen holder wrote:
> Does this sound like a driver issue (if so, how to figure out which one?)
>
> 1. If I leave the spare desktop on Ubuntu, it stays alive no matter what.
> 2. If I leave it on Windows 10, it freezes solid, even when not used.
>
> Normally I'm in Windows, but for the past month or so, the desktop, which
> is mostly unused but which stays on to serve shares, freezes solid.
Did you use a search engine and see if others had similar issue with the
> Does this sound like a driver issue (if so, how to figure out which one?)
>
> 1. If I leave the spare desktop on Ubuntu, it stays alive no matter what.
> 2. If I leave it on Windows 10, it freezes solid, even when not used.
>
> Normally I'm in Windows, but for the past month or so, the desktop, which
> is mostly unused but which stays on to serve shares, freezes solid.
same version of the graphics driver, ms-windows version, similar hardware?
> Nothing can be done when it freezes solid, except a reboot.
> Even then, a reboot often comes up with a frozen screen in minutes.
>
> Hmmmmm...
> So I rebooted to Ubuntu 18.04 and let it sit for days.
> It never froze.
>
> Does this sound like a driver issue - or something else?
could even be a hardware issue, for example the OS with larger memory
foot print can cause the issue to happen while the OS with a smaller
foot print don't use the faulty memory...
> If so, how can I figure out _which_ driver is causing the problem?
--
//Aho
π Good Guy π
Apr 15, 2019, 4:20:55β―PM4/15/19
to
On 15/04/2019 21:08, J.O. Aho wrote:
Did you use a search engine and see if others had similar issue with the same version of the graphics driver, ms-windows version, similar hardware?
No he has got people like you bending backwards to waste time onΒ
pedo activities.
Can be anything from a driver issue to operating system issue or it could even be a hardware issue, for example the OS with larger memory foot print can cause the issue to happen while the OS with a smaller foot print don't use the faulty memory...
Or could be some files deleted deliberately.Β The OP is a known pedo
here and he has deleted many critical files on his Windows 10
machine because Microsoft millionaires staff have plenty of time to
waste spying on him.Β These are his own words I have paraphrased!!.
If so, how can I figure out _which_ driver is causing the problem?
Did you look at the logs and see what they said?
This is too much work for him even if he knows how to do it.Β He is
too busy abusing young boys.
--
With over 950 million devices now
running Windows 10, customer satisfaction is higher than any
previous version of windows.
arlen holder
Apr 20, 2019, 3:33:58β―PM4/20/19
to
On Sat, 20 Apr 2019 10:41:55 -0400, Paul wrote:
> On Linux, you can declare your serial port as "The Console",
> and if the screen ever dies, you can restart Xorg over the
> serial port.
Hi Paul,
Thanks for being purposefully helpful & in not leaving me high & dry
on my dual-boot Linux/Windows desktop which only freezes on Windows.
I do very much admire that you seem to keep your cool when helping people
much more than I can do (you have better "people skills" than I have!).
In return, to always strive to be a good Usenet citizen, I'll try to add
additional value to this Potluck Picnic question, so that this thread can
become an archival reference for future users as well as ideas for those
readers who read it today.
The use of Linux is, already, a great diagnostic, as the fact that Ubuntu
18.04 doesn't seem to freeze indicates it's not necessarily hardware,
but some kind of "interaction" in the software environment (perhaps to
hardware drivers).
> If a computer has a serial port, you can run Windbg
> remotely from a second computer. You can debug another
> computer over a serial port.
I just checked and the bad desktop does not have a serial port in back,
so those suggestions for linux/windows serial port connections while it's
frozen, won't work unfortunately.
> The ping test is important, in the sense that it does
> leave the door open to debugging.
Yesterday, after I switched back from Linux to Windows, and while it was
still running, I set a static IP address so that I could run the ping test
you suggested. This morning, after I got your post above, I "woke up" the
computer from sleep, and it was running for about 10 minutes or so before I
noticed it had frozen up solid.
It's currently frozen now where, it froze on a PC Banter browser page
where nothing but the frozen display appears to be working:
o CTRL+ALT+DEL fails to do anything
Pinging from another Windows 10 computer... returned, unfortunately:
o Destination host unreachable
I happen to have a NETBIOS share shortcut on the good computer, pointing to
the frozen computer, but NETBIOS, unfortunately, also did not connect.
"Windows Network Diagnostics: Your computer appears to be correctly
configured, but the device Detected or resource (IP address)
is not responding."
> You could also try setting it up for remoting into it
> with some tool. mstsc.exe ? TeamViewer ? If you know
> the freeze leaves the network running, there might be
> other ways.
Thanks for that Remote Desktop suggestion, which I'll soon try:
o Start > Run > mstsc.exe
<https://support.microsoft.com/en-us/help/17463/windows-7-connect-to-another-computer-remote-desktop-connection>
> Whereas, as far as I know, using Windbg just requires
> the kernel to still be responding.
I had to look about for "windbg.exe", where I think I found it here:
<https://technet.microsoft.com/en-us/ff551063(v=vs.105)>
<https://www.tenforums.com/tutorials/2082-install-configure-windbg-bsod-analysis.html>
Where that Windows Debugger requires .NET Framework 4.6:
<https://docs.microsoft.com/en-us/dotnet/framework/index>
<https://docs.microsoft.com/en-us/dotnet/framework/install/index>
Maybe I should download the latest, which is .NET Framework 4.8?
<https://docs.microsoft.com/en-us/dotnet/framework/install/on-windows-10>
There's also something called the "Windows Debugger Preview" apparently:
<https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools>
Which apparently is a standalone debugging tools in the Windows SDK:
<https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk>
Where, that's all so freaking confusing, I'll have to write a _separate_
tutorial to help (me and) others figure out what's the bare minimum needed
out of that confusing amalgam of developer-focused tool suites.
I hate to mention "voodoo science", but it seems that it hangs when I leave
a browser session open. At first, I thought it was Firefox, so I wiped it
out, but it just froze this morning on SRWare Iron, so it may just be a
coincidence. When I reboot, I will test for a day or two with no browser
session open and then with a browser open (this current frozen SRWare Iron
episode is open to PC Banter via http://tinyurl.com/alt-comp-os-windows-10
but it's usually hung at the Google http://news.google.com which is what I
use mostly on that frozen PC since it's a spare in a side room).
I'm scratching my head for what I can do, proactively, for additional
debugging information, where what I may do is run some debugging tools
graphically which can report information as the screen freezes.
This site says drivers cause most of the freezes:
<https://superuser.com/questions/26862/how-do-i-troubleshoot-a-windows-freeze-or-slowness>
It suggests the "Windows Assessment and Deployment Kit (Windows ADK):
o Windows Performance Analyzer
<https://docs.microsoft.com/en-us/windows-hardware/test/wpt/windows-performance-analyzer>
Which can log things from an admin prompt _before_ the system freezes:
o xperf -start perf!GeneralProfiles.InBuffer && timeout -1 && xperf -stop perf!GeneralProfiles.InBuffer myTrace.etl
From there, I know you are familiar with xbootmgr.exe analysis:
o xbootmgr -trace shutdown -traceFlags BASE+DIAG+LATENCY -noPrepReboot
o Drag the trace at %ProgramFiles%\Microsoft Windows Performance Toolkit
o Onto xperf.exe and it will be opened in a GUI with performance graphs
Apparently we can look into the stack traces by adding a switch:
o xbootmgr -trace shutdown -traceFlags BASE+DIAG+LATENCY -noPrepReboot -stackWalk profile
<https://superuser.com/questions/345006/how-can-i-identify-the-culprit-of-my-slow-windows-shutdown/347191#347191>
While searching, I found a "Windows Driver Kit" of debugging tools:
<https://docs.microsoft.com/en-us/windows-hardware/drivers/>
<https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk>
Which is part of the Windows Debugging Tools:
o WinDbg, KD, CDB, NTSD
<https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/index>
The HDD is not constrained AFAIK, but I should run these anyway:
o sfc /scannow
o chkdsk /r
o %windir%\system32\perfmon.msc /s
o %windir%\system32\perfmon.exe /res
o %windir%\system32\dfrgui.exe <=== (probably not diagnostic)
o %windir%\system32\cleanmgr.exe <== cleanup (probably not diagnostic)
Where the "Disk Cleanup" needs to be tweaked to be fully effective:
<https://www.howtogeek.com/howto/36924/why-doesnt-disk-cleanup-delete-everything-from-the-temp-folder/>
And, I should free up drive space anyway (although there is plenty):
<https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space>
I have no reason to suspect memory, but I can run a memory test anyway:
o Windows Memory Diagnostic Tool
o Start > Run > %windir%\system32\MdSched.exe
Apparently it will reboot after the test so we have to view results here:
o Start > Run > eventvwr.exe > Windows Logs > System
o Find > MemoryDiagnostics-Results > Find Next
<https://www.windowscentral.com/how-check-your-pc-memory-problems-windows-10>
Windows is updated, but I can doublecheck it for the record:
o Start > Settings > Update & Security > Windows Update > Check for updates
I can clean up the file system & registry & autoruns a bit:
o Ccleaner
<https://www.ccleaner.com/>
<https://download.ccleaner.com/ccsetup556.exe>
I can check leftover auto-runs for anything suspicious:
o Autoruns for Windows v13.94
<https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns>
<https://download.sysinternals.com/files/Autoruns.zip>
I can check the autoruns in the registry:
o HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
I can _look_ at the running services to disable some:
o Start > Run > services.msc
But it's voodoo science sometimes what to disable & what to keep:
<https://www.tweakhound.com/2015/12/05/windows-10-services/>
<https://www.tweakhound.com/2015/12/09/tweaking-windows-10/10/>
<https://www.askvg.com/beginners-guide-to-configure-windows-10-services/>
<http://www.blackviper.com/service-configurations/black-vipers-windows-10-service-configurations/>
I can check the processes before the machine freezes:
o Start > Run > taskmgr.exe
o Process Explorer
<https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer>
<https://download.sysinternals.com/files/ProcessExplorer.zip>
o Process Monitor
<https://docs.microsoft.com/en-us/sysinternals/downloads/procmon>
<https://download.sysinternals.com/files/ProcessMonitor.zip>
While I have no reason to suspect thermal shutdown, I'll run a GPU and CPU
temperature utility. Googling, I will try whichever one of these has a
constant graphical display that I would still be able to see on a frozen
screen.
o Open Hardware Monitor
<https://openhardwaremonitor.org/>
<https://github.com/openhardwaremonitor/openhardwaremonitor>
<https://openhardwaremonitor.org/files/openhardwaremonitor-v0.8.0-beta.zip>
o Real Temp
<https://www.techpowerup.com/realtemp/>
<https://www.techpowerup.com/download/techpowerup-real-temp/>
<http://us2-dl.techpowerup.com/files/ECF5vQK4k1JzVVvWIVWJjw/1555780281/RealTemp_370.zip>
o Speed Fan
<http://www.almico.com/speedfan.php>
<http://www.almico.com/sfdownload.php>
<http://www.almico.com/instspeedfan452.exe>
o CoreTemp
<https://www.alcpu.com/CoreTemp/>
<https://www.alcpu.com/CoreTemp/Core-Temp-setup.exe>
o HWMonitor
<https://www.cpuid.com/softwares/hwmonitor.html>
<http://download.cpuid.com/hwmonitor/hwmonitor_1.40.zip>
<http://download.cpuid.com/hwmonitor/hwmonitor_1.40.exe>
I tried to find the canonical site for HijackThis, at TrendMicro
<https://www.trendmicro.com/en_us/forHome/products/free-tools.html>
But apparently it's sourced from Sourceforge.net now:
o HiJackThis
<https://sourceforge.net/projects/hjt/>
<https://cfhcable.dl.sourceforge.net/project/hjt/2.0.5%20beta/HijackThis.exe>
I should check if the latest Adobe Flash Player is installed:
<https://helpx.adobe.com/flash-player.html>
<https://get.adobe.com/flashplayer/>
<https://admdownload.adobe.com/bin/live/flashplayer32pp_xa_install.exe>
I can check if the latest Java Runtime JDK is installed:
<https://www.oracle.com/technetwork/java/javase/downloads/index.html>
<https://www.oracle.com/technetwork/java/javase/downloads/jdk12-downloads-5295953.html>
<https://download.oracle.com/otn-pub/java/jdk/12.0.1+12/69cfe15208a647278a19ef0990eea691/jdk-12.0.1_windows-x64_bin.exe>
<https://download.oracle.com/otn-pub/java/jdk/12.0.1+12/69cfe15208a647278a19ef0990eea691/jdk-12.0.1_windows-x64_bin.zip>
Before I start deleting stuff, I can make an 8GB recovery drive:
o Insert an 8GB+ USB flash drive that will be completely overwritten
o %windir%\system32\RecoveryDrive.exe
One option for testing is to load selective drivers on reboot:
o Start > Run > msconfig
- Normal startup (load all device drivers and services)
- Diagnostic startup (load basic devices and services only)
- Selective startup (three options)
Another option I can try is to wipe out all the hardware drivers and start
fresh with new drivers from the various hardware manufacturers.
I suspect I'll need to back them up first, perhaps.
<https://www.techspot.com/community/topics/how-to-backup-your-drivers-and-reinstall-them-later-when-needed.151773/>
o Double Driver
<https://www.majorgeeks.com/files/details/double_driver.html>
<https://www.majorgeeks.com/mg/getmirror/double_driver,1.html>
<http://files1.majorgeeks.com/3c3a97157cd3255883ce12218e316ddb91543097/drivers/double_driver_4.1.0_portable.zip>
o Driver Backup!
<https://sourceforge.net/projects/drvback/>
<https://sourceforge.net/projects/drvback/files/latest/download>
<https://iweb.dl.sourceforge.net/project/drvback/DriverBackup%21%202/DrvBK%202.1/DrvBK_21_Rev7.zip>
After backing them up, I may wipe out all the drivers:
o Start > Run > devmgmt.msc
<https://docs.microsoft.com/en-us/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages>
<https://www.drivethelife.com/windows-10/completely-remove-uninstall-drivers-windows-10.html>
If necessary, I can unplug everything inside and outside the PC other than:
o Power
o Monitor
o Keyboard
o Mouse
Some even suggest resetting the CMOS & removing the battery:
<https://superuser.com/questions/224515/how-do-i-troubleshoot-hardware-issues-related-to-a-computer-freeze-crash>
Any other suggestions before I start doing these things?
--
Archive bits set for re-use, but followup set to the unarchived win10 ng.
> On Linux, you can declare your serial port as "The Console",
> and if the screen ever dies, you can restart Xorg over the
> serial port.
Hi Paul,
Thanks for being purposefully helpful & in not leaving me high & dry
on my dual-boot Linux/Windows desktop which only freezes on Windows.
I do very much admire that you seem to keep your cool when helping people
much more than I can do (you have better "people skills" than I have!).
In return, to always strive to be a good Usenet citizen, I'll try to add
additional value to this Potluck Picnic question, so that this thread can
become an archival reference for future users as well as ideas for those
readers who read it today.
The use of Linux is, already, a great diagnostic, as the fact that Ubuntu
18.04 doesn't seem to freeze indicates it's not necessarily hardware,
but some kind of "interaction" in the software environment (perhaps to
hardware drivers).
> If a computer has a serial port, you can run Windbg
> remotely from a second computer. You can debug another
> computer over a serial port.
I just checked and the bad desktop does not have a serial port in back,
so those suggestions for linux/windows serial port connections while it's
frozen, won't work unfortunately.
> The ping test is important, in the sense that it does
> leave the door open to debugging.
Yesterday, after I switched back from Linux to Windows, and while it was
still running, I set a static IP address so that I could run the ping test
you suggested. This morning, after I got your post above, I "woke up" the
computer from sleep, and it was running for about 10 minutes or so before I
noticed it had frozen up solid.
It's currently frozen now where, it froze on a PC Banter browser page
where nothing but the frozen display appears to be working:
o CTRL+ALT+DEL fails to do anything
Pinging from another Windows 10 computer... returned, unfortunately:
o Destination host unreachable
I happen to have a NETBIOS share shortcut on the good computer, pointing to
the frozen computer, but NETBIOS, unfortunately, also did not connect.
"Windows Network Diagnostics: Your computer appears to be correctly
configured, but the device Detected or resource (IP address)
is not responding."
> You could also try setting it up for remoting into it
> with some tool. mstsc.exe ? TeamViewer ? If you know
> the freeze leaves the network running, there might be
> other ways.
Thanks for that Remote Desktop suggestion, which I'll soon try:
o Start > Run > mstsc.exe
<https://support.microsoft.com/en-us/help/17463/windows-7-connect-to-another-computer-remote-desktop-connection>
> Whereas, as far as I know, using Windbg just requires
> the kernel to still be responding.
I had to look about for "windbg.exe", where I think I found it here:
<https://technet.microsoft.com/en-us/ff551063(v=vs.105)>
<https://www.tenforums.com/tutorials/2082-install-configure-windbg-bsod-analysis.html>
Where that Windows Debugger requires .NET Framework 4.6:
<https://docs.microsoft.com/en-us/dotnet/framework/index>
<https://docs.microsoft.com/en-us/dotnet/framework/install/index>
Maybe I should download the latest, which is .NET Framework 4.8?
<https://docs.microsoft.com/en-us/dotnet/framework/install/on-windows-10>
There's also something called the "Windows Debugger Preview" apparently:
<https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools>
Which apparently is a standalone debugging tools in the Windows SDK:
<https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk>
Where, that's all so freaking confusing, I'll have to write a _separate_
tutorial to help (me and) others figure out what's the bare minimum needed
out of that confusing amalgam of developer-focused tool suites.
I hate to mention "voodoo science", but it seems that it hangs when I leave
a browser session open. At first, I thought it was Firefox, so I wiped it
out, but it just froze this morning on SRWare Iron, so it may just be a
coincidence. When I reboot, I will test for a day or two with no browser
session open and then with a browser open (this current frozen SRWare Iron
episode is open to PC Banter via http://tinyurl.com/alt-comp-os-windows-10
but it's usually hung at the Google http://news.google.com which is what I
use mostly on that frozen PC since it's a spare in a side room).
I'm scratching my head for what I can do, proactively, for additional
debugging information, where what I may do is run some debugging tools
graphically which can report information as the screen freezes.
This site says drivers cause most of the freezes:
<https://superuser.com/questions/26862/how-do-i-troubleshoot-a-windows-freeze-or-slowness>
It suggests the "Windows Assessment and Deployment Kit (Windows ADK):
o Windows Performance Analyzer
<https://docs.microsoft.com/en-us/windows-hardware/test/wpt/windows-performance-analyzer>
Which can log things from an admin prompt _before_ the system freezes:
o xperf -start perf!GeneralProfiles.InBuffer && timeout -1 && xperf -stop perf!GeneralProfiles.InBuffer myTrace.etl
From there, I know you are familiar with xbootmgr.exe analysis:
o xbootmgr -trace shutdown -traceFlags BASE+DIAG+LATENCY -noPrepReboot
o Drag the trace at %ProgramFiles%\Microsoft Windows Performance Toolkit
o Onto xperf.exe and it will be opened in a GUI with performance graphs
Apparently we can look into the stack traces by adding a switch:
o xbootmgr -trace shutdown -traceFlags BASE+DIAG+LATENCY -noPrepReboot -stackWalk profile
<https://superuser.com/questions/345006/how-can-i-identify-the-culprit-of-my-slow-windows-shutdown/347191#347191>
While searching, I found a "Windows Driver Kit" of debugging tools:
<https://docs.microsoft.com/en-us/windows-hardware/drivers/>
<https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk>
Which is part of the Windows Debugging Tools:
o WinDbg, KD, CDB, NTSD
<https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/index>
The HDD is not constrained AFAIK, but I should run these anyway:
o sfc /scannow
o chkdsk /r
o %windir%\system32\perfmon.msc /s
o %windir%\system32\perfmon.exe /res
o %windir%\system32\dfrgui.exe <=== (probably not diagnostic)
o %windir%\system32\cleanmgr.exe <== cleanup (probably not diagnostic)
Where the "Disk Cleanup" needs to be tweaked to be fully effective:
<https://www.howtogeek.com/howto/36924/why-doesnt-disk-cleanup-delete-everything-from-the-temp-folder/>
And, I should free up drive space anyway (although there is plenty):
<https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space>
I have no reason to suspect memory, but I can run a memory test anyway:
o Windows Memory Diagnostic Tool
o Start > Run > %windir%\system32\MdSched.exe
Apparently it will reboot after the test so we have to view results here:
o Start > Run > eventvwr.exe > Windows Logs > System
o Find > MemoryDiagnostics-Results > Find Next
<https://www.windowscentral.com/how-check-your-pc-memory-problems-windows-10>
Windows is updated, but I can doublecheck it for the record:
o Start > Settings > Update & Security > Windows Update > Check for updates
I can clean up the file system & registry & autoruns a bit:
o Ccleaner
<https://www.ccleaner.com/>
<https://download.ccleaner.com/ccsetup556.exe>
I can check leftover auto-runs for anything suspicious:
o Autoruns for Windows v13.94
<https://docs.microsoft.com/en-us/sysinternals/downloads/autoruns>
<https://download.sysinternals.com/files/Autoruns.zip>
I can check the autoruns in the registry:
o HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
I can _look_ at the running services to disable some:
o Start > Run > services.msc
But it's voodoo science sometimes what to disable & what to keep:
<https://www.tweakhound.com/2015/12/05/windows-10-services/>
<https://www.tweakhound.com/2015/12/09/tweaking-windows-10/10/>
<https://www.askvg.com/beginners-guide-to-configure-windows-10-services/>
<http://www.blackviper.com/service-configurations/black-vipers-windows-10-service-configurations/>
I can check the processes before the machine freezes:
o Start > Run > taskmgr.exe
o Process Explorer
<https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer>
<https://download.sysinternals.com/files/ProcessExplorer.zip>
o Process Monitor
<https://docs.microsoft.com/en-us/sysinternals/downloads/procmon>
<https://download.sysinternals.com/files/ProcessMonitor.zip>
While I have no reason to suspect thermal shutdown, I'll run a GPU and CPU
temperature utility. Googling, I will try whichever one of these has a
constant graphical display that I would still be able to see on a frozen
screen.
o Open Hardware Monitor
<https://openhardwaremonitor.org/>
<https://github.com/openhardwaremonitor/openhardwaremonitor>
<https://openhardwaremonitor.org/files/openhardwaremonitor-v0.8.0-beta.zip>
o Real Temp
<https://www.techpowerup.com/realtemp/>
<https://www.techpowerup.com/download/techpowerup-real-temp/>
<http://us2-dl.techpowerup.com/files/ECF5vQK4k1JzVVvWIVWJjw/1555780281/RealTemp_370.zip>
o Speed Fan
<http://www.almico.com/speedfan.php>
<http://www.almico.com/sfdownload.php>
<http://www.almico.com/instspeedfan452.exe>
o CoreTemp
<https://www.alcpu.com/CoreTemp/>
<https://www.alcpu.com/CoreTemp/Core-Temp-setup.exe>
o HWMonitor
<https://www.cpuid.com/softwares/hwmonitor.html>
<http://download.cpuid.com/hwmonitor/hwmonitor_1.40.zip>
<http://download.cpuid.com/hwmonitor/hwmonitor_1.40.exe>
I tried to find the canonical site for HijackThis, at TrendMicro
<https://www.trendmicro.com/en_us/forHome/products/free-tools.html>
But apparently it's sourced from Sourceforge.net now:
o HiJackThis
<https://sourceforge.net/projects/hjt/>
<https://cfhcable.dl.sourceforge.net/project/hjt/2.0.5%20beta/HijackThis.exe>
I should check if the latest Adobe Flash Player is installed:
<https://helpx.adobe.com/flash-player.html>
<https://get.adobe.com/flashplayer/>
<https://admdownload.adobe.com/bin/live/flashplayer32pp_xa_install.exe>
I can check if the latest Java Runtime JDK is installed:
<https://www.oracle.com/technetwork/java/javase/downloads/index.html>
<https://www.oracle.com/technetwork/java/javase/downloads/jdk12-downloads-5295953.html>
<https://download.oracle.com/otn-pub/java/jdk/12.0.1+12/69cfe15208a647278a19ef0990eea691/jdk-12.0.1_windows-x64_bin.exe>
<https://download.oracle.com/otn-pub/java/jdk/12.0.1+12/69cfe15208a647278a19ef0990eea691/jdk-12.0.1_windows-x64_bin.zip>
Before I start deleting stuff, I can make an 8GB recovery drive:
o Insert an 8GB+ USB flash drive that will be completely overwritten
o %windir%\system32\RecoveryDrive.exe
One option for testing is to load selective drivers on reboot:
o Start > Run > msconfig
- Normal startup (load all device drivers and services)
- Diagnostic startup (load basic devices and services only)
- Selective startup (three options)
Another option I can try is to wipe out all the hardware drivers and start
fresh with new drivers from the various hardware manufacturers.
I suspect I'll need to back them up first, perhaps.
<https://www.techspot.com/community/topics/how-to-backup-your-drivers-and-reinstall-them-later-when-needed.151773/>
o Double Driver
<https://www.majorgeeks.com/files/details/double_driver.html>
<https://www.majorgeeks.com/mg/getmirror/double_driver,1.html>
<http://files1.majorgeeks.com/3c3a97157cd3255883ce12218e316ddb91543097/drivers/double_driver_4.1.0_portable.zip>
o Driver Backup!
<https://sourceforge.net/projects/drvback/>
<https://sourceforge.net/projects/drvback/files/latest/download>
<https://iweb.dl.sourceforge.net/project/drvback/DriverBackup%21%202/DrvBK%202.1/DrvBK_21_Rev7.zip>
After backing them up, I may wipe out all the drivers:
o Start > Run > devmgmt.msc
<https://docs.microsoft.com/en-us/windows-hardware/drivers/install/using-device-manager-to-uninstall-devices-and-driver-packages>
<https://www.drivethelife.com/windows-10/completely-remove-uninstall-drivers-windows-10.html>
If necessary, I can unplug everything inside and outside the PC other than:
o Power
o Monitor
o Keyboard
o Mouse
Some even suggest resetting the CMOS & removing the battery:
<https://superuser.com/questions/224515/how-do-i-troubleshoot-hardware-issues-related-to-a-computer-freeze-crash>
Any other suggestions before I start doing these things?
--
Archive bits set for re-use, but followup set to the unarchived win10 ng.
0 new messages