Windows 10: Infinit boot bluescreens with no issus

Hello,When I start my pc, in 1 case over 10 my pc normally start but a few minutes later it crashed with a bluescreens that didn't want to be repaired automatically or with commands like "bootrec /fixmbr and /fixboot". safe mode for the starting didn't want to load. in the other 9 cases over 10. it directly crashed. this solution doesn't work in my case: https://answers.microsoft.combut all steps were completely successful.Any solution or the reinstallation of Windows 10 is mandatory? In this case do we have windows accessible for free?in my case a tried many times to load windows with a recu

:)

 

Chrome kiosk create infinite window

Context

I'm trying to configure Windows 10 to boot directly on chrome in kiosk mode so the user can only see the webpage.

So I've followed those steps and launch Chrome in kiosk mode with the selected webpage.

Issues

Unfortunately, there is one more problem :

When I reboot sometimes (Once in three) Chrome open an infinite amount of Chrome browser, not new tabs but new windows.

Expectation

My needs for this system is to be fully optional anytime even if I ghost this OS on hundreds of device. So if anyone has an idea or suggestions, I will be thankful.

 

Bluescreen issue

Hello Brent, bluescreen issue is often resulted by faulty hardware or drivers. I suggest updating Graphics card drivers and Network adapter drivers because they usually cause this

https://support.microsoft.com/en-us/help/402844...

Another option is to perform bluescreen troubleshooting steps, which you can find in the following article

https://support.microsoft.com/en-us/help/14238/...

 

Constant bluescreens - still not fixed

I don't think you understood my issue - my bluescreens are random, so I can't do a clean boot and provoke a bluescreen. I am not sure what the steps you suggested have anything to do with my problem and it is not clear how it will help. The PC does boot
up normally, it just crashes randomly during the day.

I am pretty sure the issue is related to a driver that could be incompatible with Win 10. Please check the older threads to further understand the issue.

Thank you.