Ask / Submit

getting blue screen of death on PC

asked 2014-10-30 22:41:42 +0200

ayush gravatar image

updated 2014-10-30 22:44:21 +0200

today i connected my jolla to my PC running windows 10 tech preview. First, it do not connect easily, this had happened in W8.1 also. either i had to try a lot, or have to disable portable drvice driver and enable the driver again. But today it had given up. The blue screen of death finally haunted my Windows PC and it shows many errors when i connected my jolla and restarted driver. The first and main error was DRIVER OVER RUN STACK. Followed by several other errors on every startup like SYSTEM THREAD EXCEPTION NOT HANDELED, . .. MEMORY MAINTENANCE ... Etc. and currently my pC state is in restart loop with BSOD showing up everytime. i tried restoring system. before that it did run for once, but when i.connected the Jolla phone, it again started looping at startup. on searching Windows help, they suggested to re install the driver. which cld only be possible once my pc start again. I know its technical preview and error might be in system, but i guess Jolla driver needs update with support to show sd card and preferably a file transfer mode.

edit retag flag offensive close delete



I think Micro$oft HATES Jolla ;-)

objectifnul ( 2014-10-30 23:39:13 +0200 )edit

Jolla does not provide a driver, it is Windows' own driver. So if it crashes it is a problem with the driver from Microsoft.

Philippe De Swert ( 2014-10-31 13:52:29 +0200 )edit

2 Answers

Sort by » oldest newest most voted

answered 2014-10-30 23:11:58 +0200

Fuzzillogic gravatar image

Jolla might be to blame for not following a standard correctly (if you can call MTP a "standard"...), but an OS, Windows in this case, should never ever crash. Given that in this case it's Microsoft's own driver and not Jolla's, it is their problem in the first place. They need to fix this first, not Jolla.

edit flag offensive delete publish link more

answered 2014-10-30 22:49:25 +0200

Keeper-of-the-Keys gravatar image

The Jolla team shouldn't have to waste their valuable time on a preview OS that is not stable and may still have plenty of changes coming where the bug may not even be theirs...

When it becomes RTM if the driver turns out to be the culprit and not W10 is when they should start looking at it...

edit flag offensive delete publish link more


how to find who is culprit. s i had problems with w8.1 too, that i had to re enable the driver, it seems driver may be buggy. its not about driver for W10 prvw.

ayush ( 2014-10-30 22:54:40 +0200 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2014-10-30 22:41:42 +0200

Seen: 177 times

Last updated: Oct 30 '14