Forum Replies Created
If Windows isn’t saving dump files after a BSOD, do this:
Make sure the folder C:\Windows\Minidump exists. If not, create it.
Go to System Properties > Startup and Recovery. Set “Write debugging information” to Small memory dump (256 KB) and make sure the path is C:\Windows\Minidump.
Check that the page file is enabled on the C: drive. Windows needs it to write dump files.
Open Command Prompt as admin and run:
wevtutil sl System /e:true
This makes sure system logging is enabled.
If you use any system cleaner apps, turn them off. They might be deleting the dump files.
Restart and check again after a crash.
I’d skip the DIY experiments. More tinkering = higher chance of frying the storage chip. Good labs do “no data, no fee,” so at least you won’t be charged if it’s truly gone.
For reference, a basic power circuit fix can be under $200; full chip-off recovery can hit $700+.”
If your Windows 11 PC is stuck in a CHKDSK loop, boot into Recovery Mode and open Command Prompt. Run chkntfs /x C: to stop CHKDSK from running at startup.
Next, use a bootable USB drive to back up your important files to another drive. Then, in Command Prompt, run chkdsk C: /f /r to check the disk for errors. If the scan hangs or fails, your drive may be failing.
You can also stop automatic repair by running bcdedit /set {default} recoveryenabled No. Replace the drive if the issue continues after backup.
Try these fixes –
1. Reset the app:
Open PowerShell as Administrator
Run:
Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage
2. Delete the broken app files:
Go to:
C:\Program Files\WindowsApps\
Find and delete folders starting with Microsoft.SecHealthUI
You may need to take ownership first
3. Re-register all apps:
In PowerShell (Admin), run:
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
4. If it still doesn’t work, do a repair install using Windows 11 ISO. It keeps your files and apps.
Try this:
1. Set an admin password in BIOS → reboot → Secure Boot should unlock.
2. Turn off CSM in the Boot tab.
3. Make sure BIOS is in UEFI mode and your drive is GPT.
If it still doesn’t work, update your BIOS.
Every time my system crashes (BSOD), I get the message “Dump file creation failed due to error during dump creation.” It used to generate minidumps normally, but now nothing gets saved in the C:\Windows\Minidump folder.
Here’s what I’ve already tried:
Verified system is set to create kernel or small memory dumps
Made sure there’s enough space on the C: drive
Checked permissions on the Minidump folder
Ran SFC and DISM (no corruption found)
Still no luck. Any idea how to get Windows to start saving dump files again after crashes?
My Windows 11 PC is stuck in a CHKDSK loop on startup. It keeps running scan and repair every time I boot, but never finishes or lets me log in normally. I’m worried I might lose my data if I force shutdown too many times.
I’ve already tried:
Letting CHKDSK run completely (no success)
Booting into Safe Mode (still triggers CHKDSK)
Startup Repair (didn’t detect any issues)
Is there a safe way to stop this loop and recover my files before something goes wrong?
Getting a Bad Image error (0xc0e90002) for MicrosoftSecurityApp.exe every time I try to launch Windows Security on Windows 11 (24H2). It says something like the file is either not designed to run on Windows or it contains an error.
I’ve tried:
Running SFC and DISM (no issues found)
Restarting the PC
Updating Windows
Nothing has worked so far. Anyone else faced this? How do I fix or repair this specific error?
I was checking my system settings and noticed that Secure Boot is greyed out in my BIOS. I’m using Windows 11 Pro (24H2) and the system is running in UEFI mode. TPM 2.0 is enabled. I didn’t set any BIOS password, and there’s no option to toggle Secure Boot.
Has anyone figured out how to fix this or enable Secure Boot when it’s greyed out?
Yeah, I tried on iTunes already ..nothing shows up. Guess it’s past the easy fixes.
Before you shell out, try plugging it into a Mac or PC with Finder or itunes open. I’ve seen phones that look completely dead still show up in recovery mode. If it does, you can update or at least back up.
But if it’s not even being detected, board repair is your best shot.
Ummm..pretty much, yeah. They’ll usually do a “temporary repair” (replace or bypass the dead parts just to get your phone to turn on). Look for board level repair or iPhone data recovery places in your city.
Most decent ones won’t charge if they can’t recover anything. Just avoid the too-good-to-be-true ones; this stuff needs specialized gear.
So should I be hopefull? Apple basically told me I’d be better off recycling it. How do I even find one of those labs? Are we talking “strip the phone apart” kind of repair here?
My iPhone X died like that last year ..turned out it wasn’t the logic board but the power IC that failed. Apple told me it was “beyond repair,” but a local data recovery guy pulled my photos. They basically bypassed the dead components to get it to boot long enough to extract stuff.
One more thing.. if the phone had a passcode, your data’s still encrypted. That’s actually good news: even if someone else got hold of the phone, they can’t read your stuff. Labs just need to get the phone working enough to decrypt using your passcode.