BSOD playing TF2 and Minecraft


  1. Posts : 3
    Windows 7 x64
       #1

    BSOD playing TF2 and Minecraft


    Need some help determining the cause of frequent crashes while playing either game, a variety of error numbers. Tried updating graphic drivers, no change.

    Win7 x64

    DMP files attached.

    Thanks in advance!
      My Computer


  2. Posts : 3
    Windows 7 x64
    Thread Starter
       #2

    Bump.
    Recent errors include:
    0.00000003B and 0.00000001E
      My Computer


  3. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #3

    Code:
    1. Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [J:\BSODDmpFiles\thrillhouse87\Windows_NT6_BSOD_jcgriff2\012212-19796-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50 Debug session time: Sun Jan 22 17:25:29.581 2012 (UTC - 7:00) System Uptime: 0 days 0:06:41.064 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1E, {0, 0, 0, 0} Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* KMODE_EXCEPTION_NOT_HANDLED (1e) 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. Arguments: Arg1: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, The address that the exception occurred at Arg3: 0000000000000000, Parameter 0 of the exception Arg4: 0000000000000000, Parameter 1 of the exception Debugging Details: ------------------ EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +6562373162316435 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0 BUGCHECK_STR: 0x1E_0 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 2 EXCEPTION_RECORD: fffff800050172c8 -- (.exr 0xfffff800050172c8) ExceptionAddress: fffff80002c8594b (nt!KiInsertTimerTable+0x000000000000013b) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000000 Parameter[1]: ffffffffffffffff Attempt to read from address ffffffffffffffff TRAP_FRAME: fffff80005017370 -- (.trap 0xfffff80005017370) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000 rdx=dffff80002df50e8 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80002c8594b rsp=fffff80005017500 rbp=fffff80002df50e8 r8=fffffa80056443f8 r9=0000000000000073 r10=fffff80002df1e80 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po cy nt!KiInsertTimerTable+0x13b: fffff800`02c8594b 488b42f8 mov rax,qword ptr [rdx-8] ds:0001:dffff800`02df50e0=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff80002c70c2e to fffff80002c78ed0 STACK_TEXT: fffff800`050163a8 fffff800`02c70c2e : 00000000`00000002 00000000`00000000 fffff800`05016b20 fffff800`02ca5e28 : nt!KeBugCheck fffff800`050163b0 fffff800`02c9ebed : fffff800`02e85c24 fffff800`02dbea3c fffff800`02c07000 fffff800`050172c8 : nt!KiKernelCalloutExceptionHandler+0xe fffff800`050163e0 fffff800`02ca6250 : fffff800`02dc6b5c fffff800`05016458 fffff800`050172c8 fffff800`02c07000 : nt!RtlpExecuteHandlerForException+0xd fffff800`05016410 fffff800`02cb31b5 : fffff800`050172c8 fffff800`05016b20 fffff800`00000000 fffff800`02df1e80 : nt!RtlDispatchException+0x410 fffff800`05016af0 fffff800`02c78542 : fffff800`050172c8 fffffa80`056443b8 fffff800`05017370 00000000`00001060 : nt!KiDispatchException+0x135 fffff800`05017190 fffff800`02c76e4a : fffffa80`03da7480 00000000`00000000 fffff800`02df1e80 fffffa80`05def001 : nt!KiExceptionDispatch+0xc2 fffff800`05017370 fffff800`02c8594b : fffff800`02df1e80 00000000`00000000 fffffa80`076a8060 fffff800`02dffc40 : nt!KiGeneralProtectionFault+0x10a fffff800`05017500 fffff800`02c82a9a : ffffffff`fff0bdc0 fffff800`02c84fa6 00000000`00000004 fffff800`00000000 : nt!KiInsertTimerTable+0x13b fffff800`05017560 fffff800`02c842cd : fffffa80`056443b8 fffffa80`0704aae8 00000000`00000000 00000000`00000000 : nt!KiTimerWaitTest+0x15a fffff800`050175e0 fffff800`02c84e7e : 00000000`ef0d87de fffff800`05017c58 00000000`0000646d fffff800`02df5028 : nt!KiProcessExpiredTimerList+0x6d fffff800`05017c30 fffff800`02c84697 : 00000000`4617e3c9 00000000`0000646d 00000000`4617e3bb 00000000`0000006d : nt!KiTimerExpiration+0x1be fffff800`05017cd0 fffff800`02c816fa : fffff800`02df1e80 fffff800`02dffc40 00000000`00000000 fffff880`0127ac50 : nt!KiRetireDpcList+0x277 fffff800`05017d80 00000000`00000000 : fffff800`05018000 fffff800`05012000 fffff800`05017d40 00000000`00000000 : nt!KiIdleLoop+0x5a STACK_COMMAND: kb FOLLOWUP_IP: nt!KiKernelCalloutExceptionHandler+e fffff800`02c70c2e 90 nop SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: nt!KiKernelCalloutExceptionHandler+e FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 FAILURE_BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e BUCKET_ID: X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e Followup: MachineOwner ---------
    2. Loading Dump File [J:\BSODDmpFiles\thrillhouse87\Windows_NT6_BSOD_jcgriff2\012212-21606-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e45e50 Debug session time: Sun Jan 22 17:15:20.668 2012 (UTC - 7:00) System Uptime: 0 days 1:30:17.150 Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff880010b2f60, fffff880088319d0, 0} Probably caused by : WRkrn.sys ( WRkrn+bf60 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff880010b2f60, Address of the instruction which caused the bugcheck Arg3: fffff880088319d0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: WRkrn+bf60 fffff880`010b2f60 833b00 cmp dword ptr [rbx],0 CONTEXT: fffff880088319d0 -- (.cxr 0xfffff880088319d0) rax=0000000000000aa4 rbx=dffff8a00b255010 rcx=fffffa800442c010 rdx=fffff8a0030b0e78 rsi=fffff880088324e0 rdi=0000000000000001 rip=fffff880010b2f60 rsp=fffff880088323b0 rbp=fffff88008832450 r8=0000000000000003 r9=fffff88008832450 r10=fffffa8006910c6c r11=fffffa8006910c70 r12=fffff880088324d0 r13=fffff880010bc6e0 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 WRkrn+0xbf60: fffff880`010b2f60 833b00 cmp dword ptr [rbx],0 ds:002b:dffff8a0`0b255010=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: hl2.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880010b2f60 STACK_TEXT: fffff880`088323b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WRkrn+0xbf60 FOLLOWUP_IP: WRkrn+bf60 fffff880`010b2f60 833b00 cmp dword ptr [rbx],0 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: WRkrn+bf60 FOLLOWUP_NAME: MachineOwner MODULE_NAME: WRkrn IMAGE_NAME: WRkrn.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4f10a210 STACK_COMMAND: .cxr 0xfffff880088319d0 ; kb FAILURE_BUCKET_ID: X64_0x3B_WRkrn+bf60 BUCKET_ID: X64_0x3B_WRkrn+bf60 Followup: MachineOwner ---------
    3. Loading Dump File [J:\BSODDmpFiles\thrillhouse87\Windows_NT6_BSOD_jcgriff2\012112-17144-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c0b000 PsLoadedModuleList = 0xfffff800`02e48e50 Debug session time: Sat Jan 21 20:05:22.957 2012 (UTC - 7:00) System Uptime: 0 days 0:16:42.440 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002c93ae4, fffff8800be51ee0, 0} Probably caused by : ntkrnlmp.exe ( nt!KeReleaseSemaphore+94 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002c93ae4, Address of the instruction which caused the bugcheck Arg3: fffff8800be51ee0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!KeReleaseSemaphore+94 fffff800`02c93ae4 488b6d00 mov rbp,qword ptr [rbp] CONTEXT: fffff8800be51ee0 -- (.cxr 0xfffff8800be51ee0) rax=0000000000000001 rbx=fffffa8006abf140 rcx=fffffa8006abf140 rdx=0000000000000001 rsi=dffffa8006f78168 rdi=0000000000000001 rip=fffff80002c93ae4 rsp=fffff8800be528c0 rbp=dffffa8006f78168 r8=0000000000000000 r9=0000000000000001 r10=0000000000000000 r11=fffff8800be52a20 r12=0000000000000000 r13=fffff80002df5e80 r14=fffffa8003e6e890 r15=fffffa8006abf148 iopl=0 nv up ei ng nz na pe cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283 nt!KeReleaseSemaphore+0x94: fffff800`02c93ae4 488b6d00 mov rbp,qword ptr [rbp] ss:0018:dffffa80`06f78168=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: javaw.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002c93ae4 STACK_TEXT: fffff880`0be528c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeReleaseSemaphore+0x94 FOLLOWUP_IP: nt!KeReleaseSemaphore+94 fffff800`02c93ae4 488b6d00 mov rbp,qword ptr [rbp] SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KeReleaseSemaphore+94 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 STACK_COMMAND: .cxr 0xfffff8800be51ee0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KeReleaseSemaphore+94 BUCKET_ID: X64_0x3B_nt!KeReleaseSemaphore+94 Followup: MachineOwner ---------
    4. Loading Dump File [J:\BSODDmpFiles\thrillhouse87\Windows_NT6_BSOD_jcgriff2\012112-22869-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7600 MP (2 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7600.16385.amd64fre.win7_rtm.090713-1255 Machine Name: Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e8ae50 Debug session time: Sat Jan 21 19:06:59.044 2012 (UTC - 7:00) System Uptime: 0 days 0:16:29.527 Loading Kernel Symbols ............................................................... ................................................................ ............................ Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff80002cffc22, fffff8800a1e6cb0, 0} Probably caused by : ntkrnlmp.exe ( nt!KxWaitForLockOwnerShip+12 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff80002cffc22, Address of the instruction which caused the bugcheck Arg3: fffff8800a1e6cb0, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!KxWaitForLockOwnerShip+12 fffff800`02cffc22 48890a mov qword ptr [rdx],rcx CONTEXT: fffff8800a1e6cb0 -- (.cxr 0xfffff8800a1e6cb0) rax=0000000002e4b660 rbx=fffffa8000ec3c10 rcx=fffff8800a1e7728 rdx=2000000000000000 rsi=0000000000000001 rdi=fffff8800a1e7728 rip=fffff80002cffc22 rsp=fffff8800a1e7690 rbp=fffff8800a1e7700 r8=fffff880009e6180 r9=0000000000000000 r10=fffff80002ef7840 r11=0000058000000000 r12=fffffa8003902800 r13=000000000008f200 r14=00000000000024b8 r15=0000000000000000 iopl=0 nv up ei ng nz na pe nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282 nt!KxWaitForLockOwnerShip+0x12: fffff800`02cffc22 48890a mov qword ptr [rdx],rcx ds:002b:20000000`00000000=???????????????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x3B PROCESS_NAME: WRSA.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002cffc22 STACK_TEXT: fffff880`0a1e7690 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x12 FOLLOWUP_IP: nt!KxWaitForLockOwnerShip+12 fffff800`02cffc22 48890a mov qword ptr [rdx],rcx SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KxWaitForLockOwnerShip+12 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600 STACK_COMMAND: .cxr 0xfffff8800a1e6cb0 ; kb FAILURE_BUCKET_ID: X64_0x3B_nt!KxWaitForLockOwnerShip+12 BUCKET_ID: X64_0x3B_nt!KxWaitForLockOwnerShip+12 Followup: MachineOwner ---------
    1. Possible causes are Memory problems... Viruses... Corrupted hard disk system files... Corrupted System Files... Lack of Windows updates... Drivers...
      Thanks to JMH for helping with my understanding of this crash.
    2. Caused by WebRoot antivirus driver.
    3. Possible causes are Memory problems... Corrupted hard disk system files... Corrupted System Files... Graphics Driver...
    4. Caused by WebRoot antivirus application.


    Thanks to Dave76 for help understanding possible causes.

    We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.


      My Computer


  4. Posts : 3
    Windows 7 x64
    Thread Starter
       #4

    Awesome! Thanks for the input, I will try those suggestions tonight and report back.
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #5

    Any change in stability after doing the steps?
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:58.
Find Us