---

BugCheck 1000007E, {c0000005, 8067d5d0, f78f2be4, f78f28e0}

Probably caused by : ntkrnlmp.exe ( nt!VfStackSeedStack+7 )
...
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: c0000005, The exception code that was not handled
Arg2: 8067d5d0, The address that the exception occurred at
Arg3: f78f2be4, Exception Record Address
Arg4: f78f28e0, Context Record Address
...
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!VfStackSeedStack+7
8067d5d0 6a05            push    5

EXCEPTION_RECORD:  f78f2be4 -- (.exr 0xfffffffff78f2be4)
.exr 0xfffffffff78f2be4
ExceptionAddress: 8067d5d0 (nt!VfStackSeedStack+0x00000007)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 335ad98b
Attempt to write to address 335ad98b

CONTEXT:  f78f28e0 -- (.cxr 0xfffffffff78f28e0)
.cxr 0xfffffffff78f28e0
eax=00000000 ebx=86b40e00 ecx=ffffffff edx=00000000 esi=80702428 edi=865235f0
eip=8067d5d0 esp=f78f2cac ebp=f78f2cb4 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
nt!VfStackSeedStack+0x7:
8067d5d0 6a05            push    5
.cxr
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

WRITE_ADDRESS:  335ad98b 

BUGCHECK_STR:  0x7E

EXCEPTION_DOESNOT_MATCH_CODE:  This indicates a hardware error.
Instruction at 8067d5d0 does not read/write to 335ad98b

---

Lainaus, alkuperäisen viestin kirjoitti tukis:

---

Enpä tuosta tiedä, mutta muistin kunnon voisit testata vaikkapa memetest86+ ohjelmalla boottaavalta levyltä/tikulta/korpulta.

---