Replies

EP wrote:

so always download & run the latest version of that app & replace the old version

Or, set it to update on start…

 

1 user thanked author for this post.

Cybertooth

Andy wrote:

Try running this command from the recovery CMD it worked for me: BCDBoot C:\windows

Note that the drive letter may not be C: in the recovery/repair environment.

You would need to run diskpart then list vol to find the correct letter.

BCDBoot Command-Line Options

 

I saw an screen shot from 2019 that showed the option in a context menu, when right-clicking on an existing backup task.

However, I downloaded the PDF User Guide, and the only reference is to the manual check…it is no longer available in the context menu.

I would suggest contacting EaseUS Support for the post command.

 

 

 

Have there been any firmware updates on your WD external USB drives that failed recently?

I would hide it until we get diagnostics for the BSOD issue in your other thread.

 

 

sahalen wrote:

I have checked my crash dump files (*.dmp) and there aren’t any for the issue and date of occurrence.

Check that it’s set up…

https://www.askwoody.com/forums/topic/random-bsod/#post-2665177

When you get a crash dump, follow the Sysnative BSOD Posting Instructions and start a thread there.

sahalen wrote:

I save both the Windows Backup and Restore and Macrium Reflect system images to drives M: and N:. These are both Western Digital, removal, USB drives.

In the meantime, run chkdsk /r and the SeaTools Long Generic Test on those two drives.

 

Bob99 wrote:

Thanks for providing the crash dump minidump file and the screenshot.

I didn’t see a crash dump file…

There was a Reliability Monitor report, and a screen shot.

 

funhitman wrote:

OldNavyGuy, I ran the first two command lines and the drives are gone. What’s the purpose of the mountvol /R command line?

Sometimes, mountvol <Drive Letter> /D does not work.

mountvol /R will remove all mount points (including drive letters) for devices that are no longer connected to the system.

 

1 user thanked author for this post.

funhitman

wcandres wrote:

I’d like to have the backup image checked automatically.

I get that…

OldGuyForum wrote:

on most imaging software, it’s an option you select that runs automatically when imaging completes

Try right-clicking on the backup task in EaseUS, and see if there are any options available.

 

Who is the user (Standard, Administrator), what are they using (app, website, etc.), and what exactly are they attempting to do?

Attach a screen shot of the message.

 

MountMassive wrote:

The fact that two companies are experiencing the same exact problem tells me that there may be more out there.

However, one company (the hospital) installed the KB, while yours did not.

Has there been any unusual activity in the logs?

 

 

 

You might look in the User Guide…

https://www.easeus.com/tutorial/tb-free-user-guide.html

Usually, on most imaging software, it’s an option you select that runs automatically when imaging completes.

WSpaulh7436 wrote:

Attached is the minidump file time stamped at the time of the crash.

Follow the screen shots in #2665177 and change the type to “Kernel memory dump”.

When it happens again, follow the Sysnative BSOD Posting Instructions and start a thread there.

sahalen wrote:

Do you have any thoughts why it seems that the Windows Backup and Restore is causing this problem? Again, I have been using this for years now without any problems until recently. Also, I continue to use Macrium Reflect without problems.

I would not walk, but run from using Backup and Restore (Windows 7)…

The main drawbacks with using it to make drive images are –

1. It uses the same folder WindowsImageBackup every time, so it will overwrite the previous disk image saved in that folder, making it impossible to keep multiple disk images…unless you rename the existing folder.

Example:

You would have to manually rename the folder WindowsImageBackup to something like WindowsImageBackup-TodaysDate BEFORE creating the new image.

So, say if you wanted to restore a disk image from a couple of weeks ago, you would need to rename the current folder to something other than WindowsImageBackup (like WindowsImageBackup-Ignore) and rename the folder WindowsImageBackup-TwoWeeksAgoDate to WindowsImageBackup.

WindowsImageBackup is the only folder name that is recognized.

It’s a mess.

2. There is no “byte-for-byte” validation, so there is no way to verify that files on the disk image match those on the drive that was backed up.

3. There is no way to control how the disk image file is compressed on the backup drive. Larger backups mean fewer disk images can be stored.

Stick with Macrium.

I personally use Terabyte Unlimited’s Image for Windows/Linux for full images and restores…and Hasleo Backup Suite for folder images such as user profiles, and the driver store.

All that being said…

Was a crash dump file (.dmp) generated for the latest BSOD?

Have you run chkdsk /r on the backup media?

I would recommend downloading Seagate’s SeaTools Bootable.

https://www.seagate.com/support/downloads/seatools/

After creating the bootable media on a USB flash drive, boot and run the Long Generic Test on the backup media, and see if it finds errors…it could take a while to run to completion.

Note: It doesn’t matter if the drive is not a Seagate…I’ve run it successfully on WD drives.

Ed Bott’s article on the new HP subscription plan…

https://www.zdnet.com/home-and-office/smart-office/hp-says-its-new-subscription-plan-will-make-you-hate-your-printer-less-but-will-it/

We moved to Brother printers, and have never looked back.

 

Alex5723 wrote:

Enablement package is a feature update which can be blocked by the usual blocking settings.

A Microsoft-initiated forced upgrade to a new version isn’t the usual circumstance…

 

1 user thanked author for this post.

Mark