Windows 7 Repeat BSODs

[scotbruce]

My partner's laptop has BSOD'd twice today and a handful of times since she bought it.

Could someone please have a look at the (I think!) attached logs and let me know if they can see a/the problem?

Thanks in advance.

Link Removed

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer Acer
System Model Aspire 5742
System Type x64-based PC
Processor Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz, 2399 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date Acer V1.05, 24/08/2010
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7600.16385"
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.68 GB
Available Physical Memory 2.18 GB
Total Virtual Memory 7.35 GB
Available Virtual Memory 5.69 GB
Page File Space 3.68 GB
Page File C:\pagefile.sys

 

[Elmer]

Your last 3 dump files give a stop error code: 0x7F.

Its a stop error that ZoneAlarm firewall gives frequently. You have a couple of (?) options:

ZoneAlarm Firewall is known to be a cause of BSOD's on many Windows 7 systems. Download the ZoneAlarm Remover - Link Removed due to 404 Error. Uninstall ZoneAlarm through Programs and Features. Boot to safe mode and run the ZoneAlarm Remover. Reboot. Make sure that Windows Firewall is enabled.
Alternatively
Try this Microsoft hotfix if you wish to keep ZoneAlarm: Stop Error 0x07F when you run apps. that transfer data by the UDP protocol in Win 7. This fix may work, it may not.

 

[Captain Jack]

Hello and Welcome to W7F!

Few things are going on. Lets start with basic. Uninstall AVG and Zone completely and use the uninstaller tool and remove the left over files. And install Microsoft Security essentials.

Run a Hardware Diagnostic Link Removed - Invalid URL

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: 00000000000006f8
Arg4: fffff80002c8dec0

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 fffff80002cc4ca9 to fffff80002cc5740

STACK_TEXT:  
fffff800`00ba4d28 fffff800`02cc4ca9 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx
fffff800`00ba4d30 fffff800`02cc3172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00ba4e70 fffff800`02c8dec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`06303c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiDoubleFaultAbort+b2
fffff800`02cc3172 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

 

[scotbruce]

Created a system restore point, installed hotfix and was replying to this thread when - BSOD!

Bye bye Zonealarm - you were a good and faithful friend, but no longer!

 

[Elmer]

A couple of other things that could do with updating as well:

mwlPSDFilter.sys Tue Jun 02 11:07:30 2009
mwlPSDNServ.sys Tue Jun 02 11:07:39 2009
mwlPSDVDisk.sys Tue Jun 02 11:15:29 2009
Link Removed

RTKVHD64.sys Tue Jun 22 10:27:26 2010
Link Removed