Im getting BSOD after installing bitdefender 2015 suite? Windows 7 x64

I am actually amazed this bug still exists in Bitdefender. It's been years and I keep seeing it, so maybe it's time to actually document it.

It's impossible to show/explain with a small dump, so can you do two things for me?

1 (do first!). Get me the kernel dump from C:\Windows (MEMORY.DMP). Upload it to a site of your choice and paste the link in your next reply (reply with link before following #2).

2. After #1 is done (remember, do #1 first), enable Driver Verifier so it will catch Bitdefender and I can explain it even further. Follow step #1 again to give me the verifier enabled kernel dump after the system crashes with verifier enabled.

The reason for doing #1 first is by default, kernel dumps are overwritten after each crash. It's best to keep it that way, and that's why it's important to do #1 first, so I also have a non-verifier enabled kernel dump to compare. With both a normal kernel dump/verifier enabled kernel dump, I can explain in as much detail to you as I can as to what is going wrong, and maybe even tell Bitdefender to fix their damn software.
 
No problem.

Secondly.... my MEMORY.DMP file is 767MB!!..... is that normal?
Click to expand...

Yep, as a kernel dump contains the entire kernel memory space that was in use at the time of the bug check. In your case, that's how much there was. It can get as high as a gig on certain machines.

Anyway, that's why it's so informative for situations like this. A small dump barely contains any useful information for this bug check, and situation especially. Every time I've had this Bitdefender bug pop up, I've never gotten a chance to get both a kernel/verifier kernel dump, so I could never find out why it happens as it's never been publicly documented.

Hopefully we can do it this time around : )
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top