1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Can't identify source of Blue Screens

Discussion in 'Windows 7' started by wwdkd, 2011/01/25.

  1. 2011/01/25
    wwdkd

    wwdkd Inactive Thread Starter

    Joined:
    2011/01/25
    Messages:
    2
    Likes Received:
    0
    About a month ago I got a new Graphics card and some additional ram and since then my computer seems to randomly blue screen and restart. It has happened when i'm playing a game and other times it has happened when my computer was idle. I checked my CPU and GPU temps and they were both fine at the time of the crashes. I don't know what is causing this but I can't figure it out, and someone told me to post my windows minidumps here and maybe someone could figure out whats wrong. So, here they are :http://www.mediafire.com/?435cqc683mxrh1d

    It's annoying have my computer crash every other day.
    If anyone could help it would be greatly appreciated.
     
    wwdkd,
    #1
  2. 2011/01/25
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Welcome to WindowsBBS :)

    We are happy to look at the debug logs of your dump files, but we do not do the analysis for you :)

    Also please note ....
    Run the dumps through our Dump Data Collection Tool and copy /paste the logs here - a couple will be enough for starters.
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2011/01/25
    Christer

    Christer Geek Member Staff

    Joined:
    2002/12/17
    Messages:
    6,585
    Likes Received:
    74
    Hello wwdkd,
    welcome to WindowsBBS ... :) ... !

    That sets off my alarm. Are the new modules the same as the existing ones? If they aren't, there's no guaranties that they play well together. Newer systems are more sensitive than older systems so, please post your system details to make it easier helping you.

    User CP > Edit System Specs and also Edit Options > System Specifications - change to YES to show them.
     
    Christer,
    #3
  5. 2011/01/25
    wwdkd

    wwdkd Inactive Thread Starter

    Joined:
    2011/01/25
    Messages:
    2
    Likes Received:
    0
    Here are some of the minidump logs

    *******************************************************************************
    * *
    * 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: fffff800034d79c2, Address of the instruction which caused the bugcheck
    Arg3: fffff88008162180, 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!KeSetEvent+332
    fffff800`034d79c2 48894108 mov qword ptr [rcx+8],rax

    CONTEXT: fffff88008162180 -- (.cxr 0xfffff88008162180)
    rax=fffffa800a7bc1e8 rbx=0000000000000000 rcx=f7fffa800a7bc1e8
    rdx=fffffa8008d51c68 rsi=0000000000000000 rdi=fffff880009e7180
    rip=fffff800034d79c2 rsp=fffff88008162b50 rbp=0000000000000000
    r8=fffffa8008d51c68 r9=fffffa800a7bc1e0 r10=fffffa8006be6200
    r11=00000000001f0003 r12=000000007ef6e001 r13=0000000001f2fd20
    r14=0000000001f2f170 r15=0000000074132450
    iopl=0 nv up ei pl zr na po nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
    nt!KeSetEvent+0x332:
    fffff800`034d79c2 48894108 mov qword ptr [rcx+8],rax ds:002b:f7fffa80`0a7bc1f0=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: ccsvchst.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from fffff800037f0154 to fffff800034d79c2

    STACK_TEXT:
    fffff880`08162b50 fffff800`037f0154 : fffff880`00000000 fffff880`00000001 fffffa80`06be6200 fffffa80`08d51c68 : nt!KeSetEvent+0x332
    fffff880`08162bc0 fffff800`034d2993 : fffffa80`09748060 00000000`00002f48 fffff880`00000000 fffffa80`081c87e0 : nt!NtSetEvent+0x90
    fffff880`08162c20 00000000`74132dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`01f2f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74132dd9


    FOLLOWUP_IP:
    nt!KeSetEvent+332
    fffff800`034d79c2 48894108 mov qword ptr [rcx+8],rax

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt!KeSetEvent+332

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

    STACK_COMMAND: .cxr 0xfffff88008162180 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_nt!KeSetEvent+332

    BUCKET_ID: X64_0x3B_nt!KeSetEvent+332

    Followup: MachineOwner

    *******************************************************************************
    * *
    * 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: fffff95ff8103ad0, memory referenced.
    Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
    Arg3: fffff95ff8103ad0, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000005, (reserved)

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


    Could not read faulting driver name

    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800036f70e0
    fffff95ff8103ad0

    FAULTING_IP:
    +6630626638643664
    fffff95f`f8103ad0 ?? ???

    MM_INTERNAL_CODE: 5

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: firefox.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: fffff88009338a20 -- (.trap 0xfffff88009338a20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff900c37378f0 rbx=0000000000000000 rcx=0000000000010005
    rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff95ff8103ad0 rsp=fffff88009338bb8 rbp=0000000000010005
    r8=0000000076a3408b r9=0000000076a287f4 r10=fffff9600015be44
    r11=000000007efdb000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    fffff95f`f8103ad0 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff8000353e8c1 to fffff800034bf740

    STACK_TEXT:
    fffff880`093388b8 fffff800`0353e8c1 : 00000000`00000050 fffff95f`f8103ad0 00000000`00000008 fffff880`09338a20 : nt!KeBugCheckEx
    fffff880`093388c0 fffff800`034bd82e : 00000000`00000008 00000000`00000000 00000000`0025e600 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40e8b
    fffff880`09338a20 fffff95f`f8103ad0 : fffff960`00106338 00000000`0025fd20 fffffa80`0a615b60 fffff880`09338ca0 : nt!KiPageFault+0x16e
    fffff880`09338bb8 fffff960`00106338 : 00000000`0025fd20 fffffa80`0a615b60 fffff880`09338ca0 00000000`76a90a74 : 0xfffff95f`f8103ad0
    fffff880`09338bc0 fffff960`0015be7d : 00000000`00000000 fffff880`09338ca0 00000000`00000000 00000000`0025de18 : win32k!HMValidateHandle+0xd8
    fffff880`09338bf0 fffff800`034be993 : fffffa80`0a615b60 00000000`0025de00 00000000`00000018 00000000`08868a00 : win32k!NtUserSetCursor+0x39
    fffff880`09338c20 00000000`736e2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0025e708 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x736e2dd9


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!HMValidateHandle+d8
    fffff960`00106338 85c0 test eax,eax

    SYMBOL_STACK_INDEX: 4

    SYMBOL_NAME: win32k!HMValidateHandle+d8

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4cbe5d3e

    FAILURE_BUCKET_ID: X64_0x50_win32k!HMValidateHandle+d8

    BUCKET_ID: X64_0x50_win32k!HMValidateHandle+d8

    Followup: MachineOwner
    ---------
    *******************************************************************************
    * *
    * 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: fffff880048100a4, Address of the instruction which caused the bugcheck
    Arg3: fffff88006bda5f0, 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:
    dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
    fffff880`048100a4 48897108 mov qword ptr [rcx+8],rsi

    CONTEXT: fffff88006bda5f0 -- (.cxr 0xfffff88006bda5f0)
    rax=0000000000000000 rbx=fffffa800978a708 rcx=f7fffa80097576e8
    rdx=0000000000000000 rsi=fffffa800978a6f8 rdi=fffffa8009757018
    rip=fffff880048100a4 rsp=fffff88006bdafc0 rbp=fffffa800978a500
    r8=fffff88006bdafe0 r9=0000000000000000 r10=0000000000000000
    r11=fffff88006bdb0c0 r12=fffffa800978a500 r13=0000000000000000
    r14=0000000000000001 r15=fffffa8009bc3410
    iopl=0 nv up ei ng nz na pe cy
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
    dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30:
    fffff880`048100a4 48897108 mov qword ptr [rcx+8],rsi ds:002b:f7fffa80`097576f0=????????????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x3B

    PROCESS_NAME: dwm.exe

    CURRENT_IRQL: 2

    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff880048100a4

    STACK_TEXT:
    fffff880`06bdafc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+0x30


    FOLLOWUP_IP:
    dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30
    fffff880`048100a4 48897108 mov qword ptr [rcx+8],rsi

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: dxgmms1

    IMAGE_NAME: dxgmms1.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

    STACK_COMMAND: .cxr 0xfffff88006bda5f0 ; kb

    FAILURE_BUCKET_ID: X64_0x3B_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

    BUCKET_ID: X64_0x3B_dxgmms1!VidSchiInterlockedRemoveHeadListIfExist+30

    Followup: MachineOwner
     
    wwdkd,
    #4
  6. 2011/01/26
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Start by testing your memory. Run Memtest86 or Windows Memory Diagnostic.

    Windows 7 DVD also includes a memory testing option called Windows Memory Diagnostic which can be accessed by booting off your Windows DVD, choosing your language/keyboard options, and clicking the link Repair your computer at the bottom left on the Install Now screen. When prompted select your Windows Installation and click Next, here you can select the Windows Memory Diagnostic option.

    Please note:

    To work around the above, test the installed RAM in various configurations. If you have a single module, swap it around the slots. If you have a pair of modules, run each one singly, swapping between slots; and then run them in pairs swapping between pairs of slots. If you have 2 sets of matched modules do not get them mixed up.
     
    Arie,
    #5
  7. 2011/01/26
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    You have not posted the complete debug log for each BSOD, but from a reading of what is there you may have a problem with memory ......
    One or other of those hardware items is the most likely culprit. You will need to work logiically on this ....

    Remove the additional memory and replace the graphics card with the original and check that the system is stable in it's original configuration..

    Replace the additional memory and check for stability.

    Remove the additional memory and replace the new graphics card and test for stability.

    EDIT - Arie posted while I was composing.
     
    PeteC,
    #6

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...