Windows 8 and 8.1 Forums


Various BSODs in Past Two Days

  1. #31


    Posts : 5,139
    Win8.1Pro - Finally!!!


    MSI Afterburner (or it could be Riva Tuner or EVGA Precision) is still running in these memory dumps. Please verify that they have been un-installed. Let us know and I'll include directions on how to safely remove the RTCore64.sys driver.

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Jan  1 22:24:12.641 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010113-13431-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:0 days 4:14:26.370
    Probably caused by :hardware ( dxgmms1!VidSchiAdjustWorkerThreadPriority+1cf )
    BugCheck 1000007E, {ffffffffc000001d, fffff800510e4d73, fffff8801c3699c8, fffff8801c369200}
    BugCheck Info: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    Arguments: 
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff800510e4d73, The address that the exception occurred at
    Arg3: fffff8801c3699c8, Exception Record Address
    Arg4: fffff8801c369200, Context Record Address
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: IP_MISALIGNED
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Tue Jan  1 18:08:19.038 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010113-14742-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:5 days 22:17:32.768
    Probably caused by :memory_corruption ( nt!MiAddPageToFlushMdl+140 )
    BugCheck A, {4, 2, 1, fffff802582fb9c0}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: 0000000000000004, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, bitfield :
        bit 0 : value 0 = read operation, 1 = write operation
        bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff802582fb9c0, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: AV_nt!MiAddPageToFlushMdl
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue Jan  1 22:24:12.641 2013 (UTC - 5:00)**************************
    vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
    vsock.sys                   Mon Apr 30 21:15:24 2012 (4F9F392C)
    Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
    amd_sata.sys                Tue Jun 12 10:24:37 2012 (4FD75125)
    amd_xata.sys                Tue Jun 12 10:24:45 2012 (4FD7512D)
    VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
    vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
    vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
    xusb22.sys                  Wed Jul 25 22:26:57 2012 (5010AAF1)
    hcmon.sys                   Wed Aug  1 20:10:29 2012 (5019C575)
    RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
    vmnetuserif.sys             Wed Aug 15 16:31:54 2012 (502C073A)
    vmx86.sys                   Wed Aug 15 18:05:11 2012 (502C1D17)
    LEqdUsb.Sys                 Tue Sep 18 05:26:44 2012 (50583E54)
    LHidEqd.Sys                 Tue Sep 18 05:26:46 2012 (50583E56)
    LHidFilt.Sys                Tue Sep 18 05:26:53 2012 (50583E5D)
    LMouFilt.Sys                Tue Sep 18 05:26:58 2012 (50583E62)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Tue Jan  1 18:08:19.038 2013 (UTC - 5:00)**************************
    RTCore64.sys                Tue Sep  6 08:24:50 2011 (4E661112)
    
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    xusb22.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
    http://www.carrona.org/drivers/driver.php?id=RTCore64.sys

      My System SpecsSystem Spec

  2. #32


    I had previously thought that Riva Tuner was an extension of MSI Afterburner used for the OSD (On Screen Display) for frame rates and such. I had just disabled the RT OSD before, but I have now uninstalled MSI Afterburner completely. Would it be safe to use Sapphire TRIXX as an alternative or is that known for BSODs also?
      My System SpecsSystem Spec

  3. #33


    Posts : 5,139
    Win8.1Pro - Finally!!!


    For now don't use anything. Once we get the BSOD's under control - then feel free to try Trixx (I suggested it's use long ago in another forum - but haven't followed up on it since).
      My System SpecsSystem Spec

  4. #34


    Just got another one

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck D1, {ffffe9805503bbd9, 2, 1, fffff88006401f7b}
    
    
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
    Page 423e74 not present in the dump file. Type ".hh dbgerr004" for details
    Probably caused by : atikmdag.sys ( atikmdag+136f7b )
    
    
    Followup: MachineOwner
    ---------
    
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: ffffe9805503bbd9, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88006401f7b, address which referenced memory
    
    
    Debugging Details:
    ------------------
    
    
    Page 423e74 not present in the dump file. Type ".hh dbgerr004" for details
    
    
    WRITE_ADDRESS:  ffffe9805503bbd9 
    
    
    CURRENT_IRQL:  2
    
    
    FAULTING_IP: 
    atikmdag+136f7b
    fffff880`06401f7b 488b5c2460      mov     rbx,qword ptr [rsp+60h]
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  AV
    
    
    PROCESS_NAME:  System
    
    
    TRAP_FRAME:  fffff8801c569240 -- (.trap 0xfffff8801c569240)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000080000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=fffffa800f61e080 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88006401f7b rsp=fffff8801c5693d0 rbp=fffff8801c569410
     r8=0000000000000005  r9=0000000000000000 r10=00000000fffffff6
    r11=fffff8801c569418 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    atikmdag+0x136f7b:
    fffff880`06401f7b 488b5c2460      mov     rbx,qword ptr [rsp+60h] ss:0018:fffff880`1c569430=00e0610f80faffff
    Resetting default scope
    
    
    LAST_CONTROL_TRANSFER:  from fffff800bd0f0669 to fffff800bd0f1340
    
    
    STACK_TEXT:  
    fffff880`1c5690f8 fffff800`bd0f0669 : 00000000`0000000a ffffe980`5503bbd9 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`1c569100 fffff800`bd0eeee0 : 00000000`00000001 fffffa80`0d2a1274 00000000`00000000 fffff880`1c569240 : nt!KiBugCheckDispatch+0x69
    fffff880`1c569240 fffff880`06401f7b : fffff880`06503c78 fffff880`1c569480 00000000`00000006 fffff880`06401cf9 : nt!KiPageFault+0x260
    fffff880`1c5693d0 fffff880`06400d14 : fffff880`1c569480 00000000`00000007 fffffa80`0f61e000 00000000`00000006 : atikmdag+0x136f7b
    fffff880`1c569420 fffff880`063a54b9 : fffff880`1c569640 fffffa80`0d277020 fffff880`053b9c00 fffffa80`0d277000 : atikmdag+0x135d14
    fffff880`1c569460 fffff880`063c6db3 : fffffa80`0d277000 fffff880`053b9c00 00000000`14508000 fffff880`063ca4de : atikmdag+0xda4b9
    fffff880`1c569570 fffff880`063ca15c : fffffa80`0f7d4900 00000000`14508000 fffffa80`0f7d4920 00000000`00000000 : atikmdag+0xfbdb3
    fffff880`1c5695c0 fffff880`062db8a0 : fffffa80`0f7d4920 fffffa80`0d25b040 fffffa80`0d261c80 fffffa80`0f7d4920 : atikmdag+0xff15c
    fffff880`1c5698b0 fffff880`060dcd0a : fffffa80`0d25b040 fffffa80`0d25b040 fffffa80`0da7df80 fffff880`1c569a70 : atikmdag+0x108a0
    fffff880`1c569910 fffff880`05a1510e : fffff880`1c569a70 fffffa80`0d13c010 fffffa80`0efd34c0 00000000`00000000 : atikmpag+0x7d0a
    fffff880`1c5699c0 fffff880`05b8a601 : fffffa80`0ef3a5c8 fffff880`1c569aa9 fffffa80`0ef3ac40 00000000`00000009 : dxgkrnl!ADAPTER_RENDER_DdiSubmitCommand+0x7e
    fffff880`1c569a00 fffff880`05bc3427 : fffffa80`0dd2fe00 fffffa80`0dd2fe00 00000000`00000000 fffffa80`0d13d010 : dxgmms1!VidSchiSendToExecutionQueue+0x899
    fffff880`1c569b10 fffff880`05bc2b25 : 00000000`00000000 fffff880`00000000 fffff780`00000005 fffff800`00000e80 : dxgmms1!VidSchiSubmitRenderCommand+0x81b
    fffff880`1c569ce0 fffff880`05bc2662 : fffffa80`0dc9b400 fffffa80`0dd2fe00 fffffa80`17d76e00 fffffa80`0d13d010 : dxgmms1!VidSchiSubmitQueueCommand+0x51
    fffff880`1c569d10 fffff800`bd098551 : fffffa80`0ef45b00 fffffa80`0d13d010 fffff800`bd3c6880 00000000`0acfc35b : dxgmms1!VidSchiWorkerThread+0xe6
    fffff880`1c569d50 fffff800`bd0d6dd6 : fffff800`bd36c180 fffffa80`0ef45b00 fffff800`bd3c6880 fffffa80`0d040680 : nt!PspSystemThreadStartup+0x59
    fffff880`1c569da0 00000000`00000000 : fffff880`1c56a000 fffff880`1c564000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    atikmdag+136f7b
    fffff880`06401f7b 488b5c2460      mov     rbx,qword ptr [rsp+60h]
    
    
    SYMBOL_STACK_INDEX:  3
    
    
    SYMBOL_NAME:  atikmdag+136f7b
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: atikmdag
    
    
    IMAGE_NAME:  atikmdag.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  50650821
    
    
    FAILURE_BUCKET_ID:  AV_atikmdag+136f7b
    
    
    BUCKET_ID:  AV_atikmdag+136f7b
    
    
    Followup: MachineOwner
    ---------
    
    
    windbg> .hh dbgerr004
      My System SpecsSystem Spec

  5. #35


    Posts : 5,139
    Win8.1Pro - Finally!!!


    If nothing is overclocked at this point, then try Driver Verifier using these instructions (just a hunch on my part): Driver Verifier Settings

    If Driver Verifier doesn't reveal anything, then we'll try hardware diagnostics (you can start these before we see the results from Driver Verifier if you'd like): Hardware Diagnostics I'd particularly concentrate on the video stress tests (as the errors are pointing at the video sub-system).

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sun Jan  6 01:43:54.042 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010613-15459-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:4 days 3:18:44.603
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
    Probably caused by :atikmdag.sys ( atikmdag+136f7b )
    BugCheck D1, {ffffe9805503bbd9, 2, 1, fffff88006401f7b}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: ffffe9805503bbd9, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88006401f7b, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: AV_atikmdag+136f7b
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Sun Jan  6 01:43:54.042 2013 (UTC - 5:00)**************************
    vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
    vsock.sys                   Mon Apr 30 21:15:24 2012 (4F9F392C)
    Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
    amd_sata.sys                Tue Jun 12 10:24:37 2012 (4FD75125)
    amd_xata.sys                Tue Jun 12 10:24:45 2012 (4FD7512D)
    VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
    vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
    vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
    hcmon.sys                   Wed Aug  1 20:10:29 2012 (5019C575)
    RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
    vmnetuserif.sys             Wed Aug 15 16:31:54 2012 (502C073A)
    vmx86.sys                   Wed Aug 15 18:05:11 2012 (502C1D17)
    LEqdUsb.Sys                 Tue Sep 18 05:26:44 2012 (50583E54)
    LHidEqd.Sys                 Tue Sep 18 05:26:46 2012 (50583E56)
    LHidFilt.Sys                Tue Sep 18 05:26:53 2012 (50583E5D)
    LMouFilt.Sys                Tue Sep 18 05:26:58 2012 (50583E62)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
    
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
      My System SpecsSystem Spec

  6. #36


    I first ran the FurMark stress test with both of my GPUs at the standard clocking settings (I haven't changed clock settings since installing the GPU drivers with the driver only method). Attached is the FurMark results. After that, I enabled Driver Verifier with the settings you suggested and so far no BSODs. Is it worth while trying other GPU diagnostic tests or should I just sit tight to see if Driver Verifier results in a BSOD?

    Attachment 14333
      My System SpecsSystem Spec

  7. #37


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Check the cooling on your video card - 92บC is awfully high.
    Make sure that the fan is turning, that there's nothing clogging inside the cooler and that you've got adequate airflow around the cooler (open space for air to flow easily).

    Continue with Driver Verifier. No BSOD is also a diagnostic tool - it's suggestive of a hardware problem (although Windows drivers haven't been tested either).
      My System SpecsSystem Spec

  8. #38


    I just got a BSOD within the first 5 minutes of playing a game. I checked the GPU fans and they are both working (I actually had to RMA one a few months back because the fan stopped spinning). Airflow seems fine and I cleared out the small amount of dust that was there. The top GPU generally runs about 10C higher than the lower one and it idles around 48C.

    Edit: The game seems to be choppier now. Does this have something to do with the driver verifier? Is it ok to turn the driver verifier off now?

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 139, {3, fffff8801c7696d0, fffff8801c769628, 0}
    
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa )
    
    
    Followup: MachineOwner
    ---------
    
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    KERNEL_SECURITY_CHECK_FAILURE (139)
    A kernel component has corrupted a critical data structure.  The corruption
    could potentially allow a malicious user to gain control of this machine.
    Arguments:
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8801c7696d0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8801c769628, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    
    
    Debugging Details:
    ------------------
    
    
    
    
    TRAP_FRAME:  fffff8801c7696d0 -- (.trap 0xfffff8801c7696d0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8016030d10 rbx=0000000000000000 rcx=0000000000000003
    rdx=fffff8a019ec8e58 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88005c267de rsp=fffff8801c769860 rbp=0000000000000000
     r8=fffffa8012b261b0  r9=fffffa800d16d001 r10=0000000000000003
    r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x1aa:
    fffff880`05c267de cd29            int     29h
    Resetting default scope
    
    
    EXCEPTION_RECORD:  fffff8801c769628 -- (.exr 0xfffff8801c769628)
    ExceptionAddress: fffff88005c267de (dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x00000000000001aa)
       ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
      ExceptionFlags: 00000001
    NumberParameters: 1
       Parameter[0]: 0000000000000003
    
    
    DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
    
    
    BUGCHECK_STR:  0x139
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    
    
    EXCEPTION_PARAMETER1:  0000000000000003
    
    
    LAST_CONTROL_TRANSFER:  from fffff8015668f669 to fffff80156690340
    
    
    STACK_TEXT:  
    fffff880`1c7693a8 fffff801`5668f669 : 00000000`00000139 00000000`00000003 fffff880`1c7696d0 fffff880`1c769628 : nt!KeBugCheckEx
    fffff880`1c7693b0 fffff801`5668f990 : 00000000`00000000 00000000`03300495 00000000`00000002 00000000`12440000 : nt!KiBugCheckDispatch+0x69
    fffff880`1c7694f0 fffff801`5668ebf4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiFastFailDispatch+0xd0
    fffff880`1c7696d0 fffff880`05c267de : fffff8a0`10128bf0 fffffa80`18a13e70 fffffa80`0d16d000 fffff8a0`49b19ba8 : nt!KiRaiseSecurityCheckFailure+0xf4
    fffff880`1c769860 fffff880`05c23c02 : 00000000`00000000 fffff880`1c7699a0 fffffa80`1880d290 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x1aa
    fffff880`1c7698a0 fffff880`05c3ee02 : fffffa80`0f057010 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0x16fa
    fffff880`1c769b10 fffff880`05c3eb25 : 00000000`00000000 fffff880`00000000 fffff780`00000005 fffff801`00000e80 : dxgmms1!VidSchiSubmitRenderCommand+0x1f6
    fffff880`1c769ce0 fffff880`05c3e662 : fffffa80`19214c70 fffffa80`1926fab0 fffffa80`1a346010 fffffa80`0f057010 : dxgmms1!VidSchiSubmitQueueCommand+0x51
    fffff880`1c769d10 fffff801`56637551 : fffffa80`0d19b900 fffffa80`0f057010 fffff801`56965880 00000000`0c81f9b7 : dxgmms1!VidSchiWorkerThread+0xe6
    fffff880`1c769d50 fffff801`56675dd6 : fffff801`5690b180 fffffa80`0d19b900 fffff801`56965880 fffffa80`0d0ce940 : nt!PspSystemThreadStartup+0x59
    fffff880`1c769da0 00000000`00000000 : fffff880`1c76a000 fffff880`1c764000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa
    fffff880`05c267de cd29            int     29h
    
    
    SYMBOL_STACK_INDEX:  4
    
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: dxgmms1
    
    
    IMAGE_NAME:  dxgmms1.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  505ab2a9
    
    
    BUCKET_ID_FUNC_OFFSET:  1aa
    
    
    FAILURE_BUCKET_ID:  0x139_3_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission
    
    
    BUCKET_ID:  0x139_3_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission
    
    
    Followup: MachineOwner
    ---------
    Last edited by sharkya; 07 Jan 2013 at 20:57.
      My System SpecsSystem Spec

  9. #39


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Driver Verifier does extra things to torture drivers - so some performance losses are to be expected.
    How long have you been running Driver Verifier?

    The memory dump isn't a Driver Verifier enabled memory dump.
    If we presume that Driver Verifier isn't going to spit out a memory dump, then we're presuming that the 3rd party drivers are OK
    That then suggests that the last BSOD was most likely a hardware problem (although Windows problems are possible - just less likely).

    Options here are to:
    - track down the hardware problem (IMO it's most likely video)
    - rule out Windows problems
    - or attack both simultaneously.

    Hardware problems are most likely - and I suspect the video because of the 92บC temp, the video sub-system drivers cited in the last couple of memory dumps, and the fact that we've ruled out most possible 3rd party problems by updating/replacing drivers. I'd suggest starting with the video stress tests (and Prime95) listed here: Additional Hardware Diagnostics

    Not a whole bunch to do with Windows. Our options are usually:
    - SFC.EXE /SCANNOW (from an elevated (Run as adminsitrator) Command Prompt)
    - use a System Restore Point
    - Refresh the system
    - Reset the system
    - Backup/Wipe/Reinstall Windows from disk

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Jan  7 19:36:16.171 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\010713-17253-01.dmp]
    Windows 8 Kernel Version 9200 MP (6 procs) Free x64
    Built by: 9200.16461.amd64fre.win8_gdr.121119-1606
    System Uptime:1 days 17:50:42.108
    Probably caused by :dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+1aa )
    BugCheck 139, {3, fffff8801c7696d0, fffff8801c769628, 0}
    BugCheck Info: KERNEL_SECURITY_CHECK_FAILURE (139)
    Arguments: 
    Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
    Arg2: fffff8801c7696d0, Address of the trap frame for the exception that caused the bugcheck
    Arg3: fffff8801c769628, Address of the exception record for the exception that caused the bugcheck
    Arg4: 0000000000000000, Reserved
    BUGCHECK_STR:  0x139
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x139_3_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission
      BIOS Version                  1604
      BIOS Release Date             10/16/2012
      Manufacturer                  To be filled by O.E.M.
      Product Name                  To be filled by O.E.M.
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Mon Jan  7 19:36:16.171 2013 (UTC - 5:00)**************************
    vmci.sys                    Mon Apr 30 21:14:27 2012 (4F9F38F3)
    vsock.sys                   Mon Apr 30 21:15:24 2012 (4F9F392C)
    Rt630x64.sys                Tue Jun 12 09:37:53 2012 (4FD74631)
    amd_sata.sys                Tue Jun 12 10:24:37 2012 (4FD75125)
    amd_xata.sys                Tue Jun 12 10:24:45 2012 (4FD7512D)
    VMNET.SYS                   Sun Jul  8 03:58:34 2012 (4FF93DAA)
    vmnetadapter.sys            Sun Jul  8 03:58:35 2012 (4FF93DAB)
    vmnetbridge.sys             Sun Jul  8 03:59:19 2012 (4FF93DD7)
    hcmon.sys                   Wed Aug  1 20:10:29 2012 (5019C575)
    RTKVHD64.sys                Tue Aug  7 06:49:39 2012 (5020F2C3)
    vmnetuserif.sys             Wed Aug 15 16:31:54 2012 (502C073A)
    vmx86.sys                   Wed Aug 15 18:05:11 2012 (502C1D17)
    LEqdUsb.Sys                 Tue Sep 18 05:26:44 2012 (50583E54)
    LHidEqd.Sys                 Tue Sep 18 05:26:46 2012 (50583E56)
    LHidFilt.Sys                Tue Sep 18 05:26:53 2012 (50583E5D)
    LMouFilt.Sys                Tue Sep 18 05:26:58 2012 (50583E62)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    HWiNFO64A.SYS               Wed Nov 14 06:15:59 2012 (50A37D6F)
    
    http://www.carrona.org/drivers/driver.php?id=vmci.sys
    http://www.carrona.org/drivers/driver.php?id=vsock.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=VMNET.SYS
    http://www.carrona.org/drivers/driver.php?id=vmnetadapter.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetbridge.sys
    http://www.carrona.org/drivers/driver.php?id=hcmon.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=vmnetuserif.sys
    http://www.carrona.org/drivers/driver.php?id=vmx86.sys
    http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys
    http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
      My System SpecsSystem Spec

  10. #40


    I had Driver Verifier enabled since you suggested using it. I ran SFC.exe and it resulted in "Windows Resource Protection did not find any integrity violations." I ran Prime95 and I got 2 errors: "FATAL ERROR: Rounding was 0.5, expected less than 0.4Hardware failure detected, consult stress.txt file." After a quick search, I found that it might be due to OC settings. I don't normally change CPU clock settings, but I noticed that occasionally the Performance Profile changes between Normal and the higher performance one in my BIOS (see screenshot), especially after a BSOD. I'm going to remove the Driver Verifier setting, make sure the CPU Performance Profile is on Normal, and re-run Prime95. I'll report back with results.

    Attachment 14457
      My System SpecsSystem Spec

Page 4 of 6 FirstFirst ... 23456 LastLast
Various BSODs in Past Two Days
Related Threads
I've been getting seemingly random BSODs on my Win8.1 box for months now. There are several different errors that show up, and most of them seem to point to the drivers. I have no idea which driver could be causing the issue though, as I've reinstalled the majority of them. A few I can remember:...
2x WHEA_UNCORRECTABLE_ERROR BSODs in 3 days in BSOD Crashes and Debugging
I suffered my first BSOD 2 days ago while playing Elite Dangerous. It was a WHEA_UNCORRECTABLE_ERROR with references to GenuineIntel, WIN8_DRIVER_FAULT, and the process was Elite Dangerous. I put it down to faulty code in the game somewhere, but just tonight, while browsing on Firefox, I...
Four different BSODs in two days in BSOD Crashes and Debugging
Hi, In the past two days my Dell laptop (Win8 OS) has crashed four times with different BSOD error messages. What I have attempted is to run my anti-malware software and to go back to a restore point, but it hasn't work so I'm worried it is a problem with the RAM. The errors shown are...
Solved BSODs over the last couple of days in BSOD Crashes and Debugging
Over the last couple of days I've been having random BSOD after a few hours of use or so. I've been unable to find anything that causes it to occur, it appears to just happen randomly. Thanks for any help!
Ended up getting 4 Acer All in One 23" touchscreens at work this past week. Getting them set up for a tradeshow. They are the Acer Aspire 5600U's. They were $999 from NewEgg for Core i3-3110m, 8gb ram, 1TB hard drive, Intel HD400 graphics, DVD burner, 23" 1080p 10 point touchscreen, Windows...
4 of them for work, and 1 which is a Christmas present. Gotta buy some pc's before somebody declares the pc dead.
Hi everyone! I just installed Windows 8 yesterday and after the initial "wow" factor I installed my graphics drivers and rebooted. Upon restart, I got past the welcome screen and logged in (no password error) and after the screen quickly goes blank as if it's about to log in, then it returns to...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook