BSOD number 102512-30217-01

Page 1 of 2 12 LastLast

  1. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit Service Pack 1
       #1

    BSOD number 102512-30217-01


    Hello,

    I have recently bought a new computer with have 16Gb and 2133Hz of RAM, and i did a overclock at my motherboard to use the RAM , now i got a BSOD, then i opened my computer information and i find out that my RAM was at 8Gb, so i opened my computer and relocate the ram, now it's working fine, but i would like to confirme what was the problem.

    Here is my Minedump file, for those who is interested to review it.

    Regards,

    FelipeCODX
    Last edited by FelipeCODX; 28 Oct 2012 at 21:54.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome

    You need to attach everything in the zip following the instructions again and it's hard to say anything with just one dump.

    Code:
    STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
    Usual causes:  Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8a00b40b6d9, 0, fffff8800861d2ee, 0}
    
    
    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39e )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        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: fffff8a00b40b6d9, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8800861d2ee, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000000, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80005705100
    GetUlongFromAddress: unable to read from fffff800057051c0
     fffff8a00b40b6d9 Paged pool
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39e
    fffff880`0861d2ee 385f59          cmp     byte ptr [rdi+59h],bl
    
    MM_INTERNAL_CODE:  0
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  Gw2.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800df37f60 -- (.trap 0xfffff8800df37f60)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8a00b47af80 rbx=0000000000000000 rcx=00000000000008d0
    rdx=0000000053cc0130 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800861d2ee rsp=fffff8800df380f0 rbp=fffff8800df38900
     r8=fffffa800712f130  r9=0000000000000003 r10=0000000000000035
    r11=00000000c0023400 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39e:
    fffff880`0861d2ee 385f59          cmp     byte ptr [rdi+59h],bl ds:00000000`00000059=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff8000547deec to fffff800054d5fc0
    
    STACK_TEXT:  
    fffff880`0df37df8 fffff800`0547deec : 00000000`00000050 fffff8a0`0b40b6d9 00000000`00000000 fffff880`0df37f60 : nt!KeBugCheckEx
    fffff880`0df37e00 fffff800`054d40ee : 00000000`00000000 fffff8a0`0b40b6d9 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4514f
    fffff880`0df37f60 fffff880`0861d2ee : 00000000`0000000c 00000000`0000000f fffffa80`1059b001 fffffa80`1059b010 : nt!KiPageFault+0x16e
    fffff880`0df380f0 fffff880`086033e7 : fffffa80`07168001 fffffa80`0e092ad0 00000000`53cc0130 fffff880`000000dc : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x39e
    fffff880`0df381e0 fffff880`0873ffae : 00000000`00000000 00000000`00000200 fffff880`0df38900 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
    fffff880`0df38230 fffff880`0873f773 : fffff8a0`00000001 fffff8a0`097a7430 fffff880`0df388b0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326
    fffff880`0df38840 fffff960`001e03ce : 00000000`3859e6b0 00000000`fff59000 00000000`3859fd20 00000000`fff59000 : dxgkrnl!DxgkRender+0x3e7
    fffff880`0df38ab0 fffff800`054d5253 : fffffa80`0fc5e060 00000000`00001520 00000000`00000000 fffffa80`103a6820 : win32k!NtGdiDdDDIRender+0x12
    fffff880`0df38ae0 00000000`7540164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`3859e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7540164a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39e
    fffff880`0861d2ee 385f59          cmp     byte ptr [rdi+59h],bl
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39e
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39e
    
    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39e
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #3

    I got that error again, that time i was playing guild wars 2, talking at skype and hearing a music at the youtube.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    Is anything connected to your USB ports?
    See if these tutorials help:


    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {4389405b, 2, 1, fffff880082904aa}
    
    Probably caused by : usbehci.sys ( usbehci!EHCI_ControlTransfer+3e6 )
    
    Followup: MachineOwner
    ---------
    AVG contributes in BSODs, please uninstall and use MSE at least to test.


    Recommended antivirus program for Windows 7 based on stability compared to others:-

    Run a full scan with both (separately) once downloaded, installed and updated.
      My Computer


  5. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #5

    Could you please explain that for me, it's a driver problem? or a lack of energy?
      My Computer


  6. Posts : 15,026
    Windows 10 Home 64Bit
       #6

    You can fill in your specs in my system specs:
    __________________

    1. Click on User CP on the top right of this page
    2. Click on Edit System Spec
    3. Fill in your computer specs

    __________________
    I'm not sure yet what's causing the BSODs, so this is a new computer? How many sticks of ram do you have
      My Computer


  7. Posts : 26,863
    Windows 11 Pro
       #7

    Can you tell us exactly what you did to overclock your system? How about going into BIOS and set optimized defaults, set your ram voltage by specs of the ram, set your sata controller to what it is right now, set your boot configuration and save and exit. See if your problem goes away.
      My Computer


  8. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #8

    Thank you guys for your time.

    I'm unsing my keyboard at a 3.0 USB output, because when i try to use it at a 2.0 USB output my headset stop working. (my headset is plugged at a 2.0 USB).

    I'm using a motherboard USB driver (Asmide ASM104x USB3.0 Host Controller Driver).

    I did my memory overclock changing the (Bios flap "AI Tweakers") "AI Overclock Tuner" to Manual, and the "Memory Frequency" to DDR3-2133MHZ.

    Sometimes when i'm starting the computer, i got a error saying "overclock failed" and it ask me to reconfig it at the BIOS.

    I have updated my System Spec at my Sevenforums Profile.

    All my USB (except the keyboard) is plugged at a 2.0 USB output.

    I'm attaching some photo for more informations. (it's about 40 pictures about my cables allocations, tower, memory, BIOS and programs)

    Photo.zip download - 2shared
      My Computer


  9. Posts : 9
    Microsoft Windows 7 Ultimate 64-bit Service Pack 1
    Thread Starter
       #9

    About he overclock, now i tryed to set the "AI Overclock Tuner" to X.M.P
    then it auto configurated everything about the memory.



      My Computer


  10. Posts : 26,863
    Windows 11 Pro
       #10

    In your bios, under advanced settings, USB configuration, do you have an option under USB 3.0 to enable legacy devices? If you do, enable it. USB 3.0 will not work until the OS loads. The USB 3.0 drivers are in the OS. Your front pannel headers has an audio connection, is it plugged into the HD audio connection or the AC97 connection? Try plugging your Keyboard to a rear USB 2.0 port and the headphones into a front USB 2.0 port. Also, set the voltage for the ram by manufacturers specs and make sure the timings are the same. Let us know how that works for you.
      My Computer


 
Page 1 of 2 12 LastLast

  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 13:41.
Find Us