View Single Post
12 Nov 2011  
yowanvista

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by bshomaker View Post
I had no BSODs yesterday but just had another one today.

The suggestion to remove ZA - is that based on general experience or something specific based on items from the dump files?

Here is the latest dump.
Based on dumps which indicate bugcheck 7f caused by ZoneAlarm
It should be removed.
Code:
*******************************************************************************
*                                                                             *
*                        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: 0000000080050033
Arg3: 00000000000406f8
Arg4: fffff88004aec38c

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


OVERLAPPED_MODULE: Address regions for 'nvhda64v' and 'monitor.sys' overlap

BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  a

LAST_CONTROL_TRANSFER:  from fffff80002e921e9 to fffff80002e92c40

STACK_TEXT:  
fffff800`04cb2d28 fffff800`02e921e9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000406f8 : nt!KeBugCheckEx
fffff800`04cb2d30 fffff800`02e906b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`04cb2e70 fffff880`04aec38c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`237f3fe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessIsrVSync+0x64


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiProcessIsrVSync+64
fffff880`04aec38c e86b620000      call    dxgmms1!VidSchiUpdateCurrentIsrFrameTime (fffff880`04af25fc)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VidSchiProcessIsrVSync+64

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1

FAILURE_BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiProcessIsrVSync+64

BUCKET_ID:  X64_0x7f_8_dxgmms1!VidSchiProcessIsrVSync+64

Followup: MachineOwner
---------
My System SpecsSystem Spec