Windows 10: Intel Compute Stick, first BSOD

Hi BSOD squad, I hope you are able to tell me what caused this BSOD today.

Background: Intel Compute Stick, used as HTPC. Never had any issues, works like a charm. Upgraded last night to build 10547 EN-GB x86.

Today VPN connection to Finland to watch news from Finnish TV, switch VPN to Sweden to watch Swedish news, switched VPN to UK to watch rugby when at the same moment the VPN told connection is established I got the BSOD. VPN is CyberGhost version 5.0.15.14 (15.9.7.5IE), the latest.

Specs summary:
Attachment 38240

DM Log Collector ZIP: Attachment 38241

Thanks in advance,



:)

 

Intel Compute Stick Useless

Just getting a total view of my error across and storing images of the fault while i can. The images function in this thread is terrible. Mind your own business.

 

Intel Compute Stick Useless

Hello, ive been having nothing but problems since I got the compute stick. It kept resetting itself saying kernel error, iqrl error etc. Now there is no internet connection. It wont let me reset anything, view events, connect to the internet or troubleshoot.
Can I have a refund please? Every 5 - 20 minutes it resets and wont let me into safemode.

Moved from: Windows / Windows 10 / Performance & system failures

 

Hi Kari ^_^,


I am trying to analyse the dump file but I am getting symbol errors. Furthermore, the WinDBG stalls when trying to run any command for your dump file at least on my system *Sad
But, I managed to see that the problem is indeed being caused by your VPN software.

If you really like your VPN, I would suggest you to contact their support services and raise a ticket.


Let me know how it goes ^_^


-Pranav

 

Thanks. I got this figured out, the BSOD Team members pointed me to the right track in another thread.

The culprit is tap0901.sys, the TAP network driver for the VPN. It works perfectly up to Windows 10 build 10532, crashes in build 10547.

However, I didn't restore the earlier build 10532 because I found a bit strange workaround, after noticing a pattern in these BSODs which after reporting the first one started to occur regularly. I noticed that I got the BSOD every time when the computer was booted to the desktop but the VPN connection was not created / used until later, at 3 to 5 minutes after the boot and later. Simply like this:

• Always a BSOD:
  • Boot the computer to desktop, do not create a VPN connection until several minutes after the boot. First time establishing the VPN connection will cause the BSOD
• Never a BSOD:
  • Boot the computer to desktop, create a VPN connection immediately, within a couple of minutes after the boot. No BSOD, I can disconnect VPN and reconnect as often as I want to

After finding this out it was easy, I just made the VPN to start when Windows is started and establish a connection automatically by startup:
Attachment 39051

 

Well done finding a work around @Kari and thank you for posting it *Smile

 

Thanks Axe0.

Any insight about what's behind this workaround, or rather in my case the complete solution? How can it be possible that I never get a BSOD if the VPN is launched and connection established immediately after the boot, but I always get a BSOD when establishing a VPN connection if the first connection is made some minutes after the boot?

 

That would only be possible if we could read the dump files.

 

I think something has gone wrong I haven't posted that I'm aware of if by any chance I have it would be an error obviously on my part for which I truly apologize.

 

Pretty clear yes that something is wrong.
Normally when a VPN causes a BSOD is because it is trying to connect to the internet.