Unusual Crash Related To Vsserv.exe
I'm getting an BSOD under unusual circumstances that may be pointing to a glitch in Bitdefender. Dunno if you'll be able to replicate this or not, but I'll explain things the best I can and upload a minidump.
I'm running Calibre 2.4.0 x64 on Windows 10 x64
When I engage the bulk Download Metadata function (CTRL-D after selecting several books), the program automatically downloads book info. After a while the whole system crashes. So I decided to look at the minidump.
It comes up with this message.
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8009924df13, ffffd00022524fb0, 0}
*** WARNING: Unable to verify timestamp for bdfwfpf.sys
*** ERROR: Module load completed but symbols could not be loaded for bdfwfpf.sys
Probably caused by : NETIO.SYS ( NETIO!StreamProcessCallout+793 )
So I click on !analyze and it points me to this:
CPU_COUNT: 4
CPU_MHZ: c79
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3c
CPU_STEPPING: 3
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: vsserv.exe
CURRENT_IRQL: 0
ANALYSIS_VERSION: 10.0.10240.9 amd64fre
LAST_CONTROL_TRANSFER: from fffff8009924b555 to fffff8009924df13
VSSERV.exe is related to BitDefender, so that's why I come here- the crash hasn't come up at any other time; only after the recent update to windows 10 (KB2267602) has it occurred. The BSOD only happens why I run the automated metadata download for over 50 books- it doesn't seem to occur at any other time, or when manually downloading metadata. Also, the Debug minidump doesn't say anything about Calibre, so I don't get it.
I've included the most recent minidump- hope it's helpful in some form.
https://www.dropbox.com/s/kwceerlzrzpzvdn/N...rchive.zip?dl=0
Comments
-
I upgraded Calibre to 2.4.1. and I have yet to replicate the BSOD crash. It could be fixed; I'll keep trying to replicate but for now, put this issue on your back burner.
0