BSOD! Crashes, Random Restarts- Firefox related ?

Tudor

Solid State Member
Messages
17
Hello guys .. so here's my problem: since yesterday my PC is running very weird when i open Firefox 12(running on Windows XP SP2). The browser randomly crashes, when it doesn't crash the pages don't load, and also i think it causes BLUE SCREEN OF DEATH ! I thought i might have caught a virus, so i used System Restore to get back to a previous day when all was fine, i scanned my PC with Avira, i used Registry Mechanics to check for errors on registries and other files, i checked the PC with SpyBot Search&Destroyed and immunized my PC, and used HD Tune to verify the integrity of the HDD. ALL RESULTS WERE GOOD ! I can't find the problems that making my PC show the BSOD. I installed WhoCrashed and got these results , can anyone PLEASE HELP ME interpret them, because i don't understand much that it says.
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Sun 03.06.2012 16:11:03 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060312-03.dmp
This was probably caused by the following module: win32k.sys (win32k+0xB4899)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8B4899, 0xFFFFFFFFA776BBC0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 03.06.2012 13:03:09 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060312-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x100D5)
Bugcheck code: 0x10000050 (0xFFFFFFFFC08C1B24, 0x0, 0xFFFFFFFF804E70D5, 0x2)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 03.06.2012 12:53:15 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini060312-01.dmp
This was probably caused by the following module: d347bus.sys (d347bus+0xD7AC)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8054B585, 0xFFFFFFFFF81E65B0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\d347bus.sys
product:
company:
description: PnP BIOS Extension
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.
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: d347bus.sys (PnP BIOS Extension, ).
Google query: d347bus.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M




On Fri 28.10.2011 17:18:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini102811-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0x16DA)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8016DA, 0xFFFFFFFFF8316A80, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 07.10.2011 12:48:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini100711-01.dmp
This was probably caused by the following module: avgntflt.sys (avgntflt+0x5A9B)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFF875C1A3, 0xFFFFFFFFAA76CAC8, 0xFFFFFFFFAA76C7C4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\avgntflt.sys
product: AntiVir Workstation
company: Avira GmbH
description: Avira Minifilter Driver
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.
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: avgntflt.sys (Avira Minifilter Driver, Avira GmbH).
Google query: avgntflt.sys Avira GmbH SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




On Fri 11.09.2009 18:30:04 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini091109-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x10877)
Bugcheck code: 0x100000EA (0xFFFFFFFF826F8DA8, 0xFFFFFFFF8246B8E8, 0xFFFFFFFFF89E9CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Fri 28.08.2009 15:06:46 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini082809-01.dmp
This was probably caused by the following module: ov519vid.sys (ov519vid+0x6F51)
Bugcheck code: 0x1000000A (0x68, 0x2, 0x0, 0xFFFFFFFF804DC25D)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ov519vid.sys
product: Dual Mode USB Camera 519
company: OmniVision Technologies, Inc.
description: Dual Mode USB Camera 519 Stream Class Mini Driver
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: ov519vid.sys (Dual Mode USB Camera 519 Stream Class Mini Driver, OmniVision Technologies, Inc.).
Google query: ov519vid.sys OmniVision Technologies, Inc. CUSTOM_ERROR




On Fri 26.06.2009 09:37:51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini062609-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x10877)
Bugcheck code: 0x100000EA (0xFFFFFFFF8263D840, 0xFFFFFFFF825DF308, 0xFFFFFFFFF89E1CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sun 14.06.2009 10:10:00 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini061409-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x10877)
Bugcheck code: 0x100000EA (0xFFFFFFFF826A2830, 0xFFFFFFFF826E2C78, 0xFFFFFFFFF89E5CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Sun 25.01.2009 21:37:05 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini012509-01.dmp
This was probably caused by the following module: ov519vid.sys (ov519vid+0x1B349)
Bugcheck code: 0x10000050 (0xFFFFFFFF8B90BFCC, 0x0, 0xFFFFFFFFA751A349, 0x0)
Error: CUSTOM_ERROR
file path: C:\WINDOWS\system32\drivers\ov519vid.sys
product: Dual Mode USB Camera 519
company: OmniVision Technologies, Inc.
description: Dual Mode USB Camera 519 Stream Class Mini Driver
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: ov519vid.sys (Dual Mode USB Camera 519 Stream Class Mini Driver, OmniVision Technologies, Inc.).
Google query: ov519vid.sys OmniVision Technologies, Inc. CUSTOM_ERROR




On Sat 31.05.2008 08:27:35 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini053108-01.dmp
This was probably caused by the following module: win32k.sys (win32k+0xE5F91)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFFBF8E5F91, 0xFFFFFFFFA7C1C698, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 17.02.2008 12:13:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021708-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x10877)
Bugcheck code: 0x100000EA (0xFFFFFFFF82C23908, 0xFFFFFFFF8292E898, 0xFFFFFFFFF8A69CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Wed 13.02.2008 13:42:25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini021308-01.dmp
This was probably caused by the following module: ati2cqag.dll (ati2cqag+0x10877)
Bugcheck code: 0x100000EA (0xFFFFFFFF82BC3720, 0xFFFFFFFF82BF4BD8, 0xFFFFFFFFF8A69CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\ati2cqag.dll
product: ATI Radeon Family
company: ATI Technologies Inc.
description: Central Memory Manager / Queue Server Module
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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: ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.).
Google query: ati2cqag.dll ATI Technologies Inc. THREAD_STUCK_IN_DEVICE_DRIVER_M




On Thu 06.09.2007 16:37:02 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\Mini090607-01.dmp
This was probably caused by the following module: d347bus.sys (d347bus+0xD862)
Bugcheck code: 0x1000008E (0xFFFFFFFFC0000005, 0xFFFFFFFF8057E811, 0xFFFFFFFFA8479AD4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\d347bus.sys
product:
company:
description: PnP BIOS Extension
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.
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: d347bus.sys (PnP BIOS Extension, ).
Google query: d347bus.sys KERNEL_MODE_EXCEPTION_NOT_HANDLED_M





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

14 crash dumps have been found and analyzed. 4 third party drivers have 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:

ov519vid.sys (Dual Mode USB Camera 519 Stream Class Mini Driver, OmniVision Technologies, Inc.)

ati2cqag.dll (Central Memory Manager / Queue Server Module, ATI Technologies Inc.)

d347bus.sys (PnP BIOS Extension, )

avgntflt.sys (Avira Minifilter Driver, Avira GmbH)

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.

Now i'm using Chrome to browse this forum, and till now all is going well..
 
I had Echofon, AccuWeather, Fireshot, Adblock and Greasemonkey .. i uninstalled mozilla yesterday though and my PC stopped crashing, but now i seem to have a Desktop Hijacker of some sort, because my wallpaper is a blue color, even though when i go to Desktop Proprieties i see my wallpaper. I ran antiviruses, spyware detectors registry cleaners but i can't seem to find any problems which is weird ... and it all started with Mozilla Firefox >.>
Also, my PC was stuck at 99 CPU usage because of DBLocalServer.exe , i deleted that, and it went back down to 0 CPU usage when im doing nothing.
 
I don't think it is Firefox, although it might look that way.

Since you suspect a desktop hijack, have you analysed a HijackThis log yet?

(Keep in mind that when using HijackThis, do not "Fix" unless you are absolutely sure what you are doing.)
 
the analysis came out good .. a few unnecessary files, and a single file that the Analyzer doesn't know what it is :
HKLM\System\CCS\Services\Tcpip\..\{7FB57FA8-98D7-498B-B0AC-643B4CA83B3C}: NameServer = 213.154.124.221 193.231.252.221
should i delete it ?
 
Back
Top Bottom