Computer Crashes Randomly with BCCode: 7f

[EricDallal]

My computer randomly crashes with absolutely no warning. I sometimes obtain a BSOD, but usually the crash is so sudden that not even that appears. After the crash the computer restarts on its own. It also tends to happen when I leave the computer without putting it to sleep first, but has happened while I am using it as well.

I have already run sfc /scannow, in accordance with a post entitles "BCCode: 7f" on this forum. I have not yet run memtestx86 in windows, but I recall running it from the boot (I have this computer dual booted with Ubuntu and that is one of the options available to me).

Here are two samples:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002E93EC0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 7f
BCP1: 0000000000000008
BCP2: 0000000080050031
BCP3: 00000000000006F8
BCP4: FFFFF80002E3FEC0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

The system is 64-bit. I am running the original OS. It is OEM. The hardware and OS installation are both a little over 2 months old. I have not needed to re-install the OS.

 

[wish]

Hi,
All your dumps file have error code 0x7f = indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.

I recommend you to uninstall Zone Alarm because it's known of BSOD maker. FYI zone alarm works great on win xp but not for vista/7 which have more strict admin privilege while accessing windows network subsystem.
Uninstall ZA then re-activate your windows built-in firewall.
Command prompt(as admin) -> netsh firewall reset

And also it's no good to use 2 antivirus that could make the drivers conflicting. I suggest you to unsintall both Avast+Ad-Aware and replace it with MSE.
http://www.microsoft.com/security_essentials/

These drivers need to do update:

facap.sys    Wed Sep 24 19:34:31 2008 --> [I]FastAccess Video Capture[/I]
GEARAspiWDM.sys Mon May 18 05:17:04 2009 --> [URL="http://www.gearsoftware.com/"]CD-ROM Class Filter Driver by Gear Software[/URL]
k57nd60a.sys Fri Oct 16 03:29:38 2009 --> [URL="http://www.broadcom.com/products/"]Broadcom NetLink  Gigabit Ethernet[/URL]

Then let see if the problem persist.
-wish

Log

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

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

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

2: 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: fffff80002e3dec0

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 fffff80002e74ca9 to fffff80002e75740

STACK_TEXT:  
fffff880`03169de8 fffff800`02e74ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`03169df0 fffff800`02e73172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03169f30 fffff800`02e3dec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03185aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x58


STACK_COMMAND:  kb

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

 

[EricDallal]

Actually, this problem started long before I installed Zone Alarm. In fact, I installed ZA a few days ago because I was worried that it might be caused by a virus or something like that. The problem actually started almost a month ago but I figured that I could solve it on my own. It was only once I realized that I didn't have enough information to solve the problem (and couldn't understand the dump files when Windows restarted) that I decided to post here.

Also, I went into the device manager and it said that the drivers were up-to-date. nevertheless, I went to the two sites and downloaded drivers. I just want to make sure I have the right version before installing them. My processor is the intel core i7. I don't think the "i" stands for Itanium, but I just want to make sure since there is a separate driver for Itanium processors. As for the netlink Ethernet driver, I have assumed that I have one of the current generation chipsets but I can't figure out how to determine my chipset.

 

[wish]

So how is your progress? Follow my advice and if you still get BSOD post the new files here.
Your chipset = Intel(R) 5 Series/3400 Series Chipset Family
How to identify Intel® chipset

 

[EricDallal]

Hello again,

Sorry it took so long but I followed your instructions and the crashes are still occurring.

 

[foulchusky]

I'm in the same situation, and am receiving the exact same error codes

I do have ZoneAlarm installed as well, however that's been running for months and I've only started getting bluescreened in the last few days