From Loop to Boot: Resolving Continuous Blue Screen Errors on an Acer Laptop


I am seeking assistance with a persistent blue screen error on my wife’s laptop, which has resulted in a continuous restart loop. The device failed to launch the Windows repair utility, prompting me to attempt a manual repair via a USB installation drive. Despite exhaustive efforts, including Windows’ built-in repair tools, system recovery options, and command prompt disk repair commands as suggested in a specific YouTube tutorial, the issue remains unresolved.

Furthermore, attempts to reinstall Windows have been thwarted by an inability to format or delete partitions, as indicated by error codes 0x80042428 and 0x80070017. Even when accessing the drive through an external USB system running Fedora 39, the drive seems functional and Windows files are accessible, yet I encounter errors when using disk utilities to format the disk, specifically ‘error wiping device: failed to wipe signatures on the device ‘/dev/nvme0n1p3’ (udisks-error-quark, 0).

The laptop in question is an Acer Nitro 5 model AN515-51-7103, equipped with an Intel NVMe M.2 SSDPEKKW256G7. Any guidance on how to resolve these issues would be greatly appreciated.”

I hope this rephrasing meets your needs. If you have any more requests or need further assistance, feel free to ask!


When faced with the dreaded blue screen of death (BSOD) on a continuous loop, it’s crucial to approach the problem methodically to find a resolution. The BSOD you’re encountering, particularly the registry error screen, suggests there might be corrupt system files or hardware issues at play. The fact that the Windows repair utility didn’t pop up automatically is concerning, as it typically indicates the system cannot access the necessary recovery environment on its own.

Your efforts to repair the system using Windows’ built-in tools and the command prompt disk repair commands were a good start. However, since these did not yield results, and you’re facing error codes 0x80042428 and 0x80070017 during the reinstallation process, it’s possible that there are issues with the drive’s partitions that are preventing the installation.

The error codes you’ve encountered typically relate to issues with the disk’s partitioning or bad sectors. Error 0x80042428 can occur if the disk’s partition table is corrupt, while 0x80070017 usually indicates that there are bad sectors or other physical problems with the disk.

Since you can access the drive using Fedora 39 and the files appear normal, this is a good sign, indicating that the SSD is not completely damaged. However, the error ‘failed to wipe signatures on the device’ suggests that there are still issues with the drive’s partitions that need to be addressed.

Here are some steps you can take to resolve these issues:

: Since you can access the drive, ensure all important data is backed up externally.


Check Disk Health

: Use Fedora’s disk utility to check the health of the SSD. Look for any signs of failing sectors.


Use a Different Disk Utility

: Sometimes, using a different disk management tool can yield better results. Try a bootable USB tool like GParted to manage and format the partitions.


Secure Erase the SSD

: If possible, perform a secure erase of the SSD. This can be done through the SSD’s firmware tools, which can sometimes be accessed via the BIOS or UEFI settings.


Update Firmware

: Check if there’s a firmware update available for the SSD. An update could resolve compatibility issues or bugs that are causing the errors.


Check for Hardware Issues

: If the problem persists, consider that there might be a hardware issue with the SSD or the motherboard’s connection to the SSD.


Contact Support

: If you’re unable to resolve the issue, contacting Acer support or a professional repair service is advisable.

Remember, if the SSD is failing, it’s often more cost-effective to replace it than to attempt complex repairs. The Acer Nitro 5 AN515-51-7103 is compatible with various SSDs, so finding a replacement should be straightforward.

In conclusion, persistent blue screen errors can be daunting, but by following these steps, you can diagnose and potentially resolve the issue. If all else fails, professional assistance will be your best course of action. Good luck!

Leave a Reply

Your email address will not be published. Required fields are marked *

Privacy Terms Contacts About Us