BSOD while playing Tekkit

inaniloquent · 08 Jul 2014

I haven't had one since I reinstalled windows...I've been playing tekkit and other games fine until today. There was no error message or code on the actual BSOD. Here is my report from the dump file.

Attachment 324744

edit: haven't had a BSOD since 2011 lmao

koolkat77 · 08 Jul 2014

Remove Avast! and keep MSE only.

Free up the start-up, nothing except the antivirus is usually needed.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

Make a hard drive test from the hard drive manufacturers website:

Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

How to Use SeaTools for DOS and Windows Disk Check Utility

Drivers:

Update Logitech Camera Driver:

Driver Reference Table - lvrs64.sys

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\ARISU-PC-08_07_2014_191535_06\070814-12828-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
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`02e0f000 PsLoadedModuleList = 0xfffff800`03052890
Debug session time: Wed Jul  9 00:11:56.819 2014 (UTC + 6:00)
System Uptime: 0 days 11:45:18.550
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
.........
*** WARNING: Unable to verify timestamp for lvrs64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88003a45fc6, fffff88002afa898, fffff88002afa0f0}

Probably caused by : lvrs64.sys ( lvrs64+2fc6 )

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

0: 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: fffff88003a45fc6, The address that the exception occurred at
Arg3: fffff88002afa898, Exception Record Address
Arg4: fffff88002afa0f0, Context Record Address

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


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

FAULTING_IP: 
lvrs64+2fc6
fffff880`03a45fc6 45396924        cmp     dword ptr [r9+24h],r13d

EXCEPTION_RECORD:  fffff88002afa898 -- (.exr 0xfffff88002afa898)
ExceptionAddress: fffff88003a45fc6 (lvrs64+0x0000000000002fc6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 000000000029d334
Attempt to read from address 000000000029d334

CONTEXT:  fffff88002afa0f0 -- (.cxr 0xfffff88002afa0f0)
rax=0000000000000000 rbx=fffffa80083e8610 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003a45fc6 rsp=fffff88002afaad0 rbp=000000000029d310
 r8=0000000000000000  r9=000000000029d310 r10=0000000000000002
r11=000000000029d310 r12=fffffa80083e9750 r13=0000000000000000
r14=000000000029d310 r15=000000000029d310
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
lvrs64+0x2fc6:
fffff880`03a45fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`0029d334=????????
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%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  000000000029d334

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030bc100
GetUlongFromAddress: unable to read from fffff800030bc1c0
 000000000029d334 Nonpaged pool

FOLLOWUP_IP: 
lvrs64+2fc6
fffff880`03a45fc6 45396924        cmp     dword ptr [r9+24h],r13d

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff88003a45fc6

STACK_TEXT:  
fffff880`02afaad0 00000000`00000000 : fffffa80`0a535088 00000000`00000000 00000000`00000000 fffffa80`0a5350d0 : lvrs64+0x2fc6


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+2fc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  505cb9b9

STACK_COMMAND:  .cxr 0xfffff88002afa0f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2fc6

BUCKET_ID:  X64_0x7E_lvrs64+2fc6

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

0: kd> lmvm lvrs64
start             end                 module name
fffff880`03a43000 fffff880`03a97000   lvrs64   T (no symbols)           
    Loaded symbol image file: lvrs64.sys
    Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Sat Sep 22 01:02:17 2012 (505CB9B9)
    CheckSum:         000612AC
    ImageSize:        00054000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4