BSOD ntoskrnl.exe Help

Hi,
It seems Zone Alarm that cause BSOD problem.
Uninstall ZA completely then turn on your Windows Firewall.
http://download.zonealarm.com/bin/fr...cpes_clean.exe

Update this driver:
ISODrv64.sys Fri Nov 02 19:21:18 2007 → EZB Systems driver

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e59000 PsLoadedModuleList = 0xfffff800`03096e50
Debug session time: Sun Jan  9 02:18:30.722 2011 (GMT-8)
System Uptime: 0 days 1:31:37.863
Loading Kernel Symbols
...............................................................
................................................................
.......................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, 80050031, 6f8, fffff80002e91ec0}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

Followup: MachineOwner
---------

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002e91ec0

Debugging Details:
------------------


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002ec8ca9 to fffff80002ec9740

STACK_TEXT:  
fffff880`031e8de8 fffff800`02ec8ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`031e8df0 fffff800`02ec7172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031e8f30 fffff800`02e91ec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`009bfe00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02ec7172 90              nop

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID:  X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner
---------

shivmas said:

thanks alot, i have uninstalled zone alarm and updated ultra iso
hopefully this is enough, will wait and see!

You're welcome.
We'll see how it goes

Uninstall Eset NOD antivirus and replace it with MSE.
http://www.microsoft.com/security_essentials/

Update or reinstall your Synaptics device driver:
Drivers | Synaptics

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03061000 PsLoadedModuleList = 0xfffff800`0329ee50
Debug session time: Mon Jan 24 04:02:02.886 2011 (GMT-8)
System Uptime: 0 days 3:17:22.915
Loading Kernel Symbols
...............................................................
................................................................
...................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007ae66c0, fffff800045be518, fffffa800b7a83e0}

*** WARNING: Unable to verify timestamp for SynTP.sys
*** ERROR: Module load completed but symbols could not be loaded for SynTP.sys
Probably caused by : SynTP.sys

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007ae66c0, Physical Device Object of the stack
Arg3: fffff800045be518, Functional Device Object of the stack
Arg4: fffffa800b7a83e0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800b7a83e0

DEVICE_OBJECT: fffffa800a634920

DRIVER_OBJECT: fffffa800a1b3880

IMAGE_NAME:  SynTP.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c3fa15c

MODULE_NAME: SynTP

FAULTING_MODULE: fffff88002e34000 SynTP

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80003140273 to fffff800030d1740

STACK_TEXT:  
fffff800`045be4c8 fffff800`03140273 : 00000000`0000009f 00000000`00000003 fffffa80`07ae66c0 fffff800`045be518 : nt!KeBugCheckEx
fffff800`045be4d0 fffff800`030dd29e : fffff800`045be618 fffff800`045be618 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292b0
fffff800`045be570 fffff800`030dcdd6 : fffffa80`0cb65b18 fffffa80`0cb65b18 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`045be5e0 fffff800`030dd4be : 0000001b`92ed6e62 fffff800`045bec58 00000000`000b9574 fffff800`0324f108 : nt!KiProcessExpiredTimerList+0xc6
fffff800`045bec30 fffff800`030dccb7 : 00000005`039d8dc3 00000005`000b9574 00000005`039d8d32 00000000`00000074 : nt!KiTimerExpiration+0x1be
fffff800`045becd0 fffff800`030d9eea : fffff800`0324be80 fffff800`03259c40 00000000`00000002 fffff800`00000000 : nt!KiRetireDpcList+0x277
fffff800`045bed80 00000000`00000000 : fffff800`045bf000 fffff800`045b9000 fffff800`045bed40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_SynTP.sys

BUCKET_ID:  X64_0x9F_IMAGE_SynTP.sys

Followup: MachineOwner
---------