BSOD while gaming, KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe


  1. Posts : 2
    Windows 7 Ultimate x64
       #1

    BSOD while gaming, KMODE_EXCEPTION_NOT_HANDLED ntoskrnl.exe


    Hey, it's been happening for a while now, whenever I play a recent game, like NBA 2K12 or Dirt 3, I'll get random BSOD's it's very annoying, the sound will start skipping and it will BSOD.

    KMODE_EXCEPTION_NOT_HANDLED 0x0000001e ntoskrnl.exe+70010

    I attached the minidump.
      My Computer


  2. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #2

    Hello there!

    Seems like the crash is caused by your gaming controller CM2793.sys possibly Snakebyte FFXIV game controller. Please remove the driver and reinstall it.

    Code:
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1E
    
    PROCESS_NAME:  nba2k12.exe
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF88002F22FB0
    
    EXCEPTION_RECORD:  fffff88002f22958 -- (.exr 0xfffff88002f22958)
    ExceptionAddress: fffff8800804b783 (CM2793+0x0000000000000783)
       ExceptionCode: c0000094 (Integer divide-by-zero)
      ExceptionFlags: 00000000
    NumberParameters: 0
    
    TRAP_FRAME:  fffff88002f22a00 -- (.trap 0xfffff88002f22a00)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000002008 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800804b783 rsp=fffff88002f22b98 rbp=fffffa80059d98f0
     r8=00000000000000ad  r9=fffffa8005a3bb7a r10=0000000000000000
    r11=0000000000000005 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    CM2793+0x783:
    fffff880`0804b783 ??              ???
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002c80d6e to fffff80002c89010
    
    STACK_TEXT:  
    fffff880`02f21a48 fffff800`02c80d6e : fffffa80`04b5d1a0 fffff880`0147aa39 fffff880`02f221c0 fffff800`02cb59a8 : nt!KeBugCheck
    fffff880`02f21a50 fffff800`02cae75d : fffff800`02e96b1c fffff800`02dcfac4 fffff800`02c19000 fffff880`02f22958 : nt!KiKernelCalloutExceptionHandler+0xe
    fffff880`02f21a80 fffff800`02cb5dd0 : fffff800`02dd7990 fffff880`02f21af8 fffff880`02f22958 fffff800`02c19000 : nt!RtlpExecuteHandlerForException+0xd
    fffff880`02f21ab0 fffff800`02cc2dff : fffff880`02f22958 fffff880`02f221c0 fffff880`00000000 00000000`000000ff : nt!RtlDispatchException+0x410
    fffff880`02f22190 fffff800`02c88682 : fffff880`02f22958 00000000`00000000 fffff880`02f22a00 fffffa80`05a3bb20 : nt!KiDispatchException+0x16f
    fffff880`02f22820 fffff800`02c85e74 : 00000000`00000000 fffffa80`0451d010 fffffa80`05b48f30 fffff880`072097da : nt!KiExceptionDispatch+0xc2
    fffff880`02f22a00 fffff880`0804b783 : fffffa80`05a3bb60 fffffa80`0517d030 fffff880`0804b7e8 fffffa80`04ff5000 : nt!KiDivideErrorFault+0xf4
    fffff880`02f22b98 fffffa80`05a3bb60 : fffffa80`0517d030 fffff880`0804b7e8 fffffa80`04ff5000 00000000`00000000 : CM2793+0x783
    fffff880`02f22ba0 fffffa80`0517d030 : fffff880`0804b7e8 fffffa80`04ff5000 00000000`00000000 00000000`00000000 : 0xfffffa80`05a3bb60
    fffff880`02f22ba8 fffff880`0804b7e8 : fffffa80`04ff5000 00000000`00000000 00000000`00000000 fffff800`031f86e5 : 0xfffffa80`0517d030
    fffff880`02f22bb0 fffffa80`04ff5000 : 00000000`00000000 00000000`00000000 fffff800`031f86e5 00000000`00000000 : CM2793+0x7e8
    fffff880`02f22bb8 00000000`00000000 : 00000000`00000000 fffff800`031f86e5 00000000`00000000 00000000`00000000 : 0xfffffa80`04ff5000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    CM2793+783
    fffff880`0804b783 ??              ???
    
    SYMBOL_STACK_INDEX:  7
    
    SYMBOL_NAME:  CM2793+783
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: CM2793
    
    IMAGE_NAME:  CM2793.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c94757f
    
    FAILURE_BUCKET_ID:  X64_0x1E_CM2793+783
    
    BUCKET_ID:  X64_0x1E_CM2793+783
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 2
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks for responding. I suspected it was the controller but I didn't think it could cause BSOD's.
    I used driver manager to uninstall it, and I reinstalled.
    It seems to have caused it again, so is the controllers driver itself just faulty?
      My Computer


  4. Posts : 4,772
    Windows 7 Ultimate - 64-bit | Windows 8 Pro - 64-bit
       #4

    Hi there!

    You can try diffferent drivers if not it could be very well the controller itself.
      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 21:00.
Find Us