Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.
|
|||||||
Begin your free trial now
Pay-as-you-go options starting at $10/user/month
Pay-as-you-go options starting at $10/user/month
BSOD due to Zonealarm? debug log attached
|
|
Thread Tools | Search this Thread |
|
#1
|
|||
|
|||
|
BSOD due to Zonealarm? debug log attached
Hi everyone. Lately my computer has been crashing on average every 8 hours.
I'm pretty sure Zonealarm is to blame but I don't know why it crashes. Can some1 with more expert knowledge look at the debug log file and confirm that ZoneAlarm is indeed the problem? I'm running Windows XP SP2 and Zonealarm client pro latest version. Opened log file 'c:\debuglog.txt' kd> .sympath Symbol search path is: kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q Loading Kernel Symbols ........................................................................... ........................................................................... ............. Loading User Symbols Loading unloaded module list .................. Unable to load image vsdatant.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for vsdatant.sys *** ERROR: Module load completed but symbols could not be loaded for vsdatant.sys *************************************************************************** **** * * * Bugcheck Analysis * * * *************************************************************************** **** KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: b7357e47, The address that the exception occurred at Arg3: b616e6f4, Trap Frame Arg4: 00000000 Debugging Details: ------------------ |
|
#2
|
||||
|
||||
|
Hi. Try to unnistall it, delete temp files using CCleaner (registry includes) and install it again.
Regards
|
|
#3
|
||||
|
||||
|
If you could attach two or three minidumps that would help to confirm the ZA theory.
Have you changed any of the default settings in ZA recently, or added any other software ? In my humble etc... ZA pro is a bit bloated, and Comodo or Kerio are better options. |
|
#4
|
|||
|
|||
|
I have changed lots of ZA options but not recently.
However, for the past 2-3 days I have shut down ZA and the PC never crashed once (untill today that is that it froze without a BSOD suddently). Still 3 days of trouble free operation without ZA was an improvement. Comodo or Kerio you say? I might try them. The ZA lates versions (last 2 years) also take ages to start and use lots of resources |
![]() |
| Similar Topics | ||||
| Topic | Replies | Forum | ||
BSOD have debug from Win Debugger
|
2 | Windows BSOD, Freezing, Restarting Help | ||
Windows XP BSOD Minidump Debug Log
|
4 | Windows BSOD, Freezing, Restarting Help | ||
BSOD, have done debug, logs included
|
4 | Windows BSOD, Freezing, Restarting Help | ||
Game crashing problems and BSOD debug info
|
5 | Windows BSOD, Freezing, Restarting Help | ||
debug file attached, can anyone tell me what it means?
|
2 | Windows OS | ||
| Thread Tools | Search this Thread |
|
|
All times are GMT -4. The time now is 09:24 AM.



BSOD have debug from Win Debugger