System reboots after 07/01 update

It seems like a process called "downloader.exe" in the C:\Program Files\Bitdefender\Bitdefender Security is causing multiple reboots of my machine. The crash dump indicates:

Bug Check Summary

PAGE_FAULT_IN_NONPAGED_AREA (0x50)

Error Meaning: A process attempted to access memory that was marked as non-paged, but the page was either invalid, corrupted, or freed. This typically signals a faulty driver, hardware failure, or bad memory access in kernel mode.

Key Bugcheck Parameters

Parameter	Meaning
Arg1: `fffff8014baaeb30`	Memory address attempted to be accessed
Arg2: `0000000000000010`	Attempted instruction was a write
Arg3: `fffff8014baaeb30`	Address where the crash instruction occurred
Arg4: `0000000000000002`	Reserved

The instruction attempted to execute code at fffff8014baaeb30, which is not a valid code location. This matches:

AV.Type: Execute

Primary Fault Location

FAILED_INSTRUCTION_ADDRESS: fffff801`4baaeb30 ?? ???

This address is invalid or was freed, leading to an access violation on execute.

Faulting Process

PROCESS_NAME:  downloader.exe

This is the user-mode process running at the time of the crash. If this executable is unfamiliar or unsigned, it could indicate:

A bad 3rd-party app
Malware (if not validated)
A corrupt or incompatible file system filter

🔗 Call Stack Highlights

nt!KeBugCheckExnt!MiSystemFault+0x7a0nt!MmAccessFault+0x630nt!KiPageFault+0x38b0xfffff801`4baaeb30nt!KeInitializeEvent+0x7FLTMGR!FltpAllocateIrpCtrlInternal+0x5cb

Observations:

The crash occurred during page fault resolution (MiSystemFault)
FLTMGR.sys (Filter Manager) was involved — suggesting a file system filter driver or antivirus may have hooked the I/O path
Faulting address was passed through the FLT Manager stack

VirusTotal indicates it is not malicious which makes sense since it is a BitDefender .exe.

Find more posts tagged with

Comments

Gjoksi

Hello.

I believe that @camarie, who works at Bitdefender as Principal Software Developer, can help you with the issue.

You could also follow the steps below.

-- STEP 1 --

Repair Bitdefender, by following these steps:

https://www.bitdefender.com/consumer/support/answer/13429/

-- STEP 2 --

If the instructions from Step 1 didn't help, uninstall the Bitdefender program using the Uninstall Tool:

https://www.bitdefender.com/links/uninstall_consumer_paid.html

It will completely remove the program.

Next, reinstall Bitdefender from your Bitdefender Central account and see if the issue has been solved, as reinstalling the program usually solves the issues.

-- STEP 3 --

If the instructions from Step 2 didn't help, follow the instructions in this step.

First, take screenshot(s) of the issue

and create a log file on your Windows device using Bitdefender Support Tool, by following these steps

https://www.bitdefender.com/consumer/support/answer/1733/

Next, contact Bitdefender Consumer Support by e-mail:

https://www.bitdefender.com/consumer/support/help/

with short description of the issue.

After that, you will get an automated reply by the Bitdefender Customer Care Team, with your ticket number.

Now, in reply to that automated reply, you can send the screenshot(s) you already took and the log file you already created in the first step.

Since you are all done, just wait for the support engineers to investigate your issue and find a solution to fix the issue.

Remember that the screenshot(s) and the log file will help a lot to the support engineers for better and faster investigation on your issue and finding a solution.

NOTE: If the log file is larger than 25MB, you can upload the log file here:

https://upload.bitdefender.net/

After the upload is done, you will get a notification with the file's URL and then you can share the file's URL with the Bitdefender Consumer Support.

Regards.

camarie

downloader.exe is an user mode process and it should not provoke a BSOD. That being said, @Gjoksi is right, in order to investigate this a crash dump, error logs etc. are needed.
If there is a MEMORY.DMP (or any other .dmp) captured by Windows (either in C:\Windows or in C:\Windows\Minidump) that would be very helpful.

I would not exclude also a defective RAM (this happens more often that we realize), and checking Event Viewer (especially in System and Application sections, filtering for Error) might prove useful as well.

So I would advise to submit all the informations you can find to the support, and then try to repair or reinstall. It is possible to be another product installed that might conflict with the installation, so try to check if you have any other (security or not) programs installed that might interfere with it, if you can make this assumption and/or determination.