BSOD! Happening while playing games.

Page 5 of 6 FirstFirst ... 3456 LastLast

  1. Posts : 26
    Windows 7 64bit
    Thread Starter
       #41

    Ram or driver?
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #42

    Code:
    Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\Hantimilon\123011-16801-01\123011-16801-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
    Machine Name:
    Kernel base = 0xfffff800`02e08000 PsLoadedModuleList = 0xfffff800`0304d670
    Debug session time: Fri Dec 30 14:34:15.868 2011 (UTC - 7:00)
    System Uptime: 0 days 0:42:22.070
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc000001d, fffff88002e387c2, fffff880053f3768, fffff880053f2fc0}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiSubmitRenderCommand+3a6 )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff88002e387c2, The address that the exception occurred at
    Arg3: fffff880053f3768, Exception Record Address
    Arg4: fffff880053f2fc0, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    
    FAULTING_IP: 
    dxgmms1!VidSchiSubmitRenderCommand+3a6
    fffff880`02e387c2 488b8c2488000000 mov     rcx,qword ptr [rsp+88h]
    
    EXCEPTION_RECORD:  fffff880053f3768 -- (.exr 0xfffff880053f3768)
    ExceptionAddress: fffff88002e387c2 (dxgmms1!VidSchiSubmitRenderCommand+0x00000000000003a6)
       ExceptionCode: c000001d (Illegal instruction)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    CONTEXT:  fffff880053f2fc0 -- (.cxr 0xfffff880053f2fc0)
    rax=0000000000000000 rbx=0000000000000241 rcx=fffffa80089f6410
    rdx=0000000000000004 rsi=fffffa80089f6410 rdi=fffff800043e2080
    rip=fffff88002e387c2 rsp=fffff880053f39a0 rbp=fffffa80098e4a00
     r8=0000000000000000  r9=0000000000000007 r10=0000000000000000
    r11=fffffa8008c443e0 r12=0000000000000000 r13=fffffa8006f9a870
    r14=0000000000000000 r15=fffffa8007c78010
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    dxgmms1!VidSchiSubmitRenderCommand+0x3a6:
    fffff880`02e387c2 488b8c2488000000 mov     rcx,qword ptr [rsp+88h] ss:fffff880`053f3a28=fffffa8009b79650
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x7E
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION}  Illegal Instruction  An attempt was made to execute an illegal instruction.
    
    LAST_CONTROL_TRANSFER:  from fffff88002e38398 to fffff88002e387c2
    
    FAILED_INSTRUCTION_ADDRESS: 
    dxgmms1!VidSchiSubmitRenderCommand+3a6
    fffff880`02e387c2 488b8c2488000000 mov     rcx,qword ptr [rsp+88h]
    
    STACK_TEXT:  
    fffff880`053f39a0 fffff880`02e38398 : fffff800`043e2000 fffff880`02e37d00 fffffa80`00000000 fffffa80`00000004 : dxgmms1!VidSchiSubmitRenderCommand+0x3a6
    fffff880`053f3b90 fffff880`02e37e96 : 00000000`00000000 fffffa80`07c78010 00000000`00000080 fffffa80`089f6410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`053f3bc0 fffff800`0311ffee : 00000000`03746d51 fffffa80`08a0a770 fffffa80`066ec040 fffffa80`08a0a770 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`053f3c00 fffff800`02e765e6 : fffff800`02ffae80 fffffa80`08a0a770 fffff800`03008cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`053f3c40 00000000`00000000 : fffff880`053f4000 fffff880`053ee000 fffff880`053f3540 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiSubmitRenderCommand+3a6
    fffff880`02e387c2 488b8c2488000000 mov     rcx,qword ptr [rsp+88h]
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  dxgmms1!VidSchiSubmitRenderCommand+3a6
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799c1
    
    STACK_COMMAND:  .cxr 0xfffff880053f2fc0 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_BAD_IP_dxgmms1!VidSchiSubmitRenderCommand+3a6
    
    BUCKET_ID:  X64_0x7E_BAD_IP_dxgmms1!VidSchiSubmitRenderCommand+3a6
    
    Followup: MachineOwner
    ---------
    DirectX related again. Could be due to your RAM problems. Have you replaced the RAM, or do you still have the bad RAM installed?
      My Computer


  3. Posts : 26
    Windows 7 64bit
    Thread Starter
       #43

    Still the bad memory. Need to order them. Just wanted to check if this still was memory errors or drivers.
      My Computer


  4. Posts : 26
    Windows 7 64bit
    Thread Starter
       #44

    I've ordered the ram now.
    But when playing games that req more (Star Wars, Battlefield) they keep freezing up, or just close and go back to Windows.
    Games that dont req alot (Heroes of Newerth) never freeze up or crash.

    Can this alot be related to ram??
    Got 1 more crash, dxgmms1.sys
      My Computer


  5. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #45

    Hantimilon said:
    I've ordered the ram now.
    But when playing games that req more (Star Wars, Battlefield) they keep freezing up, or just close and go back to Windows.
    Games that dont req alot (Heroes of Newerth) never freeze up or crash.

    Can this alot be related to ram??
    Got 1 more crash, dxgmms1.sys
    It could be related to RAM as it may be trying to use more than one module at once if it requires more RAM. Did you ever try increasing the voltage for DRAM by 0.1 volt? I never received a response from you as to whether or not that worked.
      My Computer


  6. Posts : 26
    Windows 7 64bit
    Thread Starter
       #46

    I havent done that yet. Ill test that when i get back home tonight.
    Does it say voltage for DRAM in the bios? :P ill prob figure it out :)
      My Computer


  7. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #47

    Hantimilon said:
    I havent done that yet. Ill test that when i get back home tonight.
    Does it say voltage for DRAM in the bios? :P ill prob figure it out :)
    It typically says DRAM: AUTO somewhere. Just change it to manual, look up what your RAM suggests for its Voltage, try that first as AUTO may not have been setting the Voltage correctly for your set of modules. If you still blue screen after trying the recommended Voltage for your modules, then try 0.1 Volts higher than that.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #48

    Also, what motherboard and RAM are you using? Have you checked to make sure they are compatible?

    I was helping someone out yesterday who had RAM designed for Intel boards in his AMD board (he had received them as a gift, so he wasn't aware they were not compatible).
      My Computer


  9. Posts : 26
    Windows 7 64bit
    Thread Starter
       #49

    ASUS P8Z68-V PRO, Socket-1155
    Corsair Vengeance? DDR3 1600MHz 8GB CL8

    Ill try the DRAM when i get home and run the games that crash. I think ive seen that in BIOS, also think ive changed it so its 1600mhz. (which it already was)
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #50

    CORSAIR CMZ8GX3M2A1600C8(XMP) 8GB ( 2x 4GB ) DS - - 8-8-8-24 1.5 ● ● ●
    CORSAIR CMZ8GX3M2A1600C9(XMP) 8GB ( 2x 4GB ) DS - - 9-9-9-24 1.5 ● ● ●

    Yours appears to be CMZ8GX3M2A1600C8, so it should be fine. 1.5V, so try that first, then try 1.6V if 1.5V still causes crashes.
      My Computer


 
Page 5 of 6 FirstFirst ... 3456 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 05:34.
Find Us