Sign in to follow this  
jrv116psu

Adaware Causes Blue Screen of Death

Recommended Posts

I'm an IT Director of a software development company.. To the best of my knowledge at this point, Adaware seems to be causing my machine to throw a 0x00000093 stop error repeatedly. (within 15 minutes of booting.. often almost immediately after login).. I have only been testing adaware uninstalled for 120 minutes so it's not completely conculsive .. but it's pretty close. (no crashes so far)..

Heres more info:

There's also a dmp file listed below.. I can give you more examples of dmps if you need them....

'm not sure what's causing this but it's driving me crazy. The problem started occurring approximately 10 days ago. To the best of my knowledge I did not install any new software and I can say for certain I did not install any new hardware. In normal mode in Windows 7 x64, I get a blue screen somewhat randomly, although often within 1-3 minutes of booting up. (after logging in) .. I've tried logging in with different users. Same thing. It does not seem to crash during startup, (it has crashed while waiting for me to login) .. It does not seem to crash in safemode. Which points me at a kernel-mode driver. But I have no idea where to even begin to look.

Here's the output from the tool "Who Crashed"

I'm also uploading a copy of my last dump to here:

[url="http://www.blackhawkconsulting.com/dump1.dmp"]http://www.blackhawkconsulting.com/dump1.dmp[/url]

The file is about 600 MB so ...

If anyone can help me with this I'd really appreciate it.

System Information (local)
computer name: HP2015DN
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core(tm) i7 CPU X 920 @ 2.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 8577830912 total
VM: 2147352576, free: 1998946304


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Sun 5/8/2011 1:09:57 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-42026-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x93 (0xC4C, 0xFFFFF8A0000016C0, 0xFFFFF8A004A47130, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/8/2011 1:09:57 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: kernexplorer64.sys (KernExplorer64+0x1277)
Bugcheck code: 0x93 (0xC4C, 0xFFFFF8A0000016C0, 0xFFFFF8A004A47130, 0x1)
Error: INVALID_KERNEL_HANDLE
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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: kernexplorer64.sys .
Google query: kernexplorer64.sys INVALID_KERNEL_HANDLE




On Sun 5/8/2011 1:04:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-83195-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x93 (0x22F8, 0xFFFFF8A0000016C0, 0xFFFFF8A004DBABE0, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/8/2011 1:00:30 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-68078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x93 (0xDC4, 0xFFFFF8A0000016C0, 0xFFFFF8A0033EA710, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/8/2011 12:50:31 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-66269-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x93 (0x2380, 0xFFFFF8A0000016C0, 0xFFFFF8A004C1FE00, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/8/2011 12:44:55 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-67626-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x93 (0x2244, 0xFFFFF8A0000016C0, 0xFFFFF8A00590D910, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/8/2011 12:40:17 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-71089-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF880079DEC61)
Bugcheck code: 0x93 (0x26E8, 0xFFFFF8A0000016C0, 0xFFFFF8A00F8D4BA0, 0x1)
Error: INVALID_KERNEL_HANDLE
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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: Unknown .
Google query: Unknown INVALID_KERNEL_HANDLE




On Sat 5/7/2011 9:41:38 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-55879-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x3588, 0xFFFFF8A000001790, 0xFFFFF8A002633620, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/7/2011 9:31:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-54444-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x3350, 0xFFFFF8A000001790, 0xFFFFF8A002A93D40, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/7/2011 7:36:48 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-54413-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x23E4, 0xFFFFF8A000001790, 0xFFFFF8A00D5A8F90, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/7/2011 7:31:23 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-78920-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x2A70, 0xFFFFF8A000001790, 0xFFFFF8A00D2149C0, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/7/2011 6:13:32 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-57564-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x2864, 0xFFFFF8A000001790, 0xFFFFF8A00DD69190, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/7/2011 12:53:54 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-23961-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88006482C61)
Bugcheck code: 0x93 (0x286C, 0xFFFFF8A000001790, 0xFFFFF8A00E4E61B0, 0x1)
Error: INVALID_KERNEL_HANDLE
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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: Unknown .
Google query: Unknown INVALID_KERNEL_HANDLE




On Sat 5/7/2011 3:11:50 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50711-54225-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x239C, 0xFFFFF8A000001790, 0xFFFFF8A00C561E70, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
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 5/7/2011 2:59:15 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump50611-57439-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0x93 (0x2990, 0xFFFFF8A000001790, 0xFFFFF8A00D1FF640, 0x1)
Error: INVALID_KERNEL_HANDLE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that an invalid or protected handle was passed to
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


Conclusion
27 crash dumps have been found and analyzed. Only 15 are included in this report. 6 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:

unknown

kernexplorer64.sys

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.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Share this post


Link to post
Share on other sites
Same here, BSOD. Uninstalled, reinstalled. same problem. Started about a month ago. I turn off AdAware throughout the day, no more BSOD, and only use for periodic scans.

Interestingly, it keeps reloading even though I turned it off. Odd. Not on scheduler...

Share this post


Link to post
Share on other sites
Hi,

Lavasoft is investigating your issues with BSOD.

Share this post


Link to post
Share on other sites
Hello Jesse,

I have a few questions regarding this issue.
[list]
[*]Could you list the security software (AV, Firewall etc) you have installed
[*]Which Ad-Watch features are enabled. (Files, Processes, Registry, Network)
[/list]
I would greatly appreciate if you would test the following on your machine (you do not have to have Ad-Aware installed):
([b]Warning: your computer could potentially crash[/b])
[list=1]
[*]Download and "install" Process Explorer (Latest version 14.11) from [url="http://download.sysinternals.com/Files/ProcessExplorer.zip"]here[/url]
[*]Start Process Explorer with Administrator rights
[*]Press Control + H to enable handle view
[*]Find a process named 'System' (should have PID 4) and click it.
[*]Thats it, please report any problems you encounter doing this.
[/list]
Thanks

/Andreas - Developer

Share this post


Link to post
Share on other sites
Had the BSOD during the install process.
Dwld & Instd files and follow procedure.
Now the 2011 version is working thanks!



[quote name='LS Andreas' post='126801' date='May 16 2011, 08:16 AM']Hello Jesse,

I have a few questions regarding this issue.[list]
[*]Could you list the security software (AV, Firewall etc) you have installed
[*]Which Ad-Watch features are enabled. (Files, Processes, Registry, Network)
[/list]I would greatly appreciate if you would test the following on your machine (you do not have to have Ad-Aware installed):
([b]Warning: your computer could potentially crash[/b])[list=1]
[*]Download and "install" Process Explorer (Latest version 14.11) from [url="http://download.sysinternals.com/Files/ProcessExplorer.zip"]here[/url]
[*]Start Process Explorer with Administrator rights
[*]Press Control + H to enable handle view
[*]Find a process named 'System' (should have PID 4) and click it.
[*]Thats it, please report any problems you encounter doing this.
[/list]Thanks

/Andreas - Developer[/quote]

Share this post


Link to post
Share on other sites
I have purchased but been unable to use my lavasoft program for over a year awaiting a fix. Unlike my first instal my laptop is also a year old. I cannot afford another blue screen episode as it causes and entire loss of memory.

Is this confirmed fixed? And can those of us who could not use (I should have no update history) get some sort of refund/extended subscription no cost?

Share this post


Link to post
Share on other sites
Hi bcjammer,

BSOD can be caused by many things. Even if two computers have BSOD, that in some way or another is related to Ad-Aware, it might be different bugs causing the BSOD in the two computers, and it might even be a bug in another program that isn't triggered until Ad-Aware is installed or it could be a bad sector on the hard disk that corrupted an Ad-Aware file. I know that bugs have been fixed in every release of Ad-Aware 9, but it is impossible to know if one of the fixes solves your specific problem.

Since Jesse never came back with the necessary information to do an investigation, it is even impossible to know if his problem has been solved in one of the 5 later releases of Ad-Aware 9.

Regarding refunds/extension you have to contact Lavasoft support team: http://lavasoft.com/mylavasoft/support/supportcenter/contact_support

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this