Repeated BSOD

i keep getting bsods with the error report showing
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

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

ive read thru some threads on here and ran memtest overnight, which showed no problems, and yet when i try each ram stick individually, the system wont boot with one, while it works decently (only a few crashes) with the other
I also reinstalled win7 , and im using norton security suite, although it has never given me problems before :s

gotta make sure that my ram is the actual problem before i consider getting a replacement
heres the dump

hotwyre said:

i keep getting bsods with the error report showing
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

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

ive read thru some threads on here and ran memtest overnight, which showed no problems, and yet when i try each ram stick individually, the system wont boot with one, while it works decently (only a few crashes) with the other
I also reinstalled win7 , and im using norton security suite, although it has never given me problems before :s

gotta make sure that my ram is the actual problem before i consider getting a replacement
heres the dump

This one was caused by CFOSspeed. Remove it

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\051811-30950-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02a09000 PsLoadedModuleList = 0xfffff800`02c4e650
Debug session time: Wed May 18 03:00:46.736 2011 (GMT-4)
System Uptime: 0 days 0:03:17.016
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, fffff8800823d90e}

Unable to load image \SystemRoot\system32\DRIVERS\cfosspeed.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for cfosspeed.sys
*** ERROR: Module load completed but symbols could not be loaded for cfosspeed.sys
Probably caused by : cfosspeed.sys ( cfosspeed+1d90e )

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: fffff8800823d90e

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


BUGCHECK_STR:  0x7f_8

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  firefox.exe

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002a882a9 to fffff80002a88d00

STACK_TEXT:  
fffff880`031d9ce8 fffff800`02a882a9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`031d9cf0 fffff800`02a86772 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`031d9e30 fffff880`0823d90e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`009aafe0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cfosspeed+0x1d90e


STACK_COMMAND:  kb

FOLLOWUP_IP: 
cfosspeed+1d90e
fffff880`0823d90e e80d000000      call    cfosspeed+0x1d920 (fffff880`0823d920)

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  cfosspeed+1d90e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cfosspeed

IMAGE_NAME:  cfosspeed.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ad341d1

FAILURE_BUCKET_ID:  X64_0x7f_8_cfosspeed+1d90e

BUCKET_ID:  X64_0x7f_8_cfosspeed+1d90e

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

appreciate the quick response, hopefully its the only problem

hotwyre said:

appreciate the quick response, hopefully its the only problem

Me too. Good luck and keep us in the loop

one of my 2 gb stcicks ended up dying around the same time cfos started blue screening, but its running just fine with one 2 gb stick and cfos removed ^_^

hotwyre said:

one of my 2 gb stcicks ended up dying around the same time cfos started blue screening, but its running just fine with one 2 gb stick and cfos removed ^_^

Keep us in the loop