BSOD playing Dota 2

Hawke · Nov 20, 2013

Im keep getting BSOD in this game. Unfortunately I dont know the error number but I could provide it next time I get BSOD if necessery. I use msinfo32 ans SF Diagnostic and zip the files in hope that will help you determine what is going wrong.
Thank you very much for your help in this matter.

View attachment 294319
View attachment 294326

koolkat77 · Nov 21, 2013

Welcome to the forum.

Please test ram with memtest.

Test and Diagnose RAM issues with MEMTEST86+
- Pay close attention to Part 3 of the tutorial "If you have errors". Take the test for at least 7-10 passes. It may take up to 22 passes to find problems.
  - Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

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\SF_21-11-2013\SF21-11-2013\111813-34772-01\111813-34772-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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0305c000 PsLoadedModuleList = 0xfffff800`0329f6d0
Debug session time: Mon Nov 18 16:25:55.158 2013 (UTC + 6:00)
System Uptime: 1 days 20:58:41.880
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffff88000df59d0, 2, 0, fffff800031c7ed4}

Probably caused by : memory_corruption

Followup: memory_corruption
---------

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff88000df59d0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800031c7ed4, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003309100
GetUlongFromAddress: unable to read from fffff800033091c0
 fffff88000df59d0 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!PpmPerfRecordUtility+e4
fffff800`031c7ed4 44389350484400  cmp     byte ptr [rbx+444850h],r10b

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  CODE_CORRUPTION

BUGCHECK_STR:  0xA

PROCESS_NAME:  FlashPlayerPlu

TAG_NOT_DEFINED_c000000f:  FFFFF88003046FB0

TRAP_FRAME:  fffff88003046cd0 -- (.trap 0xfffff88003046cd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000000000019a
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031c7ed4 rsp=fffff88003046e60 rbp=fffffa8004bbe730
 r8=fffff88003046ed8  r9=000000000027c95b r10=0000000000000000
r11=000000000000003b r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz ac pe nc
nt!PpmPerfRecordUtility+0xe4:
fffff800`031c7ed4 44389350484400  cmp     byte ptr [rbx+444850h],r10b ds:00000000`00444850=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff800030d1169 to fffff800030d1bc0

STACK_TEXT:  
fffff880`03046b88 fffff800`030d1169 : 00000000`0000000a fffff880`00df59d0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`03046b90 fffff800`030cfde0 : fffff880`03046cc8 fffff800`03018156 fffffa80`0574e1a0 fffff880`009b1180 : nt!KiBugCheckDispatch+0x69
fffff880`03046cd0 fffff800`031c7ed4 : 00000062`4d0ed996 fffff880`009b1180 fffffa80`04bbe730 fffffa80`04bbe8a8 : nt!KiPageFault+0x260
fffff880`03046e60 fffff800`031f2ab2 : 00000000`ffffffed 00000000`00000000 00000062`4d0ed996 0000004d`a2b3cc08 : nt!PpmPerfRecordUtility+0xe4
fffff880`03046ed0 fffff800`030dc30c : fffff880`009b1180 fffffa80`009e6115 fffffa80`0574ed40 00000000`00000015 : nt!PpmPerfAction+0x22
fffff880`03046f00 fffff800`030d4d15 : a46fa46f`79547954 fffffa80`099781e0 00000000`00000000 fffff800`031f2a90 : nt!KiRetireDpcList+0x1bc
fffff880`03046fb0 fffff800`030d4b2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`06b1cbf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND:  kb

CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800031c7ed9 - nt!PpmPerfRecordUtility+e9
	[ 00:44 ]
1 error : !nt (fffff800031c7ed9)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

FOLLOWUP_NAME:  memory_corruption

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MEMORY_CORRUPTOR:  ONE_BYTE

FAILURE_BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

BUCKET_ID:  X64_MEMORY_CORRUPTION_ONE_BYTE

Followup: memory_corruption
---------
=============================================================================
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\SF_21-11-2013\SF21-11-2013\111813-32588-01\111813-32588-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Mini Kernel Dump does not have process information
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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`0305b000 PsLoadedModuleList = 0xfffff800`0329e6d0
Debug session time: Mon Nov 18 21:03:28.251 2013 (UTC + 6:00)
System Uptime: 0 days 4:36:18.329
Loading Kernel Symbols
......................................................
Loading User Symbols
Loading unloaded module list
.Missing image name, possible paged-out or corrupt data.
.Missing image name, possible paged-out or corrupt data.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 7ffffffff8, 0, 0}

Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+454f5 )

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

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, An illegal page fault occurred while holding working set synchronization.
	Parameter 2 contains the referenced virtual address.
Arg2: 0000007ffffffff8
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008e46860 -- (.trap 0xfffff88008e46860)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000007ffffffff8 rbx=0000000000000000 rcx=ffffffffffffffff
rdx=fffffa80079e9ec8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030f7a3e rsp=fffff88008e469f0 rbp=fffff88008e46a60
 r8=0000000077840ccb  r9=8000000048ed7121 r10=fffff80003254fe0
r11=fffffa80053721b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiIssueHardFault+0x3aa:
fffff800`030f7a3e 0100            add     dword ptr [rax],eax ds:0000007f`fffffff8=????????
Resetting default scope

MISALIGNED_IP: 
nt!MiIssueHardFault+3aa
fffff800`030f7a3e 0100            add     dword ptr [rax],eax

LAST_CONTROL_TRANSFER:  from fffff80003069d2e to fffff800030d0bc0

STACK_TEXT:  
fffff880`08e466f8 fffff800`03069d2e : 00000000`0000001a 00000000`00041287 0000007f`fffffff8 00000000`00000000 : nt!KeBugCheckEx
fffff880`08e46700 fffff800`030cecee : 00000000`00000001 0000007f`fffffff8 fffff880`08e46a00 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x454f5
fffff880`08e46860 fffff800`030f7a3e : fffffa80`053721b0 fffff880`08e46a80 fffffa80`079e9ec8 fffffa80`053721b0 : nt!KiPageFault+0x16e
fffff880`08e469f0 fffff800`030de28a : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : nt!MiIssueHardFault+0x3aa
fffff880`08e46ac0 fffff800`030cecee : 00000000`00000000 00000000`77840ccb 00000000`0132e901 00000000`01330000 : nt!MmAccessFault+0x146a
fffff880`08e46c20 00000000`77738f56 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0132ddb0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : <Unloaded_Unknown_Module_00000000`00000035>+0x77738f21


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+454f5
fffff800`03069d2e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+454f5

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  X64_IP_MISALIGNED

BUCKET_ID:  X64_IP_MISALIGNED

Followup: MachineOwner

Hawke · Nov 22, 2013

Hi,

I run the mem test when computer was warm for 8 hours(7 passes) and it was error free. Should I run it more? I will also run it cold and see what happens.

koolkat77 · Nov 22, 2013

Okay. Please update this driver:

|| Logitech Camera driver || Driver Reference Table - lvrs64.sys ||

Code:

*** 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, fffff880066e479b, fffff880040fe3d8, fffff880040fdc30}

Probably caused by : lvrs64.sys ( lvrs64+2079b )

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: fffff880066e479b, The address that the exception occurred at
Arg3: fffff880040fe3d8, Exception Record Address
Arg4: fffff880040fdc30, 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+2079b
fffff880`066e479b f30f100c88      movss   xmm1,dword ptr [rax+rcx*4]

EXCEPTION_RECORD:  fffff880040fe3d8 -- (.exr 0xfffff880040fe3d8)
ExceptionAddress: fffff880066e479b (lvrs64+0x000000000002079b)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  fffff880040fdc30 -- (.cxr 0xfffff880040fdc30)
rax=baddada1baddada1 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000015 rsi=fffffa8005bc2810 rdi=0000000000000012
rip=fffff880066e479b rsp=fffff880040fe610 rbp=fffffa8005bc28f0
 r8=0000000000000001  r9=00000000000002fe r10=0000000000000000
r11=fffffa800b765094 r12=0000000000000000 r13=0000000000000000
r14=0000000000000015 r15=fffffa8005bc2690
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
lvrs64+0x2079b:
fffff880`066e479b f30f100c88      movss   xmm1,dword ptr [rax+rcx*4] ds:002b:baddada1`baddada1=????????
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:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c4100
GetUlongFromAddress: unable to read from fffff800032c41c0
 ffffffffffffffff 

FOLLOWUP_IP: 
lvrs64+2079b
fffff880`066e479b f30f100c88      movss   xmm1,dword ptr [rax+rcx*4]

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff880066e479b

STACK_TEXT:  
fffff880`040fe610 00000000`00000000 : fffffa80`0c218040 fffffa80`00000200 00000000`00000400 fffffa80`0b30c040 : lvrs64+0x2079b


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+2079b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f166964

STACK_COMMAND:  .cxr 0xfffff880040fdc30 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2079b

BUCKET_ID:  X64_0x7E_lvrs64+2079b

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

0: kd> lmvm lvrs64
start             end                 module name
fffff880`066c4000 fffff880`06717a80   lvrs64   T (no symbols)           
    Loaded symbol image file: lvrs64.sys
    Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Wed Jan 18 12:40:36 2012 (4F166964)
    CheckSum:         00061E9E
    ImageSize:        00053A80
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Please uninstall Eset antivirus for testing purpose. Use Microsoft Security Essentials is recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

:ar: Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.
Reduce items at start-up. Nothing except anti-virus is required:

http://www.eset.com/us/online-scanner/
Disk Check on your hard disk for file system errors and bad sectors on it:

http://www.sevenforums.com/tutorials/433-disk-check.html

Post screenshot(s) of your Hard Drive(s) using Crystal Disk Info Software:

Run a Hard Drive test:

Hard Drive Diagnostic Procedure

Perform a System File Check:

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

Full tutorial here:

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Hawke · Nov 22, 2013

Ok I will. Thx.

BSOD playing Dota 2

Hawke

New member

My Computer

koolkat77

New member

My Computer

Hawke

New member

My Computer

koolkat77

New member

My Computer

Hawke

New member

My Computer