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

axe0 · 29 Oct 2017

Run powershell as normal user, not as administrator, to run the command.

Airider · 29 Oct 2017

Attachment 161087

English Translation below >

°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
EDIT:
InstallAgentUserBroker still WAY ahead with a high score so far of 223 >

Attachment 161115
etc., to
Attachment 161116

Airider · 29 Oct 2017

Translation:

TimeCreated: 10/29/2017 4:25:53 PM
Message:

File system on C: is checked.
The type of the file system is NTFS.

A disk check is planned.
The disk check is now running.

Phase 1: The basic file system structure is investigated ...
743680 records processed.
File verification finished.
88211 large records processed.
0 invalid records processed.

Phase 2: The file name association is investigated ...
882666 Processing index entries.
Index check finished.
0 non-indexed files.
0 non-indexed files restored.

Phase 3: Security Descriptions Are Investigated
14 unused index entries from index $ SII of file 0x9 are cleared.
14 unused index entries from index $ SDH of file 0x9 are cleaned up.
14 unused safety descriptions are cleaned up.
Verification of the safety descriptions ended.
69494 Data files processed.
CHKDSK reviews USN journal ...
39439880 USN bytes processed.
The review of the USN Journal has been completed.

Phase 4: Searching for faulty clusters in user file data ...
743664 Files were processed.
Date data check finished.

Phase 5: Searching for faulty, free clusters ...
91334835 free cluster processing.
Verification of free space is finished.

File system was checked, no problems detected.
No further action required.

486945465 KB Disk space on the disk total
120422668 KB in 402934 files
293524 KB in 69495 indexes
0 KB in bad sectors
889933 KB used by the system
65536 KB from the log file
365339340 KB available on the disk

4096 bytes in each allocation unit
121736366 Allocating units on the data carrier total
91334835 Allocation units are available on the data carrier

Internal information:
00 59 0b 00 44 35 07 00 0e 6a 0a 00 00 00 00 00 .Y..D5 ... j ......
5e 06 00 00 87 00 00 00 00 00 00 00 00 00 00 00 ^ ...............

The check of the data carrier has been completed.
Please wait until the computer has restarted.

TimeCreated: 10/29/2017 3:42:30 PM
Message:

File system on C: is checked.
The type of the file system is NTFS.

A disk check is planned.
The disk check is now running.

Phase 1: The basic file system structure is investigated ...
743680 records processed.
File verification finished.
88211 large records processed.
0 invalid records processed.

Phase 2: The file name association is investigated ...
882628 Processing index entries.
Index check finished.
0 non-indexed files.
0 non-indexed files restored.

Phase 3: Security Descriptions Are Investigated
14 unused index entries from index $ SII of file 0x9 are cleared.
14 unused index entries from index $ SDH of file 0x9 are cleaned up.
14 unused safety descriptions are cleaned up.
Review ofGoogle Translate for Business:Translator Toolkit Website Translator

About Google Translate Community Mobile About Google

axe0 · 30 Oct 2017

Diagnostic Test

DRIVER VERIFIER

Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Airider · 30 Oct 2017

Right-o! > selected "all drivers installed in this PC", big fat BSOD almost immediately:

"Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you.
100% complete"

"what failed: ewusbwwan.sys "

The machine started to get very warm (though not critically, perhaps just a little bit over 40°C MAX on the outside, as I have sensitive and "trained" fingers as good temp. instrument) even with the fan running strongly, but I left it so for ca. 10 min., not knowing if that was part of the process. Then I manually shut down, selected (in German) System Restore which worked!

I think the following is perhaps very significant > normally if I manually use System Restore in order for it to complete successfully I MUST first disable Kaspersky "Self-Defense" (which prohibits changes to its settings, an obvious anti-malware/virus system AND self-protection). THIS time I forgot to do that yet the System Restore completed successfully (written in German for the first time, though the language pack is English and usually used even for Windows infos).

from How To Fix Ewusbwwan.sys Blue Screen Errors (BSOD)

Ewusbwwan.sys is a type of SYS file associated with Huawei Technologies Co., Ltd. USB NDIS Miniport Driver developed by Huawei Technologies Co., Ltd for the Windows Operating System. The latest known version of Ewusbwwan.sys is 6.0.1.321, which was produced for Windows. This SYS file carries a popularity rating of 1 stars and a security rating of "UNKNOWN".

Please note that although this failed, not recently, but I have in the past had freezes with Huawei Mobile Partner disconnected and not plugged in to the USB port (before driver & BIOS updates, and HP Optimized Power Settings, etc.). Further there is no available Mobile Partner dongle firmware update ....

However I will NOW make an experiment and leave the machine on with Mobile Partner turned off, disconnected and unplugged from the port. For the record in the past month or more, before and after driver updates, etc., , while merely looking for well more than one HOUR at stored documents but with Mobile Partner turned off, disconnected and unplugged from the port .... there have been NO freezes. Period.

axe0 · 30 Oct 2017

Please do not use any suggestions from solvusoft, its site is known for bad and improper suggestions.

Ewusbwwan.sys is a type of SYS file

Aka a driver.

Airider · 30 Oct 2017

FREEZE upon exiting Windows-induced Sleep mode from above experiment:

Left machine on unattended for ca. 45 min with Mobile Partner turned off and disconnected from USB. Had self-entered Sleep mode and easily came out .... then froze seconds after successfully coming out of Sleep. Note: when Mobile Partner disconnected and only viewing documents (and NO freezing that way.... EVER) I suppose that I inputted document movements (change page or up/down) within 5 min max. This time freeze occurred with NO input from me (or Internet download/streaming via Mobile Partner)

Associated with this freeze >

Attachment 161168
Attachment 161169

e.t.c. ....

Airider · 30 Oct 2017

axe0 said:

Please do not use any suggestions from solvusoft, its site is known for bad and improper suggestions.
Aka a driver.

I may "look stupid" but am not; had not even slightly considered downloading from there, only as a heads-up for info re: that "what failed" notice. Still, much thanks for reinforcing my decision

B.t.w., is it possible that the Kaspersky-Defender conflict is behind the Software Protection off? When that notice came w.r.t. other freezes, I checked and the Software Protection had turned back on later/afterwards

axe0 · 30 Oct 2017

The description of the software protection service

Enables the download, installation and enforcement of digital licenses for Windows and Windows applications. If the service is disabled, the operating system and licensed applications may run in a notification mode. It is strongly recommended that you not disable the Software Protection service.

Unless Kaspersky does something with digital licenses from Windows and Windows applications, there is no conflict.

Airider · 30 Oct 2017

If everything always went as planned /programmed, there would be far fewer problems. In fact, many times (perhaps 25x in the last months), upon startup -- either after a System Restore re-start, my own manual re-start after a freeze (which ca. 50% of the time REQUIRES another proper Windows complete "shut down" because even clicking on "re-start" leaves the sound driver OFF, with "no solution found", then after a new manual start, the sound functions!), or just randomly with no freeze involved -- the Firewall will be OFF and I am asked to choose Defender or Kaspersky! Then I have to indicate "yes I trust" Kaspersky. Following that I often have to actually let Kaspersky download updates (it does so automatically, but this step to seems to be required in these cases!) to let Defender "find out" that Kaspersky is REALLY functioning. Before doing this, when opening Windows Update in Settings, I may find that Defender needs to be turned on. Or when then going to Defender, finding that it is NOT doing Periodic Scanning as set before. I used to have to use System Restore to escape this loop, but have now found that simply letting Kaspersky update itself does the trick (after "trusting" Kaspersky as above).

I have gotten into the habit, after an event or in general, after startup to check that Defender is doing Periodic Scanning in Settings. I must do this check after every daily startup since the problem is so frequent.

So for whatever unplanned reason ... there IS an ongoing conflict between Kaspersky and Defender and I am forced to continually monitor it ... except when Windows itself monitors and gives a notice in Action Center that Firewall is off, and to choose Defender or Kaspersky.

Also, please note that I never had freezes using Windows 7 on my old Toshiba AND with the same Mobile Partner dongle, and NO freezes with this "pre-owned" (but great working) HP EliteBook G2 with the same Samsung SSD I had installed at the start AND using the same Mobile Partner dongle with version of Windows 10 Pro installed when I bought it months ago. The FREEZING problem started after I tried to get Spotlight to function and messed with the Registry following online advice (Spotlight is STILL not functioning, but now I know that I do not want it -- it provides very stupid photos!! -- and so do not use it, though the system may still be trying to update Spotlight) .... AND since I was tricked into installing v1703 (it was indicated as an update but not as v1703, which I had planned to avoid until it was eventually "user-debugged", etc.)

So: Mobile Partner not a previous freeze cause, nor the older, original WinX, but freezing first started with v1703 (WinX Pro)

°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°

whether symptom or cause (or innocent bystander) InstallAgentUserBroker now up to 277 failures (all other failures/errors just a small handful)

Attachment 161198
Attachment 161199