BSOD While playing FFXI/FFXIV + more.


  1. Posts : 2
    Windows 7 home 64
       #1

    BSOD While playing FFXI/FFXIV + more.


    I've been struggling with this for over a year now. Always seem to rid myself of it for a few days then it just comes right back. Finally at my end with it and decided its time to seek out help from more knowledged people than myself. There is no consistency in the rate it happens I can go all day, a couple days, or I wont even make it 10 minutes back to back without having to stare at the joy of the BSOD. If somebody could figure this out i'd appreciate it cause I have ran out of ideas other than throwing this laptop infront of a vehicle.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    The cause of your BSOD's are this driver:

    CM2793.sys Sat Sep 18 14:17:03 2010
    Snakebyte FFXIV gamepad controller driver One recommended fix = uninstall the driver

    Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Win7 systems (mostly due to the sptd.sys driver, although we have seen dtsoftbus01.sys blamed on several occasions). Please uninstall Daemon Tools.

    As an alternative, many people recommend the use of Total Mounter or Magic ISO

    Use the System File Checker tool and Run Disk Check:

    Make scans with -

    Uninstall Sunbelt Firewall Software and Ad-Aware Antivirus. Replace with Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:
    • Do not start the trial version of MalwareBytes

    You may also take a look at:

       Information
    • Download and install Revo Uninstaller free from here:
      Opt for "Advanced Mode" and uninstall the software (also delete the leftover registry entries).


    Monitor hardware temperature with system monitoring software like Speccy or HWMonitor:


    BSOD SUMMARY:
    Code:
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Thu Aug  8 16:38:27.785 2013 (UTC + 6:00)
    System Uptime: 0 days 4:43:38.299
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CM2793.sys
    *** ERROR: Module load completed but symbols could not be loaded for CM2793.sys
    Probably caused by : CM2793.sys ( CM2793+783 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Thu Aug  8 11:10:31.152 2013 (UTC + 6:00)
    System Uptime: 0 days 1:17:43.650
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CM2793.sys
    *** ERROR: Module load completed but symbols could not be loaded for CM2793.sys
    Probably caused by : CM2793.sys ( CM2793+783 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  pcsx2.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Thu Aug  8 09:52:17.723 2013 (UTC + 6:00)
    System Uptime: 0 days 0:32:21.847
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CM2793.sys
    *** ERROR: Module load completed but symbols could not be loaded for CM2793.sys
    Probably caused by : CM2793.sys ( CM2793+783 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  pcsx2.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Thu Aug  8 09:19:25.844 2013 (UTC + 6:00)
    System Uptime: 3 days 18:56:48.968
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CM2793.sys
    *** ERROR: Module load completed but symbols could not be loaded for CM2793.sys
    Probably caused by : CM2793.sys ( CM2793+783 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  pcsx2.exe
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Aug  4 14:22:05.818 2013 (UTC + 6:00)
    System Uptime: 0 days 2:55:11.728
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CM2793.sys
    *** ERROR: Module load completed but symbols could not be loaded for CM2793.sys
    Probably caused by : CM2793.sys ( CM2793+783 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
    Debug session time: Sun Aug  4 11:25:58.366 2013 (UTC + 6:00)
    System Uptime: 2 days 10:05:05.490
    BugCheck 1E, {0, 0, 0, 0}
    *** WARNING: Unable to verify timestamp for CM2793.sys
    *** ERROR: Module load completed but symbols could not be loaded for CM2793.sys
    Probably caused by : CM2793.sys ( CM2793+783 )
    BUGCHECK_STR:  0x1E
    PROCESS_NAME:  System
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
      My Computer


  3. Posts : 2
    Windows 7 home 64
    Thread Starter
       #3

    How would I locate and uninstall that driver? I was under the impression I had already uninstalled / deleted it.
      My Computer


  4. Posts : 15,026
    Windows 10 Home 64Bit
       #4

    To perform a clean install of a driver, You can follow this tutorial:
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    Any update?
      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 22:26.
Find Us