BSOD on or shortly after boot into Windows, error 0x0000007e

[AdalasRodenheim]

Hello all,

I just went through the process of upgrading my motherboard and everything worked fine except the occaisional BSOD on startup. I assume that I am missing a driver or something but I am not sure Here are two BSOD error windows and all my dmp files are attached!

_________________________________________
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF8800476C273
BCP3: FFFFF8800489ADF8
BCP4: FFFFF8800489A650
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\031815-19344-01.dmp
________________________________________________________
Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC000001D
BCP2: FFFFF88000000028
BCP3: FFFFF880048AFDD8
BCP4: FFFFF880048AF630
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\031915-19702-01.dmp
_________________________________________________

Thanks in advance for the help!

 

[Arc]

Uninstall any Cfos software you have. Here is the module that is causing the BSODs, and it comes from Cfos.

cfosspeed    [COLOR=Red]cFosSpeed for faster Internet connections[/COLOR] (NDIS 6)    c:\windows\system32\drivers\cfosspeed6.sys    Kernel Driver    Yes    System    Running    OK    Normal    No    Yes

Also Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

Let us know for any further BSOD after doing these two.
__________________________________________

BugCheck 1000007E, {ffffffffc000001d, fffff88000000028, fffff880048afdd8, fffff880048af630}

[COLOR=Red]Probably caused by : cfosspeed6.sys [/COLOR]( cfosspeed6+166276 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc000001d, The exception code that was not handled
Arg2: fffff88000000028, The address that the exception occurred at
Arg3: fffff880048afdd8, Exception Record Address
Arg4: fffff880048af630, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

FAULTING_IP: 
+9e7882543163
fffff880`00000028 ff              ???

EXCEPTION_RECORD:  fffff880048afdd8 -- (.exr 0xfffff880048afdd8)
ExceptionAddress: fffff88000000028
   ExceptionCode: c000001d (Illegal instruction)
  ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT:  fffff880048af630 -- (.cxr 0xfffff880048af630;r)
rax=fffff880048b0128 rbx=fffffa8019fadb50 rcx=fffff880048b0100
rdx=fffff880048b0118 rsi=fffffa801c6b7230 rdi=fffff880048b0730
rip=fffff88000000028 rsp=fffff880048b0018 rbp=0000000000000080
 r8=0000000000000000  r9=0000000000000000 r10=fffff880047cfef0
r11=fffffa8019ae3900 r12=fffff880047ceb08 r13=fffff8800477e2f0
r14=0000000000000000 r15=fffff880009b8040
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
fffff880`00000028 ff              ???
Last set context:
rax=fffff880048b0128 rbx=fffffa8019fadb50 rcx=fffff880048b0100
rdx=fffff880048b0118 rsi=fffffa801c6b7230 rdi=fffff880048b0730
rip=fffff88000000028 rsp=fffff880048b0018 rbp=0000000000000080
 r8=0000000000000000  r9=0000000000000000 r10=fffff880047cfef0
r11=fffffa8019ae3900 r12=fffff880047ceb08 r13=fffff8800477e2f0
r14=0000000000000000 r15=fffff880009b8040
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
fffff880`00000028 ff              ???
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x7E

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

LAST_CONTROL_TRANSFER:  from fffff88004774276 to fffff88000000028

FAILED_INSTRUCTION_ADDRESS: 
+9e7882543163
fffff880`00000028 ff              ???

STACK_TEXT:  
fffff880`048b0018 fffff880`04774276 : 00000000`00000160 fffff880`04782663 00000000`00000000 fffff880`0461cfeb : 0xfffff880`00000028
fffff880`048b0020 00000000`00000160 : fffff880`04782663 00000000`00000000 fffff880`0461cfeb fffffa80`00000000 : cfosspeed6+0x166276
fffff880`048b0028 fffff880`04782663 : 00000000`00000000 fffff880`0461cfeb fffffa80`00000000 fffff880`048b0100 : 0x160
fffff880`048b0030 00000000`00000000 : fffff880`0461cfeb fffffa80`00000000 fffff880`048b0100 fffff880`048b0100 : cfosspeed6+0x174663


FOLLOWUP_IP: 
cfosspeed6+166276
fffff880`04774276 ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  cfosspeed6+166276

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: cfosspeed6

IMAGE_NAME:  cfosspeed6.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52efa97e

STACK_COMMAND:  .cxr 0xfffff880048af630 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_cfosspeed6+166276

BUCKET_ID:  X64_0x7E_BAD_IP_cfosspeed6+166276

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_bad_ip_cfosspeed6+166276

FAILURE_ID_HASH:  {30ff8603-8ef6-4d95-65db-e0e4026d56ad}

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

2: kd> lmvm cfosspeed6
start             end                 module name
fffff880`0460e000 fffff880`047f8000   cfosspeed6 T (no symbols)           
    Loaded symbol image file: cfosspeed6.sys
    Image path: \SystemRoot\system32\DRIVERS\cfosspeed6.sys
    Image name: cfosspeed6.sys
    Timestamp:        Mon Feb 03 20:06:46 2014 (52EFA97E)
    CheckSum:         001DDDD6
    ImageSize:        001EA000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4