Blue screen due Windows IoT Core 10 B+ loading - raspberry-pi3

I try to run Windows IoT Core 10 B+ over Raspberry Pi 3 B+.
The plate is new. The OS I downloaded from here: Windows IoT 10 B+, I used:
RaspberryPi 3B+ Technical Preview Build 17661
I user this manual to install the OS to teh flash.
I have 4 INCH HDMI LCD with Touch Pad connected to the plate.
For connect the LCD I was need to modify original config (g:\config.txt) file - see code below.
But the problem not in config, when I use original config, I have no device detected in Dashboard. If I use modified config, I have monitor working, but have blue screen.
I have follow drives after FFU uploading:
USB Drive F:
EFIESP G:
MainOS H:
Data J:
I searched for logs and important files, and didn't found much:
j:\FirstBoot.Complete
Some DUMP like files, however, it is unable to open it in Visual Studio as DUMP files:
j:\DUMP0c15.tmp
j:\DUMP0c35.tmp
j:\DedicatedDumpFile.sys
Follow directories, however it are empty:
j:\Logfiles\WMI\RtBackup\
j:\CrashDump\
h:\Windows\tracing\
h:\Windows\LiveKernelReports\
h:\Windows\system32\winevt\Logs\
The modified content of: g:\config.txt:
init_uart_clock=16000000 # Set UART clock to 16Mhz
kernel_old=1 # Load kernel.img at physical memory address 0x0
safe_mode_gpio=8 # A temp firmware limitation workaround
max_usb_current=1 # Enable maximum usb current
gpu_mem=32 # Set VC to 32MB, ARM DRAM to (1008-32)MB
hdmi_force_hotplug=1 # Enable HDMI display even if it is not connected (640x480)
core_freq=250 # Frequency of GPU processor core in MHz
framebuffer_ignore_alpha=1 # Ignore the alpha channel for Windows.
framebuffer_swap=1 # Set the frame buffer to be Windows BGR compatible.
disable_overscan=1 # Disable overscan
hdmi_group=2 # Use VESA Display Mode Timing over CEA
hdmi_mode=87 # 5 inch screen
hdmi_cvt 480 800 60 6 0 0 0 # 5 inch screen
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
display_rotate=3
This is screenshot of blue screen:
As I see, there is notification about: BAD_SYSTEM_CONFIG_INFO
I read troubleshooting page and some other information.
I have follow questions:
What are the drives responsible for: G:, F:, J:, H: ?
Where can I find boot logs in the Windows IoT file system?
Where can I find more documentation about Windows IoT OS architecture and its system's directory tree?
What can be the problem?
PS: I have successful expirianse to run Windows IoT Core 10 on Raspberry Pi 3.

Please note there is no official release version of Windows IoT Core for Raspberry Pi 3B+. There is only one insider preview version 17761 suppose to working on 3B+. So use the image you download without any modification to see if it works.
But th eproblem not in config, when I use original config, I have to
device detected in Dashboard. If I use modified config, I have monitor
working, but have blue screen.
If you mean you can't detected the device in Dashboard please connect a display via HDMI to see the system boot up or not. For me "BAD_SYSTEM_CONFIG_INFO" seems due to you change the default settings so cause the system boot fails.
What are the drives responsible for: G:, F:, J:, H: ?
MainOS: OS and OEM-preloaded apps.
EFI: Fixed-size partition with the boot manager, boot configuration database.
Data: User data partition, user registry hives, apps, apps data.
More detailed information please refer to "IoT Device Layout".
Where can I find boot logs in the Windows IoT file system?
You may need use WinDbg to get boot information when the system can boot up successfully.
Where can I find more documentation about Windows IoT OS architecture
and its system's directory tree?
It seem no such dedicated document. But you can reference the following documents:
"Windows kernel", "Architecture of Windows 10", "An overview of Windows 10 IoT", "Windows file sharing"
Windows IoT Core is a Windows 10 edition for IoT. It has many commonalities with Windows 10 other editions and has some limitations due to its device limited resource. So you can compare Windows 10 IoT Core and a full version Windows 10 like Windows 10 IoT Enterprise to understand it.

Related

Windows IoT Core flashing unsuccessful unless Windows Defender 'Real-time protection' is disabled

Unless I disable Windows Defender 'Real-time protection', I get a 'Flashing Unsuccessful' error message while trying to setup a new Raspberry Pi device using Windows IoT Core Dashboard.
This is how my advanced settings are configured.
The OS on the machine on which I am having this problem is Microsoft Windows 10 Pro - 10.0.17134 Build 17134.
And this is the card reader that I am using. It is the standard one that comes built in to the Dell XPS tower (not an external USB reader for example).
I have tried setting up exclusions etc. but have not so far found one that will work.
What exclusions should I create so that I can leave 'Real-time' protection running?

Important window drivers regarding audio are missing and Audio not working

I did something crazy. While installing or removing some junk (softwares) from my pc and then suddenly i noticed that red cross sign appeared on my volume icon and no sound was there. when i checked the device manager following drivers had a small yellow triangular mark beneath them and audio was not working.
1, Microsoft Streaming Clock Proxy,
2, Microsoft Streaming Quality Manager Proxy,
3, Microsoft Streaming Service Proxy,
4, Microsoft Streaming Tee/Sink-to-Sink Converter,
5, Microsoft Streaming Tee/Sink-to-Sink Converter, (no that's not a misprint, That one was listed twice)
6, Microsoft Trusted Audio Drivers.
7, NVIDIA High Definition Audio.
8, Realtek High Definition Audio.
I am using windows 10 and my hardware is Dell optiplex 7010, Corei7 3.3Ghz, 8gb Ram, 500 gb Hard drive , 2gb Nvidia Geforce 210 Graphics card.
Thank you ever so much for sharing any knowledge you have about this to fix my pretty dumb mistake.
Hi, I Am using Sony Vaio SVS1512DCXB, Windows 10 Home
I had the same problem
Device SW{97ebaacc-95bd-11d0-a3ea-00a0c9223196}{53172480-4791-11D0-A5D6-28DB04C10000} had a problem starting.
Driver Name: ksfilter.inf
Class Guid: {4d36e96c-e325-11ce-bfc1-08002be10318}
Service: MSPCLOCK
Lower Filters:
Upper Filters:
Problem: 0x27
Problem Status: 0xC0000034
Driver Management has concluded the process to add Service HdAudAddService for Device Instance ID HDAUDIO\FUNC_01&VEN_8086&DEV_2806&SUBSYS_104D6500&REV_1000\4&ED7485A&0&0301 with the following status: 0.
Try this
Update all drivers
and
In the command line, as administrator, run the command:
c:\>sc config MSPCLOCK start= demand
and
Remove all traces of antivirus, such as kaspersky, using kavremvr.exe from https://media.kaspersky.com/utilities/ConsumerUtilities/kavremvr.exe

Deploy W10 on HP ProDesk 600 G2

I'm deploying windows 10 via SCCM on new computer it loads into PXE then reboot.. When I try ipconfig I'm not getting ip so I though it will be problem with NIC.. so I tried to load all available drivers for this desktop and still not working.. I'm out of ideas..
Thanks
"so I tried to load all available drivers for this desktop and still not working.. "
Did you mean that you add all drivers of this model into the boot image which associated with the OSD task sequence? If so, that is not recommended by MS. You should only import the actually required NIC drivers or storage drivers into the boot images(both x86 and x64).
Another important point here is you should add the NIC drivers match the boot image version instead of the OS version you are trying to deploy. For example, add NIC drivers for win10 to the boot image 10.x.xxxxx (which is from the ADK 10 RTM or later).

how to get target device's hardware details to work with windows 10 IoT

I have a device and i want to integrate it with Windows 10 IoT. Before that i need to analyze the hardware components of the device. In Windows 7 we have WINPE tap.exe which will generate a dism.pmq with all the hardware device information.
I tried searching but i could not find anything. Is there any way to find the hardware details of the device for Windows 10 IoT environment?
I need these information so that i can create my bsp.config.xml file with the required info.

How to deploy Windows 10 IoT (Rasp Pi image) as a Virtual Machine

Is it possible to deploy Windows 10 IoT (Rasp Pi image) as a Virtual Machine using VirtualBox or VMWare Player?
I need for a testing lab a network of three to five Windows 10 IoT devices. A virtual cluster would be perfect. My Google- and Bing-based research failed.
The problem could be either the non-ISO disk image file format or the non-x86 architecture of the operating system, couldn't it?
The easiest way I found is downloading Windows 10 IoT Core for MinnowBoard MAX
(here: http://go.microsoft.com/fwlink/?LinkId=691712). This MinnowBoard is x86-based and the image comes in a .iso file. I know the OP was specific about being a Rasp Pi image, but I don't really see the difference if we're just trying to use a hypervisor. Afterwards, you may just follow this tutorial: http://www.newventuresoftware.com/blog/running-windows-10-iot-core-in-a-virtual-machine
It's very simple and straight-forward, and it works with VirtualBox.
Based on #makoshichi's links here's the steps that worked for me:
Download MinnowBoard MAX IoT Core from microsoft, and install
Run ImgMount tool as Admin to mount "C:\Program Files (x86)\Microsoft IoT\FFU\MinnowBoardMax\flash.ffu"
Detach the VHD from Disk Management (in Computer Management), move the resultant .vhd file (that it informs you of on detach) to a location of your choice
Create, but don't launch, a new Virtual Machine in VirtualBox (expert mode) as Windows 32-bit, using an "existing virtual hard disk file" - the one you just moved
Goto device Settings->System and click Enable EFI (special OSes only)
Goto device Settings->Network and select Bridged Adapater
That's it - Run your virtual machine and be a happy Thing of the Internet, or something like that.
This is my short version of this wonderful post by Yavor Ivanov.
The QEMU emulator may do it, it will boot the image file directly. you may need to expand the ffu with dism first.
You don't have to fully install w10 preview: just boot the W10 real or virtual DVD and select to open a cmd box, from there you can run the updated dism command.iot w10 have no (direct) GUI, you must talk to the device via winrm and powershell
There is a good startup for you on
sourceforge
fc
https://github.com/0xabu/qemu/tree/raspi is a working way to run Windows 10 IoT on Qemu. It fully emulates a RPi2, except USB
Hi you could use the Raspberry Pi Simulator https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-raspberry-pi-web-simulator-get-started

Resources