BSOD on Windows 7 Ultimate x64

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Zameus, Dec 12, 2012.

  1. Zameus

    Zameus New Member

    Dec 12, 2012
    Likes Received:
    Hello all,

    I've recently been experiencing random BSOD on my system. Below is a mini dump file. Please help me analyze this and determine the root cause. I'm going to run a memory test for starters. Your help is greatly appreciated! :D

    View attachment 120912-14024-01.dmp
  2. kemical

    kemical Windows Forum Admin
    Staff Member Premium Supporter Microsoft MVP

    Aug 28, 2007
    Likes Received:
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {ffffb8a00a3cfe80, 0, fffff880101be2eb, 7}
    Could not read faulting driver name
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )
    Followup: MachineOwner
    The PAGE_FAULT_IN_NONPAGED_AREA bug check has a value of 0x00000050. This indicates that invalid system memory has been referenced.

    Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).
    Another common cause is the installation of a faulty system service.
    Antivirus software can also trigger this error, as can a corrupted NTFS volume.


    as you mentioned please check your RAM using this app:

    Test only one stick at a time and run for at least 7/8 passes.

    Many of your drivers are 2 or more years out of date. Please update everything to their latest versions.
  3. GeneralHiningII

    GeneralHiningII Honorable Member

    Sep 21, 2012
    Likes Received:
    Use this link: to post a BSOD report.

    Points to League of legends (and your DirectX drivers):
    Try - reinstalling League.
    - Updating your DX Software (How to download and install DirectX)
    - Updating your Graphics Drivers (Since you haven't given me all the information, so I can't tell which manufacturer you use: AMD Drivers: AMD Graphics Drivers & Software or NVIDIA Drivers: Drivers - Download NVIDIA Drivers) or if you use Intel Graphic Drivers (Intel Download Center)

    Debug session time: Mon Dec 10 14:19:15.105 2012 (UTC + 11:00)
    Loading Dump File [C:\Users\MZ\SysnativeBSODs\120912-14024-01.dmp]
    Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
    System Uptime: 0 days 1:51:10.354
    BugCheck 50, {ffffb8a00a3cfe80, 0, fffff880101be2eb, 7}
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b )
    Bugcheck code 00000050
    Arg1: ffffb8a00a3cfe80, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff880101be2eb, If non-zero, the instruction address which referenced the bad memory
    Arg4: 0000000000000007, (reserved)
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  League of Lege
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+39b

    3rd Party Drivers:
    **************************Mon Dec 10 14:19:15.105 2012 (UTC + 11:00)**************************
    [COLOR=#ff0000]pcouffin.sys                Fri Jun 30 23:40:29 2006 (44A529CD)[/COLOR]
    mcdbus.sys                  Tue Feb 24 21:34:07 2009 (49A3CD1F)
    netr28x.sys                 Thu Feb 26 14:02:09 2009 (49A60631)
    [COLOR=#ff0000]GEARAspiWDM.sys             Mon May 18 22:17:04 2009 (4A1151C0)[/COLOR]
    intelppm.sys                Tue Jul 14 09:19:25 2009 (4A5BC0FD)
    amdxata.sys                 Sat Mar 20 03:18:18 2010 (4BA3A3CA)
    L1C62x64.sys                Tue Aug 24 19:14:01 2010 (4C738D59)
    HECIx64.sys                 Wed Oct 20 10:33:43 2010 (4CBE2AD7)
    iaStor.sys                  Sat Nov  6 18:44:52 2010 (4CD50774)
    asahci64.sys                Fri Nov 19 12:30:53 2010 (4CE5D34D)
    RTKVHD64.sys                Tue Nov 30 20:03:19 2010 (4CF4BDD7)
    ElbyCDIO.sys                Fri Dec 17 09:58:13 2010 (4D0A9985)
    asmtxhci.sys                Wed Dec 29 20:18:45 2010 (4D1AFCF5)
    asmthub3.sys                Wed Dec 29 20:18:55 2010 (4D1AFCFF)
    VClone.sys                  Sun Jan 16 03:21:04 2011 (4D31C970)
    ALSysIO64.sys               Sun Jul 10 10:27:45 2011 (4E18F201)
    avkmgr.sys                  Thu Sep 15 23:36:11 2011 (4E71FF4B)
    igdkmd64.sys                Wed Feb 15 05:47:30 2012 (4F3AAC42)
    [COLOR=#ff0000]avgntflt.sys                Tue Apr 24 16:14:35 2012 (4F9644CB)
    avipbb.sys                  Thu Apr 26 20:12:40 2012 (4F991F98)[/COLOR]
    The drivers in red, and my comments:

    pcouffin.sys Fri Jun 30 23:40:29 2006 (44A529CD)
    low level access layer for CD devices (A part of many different CD/DVD burning programs)
    Driver Reference Table - pcouffin.sys
    This driver is old, so I'm just suggesting you either you uninstall this driver or update it to the latest version.

    GEARAspiWDM.sys Mon May 18 22:17:04 2009 (4A1151C0)
    CD-ROM Class Filter Driver by Gear Software.[br]Also comes with iTunes
    Driver Reference Table - GEARAspiWDM.sys
    Although your dmp file doesn't say anything about this software, but I have seen some systems that have problems with this driver, so uninstall it as a test.

    avgntflt.sys                Tue Apr 24 16:14:35 2012 (4F9644CB)
    Avira AntiVir

    avipbb.sys              Thu Apr 26 20:12:40 2012 (4F991F98)
    Avira AntiVir
    Although this AntiVirus Software is okay, I suggest using AntiVirus Software's such as:
    Microsoft Security Essentials:
    or a one-time AntiVirus Scan (NOT RECOMMENDED FOR NORMAL USE)
    Malwarebytes : Free anti-malware download
    #3 GeneralHiningII, Dec 13, 2012
    Last edited: Dec 13, 2012
  4. Zameus

    Zameus New Member

    Dec 12, 2012
    Likes Received:
    Thank you both!! This is alot of help. I will run memory tests, update drivers accordingly, and reinstall League of Legends. I will report back with my findings. Thanks again!

Share This Page