You may cancel your Bitdefender subscription from Bitdefender Central or by contacting Customer Support at: https://www.bitdefender.com/consumer/support/help/
Thank you for your understanding.
Bdselfpr.sys Blue Screen On Windows 10
I had to uninstall BitDefender . It always causes a BSOD screen.
This is the dump:
==================================================
Dump File : 073115-31781-01.dmp
Crash Time : 31/07/2015 20.26.28
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 0xc0000005
Parameter 2 : 0x9177c056
Parameter 3 : 0x00000001
Parameter 4 : 0x0044002c
Caused By Driver : bdselfpr.sys
Caused By Address : bdselfpr.sys+c056
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address : ntoskrnl.exe+1262c4
Stack Address 1 : ntoskrnl.exe+13a452
Stack Address 2 : ntoskrnl.exe+13a424
Stack Address 3 : ntoskrnl.exe+2e6b0
Computer Name :
Full Path : C:\WINDOWS\Minidump\073115-31781-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 10240
Dump File Size : 151.664
Dump File Time : 31/07/2015 20.28.07
==================================================
Help please
Comments
-
I've the same problem on two different machines since I've upgraded my Windows 7 Pro to Windows 10 Pro.
I can easily trigger the issue by opening a terminal (Start->cmd) and then click on the red cross in the upper right corner of the window to close the terminal. ->kmode_exception_not_handled (bdselfpr.sys)
After renaming the file in safe mode into bdselfpr.s_ and restart Windows the problem is gone. The file is from 16.07.2013 with SHA-1 3C6FA0C25F0EB6782E2DE45121621771A3B81DC1
Maybe the driver needs an update for Windows 10?
Best regards
usery0 -
I've the same problem on two different machines since I've upgraded my Windows 7 Pro to Windows 10 Pro.
I can easily trigger the issue by opening a terminal (Start->cmd) and then click on the red cross in the upper right corner of the window to close the terminal. ->kmode_exception_not_handled (bdselfpr.sys)
After renaming the file in safe mode into bdselfpr.s_ and restart Windows the problem is gone. The file is from 16.07.2013 with SHA-1 3C6FA0C25F0EB6782E2DE45121621771A3B81DC1
Maybe the driver needs an update for Windows 10?
Best regards
usery
Using registered Family pack, but:
I have the same problem with my new Windows 10 installation, each time I close either a cmd or powershell screen with the X I get a BSOD, and to stop using the X is not an option, please look into this and issue a fix ASAP
Best regards, Kent0 -
I had reported this bug some weeks ago so they knew about it but didn't do anything back then. They just said "is not yet officially compatible with Windows 10". How bad can a "security company" be? Wasn't it obvious that thousands of people are using their product and would upgrade to Windows 10 which automatically would render the PC unusable, and not even enter the recovery?
Thank god I was on the insider program and noticed this bug already on build 10240 two weeks before 29th of July and I was prepared :-) I also had warned all my friends, who actually bought Bitdefender because of me over the last couple of years. And because of me too, they uninstalled Bitdefender from all their PCs and will never ever by any product again by this company, like myself.
I recommend using Panda Free Antivirus. It also uses much less RAM, and has lots of better configuration, for example let you ask before disinfection, and not like Bitdefender, deletes system files without a warning.0 -
.. they uninstalled Bitdefender from all their PCs and will never ever by any product again by this company, like myself.
Well I think this is too hard. The official Version of Windows 10 is out since only a few days, so give the developers a chance.
Well, I'm not a developer, but maybe I found some intereressting issue. Or maybe it's nothing, then forgive me.
In the registry Keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdfwfpf
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
I found strange looking values for the ImagePath Key:
\??\C:\Program Files\Bitdefender\Antivirus Free Edition\bdfwfpf.sys
\??\C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
Should \??\ be really part of the path?0 -
I find two "solutions" for my problem.
First one is to change the value in the registry key ImagePath in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
From \??\C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
to C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
I'm not sure, what this \??\ really means, but it works for me.
Second one is to change the value in the registry key Start in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
From 1 to 4.
I found this idea in this thread. Maybe someone could explain what's the difference between the values 1 and 4.
Both methods works for me, but I prefer the first one. At least I can close CMD on the regular way again.
Update:
Based on this thread the Start value 4 means, that this driver is stopped. So changing the path seems to be the better way. Right?0 -
I'm not sure, what this \??\ really means, but it works for me.
Maybe this or for experts this gives an explanation?At least I can close CMD on the regular way again.
I forgot to say, the non regular way to close cmd without using my "dirty hacks" and without bsod, was to close it with the task manager.0 -
Well I think this is too hard. The official Version of Windows 10 is out since only a few days, so give the developers a chance.
Absolutely not!? There is a reason why there are beta programs. Hello? This is one of the most used Anti-Virus programs, it isnt a small company or whatsoever. We are talking about their product leading to rendering an OS unusable, where the date was loooong set, they new Windows 10 was coming, they had long time to test their products. They could had implemented a warning or a fix inside the program long before the release.0 -
I found out that there are only two drivers on my whole system they are using these \??\ pathes.
Bitdefenders bdfwfpf.sys and bdselfpr.sys
You can check this with:driverquery /V > Desktop\driverinfo.txt
Did you tried out my \??\ suggestion?0 -
after selection option 1. there is no system crash now... but firewall is disabled now. after applying registry we cant off on windows firewall settings.. any idea how to fix this..
0 -
I find two "solutions" for my problem.
First one is to change the value in the registry key ImagePath in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
From \??\C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
to C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
I'm not sure, what this \??\ really means, but it works for me.
Second one is to change the value in the registry key Start in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
From 1 to 4.
I found this idea in this thread. Maybe someone could explain what's the difference between the values 1 and 4.
Both methods works for me, but I prefer the first one. At least I can close CMD on the regular way again.
Update:
Based on this thread the Start value 4 means, that this driver is stopped. So changing the path seems to be the better way. Right?
after selection option 1. there is no system crash now... but firewall is disabled now. after applying registry we cant off on windows firewall settings.. any idea how to fix this..0 -
after selection option 1. there is no system crash now...
Do you mean the Windows Firewall? My Firewall still works.0 -
The free version is working fine except that the web scanning is not. No blue screens though.I had to uninstall BitDefender . It always causes a BSOD screen.
This is the dump:
==================================================
Dump File : 073115-31781-01.dmp
Crash Time : 31/07/2015 20.26.28
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : 0xc0000005
Parameter 2 : 0x9177c056
Parameter 3 : 0x00000001
Parameter 4 : 0x0044002c
Caused By Driver : bdselfpr.sys
Caused By Address : bdselfpr.sys+c056
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Crash Address : ntoskrnl.exe+1262c4
Stack Address 1 : ntoskrnl.exe+13a452
Stack Address 2 : ntoskrnl.exe+13a424
Stack Address 3 : ntoskrnl.exe+2e6b0
Computer Name :
Full Path : C:\WINDOWS\Minidump\073115-31781-01.dmp
Processors Count : 2
Major Version : 15
Minor Version : 10240
Dump File Size : 151.664
Dump File Time : 31/07/2015 20.28.07
==================================================
Help please0 -
I find two "solutions" for my problem.
First one is to change the value in the registry key ImagePath in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
From \??\C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
to C:\Program Files\Bitdefender\Antivirus Free Edition\bdselfpr.sys
I'm not sure, what this \??\ really means, but it works for me.
Second one is to change the value in the registry key Start in:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\bdselfpr
From 1 to 4.
I found this idea in this thread. Maybe someone could explain what's the difference between the values 1 and 4.
Both methods works for me, but I prefer the first one. At least I can close CMD on the regular way again.
Update:
Based on this thread the Start value 4 means, that this driver is stopped. So changing the path seems to be the better way. Right?
Brilliant, your first solution worked for me. Life saver because I've got a programming exam tomorrow and the command prompt kept crashing! Clumsy work from bit defender IMO.0 -
Brilliant, your first solution worked for me. Life saver because I've got a programming exam tomorrow and the command prompt kept crashing! Clumsy work from bit defender IMO.
Bitdefender Free is not compatible with Windows 10 and should not be used. It's still fine in other Windows versions. You should switch to another free product or get the paid version of BD for the time being. They have said that a new free version is coming but have given no timeframe.0
