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

Windows 10 Laptop won't boot into normal mode, can access safe mod


  • Please log in to reply

#46
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts

I actually wanted to keep Bitdefender rather than uninstalling it, it seems to work well. Also Malwarebytes seems to be picking up web malware fairly well?


  • 0

Advertisements


#47
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts

Farbar Recovery Scan Tool (x64) Version: 09.12.2018
Ran by Toshiba-laptop (09-12-2018 13:33:59)
Running from C:\Users\Toshiba-laptop\Desktop
Boot Mode: Normal

================== Search Registry: "gzflt.sys;trufos.sys" ===========


===================== Search result for "gzflt.sys" ==========

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gzflt]
"ImagePath"="system32\DRIVERS\gzflt.sys"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gzflt\Parameters]
"FsSp"="\??\c:\program files\bitdefender\bitdefender security\
\??\c:\program files\common files\bitdefender\bitdefender firewall\
\??\c:\program files\common files\bitdefender\bitdefender threat scanner\
\??\c:\program files\common files\bitdefender\bitdefender threat scanner\bdrescue\
\??\c:\program files\common files\bitdefender\setupinformation\bitdefender redline\
\??\c:\program files\common files\bitdefender\setupinformation\cl-23-79ac6696-228d-4871-8f43-ea1b84fd06c5\
\??\c:\programdata\bitdefender\desktop\obk\
\??\c:\programdata\bitdefender\desktop\profiles\
\??\c:\programdata\bitdefender\desktop\quarantine\
\??\c:\programdata\bitdefender\desktop\wifiadviser\
\??\c:\programdata\bitdefender\passwordmanager\
\??\c:\windows\system32\drivers\atc.sys
\??\c:\windows\system32\drivers\avc3.sys
\??\c:\windows\system32\drivers\bddci.sys
\??\c:\windows\system32\drivers\bdelam.sys
\??\c:\windows\system32\drivers\bdprivmon.sys
\??\c:\windows\system32\drivers\bdvedisk.sys
\??\c:\windows\system32\drivers\gzflt.sys
\??\c:\windows\system32\drivers\ignis.sys
\??\c:\windows\system32\drivers\trufos.sys"


===================== Search result for "trufos.sys" ==========

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\gzflt\Parameters]
"FsSp"="\??\c:\program files\bitdefender\bitdefender security\
\??\c:\program files\common files\bitdefender\bitdefender firewall\
\??\c:\program files\common files\bitdefender\bitdefender threat scanner\
\??\c:\program files\common files\bitdefender\bitdefender threat scanner\bdrescue\
\??\c:\program files\common files\bitdefender\setupinformation\bitdefender redline\
\??\c:\program files\common files\bitdefender\setupinformation\cl-23-79ac6696-228d-4871-8f43-ea1b84fd06c5\
\??\c:\programdata\bitdefender\desktop\obk\
\??\c:\programdata\bitdefender\desktop\profiles\
\??\c:\programdata\bitdefender\desktop\quarantine\
\??\c:\programdata\bitdefender\desktop\wifiadviser\
\??\c:\programdata\bitdefender\passwordmanager\
\??\c:\windows\system32\drivers\atc.sys
\??\c:\windows\system32\drivers\avc3.sys
\??\c:\windows\system32\drivers\bddci.sys
\??\c:\windows\system32\drivers\bdelam.sys
\??\c:\windows\system32\drivers\bdprivmon.sys
\??\c:\windows\system32\drivers\bdvedisk.sys
\??\c:\windows\system32\drivers\gzflt.sys
\??\c:\windows\system32\drivers\ignis.sys
\??\c:\windows\system32\drivers\trufos.sys"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\trufos]
"ImagePath"="system32\DRIVERS\trufos.sys"

====== End of Search ======


  • 0

#48
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts

Hottest temperature at rest was Core 0 = 64C.

 

Hottest temperature when playing video for 5 mins was Temp1 = 68C


  • 0

#49
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 09/12/2018 14:48:01

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 04/12/2018 17:37:57
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.

Log: 'System' Date/Time: 04/12/2018 17:34:26
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.

Log: 'System' Date/Time: 02/12/2018 17:02:29
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.

Log: 'System' Date/Time: 02/12/2018 15:52:14
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.

Log: 'System' Date/Time: 02/12/2018 15:49:39
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.

Log: 'System' Date/Time: 02/12/2018 15:49:39
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.

Log: 'System' Date/Time: 01/12/2018 23:36:06
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.

Log: 'System' Date/Time: 01/12/2018 23:23:41
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.

Log: 'System' Date/Time: 01/12/2018 15:15:29
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.

Log: 'System' Date/Time: 01/12/2018 15:07:08
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.

Log: 'System' Date/Time: 01/12/2018 14:08:26
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.

Log: 'System' Date/Time: 01/12/2018 14:08:26
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.

Log: 'System' Date/Time: 01/12/2018 13:26:34
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.

Log: 'System' Date/Time: 01/12/2018 12:54:35
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.

Log: 'System' Date/Time: 01/12/2018 12:46:58
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.

Log: 'System' Date/Time: 01/12/2018 09:22:58
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.

Log: 'System' Date/Time: 01/12/2018 09:13:04
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.

Log: 'System' Date/Time: 01/12/2018 09:03:52
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.

Log: 'System' Date/Time: 01/12/2018 09:03:52
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.

Log: 'System' Date/Time: 01/12/2018 09:02:10
Type: Critical Category: 173
Event: 142 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error is caused because the system stopped responding and the hardware watchdog triggered a system reset.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 09/12/2018 14:14:40
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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: 09/12/2018 14:07:38
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {784E29F4-5EBE-4279-9948-1E8FE941646D} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/12/2018 14:05:33
Type: Error 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: 09/12/2018 14:05:23
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 09/12/2018 14:05:08
Type: Error 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.WscCloudBackupProvider  and APPID  Unavailable  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 09/12/2018 14:05:06
Type: Error 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.WscCloudBackupProvider  and APPID  Unavailable  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 09/12/2018 14:05:04
Type: Error 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.WscCloudBackupProvider  and APPID  Unavailable  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 09/12/2018 14:05:04
Type: Error 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.WscCloudBackupProvider  and APPID  Unavailable  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 09/12/2018 14:05:02
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 09/12/2018 14:04:38
Type: Error Category: 0
Event: 7000 Source: Service Control Manager
The RapportMgmtService service failed to start due to the following error:  The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.

Log: 'System' Date/Time: 09/12/2018 14:04:37
Type: Error Category: 0
Event: 10000 Source: Microsoft-Windows-WLAN-AutoConfig
WLAN Extensibility Module has failed to start.  Module Path: C:\WINDOWS\system32\Rtlihvs.dll Error Code: 126

Log: 'System' Date/Time: 09/12/2018 14:04:10
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {D7FD466D-F6CF-4C8E-86DD-12E9B0FDAE48} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/12/2018 14:04:09
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {D7FD466D-F6CF-4C8E-86DD-12E9B0FDAE48} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/12/2018 14:04:09
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {D7FD466D-F6CF-4C8E-86DD-12E9B0FDAE48} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/12/2018 14:04:09
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {D7FD466D-F6CF-4C8E-86DD-12E9B0FDAE48} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/12/2018 14:04:09
Type: Error Category: 0
Event: 10010 Source: Microsoft-Windows-DistributedCOM
The server {D7FD466D-F6CF-4C8E-86DD-12E9B0FDAE48} did not register with DCOM within the required timeout.

Log: 'System' Date/Time: 09/12/2018 09:05:46
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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: 09/12/2018 08:57:44
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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: 08/12/2018 19:03:30
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user Toshiba\Toshiba-laptop SID (S-1-5-21-967705235-186355052-2569062438-1001) 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: 08/12/2018 17:56:00
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID  {D63B10C5-BB46-4990-A94F-E40B9D520160}  and APPID  {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}  to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 09/12/2018 14:04:58
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name settings-win.data.microsoft.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 09/12/2018 14:04:53
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 09/12/2018 14:04:34
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 09/12/2018 08:54:46
Type: Warning Category: 0
Event: 153 Source: Disk
The IO operation at logical block address 0x761f00 for Disk 0 (PDO name: \Device\00000034) was retried.

Log: 'System' Date/Time: 08/12/2018 23:25:52
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 08/12/2018 17:45:54
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 07/12/2018 21:24:30
Type: Warning Category: 0
Event: 1073 Source: User32
The attempt by user TOSHIBA\Toshiba-laptop to restart/shutdown computer TOSHIBA failed

Log: 'System' Date/Time: 07/12/2018 00:14:15
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name 19-10.b.cdn13.com timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2018 23:13:56
Type: Warning Category: 1014
Event: 1014 Source: Microsoft-Windows-DNS-Client
Name resolution for the name wpad timed out after none of the configured DNS servers responded.

Log: 'System' Date/Time: 06/12/2018 18:21:22
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 05/12/2018 22:24:12
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 05/12/2018 21:54:30
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 05/12/2018 21:53:56
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 05/12/2018 21:34:53
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 05/12/2018 21:26:56
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 05/12/2018 21:14:12
Type: Warning Category: 0
Event: 34 Source: BTHUSB
The local adapter does not support an important Low Energy controller state to support peripheral mode. The minimum required supported state mask is 0x491f7fffff; got 0x1fffffff. Low Energy peripheral role functionality will not be available.

Log: 'System' Date/Time: 04/12/2018 17:37:56
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\IntcAzAudAddService failed to load for the device HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_1179FC14&REV_1001\4&1ec0f511&0&0001.

Log: 'System' Date/Time: 04/12/2018 17:37:56
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\AtiHDAudioService failed to load for the device HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002\5&120d8861&0&0001.

Log: 'System' Date/Time: 04/12/2018 17:37:55
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\RtlWlanu failed to load for the device USB\VID_0BDA&PID_C811\123456.

Log: 'System' Date/Time: 04/12/2018 17:34:25
Type: Warning Category: 212
Event: 219 Source: Microsoft-Windows-Kernel-PnP
The driver \Driver\IntcAzAudAddService failed to load for the device HDAUDIO\FUNC_01&VEN_10EC&DEV_0269&SUBSYS_1179FC14&REV_1001\4&1ec0f511&0&0001.

 


  • 0

#50
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts

Vino's Event Viewer v01c run on Windows 7 in English
Report run at 09/12/2018 14:49:38

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

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 09/12/2018 14:46:25
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc000041d Fault offset: 0x0000adc1 Faulting process ID: 0x2c98 Faulting application start time: 0x01d48fc831e56c9b Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: 864cc3f9-3325-44da-8263-0f13b7a21997 Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 09/12/2018 14:46:22
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc0000005 Fault offset: 0x0000adc1 Faulting process ID: 0x2c98 Faulting application start time: 0x01d48fc831e56c9b Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: 7f2a5258-92f0-4522-a84a-e4c599341bd5 Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 09/12/2018 14:04:38
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 08/12/2018 19:00:35
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc000041d Fault offset: 0x0000adc1 Faulting process ID: 0x2ee0 Faulting application start time: 0x01d48f1df0c50711 Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: c936d5a1-30fd-4fc6-b972-5189acd033ff Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 08/12/2018 19:00:31
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc0000005 Fault offset: 0x0000adc1 Faulting process ID: 0x2ee0 Faulting application start time: 0x01d48f1df0c50711 Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: 9542f983-28aa-442d-ac76-168087199ecb Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 08/12/2018 17:45:58
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 06/12/2018 23:13:53
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc000041d Fault offset: 0x0000adc1 Faulting process ID: 0x30dc Faulting application start time: 0x01d48d908e83ae6c Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: 3c027966-286a-43ea-835f-b0c6d0ddef86 Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 06/12/2018 23:13:49
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc0000005 Fault offset: 0x0000adc1 Faulting process ID: 0x30dc Faulting application start time: 0x01d48d908e83ae6c Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: 32dfe575-9483-4f35-b728-1f57433c6436 Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 06/12/2018 18:21:26
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 23:15:40
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc000041d Fault offset: 0x0000adc1 Faulting process ID: 0x350c Faulting application start time: 0x01d48ce9531b7db3 Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: cc95d991-e08c-461d-a27d-624a8f1aae0e Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 05/12/2018 23:15:36
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Faulting module name: WNDA3100v3.EXE, version: 1.0.0.10, time stamp: 0x54b63a2b Exception code: 0xc0000005 Fault offset: 0x0000adc1 Faulting process ID: 0x350c Faulting application start time: 0x01d48ce9531b7db3 Faulting application path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Faulting module path: C:\Program Files (x86)\NETGEAR\WNDA3100v3\WNDA3100v3.EXE Report ID: 2909fc38-e8b6-47e1-be06-103a4d77a723 Faulting package full name:  Faulting package-relative application ID:

Log: 'Application' Date/Time: 05/12/2018 22:24:16
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:54:33
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:53:59
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:34:56
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:28:49
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:28:49
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:28:48
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

Log: 'Application' Date/Time: 05/12/2018 21:27:38
Type: Error Category: 1
Event: 522 Source: ESENT
ShellExperienceHost (15180,P,98) TILEREPOSITORYS-1-5-21-967705235-186355052-2569062438-1014: An attempt to open the device with name "\\.\C:" containing "C:\" failed with system error 5 (0x00000005): "Access is denied. ". The operation will fail with error -1032 (0xfffffbf8).

Log: 'Application' Date/Time: 05/12/2018 21:26:59
Type: Error Category: 0
Event: 59 Source: SideBySide
Activation context generation failed for "C:\Program Files (x86)\Trusteer\Rapport\bin\RapportMgmtService.exe".Error in manifest or policy file "C:\Program Files (x86)\Trusteer\Rapport\bin\Trusteer.FoundationLib.MANIFEST" on line 0. Invalid Xml syntax.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 05/12/2018 21:54:01
Type: Warning Category: 0
Event: 6004 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <TrustedInstaller> failed a critical notification event.

Log: 'Application' Date/Time: 05/12/2018 21:27:11
Type: Warning Category: 0
Event: 1534 Source: Microsoft-Windows-User Profiles Service
Profile notification of event Create for component {2c86c843-77ae-4284-9722-27d65366543c} failed, error code is Not implemented .   

Log: 'Application' Date/Time: 04/12/2018 18:29:43
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 04/12/2018 18:29:43
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 04/12/2018 17:38:19
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 04/12/2018 17:35:33
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 04/12/2018 17:35:33
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 04/12/2018 17:34:31
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/12/2018 22:24:17
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/12/2018 22:24:17
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/12/2018 17:02:40
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 02/12/2018 15:56:11
Type: Warning Category: 0
Event: 0 Source: Dwminit
The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: AMD Radeon HD 7600M Series)

Log: 'Application' Date/Time: 02/12/2018 15:55:13
Type: Warning Category: 0
Event: 0 Source: Dwminit
The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: AMD Radeon HD 7600M Series)

Log: 'Application' Date/Time: 02/12/2018 15:54:05
Type: Warning Category: 0
Event: 0 Source: Dwminit
The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: AMD Radeon HD 7600M Series)

Log: 'Application' Date/Time: 02/12/2018 15:53:05
Type: Warning Category: 0
Event: 0 Source: Dwminit
The Desktop Window Manager process has exited. (Process exit code: 0x0000042b, Restart count: 1, Primary display device ID: AMD Radeon HD 7600M Series)

Log: 'Application' Date/Time: 01/12/2018 23:40:53
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 01/12/2018 23:40:53
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 01/12/2018 23:36:17
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 01/12/2018 23:30:08
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

Log: 'Application' Date/Time: 01/12/2018 23:30:08
Type: Warning Category: 0
Event: 6000 Source: Microsoft-Windows-Winlogon
The winlogon notification subscriber <GPClient> was unavailable to handle a notification event.

 


  • 0

#51
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,699 posts
  • MVP

If you have Bitdefender installed that's OK.  Thought you had something else. 

 

Your temps are too high.  What happens on a laptop is the interface between the heatsink and the fan gets clogged with dust.  This reduces air flow and let's it get hot.  On some laptops it's easy to get to the fan and remove it (not the heatsink or heatpipe - removing either requires new thermal paste) so you can remove the dust from the heatsink.  On other's it's major surgery.  Some of the HP's require you to remove the motherboard to get to the fan.  Dells often have an access hatch.  Google your laptop's part number and you will usually find a video showing how to take it apart.  If blowing air backwards through the air vents or sucking with a vacuum cleaner on the air intake doesn't help you can sometimes get some relief with a laptop cooler tray.  Hot components make errors and fail sooner.

 

I see this error:

 

Log: 'System' Date/Time: 09/12/2018 08:54:46
Type: Warning Category: 0
Event: 153 Source: Disk
The IO operation at logical block address 0x761f00 for Disk 0 (PDO name: \Device\00000034) was retried.

 

This could indicate a failing hard drive, bad connector (reseat hard drive), bad ram, bad motherboard or it might just be a heat related error. 

 

I would run a  disk check

https://www.thewindo...cking-windows-8

and a memory check:

https://www.windowsc...lems-windows-10

 

Your Netgear software is not working correctly and needs to be reinstalled.  Ditto the Trusteer Raport


  • 0

#52
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts

Thanks for the latest advice. Nothing came through for the disk and memory check, both were fine. I've also just uninstalled the Netgear and Trusteer software.

 

I think you're right, the original cause is likely due to heat. I'll have a go at removing all the dust next week.

 

Is there anything else you would advise now? Otherwise is this sorted?


  • 0

#53
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,699 posts
  • MVP

Probably it's just heat.  That can cause a lot of strange symptoms.  When you boot into Safe Mode a lot of stuff doesn't run so it probably runs a bit cooler.  Make sure you run on a flat hard surface.  Leaving it on a bed or even your lap can block the air intakes on the bottom.  It also helps to prop up the the back of the laptop (without blocking the  vents).  Heat rises and the heatsink and exhaust vent are usually in the back so this helps heat flow.

 

You might check your hard drive maker's website.  Most of them have software you can download to test your hard drive.  The extended or long test is the best.  IF that passes then your drive is good.  Come to think of it there is a hard drive test in speedfan:

 

click on the S.M.A.R.T. tab.  Click on the down arrow to the right of the Hard Disk box.  Select your hard drive.  Click on Perform an In-depth Online Analysis of this hard disk.  Your browser will open.

At the bottom of the new page will be a line:  

The link to get back and see a new report about this hard disk in the future is this.

Right click on the underlined "this" and select Copy Link Address.  Move to a Reply and Paste (Ctrl + v).

 

That just quickly checks the S M A R T info which will show us if the drive is mostly healthy. 
 


  • 0

#54
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts
Thanks, I'll check that mid week
  • 0

#55
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts
Hi thanks for your patience. I gave in and gave my laptop to a laptop specialist to look at. Seems the main culprit was bad hard disk sectors, rather than heat issue. There was only a little bit of dust inside. Currently my laptop is going through complete reformat and having Windows 10 installed again.
  • 0

Advertisements


#56
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,699 posts
  • MVP

I'm not convinced that a reformat will fix the problem for long.  Sounds to me like the hard drive is failing and needs to be replaced. 

 

Also dust is not the only cause of overheating.  The thermal pads on the heatsink/heatpipe  sometimes dry out and need to be removed and replaced with new thermal paste.  That's not as common as it used to be but it still happens.


  • 0

#57
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts
Ok my IT guy says that my laptop works ok with Windows 8 and basic display driver, but doesn't work with Windows 10 and any display driver otherwise it gets black screen again. So looks like my laptop is on the way out and will be buying new laptop soon.
  • 0

#58
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,699 posts
  • MVP

Not sure I believe that.  There's very little difference between 8 and 10.  Don't suppose you are in Florida?  I'd like to look at it.


  • 0

#59
joecool90

joecool90

    Member

  • Topic Starter
  • Member
  • PipPip
  • 92 posts
So unfortunately the black screen issue affects Windows 8 as well. I'm based in UK so you can't see my laptop unfortunately. ☹️ I'll just buy a new one
  • 0

#60
RKinner

RKinner

    Malware Expert

  • Expert
  • 24,699 posts
  • MVP

Perhaps you could just have them load Win 7 on it?


  • 0






Similar Topics

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP