After powering on PC daily, its W10 seems to always seem to show :( about it running into a problem...

Paul wrote:

For an Upgrade Install, you can just mount the ISO.

I tried this first for kicks, but got its "Windows 10 installation has failed". So I gave up and did a clean
installation from my 64 GB PNY USB flash stick. It worked. I am getting its (lat/new)est updartes and drivers.
After that, things should be stable? I will have to wait! I mostly used its defaults.


With the current ISO image being so big now, it no longer
fits on a single-layer DVD. You would need a dual layer
DVD, even if you had a USB DVD drive to use with the NUC.
I only have one blank left of those, and I'm not wasting
it on Windows. (There are several versions of 1809 media,
and if the size annoys you, you can use Heidoc to get one
which is 1GB smaller than the current one.)

Ditto. I also noticed DVDs aren't that reliable like not all can be read in some drives. Some can't handle +, -,
DLs, etc. Ugh. Also, slow slow!


But for USB keys, the image is still small enough that the program
I referred to in my other posting, will work with the 5GB image.
You can use this method for your USB key "Clean Install", where
the USB key will boot in either legacy or UEFI mode.

The first link is the README, the second link the download.

http://web.archive.org/web/201201022...usbdvd_dwnTool

http://web.archive.org/web/201110052...B-DVD-tool.exe

If you operate that tool from a 64-bit OS, it can make
32 bit or 64 bit USB sticks from
32 bit ISO or 64 bit ISO files.

If you want to do a UEFI install, the stick must be booted
in UEFI mode. This is easiest to see and select, by using
the "popup boot key" when booting the NUC. There will be
two entries for the USB key in the popup boot, and one entry
will have the word "UEFI" by it, as a key to selecting the
correct key boot method. When the NUC is POSTing, try pressing
the F10 key, as shown here.

https://01.org/projectceladon/sites/...ges/splash.jpg

The "Windows7-USB-DVD-tool.exe" will take the ISO and put
it on a USB stick for you. Example here.

https://i.postimg.cc/x1TddGrX/sample...rom-an-ISO.gif

And if that doesn't work, you can always try one of the other
ISO to USB key softwares. One problem with those, is they're
usually geared for Linux ISOs, rather than Windows.

UEFI boot to the flash stick worked. It is clean installed and being updated as I type this post.

Now, the question is that NUC still going to instability problems like very slow start/boot ups. :/

To be continued...
--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:

UEFI boot to the flash stick worked. It is clean installed and being updated as I type this post.

Now, the question is that NUC still going to instability problems like very slow start/boot ups. :/

To be continued...

Oops. https://i.imgur.com/4IuCXge.jpg (volume 2 is the default new clean W10 and volume 5 is the
old 32 GB EMMC drive with "broken" W10) -- I need to figure how to make NUC PC just boot to the new
Windows. I'll just use BIOS to boot to the old "broken" W10 v1803 when needed. I don't want to
confuse the client!

--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
Ant wrote:

UEFI boot to the flash stick worked. It is clean installed and being updated as I type this post.

Now, the question is that NUC still going to instability problems like very slow start/boot ups. :/

To be continued...

Oops. https://i.imgur.com/4IuCXge.jpg (volume 2 is the default new clean W10 and volume 5 is the
old 32 GB EMMC drive with "broken" W10) -- I need to figure how to make NUC PC just boot to the new
Windows. I'll just use BIOS to boot to the old "broken" W10 v1803 when needed. I don't want to
confuse the client!


You would need to enter the BIOS and set the boot order.
On the assumption the storage media would not be constantly changing.

*******

The labeling that Windows uses can be annoying. You could look up
some articles on BCDEDIT and find a command to assign a label
to each volume.

In diskpart, you might try

list volumes
exit

to get some idea of the volumes present. I think my dual-boot
Win10/Win10 insider hard drive is "volume2 volume4". You'll need
to pick names that are relevant to the owner, for the volumes.
And the volume "label" in the partition sense, is different
than the name in BCDEDIT. You can name the SSD partition "SSD"
for example, and BCDEDIT will just ignore it and keep calling
it Volume 5. They call it a "description" here.

https://docs.microsoft.com/en-us/win...f-a-boot-entry

bcdedit /set {802d5e32-0784-11da-bd33-000476eba25f} description "Windows 10 NullModem"

Typing just BCDEDIT will display some identifiers and
volume letters. The mountvol can give some info too,
except it only gives info on things that actually
mount (the smaller 500MB volumes don't normally mount
because they're 0x27 hidden NTFS instead of regular 0x07
visible NTFS).

bcdedit
mountvol

Each disk can have its own BCD file. The BCD can be dual-boot inside.
It means you can set the boot order in the BIOS to make either
drive first, and still be able to reach both copies of Windows.

But in doing that, you also have to consider the health of the
drives. If you only put one item in the BCD boot menu, an item
that points to its own drive, it makes the drive a "self contained
fault group". If you put both drives in the menu like that,
if one drive has a total hardware failure, it might hold up
boot. I don't think the BCD boot menu is tolerant of hardware
failures and will just "ignore" broken ones.

But if another Windows version upgrade comes in, it can "mess up"
all of your tidy work and planning.

So while I can attempt to show you some of the possibilities
for control, they won't stay there forever. One day the
customer can be seeing this in the BCD menu

Win10 on old eMMC
Win10 on new SSC

and the next day the customer could see

Windows 10 on Volume2
Windows 10 on Volume5

and that sort of thing happens if the OS got upgraded.
There is really nothing in Windows 10 that is guaranteed
to stay nailed down for very long. It's all "deck furniture
you can burn to keep warm".

Paul

Paul wrote:

Oops. https://i.imgur.com/4IuCXge.jpg (volume 2 is the default new clean W10 and volume 5 is the
old 32 GB EMMC drive with "broken" W10) -- I need to figure how to make NUC PC just boot to the new
Windows. I'll just use BIOS to boot to the old "broken" W10 v1803 when needed. I don't want to
confuse the client!


You would need to enter the BIOS and set the boot order.
On the assumption the storage media would not be constantly changing.

*******

The labeling that Windows uses can be annoying. You could look up
some articles on BCDEDIT and find a command to assign a label
to each volume.

In diskpart, you might try

list volumes
exit

to get some idea of the volumes present. I think my dual-boot
Win10/Win10 insider hard drive is "volume2 volume4". You'll need
to pick names that are relevant to the owner, for the volumes.
And the volume "label" in the partition sense, is different
than the name in BCDEDIT. You can name the SSD partition "SSD"
for example, and BCDEDIT will just ignore it and keep calling
it Volume 5. They call it a "description" here.

https://docs.microsoft.com/en-us/win...f-a-boot-entry

bcdedit /set {802d5e32-0784-11da-bd33-000476eba25f} description "Windows 10 NullModem"

Typing just BCDEDIT will display some identifiers and
volume letters. The mountvol can give some info too,
except it only gives info on things that actually
mount (the smaller 500MB volumes don't normally mount
because they're 0x27 hidden NTFS instead of regular 0x07
visible NTFS).

bcdedit
mountvol

Each disk can have its own BCD file. The BCD can be dual-boot inside.
It means you can set the boot order in the BIOS to make either
drive first, and still be able to reach both copies of Windows.

But in doing that, you also have to consider the health of the
drives. If you only put one item in the BCD boot menu, an item
that points to its own drive, it makes the drive a "self contained
fault group". If you put both drives in the menu like that,
if one drive has a total hardware failure, it might hold up
boot. I don't think the BCD boot menu is tolerant of hardware
failures and will just "ignore" broken ones.

But if another Windows version upgrade comes in, it can "mess up"
all of your tidy work and planning.

So while I can attempt to show you some of the possibilities
for control, they won't stay there forever. One day the
customer can be seeing this in the BCD menu

Win10 on old eMMC
Win10 on new SSC

and the next day the customer could see

Windows 10 on Volume2
Windows 10 on Volume5

and that sort of thing happens if the OS got upgraded.
There is really nothing in Windows 10 that is guaranteed
to stay nailed down for very long. It's all "deck furniture
you can burn to keep warm".

Ugh, that's annoying. I used admin level cmd.exe to use bcdedit to rename the descriptions. That
was confusing and didn't work when I use {GUID}, but it worked for {current}! Weird. I also screwed
up earlier when I used mconfig.exe to remove the old W19;s boiot menu. I thought it would go back
to the old ways where I could boot a drive from BIOS. It seems like W10's changed the boot manager
to boot one of those drives. Argh. Oh well. MS is really making things confusing and difficult!

--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:

It seems like W10's changed the boot manager
to boot one of those drives. Argh. Oh well.
MS is really making things confusing and difficult!

At least there are lots of BCDEDIT articles to help
you program things.

If you use EasyBCD, you might need the latest version
to get good UEFI support. The version I had, couldn't
"see" a UEFI install.

It's just as well to learn how to use BCDEDIT, since
there will be times you are "repairing" an OS in its
offline state, and EasyBCD won't be available. You can
edit the menu from an emergency boot CD or from the
installer DVD.

Paul

Ant wrote:
....
UEFI boot to the flash stick worked. It is clean installed and being updated as I type this post.

Now, the question is that NUC still going to instability problems like very slow start/boot ups. :/

To be continued...

After about a couple hours, I came back and saw Intel NUC PC's blinking orange/amber power light
meaning asleep. I woke it up and logged in just fine. I decided to reboot it, but it got stuck
right after Intel NUC boot screen with a blank black screen (still have video signal). That's a new
one. Keyboard's lock lights still toggled so it is not frozen. I held down the PC's power button to
force a shut down and then powered it back on without any problems (fast boot ups for both drives'
W10). No scanning and repairing this time. Maybe because it hasn't started loading the OS yet since
it couldn't even show its boot manager?

A couple online strangers suggested to try disabling W10 fast start up, so I did that. I waited for
PC to sleep with its blinking amber/orange light. I was able to wake it up and use it. I did a
reboot back, saw the boot manager, manually selected the old W10 drive, it rebooted to load it (not
sure why it needs to reboot but it does), but got stuck at the black Intel NUC screen with its
animated spinner for a few minutes. I wasn't paying attention, but it rebooted again back to my
clean W10 drive. Ha. So, I did another couple reboots to the old one. Things seem OK.

There's seems to be a problem in starting up quickly correctly once in a while even if fast start
up is disabled. I need to run tests.

--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:


There's seems to be a problem in starting up quickly correctly once in a while even if fast start
up is disabled. I need to run tests.


Fast startup avoids kernel hibernation.

If the kernel is hibernated, that's stored in a file.
If the loader checks the file and finds the signature
is bad, then it's going to have to boot the regular way.

Disabling fast start means the OS loads the hard way
(loads a kernel executable and driver files and so on).
Then the user space loads after that.

If the storage on the machine isn't reliably,
you need to figure out why that is.

*******

When you dual-boot like you are doing presently, if
you select the "non-default" entry, the "second" item
in the list, it does a hardware restart before booting
the second item. This extends the boot time, as you would
expect. I have that problem here, on my dual boot Win10
Insider HDD that has two OS images on it.

It seems to assume all the OSes are fast boot, when it could
check and realize they aren't, and no hardware restart
would then be required.

Paul

Paul wrote:
Ant wrote:


There's seems to be a problem in starting up quickly correctly once in a while even if fast start
up is disabled. I need to run tests.


Fast startup avoids kernel hibernation.

If the kernel is hibernated, that's stored in a file.
If the loader checks the file and finds the signature
is bad, then it's going to have to boot the regular way.

Disabling fast start means the OS loads the hard way
(loads a kernel executable and driver files and so on).
Then the user space loads after that.

If the storage on the machine isn't reliably,
you need to figure out why that is.

I wonder what good software testers to use to test both flash drives.
--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Paul wrote:
Ant wrote:


There's seems to be a problem in starting up quickly correctly once in a while even if fast start
up is disabled. I need to run tests.


Fast startup avoids kernel hibernation.

If the kernel is hibernated, that's stored in a file.
If the loader checks the file and finds the signature
is bad, then it's going to have to boot the regular way.

Disabling fast start means the OS loads the hard way
(loads a kernel executable and driver files and so on).
Then the user space loads after that.

If the storage on the machine isn't reliably,
you need to figure out why that is.

I just woke this PC up, logged in, and manual rebooted. It got stuck at its Intel NUC, with its
animating spinner screen, again. I waited a few minutes and then it finally autobooted to the clean
installed W10 login. I logged in and looked around, and then noticed this new W10 was acting weird!
I couldn't type in desktop like in Contana. Start Menu was mostly black. I tried locking screen to
login screen. And then, noticed my login was missing so I had no way back in! I was able to click
on shutdown so I did that. Video signal lost, but PC still stayed on with its blue power light.
Once in wa while, I still seee it blue disk activity light come on quickly. It still won't even
shut down to power off! Argh.

OK, something is screwy now even with a new clean W10 installation. I think I am going to try
upgrading its BIOS later from
https://downloadcenter.intel.com/dow...?product=98414 with boot
up's F7 method to read from an USB flash stick. It might help?
--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
Paul wrote:
Ant wrote:

There's seems to be a problem in starting up quickly correctly once in a while even if fast start
up is disabled. I need to run tests.


Fast startup avoids kernel hibernation.

If the kernel is hibernated, that's stored in a file.
If the loader checks the file and finds the signature
is bad, then it's going to have to boot the regular way.

Disabling fast start means the OS loads the hard way
(loads a kernel executable and driver files and so on).
Then the user space loads after that.

If the storage on the machine isn't reliably,
you need to figure out why that is.

I wonder what good software testers to use to test both flash drives.

I would do a series of tests.

1) memtest (mainly detects stuck-at memory faults
2) Prime95 torture test (CPU and transient memory faults)
3) some kinda disk test

For the disk test, you have to consider whether to do
destructive testing, or a simpler test case.

For example, I could see running hashdeep on the drive that
isn't booted as the OS. And run it on the same file tree
twice and see if the checksums are the same each time. That
would be intended to detect storage that "degrades" over time.

Doing write tests, uses up some of the write cycles of the
devices. It's also destructive, unless you're writing back
to the original locations using the original data. Some tests do
it that way. And even then, if the test is "successful", it's
going to corrupt something as proof of a hardware problem.

If you use Hashdeep on a Windows 10 volume, you have to
consult an extensive list of "exclusion" parameters. You
have to tell Hashdeep to not access Reparse Points. And
you have to tell it to avoid the left-over "named pipes"
Microsoft leaves on a C: drive. They cause hashdeep to
"freeze" when doing I/O on the named pipe (it opens the pipe
for read, and there's no writer on the other end of the pipe,
so the thread freezes and doesn't come back).

Once you've done that, it depends on how much work you want
to do. If you use -j 1 (i.e. one thread which reads and
calculates MD5SUM perhaps), then the order the file tree is
processed is the same each time. if you used -j 4 (four
checksum threads), then the filenames are dumped into the
file out-of-order (different on each run). Then, you have
to sort the filenames in the output file list.

But other than that, it's a relatively simple test, and
you can reboot and retest the "data" drive, while ignoring
the C: booted at the time. You don't want to test C:
that way, because too many files are open for write.
The machine would be doing a sleep study, collecting
various EtW traces, and the end result is the file
system never "rests". Whereas, the drive which isn't
the OS drive, is relatively stable. The Flash drives
should no longer be updating "Last Accessed", as that
wastes NAND write cycles. The "data" drive should give
the same checksums, after every reboot and test.

(Starts immediate download...)

https://codeload.github.com/jessek/h...ip/release-4.4

hashdeep -C MD5 ...

You will need a series of additional parameters to successfully
handle Win10 drives without hanging behaviors being in evidence.
Step over reparse points. Avoid the left-over named pipes in
a certain crypto directory (that strictly speaking should have
been erased at shutdown). There was no need for those named
pipes to be "persistent".

Paul

Ant wrote:

I just woke this PC up, logged in, and manual rebooted. It got stuck at its Intel NUC, with its
animating spinner screen, again. I waited a few minutes and then it finally autobooted to the clean
installed W10 login. I logged in and looked around, and then noticed this new W10 was acting weird!
I couldn't type in desktop like in Contana. Start Menu was mostly black. I tried locking screen to
login screen. And then, noticed my login was missing so I had no way back in! I was able to click
on shutdown so I did that. Video signal lost, but PC still stayed on with its blue power light.
Once in wa while, I still seee it blue disk activity light come on quickly. It still won't even
shut down to power off! Argh.

OK, something is screwy now even with a new clean W10 installation. I think I am going to try
upgrading its BIOS later from
https://downloadcenter.intel.com/dow...?product=98414 with boot
up's F7 method to read from an USB flash stick. It might help?

If you're "lucky", you'll brick it during the BIOS flash
and then you can give it back to the customer :-/

Think carefully about your next step. This is a "sick patient".
What is your Plan B plan for this hardware ? If the NUC is
ruined, is the warranty still good ?

Paul

Paul wrote:
Ant wrote:

I just woke this PC up, logged in, and manual rebooted. It got stuck at its Intel NUC, with its
animating spinner screen, again. I waited a few minutes and then it finally autobooted to the clean
installed W10 login. I logged in and looked around, and then noticed this new W10 was acting weird!
I couldn't type in desktop like in Contana. Start Menu was mostly black. I tried locking screen to
login screen. And then, noticed my login was missing so I had no way back in! I was able to click
on shutdown so I did that. Video signal lost, but PC still stayed on with its blue power light.
Once in wa while, I still seee it blue disk activity light come on quickly. It still won't even
shut down to power off! Argh.

OK, something is screwy now even with a new clean W10 installation. I think I am going to try
upgrading its BIOS later from
https://downloadcenter.intel.com/dow...?product=98414 with boot
up's F7 method to read from an USB flash stick. It might help?

If you're "lucky", you'll brick it during the BIOS flash
and then you can give it back to the customer :-/

Think carefully about your next step. This is a "sick patient".
What is your Plan B plan for this hardware ? If the NUC is
ruined, is the warranty still good ?

Ah, good idea. I will let him know if he want to risk it. FYI, Prime95's 15 minutes run and
Memtest86's few minutes run seem to be OK so far. I will leave memtest86 running all night long
when I sleep.

--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Paul wrote:
Ant wrote:

I just woke this PC up, logged in, and manual rebooted. It got stuck
at its Intel NUC, with its animating spinner screen, again. I waited a
few minutes and then it finally autobooted to the clean installed W10
login. I logged in and looked around, and then noticed this new W10
was acting weird! I couldn't type in desktop like in Contana. Start
Menu was mostly black. I tried locking screen to login screen. And
then, noticed my login was missing so I had no way back in! I was able
to click on shutdown so I did that. Video signal lost, but PC still
stayed on with its blue power light. Once in wa while, I still seee it
blue disk activity light come on quickly. It still won't even shut
down to power off! Argh.

OK, something is screwy now even with a new clean W10 installation.
I think I am going to try upgrading its BIOS later from
https://downloadcenter.intel.com/dow...?product=98414
with boot up's F7 method to read from an USB flash stick. It might help?

If you're "lucky", you'll brick it during the BIOS flash
and then you can give it back to the customer :-/

Flashed BIOS countless times on hardware and never had an issue, but I
might have been lucky. Often upgrade fixed wonky issues with systems.
One prime example is this system's MSI mobo that I could not get into
BIOS with a mechanical keyboard had to use to swap out to a cheapo
rubber dome one until patched. Turns out the patch fixed a issue with
performance gaming keyboards. Anyway I would read the patch update
carefully first. Unless it seems to address your issue I wouldn't do it.
As Paul suggests the issue could be hardware and unrelated to your
actions and you get the blame.


Think carefully about your next step. This is a "sick patient".
What is your Plan B plan for this hardware ? If the NUC is
ruined, is the warranty still good ?

Yeah if it still under warranty let the mfgr fool with it. Else if
warranty has expired and the client understands the risk, what the hell,
these mini's are basically disposables.


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Ant wrote:
Paul wrote:
Ant wrote:

I just woke this PC up, logged in, and manual rebooted. It got stuck at its Intel NUC, with its
animating spinner screen, again. I waited a few minutes and then it finally autobooted to the clean
installed W10 login. I logged in and looked around, and then noticed this new W10 was acting weird!
I couldn't type in desktop like in Contana. Start Menu was mostly black. I tried locking screen to
login screen. And then, noticed my login was missing so I had no way back in! I was able to click
on shutdown so I did that. Video signal lost, but PC still stayed on with its blue power light.
Once in wa while, I still seee it blue disk activity light come on quickly. It still won't even
shut down to power off! Argh.

OK, something is screwy now even with a new clean W10 installation. I think I am going to try
upgrading its BIOS later from
https://downloadcenter.intel.com/dow...?product=98414 with boot
up's F7 method to read from an USB flash stick. It might help?

If you're "lucky", you'll brick it during the BIOS flash
and then you can give it back to the customer :-/

Think carefully about your next step. This is a "sick patient".
What is your Plan B plan for this hardware ? If the NUC is
ruined, is the warranty still good ?

Ah, good idea. I will let him know if he want to risk it. FYI, Prime95's 15 minutes run and
Memtest86's few minutes run seem to be OK so far. I will leave memtest86 running all night long
when I sleep.

Weird. I woke up and noticed the PC was off (not asleep) from overnight's memtest86. :/ I turned it
back on and booted back to clean W10 just fine. Eh? Did memtest86 finished? A crash? I am confused.
I am rerunning memtest86 again right now with one round to see if it actually quits to shut down?

--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

Ant wrote:
Ant wrote:
Paul wrote:
Ant wrote:

I just woke this PC up, logged in, and manual rebooted. It got stuck at its Intel NUC, with its
animating spinner screen, again. I waited a few minutes and then it finally autobooted to the clean
installed W10 login. I logged in and looked around, and then noticed this new W10 was acting weird!
I couldn't type in desktop like in Contana. Start Menu was mostly black. I tried locking screen to
login screen. And then, noticed my login was missing so I had no way back in! I was able to click
on shutdown so I did that. Video signal lost, but PC still stayed on with its blue power light.
Once in wa while, I still seee it blue disk activity light come on quickly. It still won't even
shut down to power off! Argh.

OK, something is screwy now even with a new clean W10 installation. I think I am going to try
upgrading its BIOS later from
https://downloadcenter.intel.com/dow...?product=98414 with boot
up's F7 method to read from an USB flash stick. It might help?

If you're "lucky", you'll brick it during the BIOS flash
and then you can give it back to the customer :-/

Think carefully about your next step. This is a "sick patient".
What is your Plan B plan for this hardware ? If the NUC is
ruined, is the warranty still good ?

Ah, good idea. I will let him know if he want to risk it. FYI, Prime95's 15 minutes run and
Memtest86's few minutes run seem to be OK so far. I will leave memtest86 running all night long
when I sleep.

Weird. I woke up and noticed the PC was off (not asleep) from overnight's memtest86. :/ I turned it
back on and booted back to clean W10 just fine. Eh? Did memtest86 finished? A crash? I am confused.
I am rerunning memtest86 again right now with one round to see if it actually quits to shut down?

I ran Memtest86's one test, and it gave me a summary and never shut down. So, something happened
overnight. Memtest86 passed after 1.75 hours. I don't know what's going on with this Intel NUC PC.
It mostly works from usages, but once in a while it has issues that I mentioned. Also, I ran
Prime95 for about 30 minutes late last night and it was fine.

I think I am going to just give up.
--
Quote of the Week: "As a thinker and planner, the ant is the equal of
any savage race of men; as a self-educated specialist in several arts
she is the superior of any savage race of men; and in one or two high
mental qualities she is above the reach of any man..." --Mark Twain
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )