Odd issues (data corruption?) after BSOD - SSL broken?

[Valantar]

A few days ago my desktop BSOD'd out of nowhere. After rebooting, it happened again in about 15-20 minutes. That's when the issues started. (No, I still don't have any idea what caused the BSODs. At least they haven't returned.)

First I couldn't log in - entering my pin would give some obscure error. Turned out it was just the pin login that was broken, and logging in with a password worked fine. Had to disable pin login and create a new pin to get that working again. Thought everything was fine after that, but apparently not:
-I can't use my LastPass extension any more (can't even access their website!)
-Logitech Gaming Software reset my mouse settings
-GOG Galaxy wouldn't start

This is what I've come across so far, but I wouldn't be surprised if there was more weirdness going on. The sheer randomness of it all does sound like data corruption to me, although I don't know of any way of checking if anything else is borked.

I fixed the latter with a reinstall (luckily I didn't have to re-download the 30GB Witcher 3 install), and fixing the mouse settings was trivial enough, but for the life of me I can't get LastPass working. Trying to log in to the extension gives me a generic error message, while attempting to access the web site gives the error message

This site can’t provide a secure connection
lastpass.com uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH

Which is obviously not true as I can get in just fine on my phone and laptop. It's the same whatever browser I try, so I'm thinking there must be some sort of corruption in my PC's SSL certificates or some such, and not just an error in Chrome. To be clear, this is the only site I've had problems with, but then it might be LP is the only service I use with this type of SSL, or some such. I have no idea.

Does anyone have any tips as to how I might troubleshoot this, besides reinstalling Windows? I don't have the slightest clue how Windows manages security certificates and the like, so if anyone could enlighten me, that would be much appreciated.

 

[XavierMace]

You're accessing their website in Chrome. The SSL is on their side, not yours. Check your TLS and SSL settings in Chrome or use a different browser.

That said, it would be a good idea to check your dump file to see what the BSOD was and check your event log to see what else you have going on.

 

[RLGL]

malware?

 

[Burpo]

First thing to try would be a System Restore to a previous date. Can't tell you how much grief that has saved me over the years.
If that works, then I'd run scannow /f & chkdsk & check the drive.

 

[Valantar]

You're accessing their website in Chrome. The SSL is on their side, not yours. Check your TLS and SSL settings in Chrome or use a different browser.

That said, it would be a good idea to check your dump file to see what the BSOD was and check your event log to see what else you have going on.

It's the same whatever browser I try

In other words, Chrome's not the problem here, but rather how my PC verifies the servers' certificates.

Happily, I managed to figure it out - like ut always is, when you ask for help, think "oh, I'll just try a bit more" and everything works out. According to Chrome the certificates of all sites that were working were "issued by" (I take it that means verified by?) Bitdefender, and I use Bitdefender free antivirus. Reinstalled that, and now Lastpass works just fine. I'll leave it to someone more knowledgeable than me to figure out why.

I'll definitely look into the dump files and event log though, never know what might be lurking in the background here.

 

[XavierMace]

Missed that it happened in all browsers. AV was going to be my next suggestion. My dad runs Kaspersky and has similar issues. Basically Kaspersky (or Bitdefender in your case) is acting as a filter/proxy for your web traffic and if it's misconfigured or malfunctioning, that can break SSL certificates.

 

[Valantar]

Missed that it happened in all browsers. AV was going to be my next suggestion. My dad runs Kaspersky and has similar issues. Basically Kaspersky (or Bitdefender in your case) is acting as a filter/proxy for your web traffic and if it's misconfigured or malfunctioning, that can break SSL certificates.

I suppose it was doing its job then, in a completely malfunctioning way Anyhow, good to know that this is something that can break, and what it looks like when it does.

As for reverting to a previous system image, this whole shenanigans (sadly) reminded me that I hadn't created one since I bought my 960 Evo and installed Windows on it a few months ago. Oh, and despite the setting for creating dump file being enabled, there isn't one. The event log tells me it should be there, but it's MIA. Yay.

Other than that, there's nothing to glean from the event log about the BSODs, sadly, just the standard "The previous system shutdown (...) was unexpected" and "The system has rebooted without cleanly shutting down first. Yadda yadda yadda" fare. The only event that tells me anything at all gave me the code 0x000000ef, which just means "CRITICAL_PROCESS_DIED". Extremely informative, that one.