Bitdefender 2013 Total Security
hi i am getting blue screens and the computer crashes , i have used a program called whocrashed and it found out that bitdefender is the cause of this problem is there a way to fix it thanks
computer name: GIZMO-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: AuthenticAMD AMD Athlon 64 X2 Dual Core Processor 4600+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 3220561920 total
VM: 2147352576, free: 1940246528
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Thu 27/09/2012 12:07:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092712-13343-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFFB098B000, 0x1, 0xFFFFFFFF82C46853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Thu 27/09/2012 12:07:30 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: avc3.sys (avc3!SetAvckfStopRoutine+0x178F)
Bugcheck code: 0x50 (0xFFFFFFFFB098B000, 0x1, 0xFFFFFFFF82C46853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\drivers\avc3.sys
product: BitDefender AVC
company: BitDefender
description: Active Virus Control filter driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: avc3.sys (Active Virus Control filter driver, BitDefender).
Google query: avc3.sys BitDefender PAGE_FAULT_IN_NONPAGED_AREA
On Mon 24/09/2012 09:35:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092412-24375-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x12068C)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF8573D3D0, 0xFFFFFFFF8573D3D0, 0x7BB7EF00)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Fri 21/09/2012 12:50:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\092112-13015-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x39853)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000006, 0xFFFFFFFF82C48853, 0xFFFFFFFFA6479B58, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 18/09/2012 12:05:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091812-15937-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFFB01DC000, 0x1, 0xFFFFFFFF82C4B853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 15/09/2012 10:08:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-12796-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFFA3C00000, 0x1, 0xFFFFFFFF82C73853, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sat 15/09/2012 10:00:20 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091512-13390-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0xBE (0xFFFFFFFFA4519000, 0xFFFFFFFFB58E7101, 0xFFFFFFFFAA76FB58, 0xB)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a driver attempts to write to a read-only memory segment.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Sun 09/09/2012 10:33:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090912-29500-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2842C0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82EBD2C0, 0xFFFFFFFFAA845B70, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 27/08/2012 10:52:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082712-15125-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFFABC81000, 0x1, 0xFFFFFFFF82C39853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 27/08/2012 10:44:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082712-15109-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFFAA24D000, 0x1, 0xFFFFFFFF82C44853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Mon 27/08/2012 10:05:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082712-17875-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFF897E6000, 0x1, 0xFFFFFFFF82C46853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 21/08/2012 15:28:44 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-17656-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x120F1F)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFF82D75F1F, 0xFFFFFFFF8D313B40, 0xFFFFFFFF8D313720)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 21/08/2012 15:10:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-12218-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x12068C)
Bugcheck code: 0x19 (0x3, 0xFFFFFFFF8573C2A0, 0xFFFFFFFF8573C2A0, 0x0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Tue 21/08/2012 11:27:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082112-14093-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x8E3BF)
Bugcheck code: 0x50 (0xFFFFFFFFAA807000, 0x1, 0xFFFFFFFF82C76853, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
On Wed 15/08/2012 10:02:49 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081512-11828-01.dmp
This was probably caused by the following module: ntkrnlpa.exe (nt+0x2842C0)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF82E8B2C0, 0xFFFFFFFF9DE7FB70, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\ntkrnlpa.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
19 crash dumps have been found and analyzed. Only 15 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
avc3.sys (Active Virus Control filter driver, BitDefender)
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.
Comments
-
Hello
A product update was released. Your build should be 16.23.0.1637(please right click on Bitdefender icon from system tray-near the clock-and choose "About". You should see in the left side the build number).
In order for the product update to be installed, you need to reboot your machine(you should see in the Events -> "Reboot required" under the Update module).
Changelog:
http://forum.bitdefender.com/index.php?sho...st&p=162888
http://forum.bitdefender.com/index.php?showtopic=35499
Let me know if the situation is solved.
Have a nice day.0
