Windows 7 Please help with my problem

ywchoman

New Member
Joined
Jun 12, 2011
I frequently experience BSOD problems ever since I bought this ASUS X53S one and a half month ago. I once reset the whole laptop back to default settings but that did not solve the problem. The OS is Win7 Home 64 bit and I used AVG Free 2011 antivirus and Zonealarm free firewalls.

I recon it might be the problem for the two graphic cards but I should have already installed the newest drivers for these cards.

The problem keep occuring when I run 3D video games.

Here I copied the most recent crash report from WhoCrashed.exe
On Sun 2011/6/12 と 09:30:04 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061211-32229-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FCD0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: NT Kernel & System
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

On Sun 2011/6/12 と 09:30:04 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheck+0x0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


Thank you very much for your help.
 

Attachments

  • minidump.rar
    645.8 KB · Views: 396
Hello there,

Seems like Zone Alarm is causing the system to crash. Please uninstall Zone Alarm completely and run the removal tool Link Removed due to 404 Error

Apply this Hotfix Stop error message when you run an application that transfers data by using the UDP protocol in Windows Server 2008 R2 or in Windows 7: "STOP 0x0000007F"

Code:
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: 00000000000406f8
Arg4: fffff800042f75e4

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff800042dc2a9 to fffff800042dcd00

STACK_TEXT:  
fffff800`00ba4d28 fffff800`042dc2a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000406f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`042da772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`042f75e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`0d643fc0 fffff800`042ef65b : 00000000`00000010 00000000`00000000 00000000`00000000 01cc2862`ed6dbf09 : nt!SepMandatoryIntegrityCheck+0x14
fffff880`0d644030 fffff800`042abb8e : fffffa80`07cc85c8 00000000`00000001 fffffa80`0c4fd920 01cc2886`f81dbd14 : nt!SeAccessCheckWithHint+0x3fb
fffff880`0d644130 fffff880`01729a4a : 00000000`00000006 00000000`00000000 00000000`00000000 01cc2862`ee0d3b3b : nt!SeAccessCheckFromState+0x102
fffff880`0d644820 fffff880`017292af : 00000008`c0000022 00000005`00000000 00000000`0000000f 00730076`0076006e : NETIO!CompareSecurityContexts+0x6a
fffff880`0d644890 fffff880`01729444 : 01cc2862`ed68fc48 00000000`0095f6df 00000000`00724230 04ef4b78`00180016 : NETIO!MatchValues+0xef
fffff880`0d6448e0 fffff880`017298f2 : 00000000`00000000 fffffa80`0952fdc0 fffff880`0d644b08 fffffa80`04e35c90 : NETIO!FilterMatch+0x94
fffff880`0d644930 fffff880`0172a6fc : 00000000`00000000 00000000`00000000 fffffa80`04e35c90 fffff880`0d644af0 : NETIO!IndexListClassify+0x69
fffff880`0d6449b0 fffff880`0188b819 : fffffa80`04e35c90 fffff880`0d644da0 00000008`00000009 fffffa80`070d4030 : NETIO!KfdClassify+0xa4e
fffff880`0d644d20 fffff880`0188d9a4 : fffffa80`04e35c90 fffffa80`0911c2c0 fffff880`0d6459d8 00000000`00000000 : tcpip!WfpAleClassify+0x49
fffff880`0d644d70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepReauthorizeInboundConnection+0x5f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
NETIO!CompareSecurityContexts+6a
fffff880`01729a4a 448b442470      mov     r8d,dword ptr [rsp+70h]

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  NETIO!CompareSecurityContexts+6a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce79381

FAILURE_BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID:  X64_0x7f_8_NETIO!CompareSecurityContexts+6a

Followup: MachineOwner
---------
 
Last edited:
Thanks Captain Jack, will it be better if I restore the whole laptop to default setting and not install the firewall this time? And is there anything wrong with the graphic drivers?
 
I think we can test it with just removing the Zone Alarm and see if that fixes it. If not then we can go to the next step.
 
Back
Top Bottom