4/5/2017 Crash Windows 10 x64 Anniversary Update Issue #10 leapdroid-team/leapdroid GitHub

Features Business Explore Pricing This repository Search Sign in or Sign up

leapdroidteam / leapdroid Watch 13 Star 38 Fork 21

Code Issues 58 Pull requests 0 Projects 0 Wiki Pulse Graphs

Crash Windows 10 x64 Anniversary Update #10 New issue

Open Mendim opened this issue on Aug 5, 2016 21 comments

Mendim commented on Aug 5, 2016 Assignees

LeapdroidDev99
Hello.i got windows crash and restart on Windows 10 x64 Anniversary Update
Can you confirm this.and try to fix Labels

None yet

MrMyth commented on Aug 6, 2016 edited

Projects

Windows 10 x64 Anniversary Update. I don't get crash of the system. The emulator works correctly. None yet

My Notebook: Milestone

CPU Central Intel core i3 3110M @ 2.40 GHz Ivy bridge Technology 22 nm No milestone

RAM 4.00 GB 1channel DDR3 @ 798 MHz (11111128)

Motherboard Fujitsu FJNBB1D (CPU socket U3E1) 8 participants
Graphics Generic PnP Monitor (1366x768@60Hz) Intel HD 4000 (Fujitsu)
1023 MB NVIDIA GeForce GT 620M (Fujitsu)
465GB Seagate ST9500325AS (SATA)
High Definition Audio Realtek

Mendim commented on Aug 8, 2016

If we disable virtual device support on bios.it works.if we enable it not work.

leapdroid commented on Aug 10, 2016 Contributor

"Disable virtual device support on bios" Do you mean disabling Intel VTx?

LeapdroidDev99 commented on Aug 11, 2016

Could you please clarify:

1. What is Virtual Device support?

2. The issue is actually:
2.a You installed leapdroid to Windows 10 anniversary update but found it not working.
2.b You installed leapdroid to Windows 10 (old version) and then upgraded to Windows 10
anniversary update, but found it not working? Did it work before upgrading Windows 10?
2.c Like 2.b. Even if you uninstall and reinstall leapdroid to upgraded Windows 10, you still
cannot get it work?
2.d or anything else, could you please describe a bit more? Such as upgrading from Windows 7
to Windows 10.....
3. Could it be possible to set up a remote access to your computer?

https://github.com/leapdroid-team/leapdroid/issues/10 1/4
4/5/2017 Crash Windows 10 x64 Anniversary Update Issue #10 leapdroid-team/leapdroid GitHub

mbsSe commented on Aug 12, 2016

I also have this problem. Had LeapDroid installed and updated to Anniversary Update (from Windows
10 1511), starting LeapDroid and it crashed, IRQL_NOT_LESS_OR_EQUAL.
Latest BIOS, and drivers. Did uninstall LeapDroid, so I could install the latest version. But when I
started the installation, Windows crashed with the same error, IRQL_NOT_LESS_OR_EQUAL

kinahwatts commented on Sep 8, 2016

I was unable to properly install Leapdroid. And I'm thinking that it might be related to the driver
signing changes in the Windows 10 Anniversary Update (version 1607). I've explained my issue in
detail in #30.

LeapdroidDev99 was assigned by leapdroid on Sep 12, 2016

LeapdroidDev99 commented on Sep 15, 2016

@mbsSe Hi, we really cannot reproduce the issue here. We do tried with several boxes at hand and
they are upgraded to Windows 10 1607 without causing problem.
Is it possible to send us your crash dump file? Depending on your Windows crash dump settings, it
might be placed at C:\Windows\memory.dmp or C:\Windows\Minidump\xxxxx.dmp. If there are
multiple files, you basically can determine the target file by looking at when the file is created.

mbsSe commented on Sep 16, 2016

@LeapdroidDev99 Sorry, I cleaned out my crash dumps a week ago. And when I try to install
LeapDroid today (hope to get a new crash dump), the installation starts, but just die's. nothing
happens. Can I find a installationlogfile somewhere?

mbsSe commented on Sep 16, 2016

Hi @LeapdroidDev99, now I have crash dump files. Where do I send/upload them (1.32GB + 416kB)?

LeapdroidDev99 commented on Sep 16, 2016

Thanks indeed! This is pretty big. Could you help to upload to this location? I have created a shared
drive on google as below:
https://drive.google.com/drive/folders/0B3QfdHIyAqyzc0huYUpNRkpoeVk?usp=sharing

mbsSe commented on Sep 16, 2016

@LeapdroidDev99 Now the files are uploaded. Please, remove them from drive.

LeapdroidDev99 commented on Sep 16, 2016

Thanks for your help! We will take a look now.

LeapdroidDev99 commented on Sep 16, 2016

@mbsSe After examining the crash dump, the only useful information is memory corruption
happened in Windows kernel space. But the component that triggered this bugcheck is a module

https://github.com/leapdroid-team/leapdroid/issues/10 2/4
4/5/2017 Crash Windows 10 x64 Anniversary Update Issue #10 leapdroid-team/leapdroid GitHub
shipped by Microsoft. It is hard to to debug, we probably will need to find a way to reproduce the
issue. I was suspect some kind of messing up as a result of Windows upgrade. Sometime app with a
kernel driver does not work cross a major OS release upgrade.

mbsSe commented on Sep 18, 2016

Ok, thanks for letting me now!

I did go around the problem for myself yesterday and installed LeapDroid in Windows 10 AU running
on HyperV, so I am about to agree it must be a result of the upgrade Windows 10 AU on my physical
computer.

sicut commented on Sep 21, 2016

Hey there,
I just had exactly the same problem after installing the Win 10 Anniversary Update on my Surface Pro
4 (m3).
So after the update the old installation of Leapdroid gave me BSODs. Iirc, it only said it encountered
an error and has to restart (no stop code) while building the crash dump.

After some fiddling around with HyperV preferences to no avail, I downloaded the lastest Leapdroid
and tried to install that. But after telling the setup which camera stream to record (that is a part of
your installation routine now, right?), I get a BSOD with IRQL_NOT_LESS_OR_EQUAL.

The installation seems to be half way done because I have the installation folder pretty populated
and something must be running already, since I can't delete the folder again without using Windows
safe mode.

I will try the BIOS/UEFI suggetions posted here as well and will report back.

Pls let me know if I can provide more help to find the problem.

LeapdroidDev99 commented on Sep 21, 2016

Hi, thanks for the feedback and the offer to help. We also want to fix this issue and we even bought a
SF Pro 4 (but not the core m model), but failed to reproduce the issue (we also got the upgrade last
weekend).
It would be great that we can take a remote access. Is it possible to do a team viewer?
I can give a short explanation: the camera stuffs is newly added. So this is something we do not
expect. We found that this would appear on boxes with both front and rear cameras. But it happened
not to appear on our test box. We will fix it later.

pascalvanderheiden commented on Sep 22, 2016

Hi, I had the same problem and this was really annoying. But I have a solution: in windows search box
just type "optionalfeatures" and uncheck the HyperV features. after that it works.

sicut commented on Sep 25, 2016 edited

Hey, wow, thank you, pascalvanderheiden!

That really did the job. I assume the update rolled back any HyperV related preferences, so we have
to deactivate everything again. It took some restarts and then HyperV was completely gone again
and after that I had no problem installing and running Leapdroid.

@LeapdroidDev99: Sorry for not coming back to you immediately, I didn't have much time the last
days. But since pascalvanderheiden helped to solve my problem, you won't probably need more from
me, right? I actually didn't think of looking for HyperV in Windows features again, since I didn't know

https://github.com/leapdroid-team/leapdroid/issues/10 3/4
4/5/2017 Crash Windows 10 x64 Anniversary Update Issue #10 leapdroid-team/leapdroid GitHub
that it would silently reinstall and reactivate everything.
But I should have known better when it comes to Microsoft's ridiculous update policies, I guess.

pascalvanderheiden commented on Sep 25, 2016

Glad to help others. I really love leapdriod. Keep up the good work.

LeapdroidDev99 commented on Sep 26, 2016

We are so happy that you guys figured out a way to solve the issue. Great! And the information is
helpful to us too. We will try hyperV case on our own box. In theory, we should be able to run with
HyperV (but with greatly decreased performance). We hope at least we can still make this case
work (though not optimized). At least, we will put a new trouble shooting on our webpage.

LeapdroidDev99 commented on Sep 26, 2016

Hi, Guys,
We've tried this. It seems from Windows 10 1607, HyperV and VBox together will produce a BSOD. I
found a similar thread on vbox forom. https://forums.virtualbox.org/viewtopic.php?
f=6&t=79028#p368859
Probably we will need either MS or Oracle to fix this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

2017 GitHub, Inc. Terms Privacy Security Status Help Contact GitHub API Training Shop Blog About

https://github.com/leapdroid-team/leapdroid/issues/10 4/4