Sign in
 
HomeWindows 8Windows 7Windows VistaWindows XPMDOPWindows IntuneLibraryForums
Windows Client >
> 
> 
BlueScreen crashing help, 7 64BIT

Answered BlueScreen crashing help, 7 64BIT

  • Thursday, January 24, 2013 6:18 AM
     
     
    Sign In to Vote
    0

    Hi,

    My windows 7 64-bit has been crashing every now and again, and the problem is like a ghost. I've had it looked at twice, ran it through a good number of scanners, and nothing. The BlueScreen itself seems to indicate a memory error as far as I can tell, but my RAM at least is fine. Maybe someone else can give me more information/help.

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7601.2.1.0.256.1
      Locale ID:    4105

    Additional information about the problem:
      BCCode:    3b
      BCP1:    00000000C0000005
      BCP2:    FFFFF9600015A056
      BCP3:    FFFFF8800B274F80
      BCP4:    0000000000000000
      OS Version:    6_1_7601
      Service Pack:    1_0
      Product:    256_1

    Here are the two files Windows says will help with the problem, and my dxDiag file on system specs:

    WER-21231-0.sysdata.xml

    012313-11497-01.dmp

    DxDiag.txt



    • Edited by Vaftss Thursday, January 24, 2013 6:20 AM
    •  
     

All Replies

  • Thursday, January 24, 2013 8:19 AM
     
     
    Sign In to Vote
    0

    *******************************************************************************
    *                                                                             *
    *                        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: fffff9600015a056, Address of the instruction which caused the bugcheck
    Arg3: fffff8800b274f80, 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: 
    win32k!xxxDestroyThreadInfo+75e
    fffff960`0015a056 4c393e          cmp     qword ptr [rsi],r15
    CONTEXT:  fffff8800b274f80 -- (.cxr 0xfffff8800b274f80)
    rax=fffff900c0c00a70 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=ffd7f900c072c2c0 rdi=fffff900c2edbc20
    rip=fffff9600015a056 rsp=fffff8800b275960 rbp=0000000000000000
     r8=0000000000000000  r9=8000000000200000 r10=0000000000000000
    r11=fffff900c0131010 r12=fffff900c086bf08 r13=fffff96000371dc0
    r14=000000000000004c r15=fffff900c2edbc20
    iopl=0         nv up ei ng nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010286
    win32k!xxxDestroyThreadInfo+0x75e:
    fffff960`0015a056 4c393e          cmp     qword ptr [rsi],r15 ds:002b:ffd7f900`c072c2c0=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  wmplayer.exe
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff9600017e863 to fffff9600015a056
    STACK_TEXT:  
    fffff880`0b275960 fffff960`0017e863 : fffffa80`0b5ca060 00000000`00000001 fffffa80`08976c00 fffff900`c2edbc20 : win32k!xxxDestroyThreadInfo+0x75e
    fffff880`0b275a30 fffff960`00155c80 : 00000000`00000000 fffffa80`0b5ca060 fffffa80`0b5ca060 00000000`00000000 : win32k!UserThreadCallout+0x93
    fffff880`0b275a60 fffff800`03969375 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0b5ca000 : win32k!W32pThreadCallout+0x78
    fffff880`0b275a90 fffff800`03969a3d : 00000000`00000000 fffff800`0398b000 00000000`75672400 00000000`00000000 : nt!PspExitThread+0x285
    fffff880`0b275b90 fffff800`03969b45 : fffffa80`0b5ca060 00000000`00000000 fffffa80`0b5ca060 00000000`7efd5000 : nt!PspTerminateThreadByPointer+0x4d
    fffff880`0b275be0 fffff800`03697253 : fffffa80`0b5ca060 fffff880`0b275ca0 00000000`7efd5000 fffffa80`0ad4b530 : nt!NtTerminateThread+0x45
    fffff880`0b275c20 00000000`77a5184a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0323e468 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a5184a
    FOLLOWUP_IP: 
    win32k!xxxDestroyThreadInfo+75e
    fffff960`0015a056 4c393e          cmp     qword ptr [rsi],r15
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  win32k!xxxDestroyThreadInfo+75e
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6
    STACK_COMMAND:  .cxr 0xfffff8800b274f80 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!xxxDestroyThreadInfo+75e
    BUCKET_ID:  X64_0x3B_win32k!xxxDestroyThreadInfo+75e
    Followup: MachineOwner
    -------------------------------------------------------------------------------------------------------------------------------------------------

    Bug Check 0x3B : http://msdn.microsoft.com/en-us/library/windows/hardware/ff558949(v=vs.85).aspx

    Please verify and repair your system files
    to run type cmd  insearch Box ----> Right click and Run as Administrator --->  SFC /SCANNOW

    Regards,

    MCT / MCITP / MCTS / MCSA / MCSE / C|EH / CCNA

     
  • Thursday, January 24, 2013 8:35 AM
     
     
    Sign In to Vote
    0

    Just ran SFC /SCANNOW in Administrator cmd, and it told me:

    "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are include in the CBS.Log..." etc. etc.

    The CBS file is big and long and looks useless to me, but to save possible time and for completeness sake, here it is:

    CBS.log

     
  • Friday, January 25, 2013 8:47 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Hi ,

    If the system file checker cannot fix them, you can perform an In-place Upgrade to repair the existing installation.

    Tracy Cai

    TechNet Community Support