New Dell, SSD M.2 pc sn530 nvme wdc 512gb restore problems.
Got the PC on 9/30/2021.
First thing I did, install Acronis, backup the PC (complete C: drive), make the Recovery CD, and then tested it could boot and work (did not restore though.
I was shipped with W10.
On 10/6/2021 it was updated to W11.
On 11/13/202 the Dell BIOS was updated.
Things went downhill fast.
In short, Dell Support Phone Agent had me try a lot of things, NONE worked. The error was:
Also got a BAD_SYSTEM_CONFIG_INFO error depending what was tried.
Didn't seem the disk could be 'saved', but I had an Acronis Backup. So I tried that. This didn't work, got the above error.
Now normally I'd just restore the C: drive itself. So I did that and Sector 0 and the EFI partition. Same error.
In the Thread above I linked it was posted that W11 might encrypt the drive, which I doubt (no, BitLocker is not in use). BTW, that is a long thread, and I've cut to the chase here...
I also read this, kb.acronis.com/content/59877
and I think I did it right? I can see all the saved files and what is in them, and it does do the restore. Just that the restore doesn't work.
I was able to install W10 to the PC, it did boot, but it was not complete, many Dell Drivers were missing. So I tried to Restore C: to the latest I had. Got the above error.
Where I stand now:
- Dell had me create a Media Install of W11 and I installed it. System boots fine.
- Did a C: Restore.
- Got the errror.
- Re-intalled from the Media W11.
- Slowly I am rebuilding the PC. Needed to find programs, data, licenses, etc. all over again.
- Still have the Acronis Backups, but did not reinstall Acronis.
What could have happened?
Does ATI 2020 work with W11?
Are my Images OK?
Should I re-install Acronis if there is a 'trick' here to make it work??? This is what I have now:
======================
P:\Acronis Backup\All Drives>dir
Volume in drive P is My Book
Volume Serial Number is 169F-19E5
Directory of P:\Acronis Backup\All Drives
10/02/2021 07:37 AM <DIR> .
10/02/2021 07:37 AM <DIR> ..
10/15/2021 09:20 AM 12,288 IRVXPS8940 All Drives.tibx
11/05/2021 09:35 AM 261,102,432,256 IRVXPS8940 All Drives-0007.tibx
11/12/2021 10:35 AM 275,046,428,672 IRVXPS8940 All Drives-0008.tibx
11/13/2021 10:35 AM 274,546,720,768 IRVXPS8940 All Drives-0009.tibx
11/13/2021 12:00 PM 292,249,526,272 IRVXPS8940 All Drives-0010.tibx
5 File(s) 1,102,945,120,256 bytes
=======================
There are 3 drives in each one. I tried 10/13 to 10/12 backups, all produced the same error, even with 3 partitions selected, 0, EFI, and C:.
Steve. great Advice, but I believe I've done all that.
I've RESET the BIOS to DEFAULT many times when I had the Problem.
I could install both W10 and W11 and they would boot.
Matter of fact, after my first Install after the BIOS problem happened I did use the ATI Boot tool I created under W10 on THIS PC. Got the posted picture problem.
If I can install W11 with ease and get around the problem I assumed:
- Just replacing ONLY the C: drive would be OK (and like I said, I've done this before and it works).
- Since it didn't, I replaced all the drive 0 partitions that I thought mattered, Sector 0, EFI, and C: and that didn't cure it.
Is it 'possible' once on W11 I need to create a NEW boot CD?
The ERROR codes are of no help to me. I'd also think that a new CD/DVD wouldn't matter as the drivers are the same?
Steve, for the record, there is a second hard drive, a 1 TB one, but I know how to tell what the difference it. Yes, the M.2 SSD is the Boot drive.
Irv, I can think of no reason why restoring your backup of Windows 11 from a time when all was working correctly shouldn't result in a successful and working OS. I am assuming here that the BIOS settings remain essentially the same as they were previously despite having reset the BIOS to defaults.
The second internal drive also shouldn't make any difference given it is only being used for data storage but testing with it disconnected while in its current working state would show immediately if there are any dependencies between the 2 drives or not?
Steve, that is what bothers me now? I can't fathom how I can't restore what I want to C:? Only reason I can think of, the backup was bad? However I can open it and see what seems to be proper files and structures?
I'm 'afraid' now that I've just about finished customizing the PC again, doing a backup, and a test RECOVER to C:. If it fails, I'll certainly NOT be a 'Happy Camper'!
Twice I installed a new copy on the OS, once Win10, and then Win11. Both times after the install, the PC booted. I could do a REBOOT and a POWER OFF/ON, it worked fine. Installed a BACKUP to C:, got the ERROR CODE.
I'm wondering if my DVD is bad? As I look at it, it has some 'hazy' spots, almost like finger smudges across it? All do, they are NOT new and it is possible the clear coat on them has aged? It takes a LONG time to load up? Do you think that could be part of the problem?
By the way, after I did the restore and use a disk to get to the CMD prompt. I ran DISKMGMT,MSC and all seemed fine. I also ran a DIR on C: and it was OK? That is why I was at a loss? Since I didn't restore the failing times I didn't restore track 0 or EFI partition? Why DIDN'T it work?
There has to be a reason that the PC loses Boot capability?
Any Suggestions?
I was thinking of restoring the other drive to a different place, another External drive maybe, but that wouldn't 'prove' anything but it can backup files OK? It is the booting that is the problem (assuming all needed boot files went down correctly?
Irv, several comments to add here:
When doing an OS recovery then you need to restore the whole of the OS drive as a single unit, so all 5 partitions as shown in your earlier screen shot of the 500GB SSD drive. You should not mix and match any of these. All the data being restored should come from a single backup image of the working system. The OS C: partition and the EFI System partition must match from the same working system - the latter contains the Boot Configuration Data store information that tells the PC how to boot into Windows!
I would suggest not using any optical media (CD or DVD) for rescue media - it is the slowest of the options and subject to potential damage to the surface etc. All modern PC's will boot from USB rescue media or an external HDD and do so much faster than using a CD.
Next, consider what might be considered a more paranoid approach - download and install a second backup application such as Macrium Reflect 8 Free and create backups using both this and Acronis, plus make bootable rescue media for both applications. This may feel like overkill but would immediately tell you whether any recovery issues are being caused by one of these applications or if there is an issue with the PC or the target drive etc!
Steve, yeah, I know how PC's boot, I've worked with Boot Manager for OS/2 :-)
Actually, I've always made sure the C: drive matched in SIZE as well as part of the other files on that particular disk. I never partition the Boot disk to hold other partitions.
Steve, you read my mind!!!
I came back her to report something, and I see you wrote this:
"Next, consider what might be considered a more paranoid approach - download and install a second backup application such as Macrium Reflect 8 Free and create backups using both this and Acronis, plus make bootable rescue media for both applications. "
WAY AHEAD of you I guess? My next plan was to do exactly that,, get Macrium Free and create a backup. Also ATI, both of the C:. Then get one of my Externals and make 2 partitions on it to restore C: on each partition with the different programs. Then do a COMPARE of the 2 partitions...
Well, I didn't get that far.
Macrium didn't get that far, it complained the C: drive had
| MFT corrupt - Error code = 6. Please run 'chkdsk C: /r' |
Did run it, and it took some time on reboot, can't see any remnants of what it did? Not anything in the Event Viewer that seems to be connected either?
Not sure if this is/was the cause or not? Not even sure if ATI would have seen this and I have not installed it yes since the last install?
I'm on the fence what to do next?
Does ATI 2020 allow one to make an "USB rescue media"? If so, I missed it. Rather do that if I could? Don't want to use an External drive either. DVD/CD was always convenient for me since it was rarely used... file it away until I needed it, speed wasn't of a concern.
MFT errors would certainly complicate things!
Yes, all recent versions of ATI allow creating of USB rescue media, you just need to have the USB media connected before starting for it to be offered as a choice. USB memory sticks should be 2GB min size up to a max of 32GB size. The media will be formatted as FAT32.
Steve,
Other than taking a chance that I can save C: and then restore it without a problem, is there any other way to ensure I wouldn't have a problem?
Am I correct in assuming since all other drive partitions were the same, I can only recover the C: partition or must I recover ALL, even the partitions that are not part of booting?
I've normally only recovered C: when needed and not the others with no problem.
Irv, the approach that I have used is to have a spare NVMe M.2 boot SSD for when I have been in any doubt about recovery.
In terms of restoring partitions, your EFI partition is only 150MB and would take a few seconds to restore at most but will ensure that the boot configuration it holds matches with the OS backup of the C: partition.
Your earlier image shows you have 3 recovery partitions, one being a larger factory restore partition and the others being an active and inactive Windows recovery one.
If you have performed a new clean install of Windows (10 or 11) then all of these partitions will have changed from how they were for an earlier backup from a prior installation of Windows. This means that the unique partition identifies used by the boot configuration will all be different for each installation (stored in the EFI partition BCD files).
Irv,
Your on screen error refers to Driver Verifier. You may find what's below helpful.
This bug check can only occur when Driver Verifier has been instructed to monitor one or more drivers. If you did not intend to use Driver Verifier, you should deactivate it. You might also consider removing the driver that caused this problem.
So please disable driver verifier. Please check the information below:
https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html
Or you could try to modify the registry below to disable.
the verifier settings are stored in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers and HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel. Delete both entries to get rid of Driver Verifier
It would be my bet that Dell themselves had run Driver Verifier on your machine and then neglected to disable it when finished unless of course you did so yourself which is doubtful. Quality control at the OEM's these days is suffering.
I recommend that you disable Driver Verifier per the link above so that it does not run and cause a driver failure during your restore attempts which I believe will solve your issue.
Steve, don't have that SSD spare... not sure I'd want to buy on either?
Yes, there could be 3 restores... the Original W10 from Dell, the W10 from when I installed it, and W11 from when I installed it.
Dell Phone agent had me try and do a re-install via BIOS tools, didn't work. Didn't do the W10 or W11 re-installs from DVD before that.
I almost think the 'corrupted' BIOS might play into that. Resetting the BIOS to DEFAULT didn't change that.
I know how Boot works, BIOS to Sector 0 which then branches to the Boot Loader (EFI), which has the OS Loader address and branches to it.
BCD looks good now:
=======================
C:\Windows\system32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume4
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {57f56ec4-481a-11ec-bcf0-fd92c4681119}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {57f56ec6-481a-11ec-bcf0-fd92c4681119}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {57f56ec4-481a-11ec-bcf0-fd92c4681119}
nx OptIn
bootmenupolicy Standard
=====================
When the BIOS was supposedly corrupt, it did have as the boot path the correct one. Might be due to the MFT error?
I do have a 2T External drive available I think (have to check, have a few) and I was thinking of restoring to that? Plug it in, use the Boot Menu and see if that loaded? Is this reasonable?
I'm getting out of my 'comfort zone', forgot a lot in 20 years since I retired.
Irv, please see the update from Enchantech above your last post and action the points that he has raised, in particular, follow the link Bob has provided so that you can disable the Driver Verifier to avoid any further BSOD's on booting.
With regards to restoring to your 2TB external drive, be aware that doing a Disk restore will wipe the whole drive plus you cannot test whether Windows will boot from an external drive as this is not allowed by Microsoft!
Enchantech wrote:Irv,
Your on screen error refers to Driver Verifier. You may find what's below helpful.
This bug check can only occur when Driver Verifier has been instructed to monitor one or more drivers. If you did not intend to use Driver Verifier, you should deactivate it. You might also consider removing the driver that caused this problem.
Well, good guess, I guess? But not the case, it is ALL off:
I scrolled the ENTIRE list...
Not in REGISTRY either:
Could be caused by a corrupted BIOS???
If this was a corrupt BIOS then I would expect it to impact every installation on this PC.
No recovery will change the BIOS to my knowledge other than changes to the BCD data in the EFI partition used by the BIOS when booting.
Steve Smith wrote:If this was a corrupt BIOS then I would expect it to impact every installation on this PC.
No recovery will change the BIOS to my knowledge other than changes to the BCD data in the EFI partition used by the BIOS when booting.
That was my feeling as well. I don't think the BIOS was corrupt at all? I could easily get into it and look at all the settings.
Like you, I think something blew up the BCD..
That said, since I could clean install from a DVD or USB Media tool to the Drive 0, I wouldn't think that the SSD was 'damaged'? So it point to a corrupt BCD. OK, so why couldn't Acronis work then with only a C: restore (to a booting W11 system) or with Track 0, the EFI and C: Partition restored at the same time?
I can't figure that out? Only 'reasonable one' would be the backup was 'damaged'? I never turn on Validate, maybe I should?
Why Acronis never caught the MFT error either? Assuming Acronis caused that (I am not saying it did), then my clean Media Creation Tool for W11 should have cleared that? That was what I ran Macrium on?
The MFT is stored on the first sector of the disk, TRACK 0.
So not putting down TRACK 0 on a Restore should not cause a problem, that is unless the disk layout had changed? Since C: was 'supposedly' not moved or changed, writing INTO that partition should be OK?
I wish I had a debugger to see what is happening?
Still, at this point I am unsure how to proceed?
- As it stands NOW, is it SAFE to rely on Acronis being able to restore a backup?
- Should I restore to another DRIVE letter and COMPARE?
- Should I capture the BCD data, assuming I could restore it later if something happens?
- Could my SSD be 'flaky'?
Assuming the LAST POINT and the SSD itself is the problem, maybe I should just wait for it to fail? Run CHKDSK randomly to see if there are errors on it?
I am conflicted, that is for sure. Working FINE now. I am on a UPS so I'm not worried about power loss or voltage changes. Short of a H/W failure, my 'risk factor' should be low.
About the ONLY time I've used the recover has been a disk failure, and once when my wife's PC was infected. Maybe a handful of times to recover a file or folder, but nothing major was lost if we couldn't.
Irv, I subscribe to the KISS principle in dealing with these type of issues. I make backups of my OS disk with all associated partitions, and when / if recovering, I recover the whole backup image so that it is put back exactly how it was when the backup was created.
I don't worry about the hidden / system partitions captured alongside the OS partition as I know they all were correct and working at the time the backup was created.
This approach has not let me down.
When doing a recovery, the first action is normally to wipe the target drive (assuming a Disk restore is being done) hence the full partitions structure will be recreated from the information held in the backup image selected, including track 0, MFT, BCD etc.
OK, for the boot drive I guess I'll need to do a Disk recovery vs. a Partition.
Hope I never have to do one, but if I do, I'll do it that way.
Thanks.
Steve,
I've re-installed ATI 2020, and made a FULL BACK up with Validation.
Next I was looking at some performance issue that could be improved.
One was Disable VBS. Did that, and this popped up:
Mind you, I am on W11.
Can't see how to clear that?
Ir also implies with VBS on, that file would not be loaded?
Search for "Why do incompatible drivers prevent using Memory integrity?", I can include the link?
Is this a problem, not loading that file?
Irv,
Memory Integrity - Core Isolation are not compatible with True Image, it is a known issue.
The reason that you did not find the Driver Verifier active on your system is simple. you reinstalled the OS thus killing that service.
The reason for your MFT error is attributable to your recovery of only the C: partition to the disk. That would cause the MFT to have errors due to partition information changes between the current MFT and the backup MFT. Acronis would have eventually caught the error, just not sure when.
Enchantech wrote:Irv,
Memory Integrity - Core Isolation are not compatible with True Image, it is a known issue.
The reason that you did not find the Driver Verifier active on your system is simple. you reinstalled the OS thus killing that service.
The reason for your MFT error is attributable to your recovery of only the C: partition to the disk. That would cause the MFT to have errors due to partition information changes between the current MFT and the backup MFT. Acronis would have eventually caught the error, just not sure when.
EnchanTech,
Thank you, that answers the DMA error...
I did find TIB.SYS later was the problem and related to T&D which I do not use.
Unlike other, I was on W11 and DID a clean install of W11, and THEN ATI2020. Core Verifier WAS on when I installed it. I had no install problems with it on W11, which others seem to have reported?
What happened was I was reading on some sites that VBS (Core Verifier) can be turned OFF to improve Performance. Not that I needed it, i7 11700, 16GB's of fast RAM, and OS on an SSD. So I turned it OFF and tested. Decided that I felt it was better to have that on. However, no I can't turn it back on due to TIB.SYS?
Obviously, Acronis has had this problem for a long time, and it appears to me, are not going to fix it? So, how can I re-enble it?
I'm thinking I can RENAME the file and reboot, then I could enable the setting? Boot to SAFE MODE and TRY to re-enable it? Not sure what to do, but I think I'd want that setting on?
Steve, I did make the USB boot drive. Works fine, but I wouldn't say it is faster than the DVD? It is quieter though :-)
Irv, I think that you are confusing issues here. Core Isolation is not the same as Device Verifier and the tib.sys driver issue only applies to Core Isolation.
I would suggest making a decision whether you want to use ATI 2020 or use Core Isolation and not attempt to trick the system into using them together!
Windows 11 does not turn on Core Isolation by default when upgrading or has not done so on the systems I have upgraded to 11 to date! Driver Verifier is a different tool with a completely different purpose and one that I have never used to my knowledge!
The other key benefit of using a USB boot device for Acronis Rescue Media is that it is read/write media, so you can capture logs, images etc to it if needed. You can also update the USB media easier too by creating a new boot.wim file and copying it over to the Sources folder on the USB stick / drive.
Steve, my Core Isolation was ON by Default, at least on the fresh install via the Media Creation tool.
When I turned it off, not a problem, until I tried to turn it back on.
Was able to do that when I renamed TIB.SYS and rebooted. Then I could turn it on again. Renamed the file back, but I guess it will not load (can't find any indication that it has not loaded though)? If it doesn't, it seem T&D will not work, but I am not using that, so I should be OK.
Device Verifier is not related to this, and it is and was already off. Did not cause the DMA error.