There are several BitDefender users posting WhoCrashed output in the BSOD, Crashes, Kernel Debugging board that show that mwac.sys (Malwarebytes Web Access Control) was the last driver to load before a BAD_POOL_CALLER BSODs. The output from one of these WinDbg analyses is shown.
#Firefox 37.0 windows xp sp2 download full#
It required a full analysis of the crash dumps with the Windows Debugger Tool WinDbg to show that crashes were in fact caused by the EasyTuneEngine driver, and once the EasyTune utility was uninstalled and Norton was reinstalled the crashes stopped. was loaded into memory at the time of the crashes but did not indicate that any Gigabyte driver was involved in the crash.
BlueScreenView would show that the Gigabyte driver gdrv.sys used by multiple Gigabyte utilities such as Fast Boot, EasyTune, Smart Backup, etc. Utilities like BlueScreenView and WhoCrashed are usefull tools but will only show the last driver loaded into memory before the crash. In most cases BlueScreenView or WhoCrashed would show a crash caused by Microsoft files ntoskrnl.exe (Windows NT Operating System Kernel) or hal.dll (Hardware Abstraction Layer), and not a Norton driver. BSODs stopped when Norton was removed from their system. BSODs would only occur when the Norton AV was running a scan or performing a background idletime task. Just a bit more info to clarify my last post about BSODs reported in the Norton forum by users with Gigabyte motherboards. About the crash bios, it's not systematic. Many of m'y customers who use Mbam and Bitdefender encounter this issue. Only fresh w10, bitdef, mbam premium, firefox to get bsod. I have not installed Asus or Gigabyte apps. Thanks for the answer but without Mbam there is no problem on Z87, Z97 or Z170 GA or Asus motherboard, same thing on old P55.
0 kommentar(er)
