Forum Discussion
Windows Insider builds keeps bricking my laptop
That error indicates a high chance that you have a hardware issue which means that the boot loop is a symptom only. It *may* be possible that the pre-release has some code that's causing or interacting with your CPU or other hardware to create the boot loop. Having no issues in Safe Mode supports that it could be a hardware/driver or CPU issue still.
Reinstalling Windows will not have any effect to resolve that if that is in fact the issue.
Prior to doing anything like re-installing, try a selective boot using these steps and confirm if the boot-loop goes away: https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows
After that you'll start getting enough info to try to diagnose if you have a hardware or driver issue by selectively turning things back on.
Thanks for the tips. Would you have any idea as to what hardware it may be referring to? I know that without any diagnostics it's a wild guess, but I have seen references to a defective RAM while reading up on the issue online.
Dos the device have built in diagnostics? If so run those on everything including CPU and memory. Yeah, memory is always "low hanging fruit" but keep in mind that may mean the hard drive (where the virtual memory actually is).
If you can access the physical memory and remove/re-seat it. From what I saw here (https://us.answers.acer.com/app/answers/detail/a_id/46306/session/L3RpbWUvMTUxMDc3OTcyNi9zaWQvZlVseUczQl9ZM2pTSTJjSENUS1RsWTQwN1lZN2x4c0p6NmclN0Vnakhpdzk0UVhkNkxZb2ZQeVI0enlFaGVjZElUdlAwdWxKZmhiZ0hmJTdFZHlXamh5UzFQblEzbHFQc2VDRmYlN0VzblFlZXFLZHIxdzdoaDh1JTdFJTdFc19XUSUyMSUyMQ%3D%3D) the drives look to be spinning disk and not SSD so that's something to check with an offline disk check (chkdsk /f /v /r & then check the logs after the boot to confirm if there's any bad sectors).Yeah I should probably test RAM modules as well. I did several disk checks, and sometimes the Windows error checking tool reported errors, and sometimes no. Now I did a fresh install off of USB and it seems that I finally got rid of the Insider-version. Let's hope it now works.
