Justin

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.

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.

Same symptoms for me. Also gets hot pretty quickly when plugged in. I'm using an Opus 200, most of the issues with these seem to be blown fuses. From what I can tell, that's not the case with my device. Black screen, no Escribe.

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.

John, it is definitely an improvement. It's something that I noticed immediately and it has made my vaping experience just that much better. Thank you!

Working great on my out of date x64 Win10 technical preview. Though I do have issues upgrading the firmware over USB 3.0

If anyone knows the mod resistance for the Opus 200, that would be extremely useful. I realize it can vary a bit from each device, but a roundabout would be great. Unfortunately I don't have any solid copper or a temp gun around.

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.

What operating system are you using? Any chance you're using the Windows 10 preview on USB 3.0? I had the same issue.

Interesting, well... I'll likely be upgrading to the full release ASAP. I'm going to run a few OS updates and make sure my chipset drivers are up to date and everything, but I'm fairly certain they are. I'll be sure to provide any additional information as I discover it.

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

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.

Cheers! I have a tiny bit of software development experience so it should be a fairly smooth process. I have some free time tomorrow, I'll do a little testing and dump some info here if I don't hear from James.

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 Edit: Just to clarify, this wasn't a silly "Application not responding" windows error message, they were errors from the software itself.

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.