BSOD launching Terraria, error 1000007e

This is the log I received after the reboot:

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: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880010AF039
BCP3: FFFFF880033473D8
BCP4: FFFFF88003346C30
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\070415-19188-01.dmp
C:\Users\Ron\AppData\Local\Temp\WER-31356-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I uploaded the minidump file here: https://mega.co.nz/#!6p4UUYwC!gWKNkq...XAb25-0igV5ySE

If there is anything else I need to provide, please ask me!

archangelix said:

If there is anything else I need to provide, please ask me!

One thing .... is it happening anywhere else other than that said game?

Please try to confirm it, this information will be very vital before troubleshooting starts.
_______________________________________________

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff880010af039, fffff880033473d8, fffff88003346c30}

Probably caused by : luafv.sys ( luafv!LuafvPreClose+56 )

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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880010af039, The address that the exception occurred at
Arg3: fffff880033473d8, Exception Record Address
Arg4: fffff88003346c30, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

FAULTING_IP: 
fltmgr!GetContextFromStreamList+99
fffff880`010af039 488b4820        mov     rcx,qword ptr [rax+20h]

EXCEPTION_RECORD:  fffff880033473d8 -- (.exr 0xfffff880033473d8)
ExceptionAddress: fffff880010af039 (fltmgr!GetContextFromStreamList+0x0000000000000099)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff88003346c30 -- (.cxr 0xfffff88003346c30;r)
rax=ffdff8a00a18e458 rbx=0000000000000000 rcx=fffffa8008bd2890
rdx=fffffa80069dbf20 rsi=fffffa8008bd28e8 rdi=fffffa8008bd2890
rip=fffff880010af039 rsp=fffff88003347610 rbp=fffffa80069dbf20
 r8=fffffa80098a7010  r9=fffff880033477b8 r10=fffffa8008bd2898
r11=0000000000000011 r12=fffff880033477b8 r13=fffffa800770c950
r14=fffffa80098a7010 r15=fffffa80069dbf20
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
fltmgr!GetContextFromStreamList+0x99:
fffff880`010af039 488b4820        mov     rcx,qword ptr [rax+20h] ds:002b:ffdff8a0`0a18e478=????????????????
Last set context:
rax=ffdff8a00a18e458 rbx=0000000000000000 rcx=fffffa8008bd2890
rdx=fffffa80069dbf20 rsi=fffffa8008bd28e8 rdi=fffffa8008bd2890
rip=fffff880010af039 rsp=fffff88003347610 rbp=fffffa80069dbf20
 r8=fffffa80098a7010  r9=fffff880033477b8 r10=fffffa8008bd2898
r11=0000000000000011 r12=fffff880033477b8 r13=fffffa800770c950
r14=fffffa80098a7010 r15=fffffa80069dbf20
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
fltmgr!GetContextFromStreamList+0x99:
fffff880`010af039 488b4820        mov     rcx,qword ptr [rax+20h] ds:002b:ffdff8a0`0a18e478=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

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

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf100
GetUlongFromAddress: unable to read from fffff80002ebf1c0
 ffffffffffffffff 

FOLLOWUP_IP: 
luafv!LuafvPreClose+56
fffff880`060128a2 85c0            test    eax,eax

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre

LAST_CONTROL_TRANSFER:  from fffff880010aecb3 to fffff880010af039

STACK_TEXT:  
fffff880`03347610 fffff880`010aecb3 : fffffa80`08bd2890 fffffa80`08bd2890 fffff6fc`500cd4f0 fffffa80`098a7010 : fltmgr!GetContextFromStreamList+0x99
fffff880`03347690 fffff880`060128a2 : fffffa80`08bd2890 00000000`00000000 fffff8a0`19a9a840 fffff880`01dffff8 : fltmgr!FltGetStreamHandleContext+0x43
fffff880`033476c0 fffff880`010ac067 : 00000000`00000000 fffffa80`08bd2890 fffffa80`098a75f0 fffffa80`0b4ab010 : luafv!LuafvPreClose+0x56
fffff880`033477b0 fffff880`010ad329 : fffff880`03347900 00000000`00000002 0000000f`ffffff00 00000000`00000000 : fltmgr!FltpPerformPreCallbacks+0x2f7
fffff880`033478b0 fffff880`010ab6c7 : fffffa80`08286c60 fffffa80`0770c950 fffffa80`07541e80 00000000`00000000 : fltmgr!FltpPassThrough+0x2d9
fffff880`03347930 fffff800`02f7df7e : fffffa80`069dbf20 fffffa80`07699a10 fffff8a0`11d9be50 fffffa80`0770c950 : fltmgr!FltpDispatch+0xb7
fffff880`03347990 fffff800`02c8cb44 : 00000000`00000001 00000000`00000000 fffffa80`0674e2a0 00000000`00000000 : nt!IopDeleteFile+0x11e
fffff880`03347a20 fffff800`02f20659 : 00000000`00000000 00000000`0008c081 fffffa80`0ae5a010 fffffa80`06d732f0 : nt!ObfDereferenceObject+0xd4
fffff880`03347a80 fffff800`02ccf511 : fffffa80`0ae5a018 00000000`00000001 00000000`00000000 00000000`00000631 : nt!MiSegmentDelete+0xa1
fffff880`03347ac0 fffff800`02ccf789 : 00000000`00000000 00000000`00000080 fffffa80`066d5b10 fffffa80`00000012 : nt!MiProcessDereferenceList+0x131
fffff880`03347b80 fffff800`02f1c456 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiDereferenceSegmentThread+0x10d
fffff880`03347c00 fffff800`02c742c6 : fffff880`02f65180 fffffa80`066f8040 fffff880`02f6ffc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03347c40 00000000`00000000 : fffff880`03348000 fffff880`03342000 fffff880`033476b0 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  luafv!LuafvPreClose+56

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: luafv

IMAGE_NAME:  luafv.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc295

IMAGE_VERSION:  6.1.7600.16385

STACK_COMMAND:  .cxr 0xfffff88003346c30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_luafv!LuafvPreClose+56

BUCKET_ID:  X64_0x7E_luafv!LuafvPreClose+56

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x7e_luafv!luafvpreclose+56

FAILURE_ID_HASH:  {3c418844-a115-2a78-19bd-05558a485f1a}

Followup: MachineOwner
---------
2: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=3786]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = 2104
BiosReleaseDate = 08/13/2013
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
SystemFamily = To be filled by O.E.M.
SystemVersion = System Version
SystemSKU = SKU
BaseBoardManufacturer = ASUSTeK COMPUTER INC.
BaseBoardProduct = P8Z77-V
BaseBoardVersion = Rev 1.xx
2: kd> !sysinfo cpuspeed
CPUID:        "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed:     3300
CurrentSpeed: 3317

The crash dump does not point to anything precisely, and the scope of stop 0x1000007e is very wide.

In most of the cases, a stray BSOD can be treated as just a glitch. It the issue continues, and if there are further crash dumps, let us see those, as those may throw some light on the probable cause of the issue.