TechSpot

BSOD, Windows 7 x64 minidump included

By calebhawley1
Jan 8, 2011
Post New Reply
  1. Random BSOD - I thought it was a hard drive issue to begin with so i swapped it with one I knew worked (from another machine). I did a fresh windows 7 (64bit) install as well. One blue screen happened while uninstalling a program, the other while watching a youtube video. Before this happens while gaming etc.

    Ive had prime95 going for an hour @100% cpu usage and nothing. Going to do memtest overnight but I think the memory is fine. Going to bed now, would be great if someone had some ideas when I wake up =| Thanks for your time. I posted the event log file above the minidump (i think they are with the right ones, might be backwards).

    Attached are the minidump files as well incase I screwed up the symbols or something.

    The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff88004880004, 0xfffff880098e3c40, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 010811-39405-01.

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

    EXCEPTION_RECORD: fffff880080990a8 -- (.exr 0xfffff880080990a8)
    ExceptionAddress: fffff880015187a9 (Ntfs! ?? ::NNGAKEGL::`string'+0x000000000000e599)
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 0000000000000000
    Parameter[1]: 0000000008000018
    Attempt to read from address 0000000008000018
    CONTEXT: fffff88008098910 -- (.cxr 0xfffff88008098910)
    rax=0000000008000000 rbx=fffff8a0168f5370 rcx=0000000000000000
    rdx=fffff8a0175c0010 rsi=fffff8a0175c0010 rdi=fffff88008099428
    rip=fffff880015187a9 rsp=fffff880080992e0 rbp=fffff880080994d8
    r8=0000000000000020 r9=fffff880080993e0 r10=fffff88008099570
    r11=fffff98080882670 r12=fffff8a0175c0040 r13=fffff880080993e0
    r14=0000000000000020 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
    Ntfs! ?? ::NNGAKEGL::`string'+0xe599:
    fffff880`015187a9 f6401806 test byte ptr [rax+18h],6 ds:002b:00000000`08000018=??
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    PROCESS_NAME: VSSVC.exe
    CURRENT_IRQL: 1
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    EXCEPTION_PARAMETER1: 0000000000000000
    EXCEPTION_PARAMETER2: 0000000008000018
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0b0e0
    0000000008000018
    FOLLOWUP_IP:
    Ntfs! ?? ::NNGAKEGL::`string'+e599
    fffff880`015187a9 f6401806 test byte ptr [rax+18h],6
    _________________________________________________________
    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000024 (0x00000000001904fb, 0xfffff880080990a8, 0xfffff88008098910, 0xfffff880015187a9). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 010811-34413-01.


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

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    FAULTING_IP:
    nvlddmkm+7c004
    fffff880`04880004 415f pop r15
    CONTEXT: fffff880098e3c40 -- (.cxr 0xfffff880098e3c40)
    rax=0000000000000501 rbx=fffff880050d78b0 rcx=0000000000000400
    rdx=0000000000000000 rsi=fffffa8006be1680 rdi=fffff8a0020716c0
    rip=fffff88004880004 rsp=fffff880098e4610 rbp=fffffa8007d9f000
    r8=0000000000000000 r9=fffffa8006be1680 r10=fffff8800487fb86
    r11=fffff8a0020716c0 r12=fffff880098e4901 r13=fffffa8006be1680
    r14=00000000c000000d r15=fffffa8007d9f000
    iopl=0 nv up ei ng nz na pe nc
    cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
    nvlddmkm+0x7c004:
    fffff880`04880004 415f pop r15
    Resetting default scope
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0x3B
    PROCESS_NAME: dwm.exe
    CURRENT_IRQL: 0
    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004880004
    STACK_TEXT:
    fffff880`098e4610 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0x7c004

    FOLLOWUP_IP:
    nvlddmkm+7c004
    fffff880`04880004 415f pop r15
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: nvlddmkm+7c004
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME: nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 4cb9dd0e
    STACK_COMMAND: .cxr 0xfffff880098e3c40 ; kb
    FAILURE_BUCKET_ID: X64_0x3B_nvlddmkm+7c004
    BUCKET_ID: X64_0x3B_nvlddmkm+7c004
    Followup: MachineOwner
    ---------
     

    Attached Files:

  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Check your memory using Memtest86. Tell us what it finds
     
  3. calebhawley1

    calebhawley1 TS Rookie Topic Starter

    did that... didnt think it was memory but it was. Had a bad stick.
     
  4. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Thanks for the update :)
     

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...