New computer, new crashing

Discussion in 'Player Support' started by LordoftheMoo, Aug 14, 2019.

  1. LordoftheMoo New Member

    Hi all, I've been trying to get the game to run on a new computer. I haven't played EQ1 in about 5 years, and figured "why not". However, the fresh install I did is just dying without much of a trace. :(
    Launcher will run OK (though it's s l o w . . .) but on hitting PLAY, the eqgame.exe starts, and then things break.
    I've tried disabling the kitchen sink in the Compatibility section of the shortcut. I'm running as Administrator (though not doing that had the same issue). If I do NOTHING on the Compatibility page, the game exe starts, no window ever opens, and then the process hangs forever with 2 threads and only about 8MB of memory used. If I do any compatibility settings, it instead crashes with a C0000005 error and this in the dbg.txt:
    ---
    [Wed Aug 14 17:52:16 2019]00000:Starting EverQuest (Built Jul 12 2019 11:58:54)
    [Wed Aug 14 17:52:16 2019]00001:EverQuest Configuration Type: RELEASE_NON_AVATAR
    [Wed Aug 14 17:52:16 2019]00002:Timezone: UTC-5h00m
    [Wed Aug 14 17:52:16 2019]00003:Loading graphics DLL.
    [Wed Aug 14 17:52:16 2019]00004:parsing INI file .\eqclient.ini
    [Wed Aug 14 17:52:16 2019]00005:INI file .\eqclient.ini loaded.
    [Wed Aug 14 17:52:16 2019]00006:parsing INI file .\defaults.ini
    [Wed Aug 14 17:52:16 2019]00007:INI file .\defaults.ini loaded.
    [Wed Aug 14 17:52:16 2019]00008:Fatal error occurred in mainthread! (Release Client #630)

    [Wed Aug 14 17:52:16 2019]00009:Client Version: Jul 12 2019 11:58:54
    [Wed Aug 14 17:52:16 2019]00010:Skin Directory:

    [Wed Aug 14 17:52:16 2019]00011:Graphics DLL NOT Loaded.

    [Wed Aug 14 17:52:16 2019]00012:Skin Directory:

    [Wed Aug 14 17:52:16 2019]00013:processor: 12 of type 586
    [Wed Aug 14 17:52:16 2019]00014:Memory: Load: 7, Total Phys: 65456, Avail Phys: 60428, Total Page: 130911, Avail Page: 124209, Total Virtual: 4095, Avail Virtual: 3933, FreeBlocks: 2047,512,505,305,179,136,67,44,28,22
    ---
    This occurs with every OS Compatibility option right back to Win95. I've tried running the game directly, with and without the patchme option. Same behaviors under the same conditions. I have tried install DX9.0c from the distro files, but that finishes instantly with a message that installation is complete. The Websetup says that I'm already up to date.
    My OS (Win7) is up to date (except for a new patch released this week, apparently), as are my video drivers. Hardware is an AMD 1600 with an AMD R9 380, and 64GB RAM.

    Thanks in advance for any suggestions...
  2. Wulfhere Augur

    What you want to see is something like this:

    [Wed Aug 14 15:14:16 2019]00003:Loading graphics DLL.
    [Wed Aug 14 15:14:17 2019]00008:Graphics DLL Configuration Type: GraphicsDLL9
    [Wed Aug 14 15:14:17 2019]00009:Graphics DLL Version 2.00.111864

    Assuming you really do have the correct version of DX9 installed, try running EQ config from the patcher's advanced tools (settings) menu. Run through "game configuration" tool and confirm that EQ sees your graphics okay.


    Maybe try installing Win7 SP1 and then platform update (SP1) that includes D3D:

    https://support.microsoft.com/en-us/help/15090/windows-7-install-service-pack-1-sp1
    https://www.microsoft.com/en-us/download/details.aspx?id=5842
    https://www.microsoft.com/en-us/download/details.aspx?id=36805
  3. CatsPaws No response to your post cause your on ignore

  4. LordoftheMoo New Member

    @Wulfhere - I have SP1 and it appears I have the Platform update that you mention. So those don't look like it. The video card is being detected by the game. I've run the config a few times and tried turning everything off including sound, but nothing.

    @CatsPaws - Just tried that, it ran through the install, it looked like it copied files, but no joy. I wonder if I have to reboot to get those to pick up. Shouldn't, but who knows. I'll try that in a bit and see if that matters any.
  5. Sarkaukar Augur

    You did say new computer, and the dbg.txt you posted does not have anything removed from the top section, when actually loading the game is not recognizing a graphics card. It should be looking like the following...notice what is missing? Yours have no information on the GPU at all, it is crashing as it attempts to load up EQ.

    Do you have EQ shortcut setup to run as Admin? If you do change it to default, not Admin (some players had issues with that with some patches).

    Generate, save then post the top section of your system's dxdiag. The reason will be to see what information is in the GPU section.

    Have you allowed the computer to complete update itself? Edit Windows 7.. originally missed that one.

    Windows 10 by default also updates drivers and from personal experience when I had allowed it to update GPU drivers every 3rd or 4th driver update fraks things up (I allow this on a backup computer.. I am a masochist...)

    Reinstall motherboard drivers, reboot then reinstall your GPU driver.


    Corwyhn Lionheart likes this.
  6. LordoftheMoo New Member

    OK, I've gathered a lot more information on this, and it's still a puzzle.
    1. Updated my Mobo drivers. Didn't think that would work, but there were newer ones out, so why not. No effect. Didn't bother with video drivers because I JUST installed them a week ago, as there was a new version out. That was a clean installation.
    2. I tried reinstalling DX9 again as Administrator, but that doesn't look like it worked either. Same problems.
    3. I did some more poking in the failure itself, and I found that I have three different methods that it can fail.
    3a. If I have no settings checked such as Compatibility, the process will start, have two threads and 135 handles (always exactly), and nothing ever happens. It can sit there forever. dbg.txt is not written to.
    3b. If I turn on compatibility using any setting other than Windows 95, the game crashes instantly with a C0000005 exception. dbg.txt is not written to.
    3c. If I select Windows 95 Compatibility, I get an error box that allows me to enter information. This method of failure does make a dbg.txt. After installing DX9 a few times, the output has changed from the one I originally posted. Note in this new one that I'm now getting a video card listed, but it's Null, and not the R9 380:
    ---
    [Sat Aug 17 08:21:41 2019]00000:Starting EverQuest (Built Jul 12 2019 11:58:54)
    [Sat Aug 17 08:21:41 2019]00001:EverQuest Configuration Type: RELEASE_NON_AVATAR
    [Sat Aug 17 08:21:41 2019]00002:Timezone: UTC-5h00m
    [Sat Aug 17 08:21:41 2019]00003:Loading graphics DLL.
    [Sat Aug 17 08:21:41 2019]00004:parsing INI file .\eqclient.ini
    [Sat Aug 17 08:21:41 2019]00005:INI file .\eqclient.ini loaded.
    [Sat Aug 17 08:21:41 2019]00006:parsing INI file .\defaults.ini
    [Sat Aug 17 08:21:41 2019]00007:INI file .\defaults.ini loaded.
    [Sat Aug 17 08:21:42 2019]00008:Fatal error occurred in mainthread! (Release Client #630)

    [Sat Aug 17 08:21:42 2019]00009:Client Version: Jul 12 2019 11:58:54
    [Sat Aug 17 08:21:42 2019]00010:Skin Directory:

    [Sat Aug 17 08:21:42 2019]00011:Graphics DLL Loaded: Graphics DLL Version 2.00.111864
    [Sat Aug 17 08:21:42 2019]00012:Graphics Build Date: Jul 12 2019 12:00:35
    [Sat Aug 17 08:21:42 2019]00013:Video Card: (null), 0.0.0.0000

    [Sat Aug 17 08:21:42 2019]00014:processor: 12 of type 586
    [Sat Aug 17 08:21:42 2019]00015:Memory: Load: 6, Total Phys: 65456, Avail Phys: 61159, Total Page: 130911, Avail Page: 125825, Total Virtual: 4095, Avail Virtual: 3926, FreeBlocks: 2047,513,505,179,154,136,84,78,44,44
    [Sat Aug 17 08:21:42 2019]00016:CPU: AMD Ryzen 5 1600 Six-Core Processor 3119

    ---
    I've noted that the fatal error is where this following line (from Sarkaukar's example) should be if things were working OK:
    [Thu Aug 15 07:02:44 2019]00008:Graphics DLL Configuration Type: GraphicsDLL9
    but I'm not getting that. Also this ONLY occurs with Win95 compatibility on.
    Here is the info form the DxDiag log, Summary to video section. Ignor the line "D3D9 Overlay: Not supported". It's a red herring, as my old computer says the exact same thing and that machine still works.
    ---
    ------------------
    System Information
    ------------------
    Time of this report: 8/16/2019, 09:52:05
    Machine name: ----
    Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.190612-0600)
    Language: English (Regional Setting: English)
    System Manufacturer: System manufacturer
    System Model: System Product Name
    BIOS: BIOS Date: 09/07/18 18:35:57 Ver: 05.0000D
    Processor: AMD Ryzen 5 1600 Six-Core Processor (12 CPUs), ~3.2GHz
    Memory: 65536MB RAM
    Available OS Memory: 65456MB RAM
    Page File: 7504MB used, 123407MB available
    Windows Dir: C:\Windows
    DirectX Version: DirectX 11
    DX Setup Parameters: Not found
    User DPI Setting: Using System DPI
    System DPI Setting: 96 DPI (100 percent)
    DWM DPI Scaling: Disabled
    DxDiag Version: 6.01.7601.17514 32bit Unicode

    ------------
    DxDiag Notes
    ------------
    Display Tab 1: No problems found.
    Sound Tab 1: No problems found.
    Sound Tab 2: No problems found.
    Input Tab: No problems found.

    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D: 0/4 (retail)
    DirectDraw: 0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay: 0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow: 0/6 (retail)

    ---------------
    Display Devices
    ---------------
    Card name: AMD Radeon (TM) R9 380 Series
    Manufacturer: Advanced Micro Devices, Inc.
    Chip type: AMD Radeon Graphics Processor (0x6938)
    DAC type: Internal DAC(400MHz)
    Device Key: Enum\PCI\VEN_1002&DEV_6938&SUBSYS_E308174B&REV_F1
    Display Memory: 4095 MB
    Dedicated Memory: 3072 MB
    Shared Memory: 1023 MB
    Current Mode: 1920 x 1080 (32 bit) (60Hz)
    Monitor Name: Generic PnP Monitor
    Monitor Model: unknown
    Monitor Id: CVT0001
    Native Mode: 1920 x 1080(p) (60.000Hz)
    Output Type: HD15
    Driver Name: aticfx64.dll,aticfx64.dll,aticfx64.dll,amdxc64.dll,aticfx32,aticfx32,aticfx32,amdxc32,atiumd64.dll,atidxx64.dll,atidxx64.dll,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a.cap,atitmm64.dll
    Driver File Version: 26.20.13001.25001 (English)
    Driver Version: 26.20.13001.25001
    DDI Version: 11
    Driver Model: WDDM 1.1
    Driver Attributes: Final Retail
    Driver Date/Size: 7/30/2019 17:40:18, 1954120 bytes
    WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
    Device Identifier: {D7B71EE2-2A78-11CF-5215-C1F14AC2D735}
    Vendor ID: 0x1002
    Device ID: 0x6938
    SubSys ID: 0xE308174B
    Revision ID: 0x00F1
    Driver Strong Name: oem2.inf:ATI.Mfg.NTamd64.6.1.1:ati2mtag_Tonga:26.20.13001.25001:pci\ven_1002&dev_6938&rev_f1
    Rank Of Driver: 00E62000
    Video Accel:
    Deinterlace Caps: n/a
    D3D9 Overlay: Not Supported
    DXVA-HD: Not Supported
    DDraw Status: Enabled
    D3D Status: Enabled
    AGP Status: Enabled
    ---
    So now I'm starting to run out of ideas. I tried copying the exe files and dll files from the EQ directory on my old computer, but that didn't do anything (as expected). Given that it hangs under "normal mode" and crashes under compatibility, and the module failing is ntdll.dll itself, it makes me wonder if there is something in Windows itself, and not DX9, that's messing me up. Not sure what to do in that case, if it's true. I think there's a User Mode patch that is optional that I haven't installed, and I'll try that, but then I don't know what to try next...
  7. Metanis Bad Company

    Windows 7 becomes "unsupported" in less than 6 months. If you have a legit copy of Win7 you can still upgrade to Win10 for free from https://www.microsoft.com/en-us/software-download/windows10

    If you're determined to avoid Win10 the only other thing I'd try is to remove half your RAM and try it.
  8. CatsPaws No response to your post cause your on ignore

    Ah I totally missed the part where OP says he is running windows 7. I just saw the "new computer" part and assumed it was windows 10. But EQ supported windows xp and vista long after they were shelved so there is hope 7 will be around a bit for EQ.

    I still see DirectX 11 and I think it needs to be 9C - make sure your not doing an upgrade every time on the DX - but a separate install of the 9C

    Some good tips in this post https://forums.daybreakgames.com/eq/index.php?threads/eq-and-windows-7-not-working.3863/
  9. Sarkaukar Augur

    Windows OS will always show the latest directx version that is installed/compatible with it.

    Just to ensure the OP is installing the last version of dx9c, which is version version 9.29.1974, see below. I keep the redistribution file for when there is an issue with a directx 9 game and want to eliminate dx file corruption.

    OP, do you have other programs installed and running (possible conflicts)? Do not have to worry about a built-in GPU with your CPU (marking that off the checklist).

    Remove compatibility settings. Is admin privileges checked? Uncheck and test (or vis versa) Compatibility settings is primarily to be used when a game/program will not run under a newer OS. EQ generally does not require it for Windows 10, much less for Windows 7.

    And to be clear the system 64gigs of memory? How many sticks? 4? Drop it to 2 or one stick and test.

    And did you do any lengthy stress testing with the system?

    Corwyhn Lionheart likes this.
  10. CatsPaws No response to your post cause your on ignore

    Your not installed EQ from an old CD are you?
  11. LordoftheMoo New Member

    I've poked at this more today. To answer a few questions first though:
    - This was an install from the website. To be sure, however, I also installed from Steam. That had the same issue.
    - Yes I'm using the June 2010 distribution. I've downloaded it three times and run the installer as both an Admin user, and AS administrator. Each time it looks to install plenty of stuff into the correct places.
    - As I mentioned in my follow-up above, I've tried all options of the Compatibility setting. The only time it manages to write to the dbg.log is when it's set to Win95. Having it set to Off causes a hang of the process (with 2 threads every time), and any other setting is aC0000005 exception and the game crashes.
    - I've done the "Run as Administrator" and I've tried without. In combination with the Compatibility settings, and without, and in combination with "Run in 256 colors/Run in 640x480" and without. All the same results.
    - I did run some stress tests when I first built the system, and they checked out OK. It is 64G installed, and yes it's on 4 sticks. I can try dropping to one or two, but that's not really ideal, as I'm not keen on taking my system apart regularly to play a single game. :/
    - @metanis - Yeah, it's a legit copy, but I really do not want to go to Windows 10. I might have to at some point, I know, especially if I choose to upgrade to a Ryzen 3000 processor (new AMD drivers released end of July explicitly state 3000 series are Win10 only). But the longer I Can avoid the OS that Microsoft does whatever it wants to, whenever it wants to, the better.

    Now, for what I've found since, and if there were hard core technical support from the Dev side this might make a difference. I decided to grab a dump file from the hung, No compatibility set, process. Threw that into windbg, and found that it's throwing a couple of messages that could explain a hang. This is from the dump analysis:
    ---
    EXCEPTION_RECORD: (.exr -1)
    ExceptionAddress: 0000000000000000
    ExceptionCode: 80000003 (Break instruction exception)
    ExceptionFlags: 00000000
    NumberParameters: 0

    FAULTING_THREAD: 000016f8
    PROCESS_NAME: eqgame.exe
    OVERLAPPED_MODULE: Address regions for 'dinput8' and 'wsock32' overlap
    ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
    EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid
    EXCEPTION_CODE_STR: 80000003
    WATSON_BKT_PROCSTAMP: 5d28d8a7
    WATSON_BKT_MODULE: unknown
    WATSON_BKT_MODVER: 0.0.0.0
    WATSON_BKT_MODOFFSET: 0
    WATSON_BKT_MODSTAMP: bbbbbbb4
    BUILD_VERSION_STRING: 6.1.7601.24475 (win7sp1_ldr.190516-0600)
    MODLIST_WITH_TSCHKSUM_HASH: bdc15495392ea98ba2533983f7b2148da04f4a5b
    MODLIST_SHA1_HASH: 02a2994297cd27f57170cfc96de7815e116919fe
    NTGLOBALFLAG: 0
    PROCESS_BAM_CURRENT_THROTTLED: 0
    PROCESS_BAM_PREVIOUS_THROTTLED: 0
    APPLICATION_VERIFIER_FLAGS: 0
    PRODUCT_TYPE: 1
    SUITE_MASK: 272
    DUMP_FLAGS: c07
    DUMP_TYPE: 3
    ANALYSIS_SESSION_HOST: --------
    ANALYSIS_SESSION_TIME: 08-19-2019 02:54:09.0662
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    THREAD_ATTRIBUTES:
    OS_LOCALE: ENU
    BUGCHECK_STR: BREAKPOINT_OVERLAPPED_MODULE_CORRUPT_MODULELIST
    DEFAULT_BUCKET_ID: BREAKPOINT_OVERLAPPED_MODULE_CORRUPT_MODULELIST
    PRIMARY_PROBLEM_CLASS: BREAKPOINT
    PROBLEM_CLASSES:
    ID: [0n321]
    Type: [@APPLICATION_FAULT_STRING]
    Class: Primary
    Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
    BUCKET_ID
    Name: Omit
    Data: Add
    String: [BREAKPOINT]
    PID: [Unspecified]
    TID: [Unspecified]
    Frame: [0]
    ID: [0n151]
    Type: [CORRUPT_MODULELIST]
    Class: Addendum
    Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
    BUCKET_ID
    Name: Add
    Data: Omit
    PID: [Unspecified]
    TID: [Unspecified]
    Frame: [0]
    ID: [0n152]
    Type: [OVERLAPPED_MODULE]
    Class: Addendum
    Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
    BUCKET_ID
    Name: Add
    Data: Omit
    PID: [Unspecified]
    TID: [Unspecified]
    Frame: [0]
    LAST_CONTROL_TRANSFER: from 0000000074fe2bf1 to 0000000074fe2e09

    STACK_TEXT:
    00000000`0018ea08 00000000`74fe2bf1 : 00000000`75d5a965 00000000`75050023 00000000`00000246 00000000`0048f008 : wow64cpu!CpupSyscallStub+0x9
    00000000`0018ea10 00000000`7505d286 : 00000000`00000000 00000000`74fe1920 00000000`77be3128 00000000`77c1c4f1 : wow64cpu!Thunk0ArgReloadState+0x23
    00000000`0018ead0 00000000`7505c69e : 00000000`00000000 00000000`00000000 00000000`75054b10 00000000`7ffe0030 : wow64!RunCpuSimulation+0xa
    00000000`0018eb20 00000000`77c143c3 : 00000000`000a2ea0 00000000`00000000 00000000`77d12e70 00000000`77be7550 : wow64!Wow64LdrpInitialize+0x42a
    00000000`0018f070 00000000`77c79780 : 00000000`00000000 00000000`77c86c7d 00000000`0018f620 00000000`00000000 : ntdll!LdrpInitializeProcess+0x17e3
    00000000`0018f560 00000000`77c2371e : 00000000`0018f620 00000000`00000000 00000000`fffdf000 00000000`00000000 : ntdll! ?? ::FNODOBFM::`string'+0x22790
    00000000`0018f5d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe

    STACK_COMMAND: ~0s; .ecxr ; kb
    THREAD_SHA1_HASH_MOD_FUNC: 01470e8c2fda97324518d4d4636a1ab62077ff45
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 5ad8866a30b312f5cb1cbc6a5f0586ba4d3ae7a7
    THREAD_SHA1_HASH_MOD: 31cc8129c2e727f537d516c2527e18338fe11819
    FOLLOWUP_IP:
    wow64cpu!CpupSyscallStub+9
    00000000`74fe2e09 c3 ret
    FAULT_INSTR_CODE: ccccccc3
    SYMBOL_STACK_INDEX: 0
    SYMBOL_NAME: wow64cpu!CpupSyscallStub+9
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: wow64cpu
    IMAGE_NAME: wow64cpu.dll
    DEBUG_FLR_IMAGE_TIMESTAMP: 5cdd7d5b
    BUCKET_ID: X64_BREAKPOINT_OVERLAPPED_MODULE_CORRUPT_MODULELIST_wow64cpu!CpupSyscallStub+9

    FAILURE_EXCEPTION_CODE: 80000003
    FAILURE_IMAGE_NAME: wow64cpu.dll
    BUCKET_ID_IMAGE_STR: wow64cpu.dll
    FAILURE_MODULE_NAME: wow64cpu
    BUCKET_ID_MODULE_STR: wow64cpu
    FAILURE_FUNCTION_NAME: CpupSyscallStub
    BUCKET_ID_FUNCTION_STR: CpupSyscallStub
    BUCKET_ID_OFFSET: 9
    BUCKET_ID_MODTIMEDATESTAMP: 5cdd7d5b
    BUCKET_ID_MODCHECKSUM: ae55
    BUCKET_ID_MODVER_STR: 6.1.7601.24475
    BUCKET_ID_PREFIX_STR: X64_BREAKPOINT_OVERLAPPED_MODULE_CORRUPT_MODULELIST_
    FAILURE_PROBLEM_CLASS: BREAKPOINT
    FAILURE_SYMBOL_NAME: wow64cpu.dll!CpupSyscallStub
    FAILURE_BUCKET_ID: BREAKPOINT_OVERLAPPED_MODULE_CORRUPT_MODULELIST_80000003_wow64cpu.dll!CpupSyscallStub
    TARGET_TIME: 2019-08-18T14:18:35.000Z
    OSBUILD: 7601
    OSSERVICEPACK: 24475
    SERVICEPACK_NUMBER: 0
    OS_REVISION: 0
    OSPLATFORM_TYPE: x64
    OSNAME: Windows 7
    OSEDITION: Windows 7 WinNt (Service Pack 1) SingleUserTS
    USER_LCID: 0
    OSBUILD_TIMESTAMP: 2019-05-16 11:21:52
    BUILDDATESTAMP_STR: 190516-0600
    BUILDLAB_STR: win7sp1_ldr
    BUILDOSVER_STR: 6.1.7601.24475
    ANALYSIS_SESSION_ELAPSED_TIME: 4d1
    ANALYSIS_SOURCE: UM
    FAILURE_ID_HASH_STRING: um:breakpoint_overlapped_module_corrupt_modulelist_80000003_wow64cpu.dll!cpupsyscallstub
    FAILURE_ID_HASH: {1c5a6b56-ae36-ceee-7e43-d8371111c7d6}
    ---

    From this, is looks like it's hanging in the WOW64 32bit virtualization module of Windows. I'm not sure why that's hanging, but the message about two memory regions overlapping might mean something to someone more familiar with the code, or with how WOW64 works. I did some searching but I didn't find much. I'm starting to suspect that there is something about Win7 on an AMD that has an issue specifically with EQ. While I do have the drivers installed that were just released, that doesn't mean they work perfectly. Of note the WOW64 subsystem is working with other programs, including games. I am tempted to try dropping to 16GB RAM just to see, but if that's the fix then, well, that's not really a fix. :/
  12. Sarkaukar Augur

    Try reducing the memory, to see if it works, for a temp solution, but I do not believe it will. But I would suggest keeping at that amount if you reinstall Windows and while running the updates. If it does work then memory may be faulty or unstable. That file supports 32 bit applications running in 64 bit machine.

    What I found was for users who had that issue, for a few it affected several programs, others it only affected a few programs, was likely due to a failure with the installation and/or windows update. Most reinstalled windows and took time on the windows up.

    A few copied the file from a working Windows 7 system and went through the process of having windows take ownership of the new file. This did not work for a few others who tried this method.

    If you do a reinstallation. Wait until all the Windows updates have been installed successfully. Reboot and run the Windows update to make sure. Install the redistribution Direct 9C file. Download and install EQ and try it before doing any driver updates.
  13. I_Love_My_Bandwidth Mercslayer

    This line from your EQ.dbg

    [Wed Aug 14 17:52:16 2019]00011:Graphics DLL NOT Loaded.


    This is straight up either DX9 or an incompatible graphics driver is installed. Try an older graphics driver. Also, if you installed a graphics card, ensure any onboard graphics card is disabled. Win7 does NOT have the capability to properly address two different graphics chipsets without additional software.

    Good luck!
    CatsPaws and Metanis like this.
  14. Metanis Bad Company

    I hope the OP will post his fix when he finds it.
  15. Flying-Chick New Member

    I get the same problem a while back after making a new PC and come back to EQ after several years. I did contact DB support and tried everything they told me without any joy at all. Then I went out to the "great www" and start searching and asking questions.

    From what I found back then, I believe it should be that EQ isn't compatible with some type of CPUs and/or GPUs. For this, SOE and/or DB would never admit it regardless provide a list of compatible and/or non-compatible CPU and GPUs.

    So, I am going to sit on this and see if any replies that can actually solve this.

    ----------------------------------
    Intel Core i7-7700 CPU @ 3.60GHz
    NVidia GeForce GTX 1060 6GB
    64GB RAM
    Win 7 Pro (legit with key code, purchased a long time ago)
  16. CatsPaws No response to your post cause your on ignore

    Well the error message would help but usually at that point it something to do with graphics like the 9c or settings in game and computer to same resolution to get signed in or try alt tab (windowed/non windowed)

    One of my computers is almost the same as yours with windows 7 and really old. I don't buy the non compatibility theory. Might have been on old systems but anything in the last 8 years will run fine. OH, except for windows Vista and XP -yeah can't use those anymore;)

    It could also be something simple like windows firewall or your avg.

    You could always pm Sarkaukar (his name is in some posts above) cause he really has a handle of this more so than DBG tech. He pretty much rules trouble shooting issues.
  17. Flying-Chick New Member

    Thanks!

    I will get to this when I have the time to sit down and started again...50 years of age and still want to play this darn old game...don't know whether its pathetic or else..ha!
  18. skabe Elder

    There is your problem right there. The latest AMD graphics drivers are not compatible with EQ is my guess.
  19. aiha Saryrn [Bertox]

    Happening to me also >> log/pass Launcher >> Play >> black screen >>Everquest Crash Notification.

    No hardware changes, crashing started after win10 updated from 1809 to 1903. Worked fine with 2080ti + 425.31 driver on 1809. Same driver and crashing on 1903. Updated to 436.48 driver (unplug ethernet, safeboot, DDU clean, install new), same crash.

    Have tried deleting eqclient.ini, changing resolutions in launcher config (640x480, 1024x768, etc), running with typical offenders disabled (RTSSoverlay/Firewall).

    I can't install the June 2010 DX Sarkaukar linked earlier, the direct DL link is broken and the dxwebsetup version tells me it won't install due to a newer version of DX.

    Will update as I try more stuff, but I don't really play EQ anymore, just log on once a month to keep guild hall from poofing. Got about a week to get this working or it's pretty much over.
  20. aiha Saryrn [Bertox]

    Tried a few edits on the new eqclient.ini (that's virtually empty): turning widowed mode on and setting to native resolution:

    [Defaults]
    WindowedMode=TRUE

    [VideoMode]
    Width=2560
    Height=1440
    WindowedWidth=2560
    WindowedHeight=1440

    Also sorted EQ dir by date and deleted everything newer than my last login (sept 8). Then ran launcher and validated files. No, joy... highly doubt its a file issue though, really seems to be something video related.

    When I try running it (eqgame.exe) in compatability for win7 and win8 I get the same crash. For winXP (SP3) I get the following launcher error: Unable to launch H:/Game/EQ/eqgame.exe - 740: The requested operation requires elevation. I'm on an admin account though, so not sure whats happening. There is no dbg.txt being output.

    Integrated graphics is disabled via BIOS. This computer has been running the same hardware for just over a year now, and has been running EQ just fine for 11 months. Crashing started after win10 updated from 1809 to 1903.

    Partial Dxdiag: (due to post character limit)
    Code:
    ------------------
    System Information
    ------------------
          Time of this report: 10/3/2019, 17:58:44
                Machine name: JWPC
                  Machine Id: {1775C640-50DC-43D1-A54F-D5BE94F54020}
            Operating System: Windows 10 Pro 64-bit (10.0, Build 18362) (18362.19h1_release.190318-1202)
                    Language: English (Regional Setting: English)
          System Manufacturer: To Be Filled By O.E.M.
                System Model: To Be Filled By O.E.M.
                        BIOS: P3.30 (type: UEFI)
                    Processor: Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz (6 CPUs), ~3.6GHz
                      Memory: 16384MB RAM
          Available OS Memory: 16312MB RAM
                    Page File: 6349MB used, 12394MB available
                  Windows Dir: C:\WINDOWS
              DirectX Version: DirectX 12
          DX Setup Parameters: Not found
            User DPI Setting: 96 DPI (100 percent)
          System DPI Setting: 96 DPI (100 percent)
              DWM DPI Scaling: Enabled
                    Miracast: Available, with HDCP
    Microsoft Graphics Hybrid: Not Supported
    DirectX Database Version: Unknown
              DxDiag Version: 10.00.18362.0329 64bit Unicode
     
    ------------
    DxDiag Notes
    ------------
          Display Tab 1: No problems found.
            Sound Tab 1: No problems found.
            Sound Tab 2: No problems found.
              Input Tab: No problems found.
     
    --------------------
    DirectX Debug Levels
    --------------------
    Direct3D:    0/4 (retail)
    DirectDraw:  0/4 (retail)
    DirectInput: 0/5 (retail)
    DirectMusic: 0/5 (retail)
    DirectPlay:  0/9 (retail)
    DirectSound: 0/5 (retail)
    DirectShow:  0/6 (retail)
     
    ---------------
    Display Devices
    ---------------
              Card name: NVIDIA GeForce RTX 2080 Ti
            Manufacturer: NVIDIA
              Chip type: GeForce RTX 2080 Ti
                DAC type: Integrated RAMDAC
            Device Type: Full Device (POST)
              Device Key: Enum\PCI\VEN_10DE&DEV_1E07&SUBSYS_150319DA&REV_A1
          Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
    Device Problem Code: No Problem
    Driver Problem Code: Unknown
          Display Memory: 19203 MB
        Dedicated Memory: 11048 MB
          Shared Memory: 8155 MB
            Current Mode: 2560 x 1440 (32 bit) (100Hz)
            HDR Support: Not Supported
        Display Topology: Internal
    Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
        Color Primaries: Red(0.639648,0.330078), Green(0.299805,0.599609), Blue(0.150391,0.059570), White Point(0.312500,0.329102)
      Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
            Monitor Name: Generic PnP Monitor
          Monitor Model: XB271HU
              Monitor Id: ACR0490
            Native Mode: 2560 x 1440(p) (59.951Hz)
            Output Type: Displayport External
    Monitor Capabilities: HDR Not Supported
    Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
          Advanced Color: Not Supported
            Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_827405c7c65146ab\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_827405c7c65146ab\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_827405c7c65146ab\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_827405c7c65146ab\nvldumdx.dll
    Driver File Version: 26.21.0014.3648 (English)
          Driver Version: 26.21.14.3648
            DDI Version: 12
          Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
            Driver Model: WDDM 2.6
    Graphics Preemption: Pixel
      Compute Preemption: Dispatch
                Miracast: Not Supported
          Detachable GPU: No
    Hybrid Graphics GPU: Not Supported
          Power P-states: Not Supported
          Virtualization: Paravirtualization
              Block List: No Blocks
      Catalog Attributes: Universal:False Declarative:False
      Driver Attributes: Final Retail
        Driver Date/Size: 9/25/2019 8:00:00 PM, 961896 bytes
            WHQL Logo'd: n/a
        WHQL Date Stamp: n/a
      Device Identifier: {D7B71E3E-5D47-11CF-2A74-0D351BC2D735}
              Vendor ID: 0x10DE
              Device ID: 0x1E07
              SubSys ID: 0x150319DA
            Revision ID: 0x00A1
      Driver Strong Name: oem11.inf:0f066de3e9306272:Section002:26.21.14.3648:pci\ven_10de&dev_1e07
          Rank Of Driver: 00D12001
            Video Accel:
            DXVA2 Modes: DXVA2_ModeMPEG2_VLD  DXVA2_ModeVC1_D2010  DXVA2_ModeVC1_VLD  DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT  DXVA2_ModeH264_VLD_Stereo_NoFGT  DXVA2_ModeH264_VLD_NoFGT  DXVA2_ModeHEVC_VLD_Main  DXVA2_ModeHEVC_VLD_Main10  DXVA2_ModeMPEG4pt2_VLD_Simple  DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC  DXVA2_ModeVP9_VLD_Profile0  DXVA2_ModeVP9_VLD_10bit_Profile2 
      Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC1,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC2,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC3,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(IMC4,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S340,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {F9F19DA5-3B09-4B2F-9D89-C64753E3EAAB}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {5A54A0C9-C7EC-4BD9-8EDE-F3C75DC4393B}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
                        {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(S342,UNKNOWN) Frames(Prev/Fwd/Back)=(0,0,0) Caps=
            D3D9 Overlay: Supported
                DXVA-HD: Supported
            DDraw Status: Enabled
              D3D Status: Enabled
              AGP Status: Enabled
          MPO MaxPlanes: 1
                MPO Caps: Not Supported
            MPO Stretch: Not Supported
        MPO Media Hints: Not Supported
            MPO Formats: Not Supported
        PanelFitter Caps: Not Supported
    PanelFitter Stretch: Not Supported
     
    -------------
    Sound Devices
    -------------
                Description: Speakers (ASUS Xonar Essence STX Audio Device)
    Default Sound Playback: Yes
    Default Voice Playback: Yes
                Hardware ID: PCI\VEN_13F6&DEV_8788&SUBSYS_835C1043&REV_00
            Manufacturer ID: 1
                Product ID: 100
                      Type: WDM
                Driver Name: cmudaxp.sys
            Driver Version: 0.00.0008.1825 (English)
          Driver Attributes: Final Retail
                WHQL Logo'd: n/a
              Date and Size: 6/22/2016 12:00:00 AM, 2818168 bytes
                Other Files:
            Driver Provider: ASUSTeK
            HW Accel Level: Basic
                  Cap Flags: 0x0
        Min/Max Sample Rate: 0, 0
    Static/Strm HW Mix Bufs: 0, 0
    Static/Strm HW 3D Bufs: 0, 0
                  HW Memory: 0
          Voice Management: No
    EAX(tm) 2.0 Listen/Src: No, No
      I3DL2(tm) Listen/Src: No, No
    Sensaura(tm) ZoomFX(tm): No
     
                Description: S/PDIF Pass-through Device (ASUS Xonar Essence STX Audio Device)
    Default Sound Playback: No
    Default Voice Playback: No
                Hardware ID: PCI\VEN_13F6&DEV_8788&SUBSYS_835C1043&REV_00
            Manufacturer ID: 1
                Product ID: 100
                      Type: WDM
                Driver Name: cmudaxp.sys
            Driver Version: 0.00.0008.1825 (English)
          Driver Attributes: Final Retail
                WHQL Logo'd: n/a
              Date and Size: 6/22/2016 12:00:00 AM, 2818168 bytes
                Other Files:
            Driver Provider: ASUSTeK
            HW Accel Level: Basic
                  Cap Flags: 0x0
        Min/Max Sample Rate: 0, 0
    Static/Strm HW Mix Bufs: 0, 0
    Static/Strm HW 3D Bufs: 0, 0
                  HW Memory: 0
          Voice Management: No
    EAX(tm) 2.0 Listen/Src: No, No
      I3DL2(tm) Listen/Src: No, No
    Sensaura(tm) ZoomFX(tm): No
     
    ---------------------
    Sound Capture Devices
    ---------------------
    ---------------------
    Video Capture Devices
    Number of Devices: 0
    ---------------------
    -------------------
    DirectInput Devices
    -------------------
          Device Name: Mouse
            Attached: 1
        Controller ID: n/a
    Vendor/Product ID: n/a
            FF Driver: n/a
     
          Device Name: Keyboard
            Attached: 1
        Controller ID: n/a
    Vendor/Product ID: n/a
            FF Driver: n/a
     
          Device Name: Controller (Xbox One For Windows)
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x045E, 0x02FF
            FF Driver: n/a
     
          Device Name: ROCCAT Kone Pure Owl-Eye
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x1E7D, 0x2DCD
            FF Driver: n/a
     
          Device Name: ROCCAT Kone Pure Owl-Eye
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x1E7D, 0x2DCD
            FF Driver: n/a
     
          Device Name: ROCCAT Kone Pure Owl-Eye
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x1E7D, 0x2DCD
            FF Driver: n/a
     
          Device Name: ROCCAT Kone Pure Owl-Eye
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x1E7D, 0x2DCD
            FF Driver: n/a
     
          Device Name: Logitech G710 Keyboard
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x046D, 0xC24D
            FF Driver: n/a
     
          Device Name: Logitech G710 Keyboard
            Attached: 1
        Controller ID: 0x0
    Vendor/Product ID: 0x046D, 0xC24D
            FF Driver: n/a
     
    Poll w/ Interrupt: No
     
    -----------
    USB Devices
    -----------
    + USB Root Hub (USB 3.0)
    | Vendor/Product ID: 0x8086, 0xA2AF
    | Matching Device ID: USB\ROOT_HUB30
    | Service: USBHUB3
    | Driver: USBHUB3.SYS, 3/19/2019 00:43:43, 618296 bytes
    |
    +-+ USB Composite Device
    | | Vendor/Product ID: 0x1E7D, 0x2DCD
    | | Location: Port_#0006.Hub_#0002
    | | Matching Device ID: USB\COMPOSITE
    | | Service: usbccgp
    | | Driver: usbccgp.sys, 3/19/2019 00:43:43, 183608 bytes
    | |
    | +-+ USB Input Device
    | | | Vendor/Product ID: 0x1E7D, 0x2DCD
    | | | Location: 0000.0014.0000.006.000.000.000.000.000
    | | | Matching Device ID: USB\Class_03&SubClass_01
    | | | Service: HidUsb
    | | | Driver: hidusb.sys, 8/24/2019 14:39:13, 45568 bytes
    | | | Driver: hidclass.sys, 8/24/2019 14:39:13, 211968 bytes
    | | | Driver: hidparse.sys, 8/24/2019 14:39:13, 46080 bytes
    | | |
    | | +-+ HID-compliant mouse
    | | | | Vendor/Product ID: 0x1E7D, 0x2DCD
    | | | | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
    | | | | Service: mouhid
    | | | | Driver: mouhid.sys, 3/19/2019 00:43:43, 35840 bytes
    | | | | Driver: mouclass.sys, 3/19/2019 00:43:43, 66872 bytes
    | | |
    | +-+ USB Input Device
    | | | Vendor/Product ID: 0x1E7D, 0x2DCD
    | | | Location: 0000.0014.0000.006.000.000.000.000.000
    | | | Matching Device ID: USB\Class_03
    | | | Service: HidUsb
    | | | Driver: hidusb.sys, 8/24/2019 14:39:13, 45568 bytes
    | | | Driver: hidclass.sys, 8/24/2019 14:39:13, 211968 bytes
    | | | Driver: hidparse.sys, 8/24/2019 14:39:13, 46080 bytes
    | | |
    | | +-+ HID Keyboard Device
    | | | | Vendor/Product ID: 0x1E7D, 0x2DCD
    | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
    | | | | Service: kbdhid
    | | | | Driver: kbdhid.sys, 3/19/2019 00:43:43, 46592 bytes
    | | | | Driver: kbdclass.sys, 3/19/2019 00:43:43, 70968 bytes
    | |
    +-+ USB Composite Device
    | | Vendor/Product ID: 0x046D, 0xC24D
    | | Location: Port_#0009.Hub_#0002
    | | Matching Device ID: USB\COMPOSITE
    | | Service: usbccgp
    | | Driver: usbccgp.sys, 3/19/2019 00:43:43, 183608 bytes
    | |
    | +-+ USB Input Device
    | | | Vendor/Product ID: 0x046D, 0xC24D
    | | | Location: 0000.0014.0000.009.000.000.000.000.000
    | | | Matching Device ID: USB\Class_03&SubClass_01
    | | | Service: HidUsb
    | | | Driver: hidusb.sys, 8/24/2019 14:39:13, 45568 bytes
    | | | Driver: hidclass.sys, 8/24/2019 14:39:13, 211968 bytes
    | | | Driver: hidparse.sys, 8/24/2019 14:39:13, 46080 bytes
    | | |
    | | +-+ HID Keyboard Device
    | | | | Vendor/Product ID: 0x046D, 0xC24D
    | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
    | | | | Service: kbdhid
    | | | | Driver: kbdhid.sys, 3/19/2019 00:43:43, 46592 bytes
    | | | | Driver: kbdclass.sys, 3/19/2019 00:43:43, 70968 bytes
    | | |
    | +-+ USB Input Device
    | | | Vendor/Product ID: 0x046D, 0xC24D
    | | | Location: 0000.0014.0000.009.000.000.000.000.000
    | | | Matching Device ID: USB\Class_03
    | | | Service: HidUsb
    | | | Driver: hidusb.sys, 8/24/2019 14:39:13, 45568 bytes
    | | | Driver: hidclass.sys, 8/24/2019 14:39:13, 211968 bytes
    | | | Driver: hidparse.sys, 8/24/2019 14:39:13, 46080 bytes
    | | |
    | | +-+ HID Keyboard Device
    | | | | Vendor/Product ID: 0x046D, 0xC24D
    | | | | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
    | | | | Service: kbdhid
    | | | | Driver: kbdhid.sys, 3/19/2019 00:43:43, 46592 bytes
    | | | | Driver: kbdclass.sys, 3/19/2019 00:43:43, 70968 bytes
     
    ----------------
    Gameport Devices
    ----------------
     
    ------------
    PS/2 Devices
    ------------
    + HID Keyboard Device
    | Vendor/Product ID: 0x046D, 0xC232
    | Matching Device ID: HID_DEVICE_SYSTEM_KEYBOARD
    | Service: kbdhid
    | Driver: kbdhid.sys, 3/19/2019 00:43:43, 46592 bytes
    | Driver: kbdclass.sys, 3/19/2019 00:43:43, 70968 bytes
    |
    + HID-compliant mouse
    | Vendor/Product ID: 0x046D, 0xC231
    | Matching Device ID: HID_DEVICE_SYSTEM_MOUSE
    | Service: mouhid
    | Driver: mouhid.sys, 3/19/2019 00:43:43, 35840 bytes
    | Driver: mouclass.sys, 3/19/2019 00:43:43, 66872 bytes
     
    ------------------------
    Disk & DVD/CD-ROM Drives
    ------------------------
          Drive: C:
    Free Space: 248.6 GB
    Total Space: 428.6 GB
    File System: NTFS
          Model: Samsung SSD 970 EVO 500GB
     
          Drive: H:
    Free Space: 95.7 GB
    Total Space: 476.9 GB
    File System: NTFS
          Model: Samsung SSD 840 EVO 500GB
     
          Drive: I:
    Free Space: 142.0 GB
    Total Space: 953.9 GB
    File System: NTFS
          Model: Samsung SSD 850 EVO 1TB
     
          Drive: J:
    Free Space: 615.6 GB
    Total Space: 1907.7 GB
    File System: NTFS
          Model: WDC WD20EFRX-68EUZN0
     
          Drive: K:
    Free Space: 1002.7 GB
    Total Space: 1907.7 GB
    File System: NTFS
          Model: Hitachi HDS723020BLA642
     
          Drive: G:
          Model: ASUS DRW-24B1ST  c
        Driver: C:\WINDOWS\SYSTEM32\DRIVERS\CDROM.SYS, 10.00.18362.0001 (English), 3/19/2019 00:43:39, 173056 bytes