Windows 10: Total system freeze/lock-up consistantly after 5 min idle

1) Were you able to download and install the latest HP BIOS UEFI diagnostics version 6.4?
2) Download and install the HP softpaq download manager: HP Software and Driver Downloads for HP Printers, Laptops, Desktops and More | HP® Customer Support

3) Run the DM log collector and post a zip into the thread so that we can troubleshoot the logs.
4) Overnight run the HP BIOS UEFI diagnostics in loop until failure as per post #58.

 

As I tried to explain above, I will NOT run this device unattended overnight. My machine, my choice. Sorry.

So after reverting to what was working at the start of last week (my undergrad Uni's motto was "Use What Works" > Logical Positivism) before I started messing with things incl. the Registry (don't ask; all reverted anyway with System Restore, dism and scannow), all is again OK so far >

 

Now, when you mentioned System restore.. Problems could be affected with S4 sleep mode (hibernation). You already disable that (with command "powercfg -h off"). Try that again (if system freeze after long sleep and is OK after short sleep)

 

Thanks. Have added that advice to my (long) FREEZE file (if that will be the case, will then try)

double checked setup now >







still good (so far)

 

The reliability control panel is an easy tool to use but it does not give you the detailed information that is available in the event.vwr.
The event logs, mini dumps, msinfo32, dxdiag are some of the files that can be troubleshooted.
Run the DM log collector to automatically collect the files for troubleshooting.
Please post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

 

In my understanding Reliability History uses the same data as those sources

And so far, still good (no problem waking from 11min sleep, likely the most I'd need w/o turning the machine off)





some of the problems previous to following Ken's advice:

 

The logs can be scanned and read for problems.
If you can run the DM log collector we can scan the logs and troubleshoot them.
BSOD - Posting Instructions - Windows 10 Forums

 

What is the time window before/after a problem event in which to download and use this tool? It may be days before it happens before I might need it or hours after it happens till I employ it

.... and it will likely not happen at all if I am careful and don't push it (as I REPEATEDLY did, "testing it" when the last issues occurred) >
"Doctor, it hurts when I of this"
"Well then don't do that"

 

The DM log collector at times gets revised.
To see what it collects you can open any thread in the BSOD forum as all OP use the DM log collector at the start of the thread.
When you run ithe DM log collector on the problematic computer it will place a file on the desktop.
Then you will post a zip into the thread.
We will unzip the post and scan the files to troubleshoot the freezing.
Our ability to scan is using English words so please change the default language to English so that we can troubleshoot the log files.
To evaluate new problems or the response to troubleshooting steps we often view multiple DM logs in the threads. So the sooner that we view the logs the sooner the troubleshooting starts.
There are some tests that we may do that are live and interactive and this depends on what is seen in the logs. These types of tests would require you to monitor the computer. Others can be done overnight as there is no user interaction. The logs though are useful to see what problems have already occurred.

 

TFdebugFiles.zipDESKTOP-FIQ3TKD-27_10_2017_142641_60.zip

this is after the fact, so I may need to do this again after forcing a freeze?

 

Hi Airider,

No need to force a freeze, just provide a list of everything that you have tried to resolve this problem *Smile

 

Well I did it again before reading above post (created freeze by leaving device on with no user or Internet input; b.t.w., does NOT happen if I view documents with no input for a long time, and of course not while watching streaming movies)
DESKTOP-FIQ3TKD-27_10_2017_152105_76.zip

 

Answering post: have done many, many things, incl. modifying Power Options, running 86x Firefox instead of new 64x, changing sleep, modifying registry incl. disabling Windows Update, etc. All reverted (changed back!) via System Restore, sfc /scannow and dism /online /cleanup-image /restorehealth (followed by scannow re-check) . What has worked, so long as I don't leave machine on in idle for more than 5 min. without entering Sleep Mode (which it will go into automatically as designed a lot of the time, obviously not today before), is not letting machine turn off ANY network adapters "to save power" (incl. Mobile Partner dongle) and using special HP Optimized Power settings.

Am running scannow to see if there were some system changes (WinX v1703 does this frequently on its own, changing my settings re various apps, Windows Defender vs Kaspersky, etc.)

B.t.w., though so far no BSOD, and except for a maybe one-minute "were fixing ...." Blue Screen, often after a re-start following a freeze then will be a short, quickly passing Blue Screen for 1 - 5 sec "wait while we're fixing..." (don't remember exact wording) going immediately to normal start screen

OK, scannow found no problems, so didn't run dism/restore health

 

have done so, started debug thread here > re: freezing told by zbook to post log here - Windows 10 Forums

 

These were some of the problems seen in the logs:

Code: Event[922]: Log Name: System Source: Microsoft-Windows-Kernel-General Date: 2017-09-22T23:30:04.188 Event ID: 5 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FIQ3TKD Description: {Registry Hive Recovered} Registry hive (file): '\??\C:\WINDOWS\ServiceProfiles\LocalService\NTUSER.DAT' was corrupted and it has been recovered. Some data might have been lost.[/quote]
Code: Event[5139]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-10-02T02:14:58.719 Event ID: 98 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FIQ3TKD Description: Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.Event[5140]: Log Name: System Source: Ntfs Date: 2017-10-02T02:15:00.347 Event ID: 55 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FIQ3TKD Description: A corruption was discovered in the file system structure on volume C:.The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.[/quote] Code: Event[1193]: Log Name: System Source: Microsoft-Windows-Kernel-Boot Date: 2017-09-23T12:31:48.753 Event ID: 29 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FIQ3TKD Description: Windows failed fast startup with error status 0xC00000D4.[/quote] Code: Event[3554]: Log Name: System Source: Service Control Manager Date: 2017-09-27T16:15:35.843 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The Kaspersky Lab service driver service failed to start due to the following error: A device attached to the system is not functioning.[/quote] Code: Event[3677]: Log Name: System Source: BTHUSB Date: 2017-09-27T16:25:07.337 Event ID: 17 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.[/quote] Code: Event[5258]: Log Name: System Source: BTHUSB Date: 2017-10-02T02:20:47.325 Event ID: 17 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.[/quote] Code: Event[17875]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-10-17T17:47:29.335 Event ID: 10317 Task: PnP Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FIQ3TKD Description: Miniport HUAWEI Mobile Connect - 3G Network Card, {04DBFEB6-308A-483B-99AC-E8AA550EBCEF}, had event Fatal error: The miniport has failed a power transition to operational power[/quote] Code: Event[20246]: Log Name: System Source: Microsoft-Windows-NDIS Date: 2017-10-22T20:40:37.803 Event ID: 10317 Task: PnP Level: Error Opcode: Info Keyword: N/A User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: Miniport HUAWEI Mobile Connect - 3G Network Card, {04DBFEB6-308A-483B-99AC-E8AA550EBCEF}, had event Fatal error: The miniport has failed a power transition to operational power[/quote] Code: Event[23390]: Log Name: System Source: BTHUSB Date: 2017-10-27T04:04:36.113 Event ID: 17 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The local Bluetooth adapter has failed in an undetermined manner and will not be used. The driver has been unloaded.[/quote] Code: Event[18020]: Log Name: System Source: Display Date: 2017-10-17T23:26:37.339 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: Display driver igfx stopped responding and has successfully recovered.[/quote] Code: Event[6263]: Log Name: System Source: Disk Date: 2017-10-03T21:34:11.240 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.[/quote] Code: Event[6263]: Log Name: System Source: Disk Date: 2017-10-03T21:34:11.240 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.[/quote] Code: Event[7619]: Log Name: System Source: Disk Date: 2017-10-09T04:06:38.963 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.Event[7620]: Log Name: System Source: Disk Date: 2017-10-09T04:06:39.177 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.Event[7621]: Log Name: System Source: Disk Date: 2017-10-09T04:06:39.380 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.Event[7622]: Log Name: System Source: Disk Date: 2017-10-09T04:06:39.598 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.Event[7623]: Log Name: System Source: Disk Date: 2017-10-09T04:06:39.809 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.[/quote] Code: Event[7626]: Log Name: System Source: Disk Date: 2017-10-09T07:02:09.724 Event ID: 11 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The driver detected a controller error on \Device\Harddisk1\DR1.[/quote] Code: Event[21559]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-10-24T04:15:41.035 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80a22481923, 0xffffe300d6d65088, 0xffffe300d6d648d0). A dump was saved in: C:\WINDOWS\Minidump\102417-11203-01.dmp. Report Id: ba6e5884-777b-4d98-9e29-48fbf944dc80.[/quote] Code: Event[21416]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-10-24T03:43:43.643 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-FIQ3TKD Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000001e (0xffffffffc0000005, 0xfffff80282271923, 0xffff80801dda7088, 0xffff80801dda68d0). A dump was saved in: C:\WINDOWS\Minidump\102417-11093-01.dmp. Report Id: d4681856-ad34-461e-b8be-8916548bbe87.[/quote] Code: Event[5139]: Log Name: System Source: Microsoft-Windows-Ntfs Date: 2017-10-02T02:14:58.719 Event ID: 98 Task: N/A Level: Error Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-FIQ3TKD Description: Volume C: (\Device\HarddiskVolume4) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.[/quote]
Version 10.0.15063 Build 15063

Code: 24/10/2017 01:56 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff80282271923 P4: ffff80801dda7088 P5: ffff80801dda68d0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-11093-01.dmp \\?\C:\Windows\Temp\WER-14375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C9B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CC5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CF4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_6c27118583b9cda955731c59a9a51f083e677b3_00000000_cab_0d51f95f Analysis symbol: Rechecking for solution: 0 Report Id: d4681856-ad34-461e-b8be-8916548bbe87 Report Status: 2049 Hashed bucket: 24/10/2017 01:44 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff80282271923 P4: ffff80801dda7088 P5: ffff80801dda68d0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-11093-01.dmp \\?\C:\Windows\Temp\WER-14375-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C9B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CC5.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1CF4.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_6c27118583b9cda955731c59a9a51f083e677b3_00000000_03b91cd9 Analysis symbol: Rechecking for solution: 0 Report Id: d4681856-ad34-461e-b8be-8916548bbe87 Report Status: 4 Hashed bucket:24/10/2017 02:22 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff80a22481923 P4: ffffe300d6d65088 P5: ffffe300d6d648d0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-11203-01.dmp \\?\C:\Windows\Temp\WER-15312-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A72.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A9B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AAC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_10dff1f3ba9d369aaa48b4c62861a6aafacff2e8_00000000_cab_037d6358 Analysis symbol: Rechecking for solution: 0 Report Id: ba6e5884-777b-4d98-9e29-48fbf944dc80 Report Status: 2049 Hashed bucket:24/10/2017 02:15 Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1e P2: ffffffffc0000005 P3: fffff80a22481923 P4: ffffe300d6d65088 P5: ffffe300d6d648d0 P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102417-11203-01.dmp \\?\C:\Windows\Temp\WER-15312-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A72.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6A9B.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6AAC.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_10dff1f3ba9d369aaa48b4c62861a6aafacff2e8_00000000_03ac6aa0 Analysis symbol: Rechecking for solution: 0 Report Id: ba6e5884-777b-4d98-9e29-48fbf944dc80 Report Status: 4 Hashed bucket:[/quote] Code: 17/10/2017 21:29 Application Error Faulting application name: Setup.exe_Intel® PROSet/Wireless Software, version: 20.0.2.0, time stamp: 0x5044b448 Faulting module name: KERNELBASE.dll, version: 10.0.15063.674, time stamp: 0x6d16dd24 Exception code: 0xc000041d Fault offset: 0x000eb872 Faulting process id: 0x1520 Faulting application start time: 0x01d3478e7dec4faa Faulting application path: C:\Users\User\AppData\Local\Temp\sefC378.tmp\Setup.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: c9968807-99e6-4bcf-9ca2-2b769da90075 Faulting package full name: Faulting package-relative application ID: 15/10/2017 10:29 Application Error Faulting application name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58d16fa6 Faulting module name: ZeroConfigService.exe, version: 19.60.0.0, time stamp: 0x58d16fa6 Exception code: 0xc0000409 Fault offset: 0x000000000022af80 Faulting process id: 0x1004 Faulting application start time: 0x01d3459ff7cf4fa3 Faulting application path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe Faulting module path: C:\Program Files\Intel\WiFi\bin\ZeroConfigService.exe Report Id: 6c6e1ffe-da20-4f9d-a842-59dba8410a19 Faulting package full name: Faulting package-relative application ID:[/quote]