Jump to content

Justin

Members
  • Posts

    22
  • Joined

  • Last visited

    Never

Posts posted by Justin

  1. I haven't seen any issues with Windows 10 and my Razer Deathstalker.

    There was a Razer driver update on 9/1/2015 to version 6.2.9200.16385
    I'm not sure if that's the same driver used for other Razer keyboards, but it might be worthwhile to be sure any drivers are up to date.

    If using the generic Microsoft HID Keyboard Device drivers with a Razer keyboard, I suspect that could be related to the issues. I'd suggest installing the Razer drivers but not Razer Synapse, as a couple posts here seem to suggest there are some compatibility issues there.

    What I have seen, is issues with Windows 10 and USB 3.0 but not to the extent that I see mentioned here. Using a 2.0 port fixed that for me.

  2. Just though I'd chime in here...
    Repair/replacement process was very smooth for me. Couple e-mails off to Roger, sent it in, and it was on its way back within 3 business days. I can understand everyone's frustration but there's really nothing to worry about. I've yet to hear any horror stories.

  3. Mines dead as well, though it doesn't seem to be the fuse. Screens black, wont connect to Escribe, and it gets hot when plugged into the charger. Fuse looks fine to me. Anything common that would cause these symptoms? Any chance of a quick fix?
    I'd like to avoid sending it back to Opus, but it looks like that's the direction I'm headed.

  4. Just wanted to chime in. Updated from 7-9 to 7-29 firmware. All is working well!

    Not sure when/what was changed, but preheat seems...different. I'm not entirely sure how, but it definitely seems more consistent with a smoother transition, if that makes any sense. I can't really give any more feedback than that without reverting and studying the device monitor, but whatever was changed was an improvement. If anything was changed at all...I suppose it could just be me.

  5. Very interesting. I'm using the Windows 10 preview, it could be a driver issue or something of that sort. I think at this point I'm going to chalk it up to wonky drivers/OS.
    Like I said though, no problems with any other devices. Here's a dump of my system info summary for reference.

    OS Name    Microsoft Windows 10 Pro Technical Preview
    Version    10.0.10041 Build 10041
    Other OS Description     Not Available
    OS Manufacturer    Microsoft Corporation
    System Name    WIN-NVP7QGR7CJN
    System Manufacturer    Gigabyte Technology Co., Ltd.
    System Model    To be filled by O.E.M.
    System Type    x64-based PC
    System SKU    To be filled by O.E.M.
    Processor    AMD FX(tm)-8350 Eight-Core Processor, 4000 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date    American Megatrends Inc. FA, 10/28/2014
    SMBIOS Version    2.7
    Embedded Controller Version    255.255
    BIOS Mode    UEFI
    BaseBoard Manufacturer    Gigabyte Technology Co., Ltd.
    BaseBoard Model    Not Available
    BaseBoard Name    Base Board
    Platform Role    Desktop
    Secure Boot State    Unsupported
    PCR7 Configuration    Not Available
    Windows Directory    C:\WINDOWS
    System Directory    C:\WINDOWS\system32
    Boot Device    \Device\HarddiskVolume1
    Locale    United States
    Hardware Abstraction Layer    Version = "10.0.10041.0"
    User Name    WIN-NVP7QGR7CJN\Justin
    Time Zone    Eastern Daylight Time
    Installed Physical Memory (RAM)    8.00 GB
    Total Physical Memory    7.97 GB
    Available Physical Memory    4.50 GB
    Total Virtual Memory    9.22 GB
    Available Virtual Memory    5.40 GB
    Page File Space    1.25 GB
    Page File    C:\pagefile.sys
    Hyper-V - VM Monitor Mode Extensions    Yes
    Hyper-V - Second Level Address Translation Extensions    Yes
    Hyper-V - Virtualization Enabled in Firmware    Yes
    Hyper-V - Data Execution Protection    Yes

  6. Hi James,

    In my testing I wasn't able to reproduce the issue. However, I've noticed that updates are very very slow over USB 3.0. I haven't had time to sit through to see the end result (I expect it could take over an hour). While I've yet to see any errors or crashes, the software does exhibit sporadic unresponsiveness.

    Everything is fine using USB 2.0
    It's worth noting that during the first update, that I reported issues with, I was using USB 3.0.
    I'm unsure whether this is specific to my hardware, but I haven't had any issues using USB 3.0 with other devices.

  7. Hi John,

    I do remember it displaying some very interesting errors, but it definitely did not offer to retry. Unfortunately I don't recall what errors exactly, but as soon as the dialog windows were dismissed the software closed completely. I'm willing to do some additional testing if you'd like, as long as you can assure me I'm not going to brick my device in the process :P


    Edit: Just to clarify, this wasn't a silly "Application not responding" windows error message, they were errors from the software itself.

  8. Just thought I'd share my experience during this first firmware upgrade,

    I believe the USB cable must have came loose, or the firmware upload was somehow corrupted.
    The software crashed, the devices screen went off and would not respond in any way, and the software would not connect.

    After I stopped freaking out, I solved this just by running the firmware update again. Worked flawlessly.

  9. 'Ello,

    I wasn't sure how to go about submitting a feature request, I figured posting here would be as good as any. Forgive me if this feature already exists or if I've overlooked something.

    While the Atomizer Analyzer feature is extremely useful for diagnosing connection issues, it would be quite nice to have this visible on the mod itself. What I'm suggesting is a "Current Ohms" field, that would provide a live update of the resistance readings.

    Cheers, and thank you for this awesome product.

×
×
  • Create New...