Unable to install win10 on the LP alpha

If you're having trouble with your LattePanda Alpha & Delta, here's the place to get help.
Forum rules
If you have not found a solution, post a new issue. To speed up the process please let us know:
- Have you tried the solutions listed above?
- What board are you using? Standard (2GB RAM/32GB eMMC) or Enhanced (4GB RAM/64GB eMMC)?
- Have you tried any other solutions?
- How long have you had your board for?
- When did you first boot your board?
- Did it work ok before the issue occurred or has the issue always been there?
- Use images and videos to help us understand the issue where possible

If you are seeking RMA:
- Please open a new topic rather than hijacking someone else's thread
- Mark RMA posts with [DEFECTIVE] + <helpful description of issue>. We can then approve/disapprove each request
- Completed RMA cases will be marked with [CLOSED]
You can find the RMA guide [here]

Resolved Issues
- If you manage to fix an issue, please share your solution for the good of the community. It could help someone else in future.
- If an issue is resolved the thread should be marked as [RESOLVED]. We can then sticky the thread to help people in future.
Post Reply
User avatar
TSF
Posts: 2
Joined: Tue Nov 17, 2020 9:35 pm

Wed Nov 18, 2020 11:56 am

Hi,
I received a "Lattepanda Alpha 800" 3 weeks ago and I'm trying to get it working without any success since then.


Premises:
- I always powered the board only by using the official LP power adapter and the USB type C port.
- The 3 USBs were always occupied by:
----The mouse,
----The keyboard and
----The bootable USB.
- The HDMI cable was always connected.
- I attached since the first start the 2 Wifi antennas to the LP board.
- I attached a fan to cool down a bit the nvme SSD to the power pins on the arduino side of the board (+5V and relative GND).
- The ssds used where always plugged on the M.2 M key connector.


My journey:
I made the first boot using Kali Linux Live, and everything worked fine,
so I ordered an ssd via Amazon choosing a "SAMSUNG V-NAND SSD 970evo Plus NVME M.2" of 250GB and
the Windows 10 Pro ESD key.

Once arrived, I prepared the USB drive following the instructions posted here: http://docs.lattepanda.com/content/alpha_edition/os/
downloaded this win10 image: https://www.dropbox.com/sh/d2d4xoe2nk7n ... -101-B.zip
The installation went well, but once I logged in the OS, I got a BSOD with the error defined as "DPC_WATCHDOG_VIOLATION". I rebooted many times the system without
seeing at least one time the desktop... so I concluded that the installation got corrupted in some way.

I formatted the ssd and tried again and again (maybe 8-9 times) to reinstall the OS, unsuccessfully.
I tried with 3 different USB keys with respectively:
---- Your recommended Windows 10 installation (the one in the docs),
---- Your recommended Ubuntu linux installation (again following the docs) and
---- A normal Windows 10 installation using their media creation tool to flash the USBs (https://www.microsoft.com/it-it/softwar ... /windows10).
I changed the order by the which mouse, keyboard and the bootable USB key where connected to the USBs ports.
I plugged and unplugged the ethernet cable.
I even put an additional 5V fan to cool down the ssd.
I tried also to unplug keyboard and mouse when the installation was going on.
The installation failed always in the middle of the process without any consistency giving an error about data corruption or a "DPC_WATCHDOG_VIOLATION" BSOD.

So I reflashed the bios on the board following the given instructions in your docs.
Booted up Ubuntu Live, it refused to start 1 time but in the next try started fine.
Tried 2-3 more times to install Windows 10 without again any result.
I didn't want to think that the LP board could be the problem, so I decided that maybe the ssd was failing to work properly and I changed it for an other one of
the same model.

When the new ssd arrived, after having prepared your recommended Windows 10 installation again, I tried it... and it worked!
I was excited to see finally the desktop, until I realized that the toolbar was unresponsive and the WIN button didn't worked.
After about 15 seconds I got an other BSOD with the error defined as "CRITICAL_SERVICE_FAILED"...
I never saw the desktop again since then.

I left the LP board hidden somewhere for maybe 3 days since it was getting me mad.
When returned in myself I tried again and again with different USBs,
following your Windows 10 installation and the classic Windows 10 installation process.
The results were... very unconsistent. Now on I got only Windows BSODs.
Sometimes the installation processes ended up fine, but the installed OS was corrupted, so on the first start they gave me BSOD error.
Sometimes the installation processes halted during the installation at different percentages of completion giving me various BSOD error.
I tried maybe 6 times and these are the Windows 10 BSOD error messages I got:
"KERNEL_MODE_HEAP_CORRUPTION"
"MEMORY_MANAGEMENT"
"KERNEL_SECURITY_CHECK_FAILURE"
"PAGE_FAULT_IN_NONPAGED_AREA"
"DPC_WATCHDOG_VIOLATION"
"IRQL_NOT_LESS_OR_EQUAL"


I don't know what to do now to get it work properly and I don't think that a third SSD could solve the problems I got, so I'm open to try all your ideas.
I wanted to work on a project using this board and I wanted to order others in the future if the prototype would work fine.

Thank you in advance,
for the time you spent reading this long post and
for the help you'll give me.

TSF.

User avatar
LattePanda
Site Admin
Posts: 2689
Joined: Wed Jan 20, 2016 9:09 am

Fri Nov 20, 2020 6:05 am

Hi TSF, pls use your computer to install windows system on SSD, and then plug it to LattePanda alpha to see if it works.
Enjoy Tinkering with LattePanda ! :lol:

User avatar
TSF
Posts: 2
Joined: Tue Nov 17, 2020 9:35 pm

Sun Nov 22, 2020 9:58 pm

I managed to find an other computer with a M.2 M-key connector on its motherboard and I installed the OS following your docs.

It worked fine on the computer, so I put it on the LP board and it started working fine.
But during a reboot it showed again a BSOD error: "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED"...
Then it booted fine.
Unconvinced I tested the rams on the board using the Windows Memory Diagnostic tool and it found them faulty.
Here are the logs shown in the event viewer:

Code: Select all

Log Name:      System
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          11/20/2020 12:07:58 PM
Event ID:      1102
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      PC
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5f92bc59-248f-4111-86a9-e393e12c6139}" />
    <EventID>1102</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2020-11-20T11:07:58.372311800Z" />
    <EventRecordID>1644</EventRecordID>
    <Correlation />
    <Execution ProcessID="7492" ThreadID="7496" />
    <Channel>System</Channel>
    <Computer>PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
      <LaunchType>Manual</LaunchType>
      <CompletionType>Fail</CompletionType>
      <MemorySize>8014</MemorySize>
      <TestType>10</TestType>
      <TestDuration>2424</TestDuration>
      <TestCount>12</TestCount>
      <NumPagesTested>2031695</NumPagesTested>
      <NumPagesUnTested>1720</NumPagesUnTested>
      <NumBadPages>32</NumBadPages>
      <T1NumBadPages>16</T1NumBadPages>
      <T2NumBadPages>0</T2NumBadPages>
      <T3NumBadPages>32</T3NumBadPages>
      <T4NumBadPages>32</T4NumBadPages>
      <T5NumBadPages>16</T5NumBadPages>
      <T6NumBadPages>0</T6NumBadPages>
      <T7NumBadPages>16</T7NumBadPages>
      <T8NumBadPages>0</T8NumBadPages>
      <T9NumBadPages>32</T9NumBadPages>
      <T10NumBadPages>32</T10NumBadPages>
      <T11NumBadPages>16</T11NumBadPages>
      <T12NumBadPages>0</T12NumBadPages>
      <T13NumBadPages>0</T13NumBadPages>
      <T14NumBadPages>0</T14NumBadPages>
      <T15NumBadPages>0</T15NumBadPages>
      <T16NumBadPages>0</T16NumBadPages>
    </Results>
  </UserData>
</Event>
And

Code: Select all

Log Name:      System
Source:        Microsoft-Windows-MemoryDiagnostics-Results
Date:          11/20/2020 12:07:58 PM
Event ID:      1202
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      PC
Description:
The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-MemoryDiagnostics-Results" Guid="{5f92bc59-248f-4111-86a9-e393e12c6139}" />
    <EventID>1202</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2020-11-20T11:07:58.372313800Z" />
    <EventRecordID>1645</EventRecordID>
    <Correlation />
    <Execution ProcessID="7492" ThreadID="7496" />
    <Channel>System</Channel>
    <Computer>PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <Results xmlns="http://manifests.microsoft.com/win/2005/08/windows/Reliability/Postboot/Events">
      <CompletionType>Fail</CompletionType>
    </Results>
  </UserData>
</Event>
I thought that this could explain the unconsistency of the errors it gave me:
- Live OSs and the installation USB keys worked fine because they could use the unfaulty part of ram before the faulty pages.
- The same for Windows on the SSD (after having installed it with an other computer)
- The installations on the LP board didn't work maybe because they use much more ram, ending up writing on the faulty part.
Since no one could know how the installation program fills the ram, it's possible that different installations with same parameters
end up writing on the faulty part of the ram in different ways. If the corrupted memory block is important or between two blocks of memory
the installation halts, otherwise the installed OS on the SSD will have corrupted files.

If you agree with me, I hope that this post could help someone else.

If you need that I do something else let me know.
Could I request an RMA for this board?

User avatar
LattePanda
Site Admin
Posts: 2689
Joined: Wed Jan 20, 2016 9:09 am

Wed Nov 25, 2020 2:15 am

@TSF, Pls take a short video of the booting issue and send it to techsupport@lattepanda.com to ask for a claim.
Enjoy Tinkering with LattePanda ! :lol:

Post Reply