Random BSOD ntoskrnl.exe and dxgmms1.sys


  1. Posts : 7
    Windows 7 Professional x64
       #1

    Random BSOD ntoskrnl.exe and dxgmms1.sys


    Hello all,

    I have had this issue on-and-off for roughly 4 months now; it is not bricking my system just seems to happen every-other log on (usually my first log-in)

    My futile attempts of fixing this issue has resulted in purchasing new memory, a new graphics card, a new PSU and finally a new USB wi-fi dongle (have not received yet)

    I have tried countless programs CCleaner, Blue screen view, tweaking.com, memtest, even a fresh install (twice). I do dabble in computer maintenance but this has been the first time I have been lost for solutions.


    This is my first time, so If you need any further info just let me know.

    Thanks in advance
    Last edited by bRAM4054; 20 Apr 2014 at 04:19.
      My Computer


  2. Posts : 7
    Windows 7 Professional x64
    Thread Starter
       #2

    I have also attached a sceenshot from the blue screen viewer
      My Computer


  3. Posts : 7
    Windows 7 Professional x64
    Thread Starter
       #3

    Bump
      My Computer


  4. Posts : 19
    ultimate 64
       #4

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck 50, {fffffa8043819010, 0, fffff8000353f596, 5}

    Could not read faulting driver name
    Probably caused by : memory_corruption
    Followup: memory_corruption
    ---------
    2: 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: fffffa8043819010, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff8000353f596, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000005, (reserved)
    Debugging Details:
    ------------------

    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034ae100
    fffffa8043819010
    FAULTING_IP:
    nt!CmpParseKey+26
    fffff800`0353f596 41388000000033 cmp byte ptr [r8+33000000h],al
    MM_INTERNAL_CODE: 5
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: CODE_CORRUPTION
    BUGCHECK_STR: 0x50
    PROCESS_NAME: svchost.exe
    CURRENT_IRQL: 0
    TRAP_FRAME: fffff880026d7e90 -- (.trap 0xfffff880026d7e90)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880026d81b8
    rdx=fffffa800cd04500 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000353f596 rsp=fffff880026d8020 rbp=7ffffa80108191c8
    r8=fffffa8010819010 r9=fffff8a003eef200 r10=fffff8a00001aca0
    r11=fffff8a003eef262 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    nt!CmpParseKey+0x26:
    fffff800`0353f596 41388000000033 cmp byte ptr [r8+33000000h],al ds:80e0:fffffa80`43819010=??
    Resetting default scope
    LOCK_ADDRESS: fffff8000347abe0 -- (!locks fffff8000347abe0)
    Resource @ nt!PiEngineLock (0xfffff8000347abe0) Available
    WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.

    WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
    1 total locks
    PNP_TRIAGE:
    Lock address : 0xfffff8000347abe0
    Thread Count : 0
    Thread address: 0x0000000000000000
    Thread wait : 0x0
    LAST_CONTROL_TRANSFER: from fffff800032f35b3 to fffff80003276bc0
    STACK_TEXT:
    fffff880`026d7d28 fffff800`032f35b3 : 00000000`00000050 fffffa80`43819010 00000000`00000000 fffff880`026d7e90 : nt!KeBugCheckEx
    fffff880`026d7d30 fffff800`03274cee : 00000000`00000000 fffffa80`43819010 fffff8a0`02e49900 fffffa80`0cd04500 : nt! ?? ::FNODOBFM::`string'+0x43801
    fffff880`026d7e90 fffff800`0353f596 : fffff8a0`02e49990 fffff880`026d8130 fffff8a0`80000258 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`026d8020 fffff800`03571db8 : fffffa80`108191c8 fffff800`03201000 fffff8a0`0001ac70 fffff800`00000001 : nt!CmpParseKey+0x26
    fffff880`026d8320 fffff800`03572fd6 : 00000000`00000000 fffffa80`10819010 00000000`00000000 fffffa80`0cd04500 : nt!ObpLookupObjectName+0x588
    fffff880`026d8410 fffff800`03529818 : fffff880`02f64180 00000000`00000000 00000000`00000000 fffff880`026d85e8 : nt!ObOpenObjectByName+0x306
    fffff880`026d84e0 fffff800`0352a0b6 : fffff880`026d88f8 fffff880`000f003f fffff880`026d8910 fffff800`034b1600 : nt!CmCreateKey+0x2e1
    fffff880`026d8650 fffff800`03275e53 : ffffffff`ffffffff 00000000`00000000 fffff6fc`5001e000 fffff800`03298c98 : nt!NtCreateKey+0x2e
    fffff880`026d86a0 fffff800`03272410 : fffff800`034e72b2 00000000`00000001 20207050`03230858 00000000`000000b5 : nt!KiSystemServiceCopyEnd+0x13
    fffff880`026d88a8 fffff800`034e72b2 : 00000000`00000001 20207050`03230858 00000000`000000b5 fffff880`026d8b20 : nt!KiServiceLinkage
    fffff880`026d88b0 fffff800`034e3f12 : 00000000`00000001 00000000`00000002 00000000`00000002 00000000`000f003f : nt!IopCreateRegistryKeyEx+0x7e
    fffff880`026d8980 fffff800`034e48d5 : 00000000`00000002 00000000`00000000 fffff880`026d8b80 00000000`00000001 : nt!IopGetDeviceInterfaces+0x146
    fffff880`026d8af0 fffff800`034e3bb5 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff8a0`01dfe900 : nt!PiGetInterfaceDeviceList+0x41
    fffff880`026d8b50 fffff800`03539c94 : fffff8a0`01dfe900 fffff800`00008000 fffff880`026d8c01 fffff800`03744da0 : nt!PiControlGetInterfaceDeviceList+0x111
    fffff880`026d8bd0 fffff800`03275e53 : fffffa80`0f3b1910 00000000`003beb70 fffff880`026d8ca0 00000000`003bebf8 : nt!NtPlugPlayControl+0x100
    fffff880`026d8c20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13

    STACK_COMMAND: kb
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8000353f597 - nt!CmpParseKey+27
    [ b8:38 ]
    1 error : !nt (fffff8000353f597)
    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: ONE_BIT
    FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
    BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
    Followup: memory_corruption
    ---------


    it's look like memory problem.
    First try Video Card - Stress Test with Furmark
    and than ,
    This Memory Diagnostics all over night wait until 10-12 pass
      My Computer


  5. Posts : 7
    Windows 7 Professional x64
    Thread Starter
       #5

    Hi,
    Tried the furmark and 10mins in, BSOD. Please find attached...
      My Computer


  6. Posts : 7
    Windows 7 Professional x64
    Thread Starter
       #6

    And one more from luck... dump after running prime95
      My Computer


  7. Posts : 19
    ultimate 64
       #7

    Try ,

    1 - Download Update for Windows 7 for x64-based Systems (KB974431) from Official Microsoft Download Center
    2 - Update video card driver
    3 - Reinstall ( Update ) Directx

    After please run furmark again
      My Computer


  8. Posts : 7
    Windows 7 Professional x64
    Thread Starter
       #8

    Just downloading AMDcleanup utility with intentions of installing latest driver. But I have completed the other steps and no change...
      My Computer


  9. Posts : 7
    Windows 7 Professional x64
    Thread Starter
       #9

    None of the previous solutions worked, end memtest came back okay.

    My last ditch effort seems to of done the trick though (fingers crossed)... I removed the zalman CPU cooler, good clean-out and re-applied a new layer of thermal paste. Installed the cpu and cooler and thus far no BSOD.

    I'll give a day or so before I close the thread; and thanks Gknrsy
      My Computer


 

  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 00:35.
Find Us