locked
Frequent BSODs - multiple error messages - have attached DMP files RRS feed

  • Question

  • Hello,

    I keep getting BSODs. When I started getting them, I hadn't changed anything, so I don't know what the issue is.

    Here are the DMP files:

    http://dl.dropbox.com/u/10369745/012313-18673-01.dmp

    http://dl.dropbox.com/u/10369745/012313-21840-01.dmp

    http://dl.dropbox.com/u/10369745/012313-72712-01.dmp

    Thanks.

    Thursday, January 24, 2013 5:48 AM

Answers

  • Hi,

    Have you tried the system restore?

    I suggest you try the following:

    1. Update your BIOS and drivers.

    2. Disable all the third party security programs and boot in Clean Boot to test the issue.

    3. Boot in Safe Mode and see if it make difference.

    4. Check the memory and the disk error. If the memory test detected the errors, you may replace the faulty RAM or contact your manufacturer and check if the memory stick is under warranty. For your information:

    http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer

    http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors


    Tracy Cai

    TechNet Community Support

    • Marked as answer by tracycai Friday, February 1, 2013 8:07 AM
    Monday, January 28, 2013 8:07 AM
  • 012313-18673-01.dmp



    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff900e073f188, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff96000134b5f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    ------------------
    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fb100
    GetUlongFromAddress: unable to read from fffff800030fb1c0
     fffff900e073f188 
    FAULTING_IP: 
    win32k!TimersProc+73
    fffff960`00134b5f 8b5348          mov     edx,dword ptr [rbx+48h]
    MM_INTERNAL_CODE:  2
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  csrss.exe
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff880026f67d0 -- (.trap 0xfffff880026f67d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000c85f rbx=0000000000000000 rcx=000000000000c86f
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff96000134b5f rsp=fffff880026f6960 rbp=0000000000000010
     r8=fffffa800a4320e8  r9=0000000000000000 r10=fffffffffffffffd
    r11=00000000002f1400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    win32k!TimersProc+0x73:
    fffff960`00134b5f 8b5348          mov     edx,dword ptr [rbx+48h] ds:00000000`00000048=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e728e0 to fffff80002ecbfc0
    STCK_TEXT:  
    fffff880`026f6668 fffff800`02e728e0 : 00000000`00000050 fffff900`e073f188 00000000`00000000 fffff880`026f67d0 : nt!KeBugCheckEx
    fffff880`026f6670 fffff800`02eca0ee : 00000000`00000000 fffff900`e073f188 fffff900`c06d8700 fffff900`e073f140 : nt! ?? ::FNODOBFM::`string'+0x437f6
    fffff880`026f67d0 fffff960`00134b5f : 00000000`00000000 00000000`00000001 00000000`00000004 fffff800`02ed4e33 : nt!KiPageFault+0x16e
    fffff880`026f6960 fffff960`0013565b : 00000000`00000000 fffff960`00356f10 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x73
    fffff880`026f69b0 fffff960`000c5148 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000944 : win32k!RawInputThread+0x9ab
    fffff880`026f6a80 fffff960`00145e9a : fffffa80`00000002 fffff880`026dbe00 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
    fffff880`026f6ab0 fffff800`02ecb253 : fffffa80`0adbc940 00000000`00000004 000007ff`fffa6000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
    fffff880`026f6ae0 000007fe`fd881eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0241f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd881eea
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    win32k!TimersProc+73
    fffff960`00134b5f 8b5348          mov     edx,dword ptr [rbx+48h]
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  win32k!TimersProc+73
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6
    FAILURE_BUCKET_ID:  X64_0x50_win32k!TimersProc+73
    BUCKET_ID:  X64_0x50_win32k!TimersProc+73
    Followup: MachineOwner
    -----------------------------------------------------------------------------------------------------------------

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

    Resolution

    Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

    Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

    Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

    Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

    Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

    ################################################################

    (012313-21840-01.dmp)

    *******************************************************************************
    *                                                                             *
    *                        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: fffff96000097989, Address of the instruction which caused the bugcheck
    Arg3: fffff8800649e040, 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!EBRUSHOBJ::vInitBrush+1f9
    fffff960`00097989 f08301ff        lock add dword ptr [rcx],0FFFFFFFFh
    CONTEXT:  fffff8800649e040 -- (.cxr 0xfffff8800649e040)
    rax=0000000000000006 rbx=fffff900c00df010 rcx=0007596800000000
    rdx=0000000000000001 rsi=fffff900c01aaa40 rdi=fffff900c2d85c3c
    rip=fffff96000097989 rsp=fffff8800649ea20 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000ffffff r10=fffff900c00ad460
    r11=fffff900c0000de0 r12=fffff900c244fcc0 r13=0000000000000001
    r14=fffff900c2d85630 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    win32k!EBRUSHOBJ::vInitBrush+0x1f9:
    fffff960`00097989 f08301ff        lock add dword ptr [rcx],0FFFFFFFFh ds:002b:00075968`00000000=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  chrome.exe  *************************
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff9600003f7fc to fffff96000097989
    STACK_TEXT:  
    fffff880`0649ea20 fffff960`0003f7fc : fffff900`00ffffff 00000000`00000000 00000000`00000000 fffff900`c0000de0 : win32k!EBRUSHOBJ::vInitBrush+0x1f9
    fffff880`0649ea80 fffff960`0003f4bc : 00000000`00000000 00000000`00f00021 fffff880`0649ecd0 fffff900`0000f0f0 : win32k!GrePatBltLockedDC+0x220
    fffff880`0649eb30 fffff960`0003f180 : fffff880`0649ecd0 fffff800`02ea60c2 fffff880`0649ed20 00000000`00000000 : win32k!GrePolyPatBltInternal+0x2ec
    fffff880`0649ec80 fffff960`0003f0ff : fffff900`c08c82c0 fffff900`c08c82c0 00000000`011000ad fffff960`00220196 : win32k!GrePolyPatBlt+0x74
    fffff880`0649ecf0 fffff960`001291c9 : fffff900`c08c82c0 00000000`011000ad 00000000`00000000 fffff900`c08c82c0 : win32k!FillRect+0x63
    fffff880`0649ed50 fffff960`001290f1 : 00000000`00000000 fffff900`c08c82c0 00000000`011000ad 00000000`6701158f : win32k!xxxPaintRect+0xb5
    fffff880`0649ed80 fffff960`0017b5e4 : 00000000`00000000 fffff900`c08c82c0 00000000`6701158f 00000000`00000000 : win32k!xxxFillWindow+0x9d
    fffff880`0649ede0 fffff960`000cb5ef : 00000000`00000000 00000000`00000014 00000000`00000000 00000000`00000000 : win32k!xxxDWP_EraseBkgnd+0xdc
    fffff880`0649ee30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxRealDefWindowProc+0x507
    FOLLOWUP_IP: 
    win32k!EBRUSHOBJ::vInitBrush+1f9
    fffff960`00097989 f08301ff        lock add dword ptr [rcx],0FFFFFFFFh
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  win32k!EBRUSHOBJ::vInitBrush+1f9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6
    STACK_COMMAND:  .cxr 0xfffff8800649e040 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!EBRUSHOBJ::vInitBrush+1f9
    BUCKET_ID:  X64_0x3B_win32k!EBRUSHOBJ::vInitBrush+1f9
    Followup: MachineOwner
    ---------------------------------------------------------------------------------------------------------------------------

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

    Please Update the Chrome to the latest version, also Disable all Extensions in Chrome also it makes a Blue Screen.

    ################################################################



    (012313-72712-01.dmp)



    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff8a0017c5db8, Virtual address for the attempted execute.
    Arg2: 80000001d2cbd963, PTE contents.
    Arg3: fffff8800c0c31d0, (reserved)
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    ------------------
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  TpKnrres.exe  ***********************
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff8800c0c31d0 -- (.trap 0xfffff8800c0c31d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8007122060
    rdx=fffffa80071220f0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8a0017c5db8 rsp=fffff8800c0c3360 rbp=fffff8a0065399d8
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8a0065399d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffff8a0`017c5db8 0100            add     dword ptr [rax],eax ds:00000000`00000000=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e3bbb4 to fffff80002e93fc0
    STACK_TEXT:  
    fffff880`0c0c3068 fffff800`02e3bbb4 : 00000000`000000fc fffff8a0`017c5db8 80000001`d2cbd963 fffff880`0c0c31d0 : nt!KeBugCheckEx
    fffff880`0c0c3070 fffff800`02e920ee : 00000000`00000008 fffff8a0`017c5db8 fffff8a0`026d1500 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44dbc
    fffff880`0c0c31d0 fffff8a0`017c5db8 : fffffa80`07122010 fffff880`0c0c3300 fffffa80`066e1201 fffff880`0c0c3300 : nt!KiPageFault+0x16e
    fffff880`0c0c3360 fffffa80`07122010 : fffff880`0c0c3300 fffffa80`066e1201 fffff880`0c0c3300 00000000`00000000 : 0xfffff8a0`017c5db8
    fffff880`0c0c3368 fffff880`0c0c3300 : fffffa80`066e1201 fffff880`0c0c3300 00000000`00000000 fffffa80`0712201a : 0xfffffa80`07122010
    fffff880`0c0c3370 fffffa80`066e1201 : fffff880`0c0c3300 00000000`00000000 fffffa80`0712201a fffff8a0`002c7da0 : 0xfffff880`0c0c3300
    fffff880`0c0c3378 fffff880`0c0c3300 : 00000000`00000000 fffffa80`0712201a fffff8a0`002c7da0 00000000`00000000 : 0xfffffa80`066e1201
    fffff880`0c0c3380 00000000`00000000 : fffffa80`0712201a fffff8a0`002c7da0 00000000`00000000 00000000`00000000 : 0xfffff880`0c0c3300
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+44dbc
    fffff800`02e3bbb4 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+44dbc
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+44dbc
    BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+44dbc
    Followup: MachineOwner
    --------------------------------------------------------------------------------------------------------------------------------------------------

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

    ** Please Update the Software ( ThinkVantage Communications Utility ) to the latest version or previous version you have.

    Regards,



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

    • Marked as answer by tracycai Friday, February 1, 2013 8:07 AM
    Monday, January 28, 2013 9:27 AM

All replies

  • Hi,

    Have you tried the system restore?

    I suggest you try the following:

    1. Update your BIOS and drivers.

    2. Disable all the third party security programs and boot in Clean Boot to test the issue.

    3. Boot in Safe Mode and see if it make difference.

    4. Check the memory and the disk error. If the memory test detected the errors, you may replace the faulty RAM or contact your manufacturer and check if the memory stick is under warranty. For your information:

    http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer

    http://windows.microsoft.com/en-US/windows7/Check-a-drive-for-errors


    Tracy Cai

    TechNet Community Support

    • Marked as answer by tracycai Friday, February 1, 2013 8:07 AM
    Monday, January 28, 2013 8:07 AM
  • 012313-18673-01.dmp



    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff900e073f188, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff96000134b5f, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    ------------------
    Could not read faulting driver name

    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030fb100
    GetUlongFromAddress: unable to read from fffff800030fb1c0
     fffff900e073f188 
    FAULTING_IP: 
    win32k!TimersProc+73
    fffff960`00134b5f 8b5348          mov     edx,dword ptr [rbx+48h]
    MM_INTERNAL_CODE:  2
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  csrss.exe
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff880026f67d0 -- (.trap 0xfffff880026f67d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=000000000000c85f rbx=0000000000000000 rcx=000000000000c86f
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff96000134b5f rsp=fffff880026f6960 rbp=0000000000000010
     r8=fffffa800a4320e8  r9=0000000000000000 r10=fffffffffffffffd
    r11=00000000002f1400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    win32k!TimersProc+0x73:
    fffff960`00134b5f 8b5348          mov     edx,dword ptr [rbx+48h] ds:00000000`00000048=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e728e0 to fffff80002ecbfc0
    STCK_TEXT:  
    fffff880`026f6668 fffff800`02e728e0 : 00000000`00000050 fffff900`e073f188 00000000`00000000 fffff880`026f67d0 : nt!KeBugCheckEx
    fffff880`026f6670 fffff800`02eca0ee : 00000000`00000000 fffff900`e073f188 fffff900`c06d8700 fffff900`e073f140 : nt! ?? ::FNODOBFM::`string'+0x437f6
    fffff880`026f67d0 fffff960`00134b5f : 00000000`00000000 00000000`00000001 00000000`00000004 fffff800`02ed4e33 : nt!KiPageFault+0x16e
    fffff880`026f6960 fffff960`0013565b : 00000000`00000000 fffff960`00356f10 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x73
    fffff880`026f69b0 fffff960`000c5148 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000944 : win32k!RawInputThread+0x9ab
    fffff880`026f6a80 fffff960`00145e9a : fffffa80`00000002 fffff880`026dbe00 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
    fffff880`026f6ab0 fffff800`02ecb253 : fffffa80`0adbc940 00000000`00000004 000007ff`fffa6000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
    fffff880`026f6ae0 000007fe`fd881eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0241f7a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd881eea
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    win32k!TimersProc+73
    fffff960`00134b5f 8b5348          mov     edx,dword ptr [rbx+48h]
    SYMBOL_STACK_INDEX:  3
    SYMBOL_NAME:  win32k!TimersProc+73
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6
    FAILURE_BUCKET_ID:  X64_0x50_win32k!TimersProc+73
    BUCKET_ID:  X64_0x50_win32k!TimersProc+73
    Followup: MachineOwner
    -----------------------------------------------------------------------------------------------------------------

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

    Resolution

    Resolving a faulty hardware problem: If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer.

    Resolving a faulty system service problem: Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode menu that displays the operating system choices. At the resulting Windows Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

    Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

    Resolving a corrupted NTFS volume problem: Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If the hard disk is SCSI, check for problems between the SCSI controller and the disk.

    Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it.

    ################################################################

    (012313-21840-01.dmp)

    *******************************************************************************
    *                                                                             *
    *                        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: fffff96000097989, Address of the instruction which caused the bugcheck
    Arg3: fffff8800649e040, 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!EBRUSHOBJ::vInitBrush+1f9
    fffff960`00097989 f08301ff        lock add dword ptr [rcx],0FFFFFFFFh
    CONTEXT:  fffff8800649e040 -- (.cxr 0xfffff8800649e040)
    rax=0000000000000006 rbx=fffff900c00df010 rcx=0007596800000000
    rdx=0000000000000001 rsi=fffff900c01aaa40 rdi=fffff900c2d85c3c
    rip=fffff96000097989 rsp=fffff8800649ea20 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000ffffff r10=fffff900c00ad460
    r11=fffff900c0000de0 r12=fffff900c244fcc0 r13=0000000000000001
    r14=fffff900c2d85630 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
    win32k!EBRUSHOBJ::vInitBrush+0x1f9:
    fffff960`00097989 f08301ff        lock add dword ptr [rcx],0FFFFFFFFh ds:002b:00075968`00000000=????????
    Resetting default scope
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0x3B
    PROCESS_NAME:  chrome.exe  *************************
    CURRENT_IRQL:  0
    LAST_CONTROL_TRANSFER:  from fffff9600003f7fc to fffff96000097989
    STACK_TEXT:  
    fffff880`0649ea20 fffff960`0003f7fc : fffff900`00ffffff 00000000`00000000 00000000`00000000 fffff900`c0000de0 : win32k!EBRUSHOBJ::vInitBrush+0x1f9
    fffff880`0649ea80 fffff960`0003f4bc : 00000000`00000000 00000000`00f00021 fffff880`0649ecd0 fffff900`0000f0f0 : win32k!GrePatBltLockedDC+0x220
    fffff880`0649eb30 fffff960`0003f180 : fffff880`0649ecd0 fffff800`02ea60c2 fffff880`0649ed20 00000000`00000000 : win32k!GrePolyPatBltInternal+0x2ec
    fffff880`0649ec80 fffff960`0003f0ff : fffff900`c08c82c0 fffff900`c08c82c0 00000000`011000ad fffff960`00220196 : win32k!GrePolyPatBlt+0x74
    fffff880`0649ecf0 fffff960`001291c9 : fffff900`c08c82c0 00000000`011000ad 00000000`00000000 fffff900`c08c82c0 : win32k!FillRect+0x63
    fffff880`0649ed50 fffff960`001290f1 : 00000000`00000000 fffff900`c08c82c0 00000000`011000ad 00000000`6701158f : win32k!xxxPaintRect+0xb5
    fffff880`0649ed80 fffff960`0017b5e4 : 00000000`00000000 fffff900`c08c82c0 00000000`6701158f 00000000`00000000 : win32k!xxxFillWindow+0x9d
    fffff880`0649ede0 fffff960`000cb5ef : 00000000`00000000 00000000`00000014 00000000`00000000 00000000`00000000 : win32k!xxxDWP_EraseBkgnd+0xdc
    fffff880`0649ee30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : win32k!xxxRealDefWindowProc+0x507
    FOLLOWUP_IP: 
    win32k!EBRUSHOBJ::vInitBrush+1f9
    fffff960`00097989 f08301ff        lock add dword ptr [rcx],0FFFFFFFFh
    SYMBOL_STACK_INDEX:  0
    SYMBOL_NAME:  win32k!EBRUSHOBJ::vInitBrush+1f9
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: win32k
    IMAGE_NAME:  win32k.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  50aeecc6
    STACK_COMMAND:  .cxr 0xfffff8800649e040 ; kb
    FAILURE_BUCKET_ID:  X64_0x3B_win32k!EBRUSHOBJ::vInitBrush+1f9
    BUCKET_ID:  X64_0x3B_win32k!EBRUSHOBJ::vInitBrush+1f9
    Followup: MachineOwner
    ---------------------------------------------------------------------------------------------------------------------------

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

    Please Update the Chrome to the latest version, also Disable all Extensions in Chrome also it makes a Blue Screen.

    ################################################################



    (012313-72712-01.dmp)



    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
    An attempt was made to execute non-executable memory.  The guilty driver
    is on the stack trace (and is typically the current instruction pointer).
    When possible, the guilty driver's name (Unicode string) is printed on
    the bugcheck screen and saved in KiBugCheckDriver.
    Arguments:
    Arg1: fffff8a0017c5db8, Virtual address for the attempted execute.
    Arg2: 80000001d2cbd963, PTE contents.
    Arg3: fffff8800c0c31d0, (reserved)
    Arg4: 0000000000000002, (reserved)
    Debugging Details:
    ------------------
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    BUGCHECK_STR:  0xFC
    PROCESS_NAME:  TpKnrres.exe  ***********************
    CURRENT_IRQL:  0
    TRAP_FRAME:  fffff8800c0c31d0 -- (.trap 0xfffff8800c0c31d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8007122060
    rdx=fffffa80071220f0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8a0017c5db8 rsp=fffff8800c0c3360 rbp=fffff8a0065399d8
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
    r11=fffff8a0065399d0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    fffff8a0`017c5db8 0100            add     dword ptr [rax],eax ds:00000000`00000000=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002e3bbb4 to fffff80002e93fc0
    STACK_TEXT:  
    fffff880`0c0c3068 fffff800`02e3bbb4 : 00000000`000000fc fffff8a0`017c5db8 80000001`d2cbd963 fffff880`0c0c31d0 : nt!KeBugCheckEx
    fffff880`0c0c3070 fffff800`02e920ee : 00000000`00000008 fffff8a0`017c5db8 fffff8a0`026d1500 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x44dbc
    fffff880`0c0c31d0 fffff8a0`017c5db8 : fffffa80`07122010 fffff880`0c0c3300 fffffa80`066e1201 fffff880`0c0c3300 : nt!KiPageFault+0x16e
    fffff880`0c0c3360 fffffa80`07122010 : fffff880`0c0c3300 fffffa80`066e1201 fffff880`0c0c3300 00000000`00000000 : 0xfffff8a0`017c5db8
    fffff880`0c0c3368 fffff880`0c0c3300 : fffffa80`066e1201 fffff880`0c0c3300 00000000`00000000 fffffa80`0712201a : 0xfffffa80`07122010
    fffff880`0c0c3370 fffffa80`066e1201 : fffff880`0c0c3300 00000000`00000000 fffffa80`0712201a fffff8a0`002c7da0 : 0xfffff880`0c0c3300
    fffff880`0c0c3378 fffff880`0c0c3300 : 00000000`00000000 fffffa80`0712201a fffff8a0`002c7da0 00000000`00000000 : 0xfffffa80`066e1201
    fffff880`0c0c3380 00000000`00000000 : fffffa80`0712201a fffff8a0`002c7da0 00000000`00000000 00000000`00000000 : 0xfffff880`0c0c3300
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+44dbc
    fffff800`02e3bbb4 cc              int     3
    SYMBOL_STACK_INDEX:  1
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+44dbc
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nt
    IMAGE_NAME:  ntkrnlmp.exe
    DEBUG_FLR_IMAGE_TIMESTAMP:  503f82be
    FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+44dbc
    BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+44dbc
    Followup: MachineOwner
    --------------------------------------------------------------------------------------------------------------------------------------------------

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

    ** Please Update the Software ( ThinkVantage Communications Utility ) to the latest version or previous version you have.

    Regards,



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

    • Marked as answer by tracycai Friday, February 1, 2013 8:07 AM
    Monday, January 28, 2013 9:27 AM