Bdelam.sys Crashing Windows 10
As stated in the title, I recently reinstalled Bitdefender 2015 on Windows 10, during the installation I got a BSOD, the next day I bored my computer and it immediately went to Windows recovery, stating that the file C:\Windows\system32\drivers\bdelam.sys had caused a critical error and Windows can't boot.
So to remedy, I tried connecting my HDD to my wife's computer and delete the file. This showed my computer to boot up normally, so I went back in and tried to get Bitdefender all good to go, a couple minutes later the computer froze, when I restarted, it went right back to the critical error.
In this article I have "ENTER to retry" and "F8 to go to system settings" but neither option works, F8 didn't even go to options, not sure if that's related or just a Windows issue. Any help or input would be greatly appreciated.
Comments
-
Hello Wardjp,
At the moment Bitdefender are not offering any support for their product with Windows 10. There have been a number of topics where other members have been able to get it to work successfully, a forum search will find them.
Ro.0 -
Well that's good to know, considering I just renewed my subscription with them
0 -
I think the point is that at the moment Microsoft are getting nearer to releasing Win 10, when they release the RC I expect to see Bitdefender release their beta for 2016. With the rapid changes and additions there have been to Win 10 it would be difficult for BD to keep up with producing a top quality antivirus.
0 -
I agree and understand, just frustrating when things like this break the entire pc
0 -
I agree and understand, just frustrating when things like this break the entire pc
Hi Wardjp,
Windows 10 is still a beta(*) version - the safest one supposed to be delivered in summer, it is logical to get issues with it.
You are brave enough to be a test user ( I usually wait a few years and only get the most stable stuff
) I hope you save your data on a back-up hard disk before using W10.
Regards,
L.
(*) in french, bêta means "a bit dumb".
0 -
Some requirements have been changed for ELAM and related components for Windows 10 and the problems should be addressed by RTM.
Thank you for reporting.
Edit: forgot to ask. Could you please provide the Windows build number and architecture that you were able to reproduce this on? It would be slightly faster to narrow down the issue with that information. Thank you.0 -
Build 10074, I was using Bitdefender 2015. If you'll clarify what information you're looking for with architecture, I'll gladly provide whatever you need, always glad to help, I got it resolved for now by refreshing my Windows 10, it 'archived' all my files in windows.old and gave me a fresh install. However, like I said, if you can elaborate on the information you're looking for as a response to the architecture, I will gladly provide that information asap.
0 -
So again, with some sleep and attention:
- Do you use a 32 bit or 64 bit build of Windows.
- Is your system booting in EFI or legacy mode?
- Does your system have Secure Boot enabled?
- Have you upgraded from a previous version of Windows, or installed a clean copy after a format/on a clean drive
The first three can be found by running msinfo32.exe (just type that in windows search) and looking for System Type, BIOS Mode and Secure Boot State.
Thank you.0 -
So sorry for the delay, long work hours had me almost forget about this! And after I thought about that, I realized what you meant with architecture lol, my apologies. As for those questions:
- 64 bit
- I have EFI on my motherboard SAID to be exact)
- I'll check that tonight after work
- I was running the most recent release of Windows 10, Build 10074 I believe, not a fresh install, but was updated from the previous.build.0 -
So, I stand corrected, according to System Information, my BIOS mode is Legacy. However, I have loaded my BIOS many times and it is the ASUS EFI BIOS. As for secure boot state, it displays as Unsupported.
0 -
Windows 10 will be pushed through probably security updates on July 29th as per reports in the media. One just needs to reserve the update which can be cancelled before July 29th if one changes their mind. I don't expect there will be a so called RC in the classic sense of the phrase. Microsoft will just keep pushing through new W10 TP Builds until we get to July 29th.
If you on board for the update through the Microsoft reserve process you will get the build that Microsoft releases on July 29th. Since July 29th is just eight weeks away I see no reason why anyone would want to upgrade from Windows 7 or Windows 8.X to Windows 10 before it gets pushed through on July 29th. Those currently using the latest slow or fast ring Windows 10 TP build should get the official RTM build update on July 29th like those upgrading from W7 and W8.X.
When Bitdefender will have a Windows 10 compatible and supported version of any of their products is anyone's guess. However, my guess is there will be no beta but just an update like any other update sometime before July 29th.0 -
Sorry for the delay. We've looked at a couple of clean install scenarios on both EFI and Legacy boot but were unable to reproduce the specific crash you mentioned. Upgrade tests are more time-consuming and are not really that relevant at this stage in development. I'd suggest holding back for a bit closer to Windows 10 RTM.
0 -
Sorry for the delay. We've looked at a couple of clean install scenarios on both EFI and Legacy boot but were unable to reproduce the specific crash you mentioned. Upgrade tests are more time-consuming and are not really that relevant at this stage in development. I'd suggest holding back for a bit closer to Windows 10 RTM.
I have the exact same problem. My system: dual boot on two ssd drives ( main and backup), two further drives grouped to form a raid 1 system. The win10 install runs without any problems, but as soon as I install bitdefender the system crashes at approx. 95% completion. What is worse is that my windows boat loader is ###### up and that my raid system is ###### up after the install.
" /> I managed to reproduce this crash 4 times at different points of the win 10 install.
hope you find a solution quickly, because I will not upgrade my main system until you find a solution.0
