Saturday, September 20, 2014

HP Envy has odd TLS "error 70" crashes; more on WLAN; more on recovery partitions for Windows 8.1


Two items:  The recurring instability of my HP ENVY all-in-one seems to be related to this curious message on the Event Log: “A fatal alert was generated and sent to the remote endpoint.  This may result in termination of the connection. The TLS protocol defined fatal error code is 70.  The Windows SChannel error state is 105”, event type 36888.
  
This error seems to occur in the “Transport Layer”, as explained here on msdn.  Microsoft forums have this info, and Arstechnica has a similar reference.
   
The way it happens is that HP suddenly says it needs to restart the system after encountering a problem.  As it “gather information” SmartDrive throws a hard disk error.  But if you turn it off on the power button, wait thirty seconds, and turn it back on, the machine quickly comes back to where it was with all browser sessions intact and responding (although Word or Office has to recover whatever was open). 
   
The machine still sometimes stops responding suddenly, and restarts quickly with the power button, and then does not fail again until shut down for a long time.  There is a warning in the event log that the “ WLAN extensibility module has stopped”. But Internet access continues OK.  
    
These problems may be connected to the Microsoft prncacln.inf driver. 
 

As for the Toshiba Satellite, Best Buy and Geek Squad replaced it with a Radius Satellite for the same price under extended contract, after Toshiba could not find a motherboard (maybe because of overseas problems).  This lighter machine does not have an Ethernet port (you buy a USB-one) or CD drive (external).  Curiously it also doesn’t have a separate drive letter for a recovery partition (discussion).
    
It is apparently common for manufacturers not to create their own recovery disks, and expect users (or retails stores) to do this. 

Update: Oct. 9, 2014

Another false hard drive warning from Smartdrive (while sleeping) was preceded by this message on the Event Viewer (no info at Microsoft): "The server {BF6C1E47-86EC-4194-9CE5-13C15DCB2001} did not register with DCOM within the required timeout". 

No comments: