Skip to main content

Major BSOD Failure

Thread solved

In doing some testing on another reported issue, I did the following...

1. Completely delete the two configured backup tasks. All looked good.

2. Added a new Disk backup, full, USB destination, no error checking.

3. I said to back up later.

I got a blue screen restart. The Windows event log showed a BugCheck 1001 error.

I though it might be some other kind of anomoly. On reboot I tried again to add the backup. When it tried to save the backup task, I got another BSOD. This time Stop Code: Unexpected Kernel Mode Trap, File: protector.sys.

I repeated the sequence with the same result.

I'll do a feedback report, then try something else.

ADDITIONAL INFO:
1. I missed the underscore... it is file_protector.sys where the failure occurs (this is an ATI file)

2. I created a simple F/F backup to USB selecting C: drive and it saved OK. Then I created a simple D/P backup for C: disk and it failed.

 

1 Users found this helpful

I uninstalled ATI 2020, reinstalled and it still failed.

I uninstalled, ran the cleanup tool, reinstalled and it still failed.

I then tried to set the backup to my networked PC and it worked.

I then replaced the USB drive with a different one and it worked.

The 256GB USB drive I was using was used on a prior Survivor Kit experiment and consisted of a 2GB FAT32 boot partition and an NTFS partition. Using MiniTool Partition Wizard I tried to get rid of the 2GB partition and extend the NTFS partition to use the whole drive. It found an error in the NTFS file system and could not extend the drive. I ran the Check File System function which found a problem. After fixing the problem and getting the drive back to one partition, the BSOD problem is gone!

Interesting.  So, I wonder if simply having a corrupted destination immediately caused the BSOD, or if it is code to check for it that is panicking and causing it.

 

Bobbo_3C0X1 wrote:

Interesting.  So, I wonder if simply having a corrupted destination immediately caused the BSOD, or if it is code to check for it that is panicking and causing it.

Who knows.

I just removed the "SOLVED:" from the title of this thread because I realized that although I solved the issue for my case, there is still a problem in ATI that is not solved.

There have been similar BSOD errors involving file_protector.sys on prior versions of ATI.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Bruno,

we've checked your report and haven't found the crash dump.. If you encounter this issue again (hopefully not!), could you please look for the auto-collected dump and send it along with the system report to us?

Ekaterina, I have five Windows mini dumps for these failures. I have attached the last three to a feedback with reference to this forum topic. Hopefully that can help, but they are small dump files so maybe not.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

BrunoC wrote:

Ekaterina, I have five Windows mini dumps for these failures. I have attached the last three to a feedback with reference to this forum topic. Hopefully that can help, but they are small dump files so maybe not.

Thank you!! Received and passed to the development for analysis.