Talk of The Villages Florida - Rentals, Entertainment & More
Talk of The Villages Florida - Rentals, Entertainment & More
|
#1
|
||
|
||
|
After all of the crashing problems I have been having on my old laptop I decided to do a total reinstall of Windows, including getting rid of all apps, settings etc.
After about an hour it was 84% complete and when I came back an hour later there was a black screen saying: Your device ran into a problem and needs to restart We'll restart for you Stop: IRQL_NOT_LESS_OR_EQUAL (0xA) What failed: ntoskrnl.exe After another hour it still hadn't restarted so I did it manually, but keep getting the above screen The web says that it most likely a memory error, but how do I start it in order to run a memory check? F2 during start-up opens the boot menu, but F8, F10 and F12 do nothing so I can't get into Safe mode Thank you Last edited by Arctic Fox; 08-23-2026 at 03:52 PM. |
|
|
|
#2
|
||
|
||
|
Claude says:
This is a classic blue screen error, and a few common causes during a Windows reinstall specifically: Most common during reinstalls: Faulty or incompatible RAM — the single most frequent cause of this stop code in general. Worth running Windows Memory Diagnostic or MemTest86 if you can boot into anything. USB installation media issues — a corrupted or improperly created bootable USB is a very common trigger during setup specifically. Try re-creating it with the Media Creation Tool, and try a different USB port (ideally USB 2.0 rather than 3.0, since 3.0 controllers sometimes cause driver conflicts during install). Outdated or incompatible drivers being loaded during setup — especially storage controller (SATA/NVMe/RAID) drivers, if the installer is trying to load a driver that doesn't match the actual hardware or BIOS mode. BIOS/UEFI settings mismatch — particularly SATA mode (AHCI vs. RAID vs. IDE) not matching what the installer expects, or Secure Boot/CSM conflicts. Failing or incompatible storage drive — a dying SSD/HDD, or a drive with corrupted sectors, can trigger this specifically during install when Windows tries to write to it. Faulty or loose hardware connections — RAM not fully seated, a failing SATA/power cable, especially if this is a desktop that's been recently opened up or moved. Where I'd start troubleshooting, in order: Reseat the RAM (or try one stick at a time if you have multiple) Re-create the USB installer on a different USB drive, using a different USB port Check BIOS: confirm SATA mode is set correctly and try disabling any RAID/Intel Optane settings temporarily Run a memory test if you can. You've got two ways to run a memory test, both accessible from where you already are: Option 1: Windows Memory Diagnostic from the installer itself If you're currently sitting at the Windows Setup screen (the "Install now" screen from your USB), look at the bottom-left corner — there should be a link that says "Repair your computer." Click that, then go: Troubleshoot → Advanced options → Windows Memory Diagnostic (or sometimes listed under UEFI Firmware Settings / Command Prompt options, but Memory Diagnostic is usually right there in Advanced options). It'll ask to restart and run the test automatically. Option 2: From BIOS/UEFI directly (often faster) Since F2 already gets you into the boot menu / BIOS on your machine, go back in there and look for a tab or option along the lines of: Memory Test Diagnostics Hardware Test / System Test Many motherboards (especially Dell, HP, Lenovo) include a built-in memory diagnostic directly in BIOS, separate from Windows entirely — no OS needed at all. This is often more thorough than Windows' own tool. A third option, if neither of those panels shows a memory test: Since you can already get to the boot menu with F2, you could boot from a MemTest86 USB (a free standalone tool, on its own bootable USB, separate from your Windows installer). Last edited by Velvet; 08-23-2026 at 04:36 PM. |
|
#3
|
||
|
||
|
Do you really need Windows? I stopped at Windows 7, wiped the drive and put on Linux Mint. I'll never go back. Nations are switching to Linux (France, Germany even China). Unless there is some very specific program that only runs on Windows, you'll find Linux does just as well, if not better. You can test Linux without wiping out your drive. If it mets your needs, you can install it. Just copy any important files you at need.
|
|
#4
|
||
|
||
|
Thank you for your answers
Just to clarify, I ran the "factory reset" from within the computer itself, not from a USB stick, so I assume that it tried to reinstall whatever version of Windows and whatever drivers the laptop originally came with. I cannot get past that screen message to do anything different, other than to boot into whatever comes up when I press the F2 function key during start-up. Along the top of that screen it says "InsydeH20 Setup Utility Rev.5.0" The only option in Boot mode is Windows Boot Manager - I was hoping I could switch to boot from a USB stick, but no such option is available. I shall see if I can get into the case and remove one, then the other, memory strips to see if one is faulty |
|
#5
|
||
|
||
|
Btw. If you would consider it, I second the motion for Linux.
You must have a way of getting on line because you are posting here. Claude.ai is very supportive with computer help. It is available free but I like to post photos — it can see things much better than me describing in words. I pay a $20 per month subscription (just for 1 month). It likes to see photos of your screen to see what is going on, what kind of computer etc. and I guarantee you that if it solvable on your laptop Claude will keep at it until your problem is fixed to your satisfaction. I find it tends to use jargon for brevity. Then I say; huh? And it repeats in very easy to understand, step by step instructions. |
|
#6
|
||
|
||
|
It sounds based on all the possible reasons why your laptop is having trouble, that you just need to suck it up and get a new laptop. There's something wrong with the hardware. Either memory, hard drive, corrupted partitions, or a bad SSD. Something is either worn out or broken. It's less time consuming and less frustrating to just replace it with a newer model.
Changing to Linux won't fix your broken/worn hardware. |
|
#7
|
||
|
||
|
Further, Claude suggests:
"InsydeH2O" (sometimes displayed as "InsydeH20" — that's a zero, not the letter O) is the name of the BIOS/UEFI firmware your computer uses. It's not made by your PC's brand directly — it's made by a company called Insyde Software, and licensed to laptop/PC manufacturers who build their BIOS on top of it. It's extremely common — used by many major brands including Acer, ASUS, MSI, and others, especially in laptops. So what you're looking at right now is your BIOS setup screen — you're already in the right place. "Rev.5.0" just means the firmware revision/version number. Since this confirms you're in an Insyde-based BIOS, here's what to look for: Look for tabs along the top (usually navigated with arrow keys, not mouse) — commonly labeled Main, Advanced, Security, Boot, Exit, or similar A memory/diagnostic test isn't always built into Insyde BIOS the way it sometimes is on Dell/HP — it's less standard here Check under Advanced or a tab that might say Diagnostics or Tools Since Insyde BIOS varies a lot by manufacturer skin, knowing your laptop brand/model (Acer, ASUS, MSI, etc.) would let me tell you exactly which tab to check, or confirm whether this BIOS build has memory diagnostics at all — many Insyde builds don't, and MemTest86 on a separate bootable USB becomes the more reliable route. |
|
#8
|
||
|
||
|
Quote:
|
|
#9
|
||
|
||
|
[QUOTE=OrangeBlossomBaby;It's less time consuming and less frustrating to just replace it with a newer model.[/QUOTE]
Yes indeed. I'm sending this from my new laptop - I went with a similar model (Acer Aspire) but I'd like to get the old one working as insurance against this one having a hissy fit one day. I upgraded the memory on the old one, so know how to pop the modules out (hoping that that is the problem) but it involves a nerve-wracking operation with the plastic base, hoping it doesn't crack on me :-) |
|
#10
|
||
|
||
|
Quote:
The BIOS screen has the tabs you mentioned, but underneath each is very minimal - I am used to seeing a lot more options there. |
|
#11
|
||
|
||
|
Thank you - I'll give that a shot before my memory foray. I have already tried F2, F8, F10 and F12 but F9 will be new ground for me. After that, I might run through the rest of those F's just in case.
|
|
#12
|
||
|
||
|
The thing is, to use the F keys on a Acer laptop, and most laptops for that matter, you have to hold down the fn button to use the F keys. They're not like a regular keyboard connected to a desktop computer.
|
|
#13
|
||
|
||
|
Quote:
I already have my function keys defaulted (because of other software I use) but it can certainly be confusing when trying to get to an alternative start up. |
|
#14
|
||
|
||
|
Thanks — that's helpful context. A quick note: Acer's Insyde-based BIOS on Aspire laptops generally does not include a built-in memory diagnostic tool, so your best bet is going to be the standalone MemTest86 route.
Here's how to do that: On another working computer, download MemTest86 (the free version) from memtest86.com (you said you had another laptop) Use their tool to write it to a separate USB drive (not the one with your Windows installer — you'll need two different USB drives) Insert that MemTest86 USB into the Acer Restart, and press F2 again to get into this same BIOS screen Look for the Boot tab (use arrow keys to navigate) — there should be a Boot Priority or Boot Override list Select the MemTest86 USB drive from that list to boot directly into it instead of Windows MemTest86 will run automatically — let it complete at least one full pass (this can take 30–60+ minutes depending on your RAM size). Any errors it finds will show up in red. A couple of Acer-specific things to check while you're in BIOS anyway: Since this is a 7-year-old Aspire, if it has two RAM slots, sometimes just reseating both sticks (removing and firmly reinserting them) resolves this error on its own — worth doing before or after the test, since Ryzen-based Aspires from that era commonly had budget RAM configurations, and a loose stick from age/heat cycling is a very common cause. If you only have one RAM stick free and a second slot open, and you have a spare stick lying around, testing with just one stick at a time can also isolate a bad stick faster than MemTest86, if you want a quicker (though less thorough) check. |
|
#15
|
||
|
||
|
Quote:
The whole screen says: Boot mode: (UEFI) Secure Boot: (Enabled) Boot priority order: 1. Windows Boot Manager |
| Closed Thread |
|
|
|
|