Razer Lycosa Mirror Edition


Recommended Posts

Does anyone else have this keyboard, and major problems with it ?

i bought one a good few months back, and for the first month or so it was fine.

then keys stopped working, randomly.

id be playing a game or just typing and suddenly the D key would just go.

i then realised to fix this i needed to unplug it and plug it back in, then depending on the game restart it.

then i started having a problem where the keyboard wont turn on.

it happens at POST, which is really annoying if i need to load windows as i have grub and often find it boots into linux cause my keyboard cant do anything.

i have to hit the keyboard from the back a few times before itll start working.

and if i have the media keys set to a player i have installed, the keyboard has a habbit of randomly opening the player, and just skipping through my library.

so i went over to the razer site after realising the NORMAL lycosa's had all these problems and that you just had to send them your serial number, and if you fell in the range of serial's with the known problems, you got a replacement.

on the page i read about this, there were commnents from other mirror users with my exact problem, and someone from razer saying the mirror lycosa cant have the problem because it was produced after the problem was fixed.

evidently not the case.

i sent an email to razer, including my serial number, the fact it's a mirror, and the fact it's having all these problems.

this was about 3 or 4 months ago.

im yet to recieve anything back.

out of inpatience, i read up a fix for it (taking it apart and removing a screw that's in the way and causes the touchscreen to go mad), but it didnt change a thing.

infact ive done it twice, because i thought i mustve done something wrong the first time, but it still didnt work.

so now im stuck in a position where i cant send it back, and ive wasted ?70

as far as im concerned, no one should ever buy this keyboard.

it seems like a hit or miss as to whether yours is actually going to work properly!

:crazy::

/rant

Link to comment
https://www.neowin.net/forum/topic/815014-razer-lycosa-mirror-edition/
Share on other sites

I've had issues with Razers equipment not working at boot-up. I believe it has something to do with the very high power requirements that their stuff requests. They attempt to max the USB specification with almost everything they sell and at post when you have a few USB devices sharing the same host controller there are times where the amount of power being requested just isn't enough which causes their devices to not work at boot-up unless you unplug and plug them back in or deactivate and then reactivate them from device manager.

I've witnessed this the most with their 5.1 Surround Sound headsets and their Mice but I've heard of it happening with others on their Keyboards as-well and only at Post. I've personally had this happen on no less than 4 different Motherboards and 2 separate Laptops so I know this is an issue with Razers stuff.

Something to note. I get my Razer 5.1 Surround Sound headset to come on every single time at post if I leave its Blue LED lighting off.

I have the same keyboard they've had problems from the start, the first batch of lycosas they released had a lot of problems but they were supposed to have been fixed so I went and bought one and the touchpad doesn't even work, the problem is it's not worth the money sending it back just to get the touchpad fixed, luckily razers drivers are quite good so I bound all the media keys to the keypad.

When I reported the problems I got a response back the next day, Razers always been pretty fast to respond, still it's the last time I buy any thing from Razer, shame I liked their mice.

Definitely WOULDN'T recommend buying one

Theirs nothing special about the keyboard to make it worth the price it's nothing more than a cheap keyboard with a backlight and a media touchpad nothing that makes it worth the price it doesn't even have anti ghosting for all the keys, I'm not even sure how you clean the keyboard I don't think you can even remove the keys. :no:

hmm Vice, after you said about them trying to max out the power specifications for USB, i unplugged my 360 controller and webcam at boot.

it still didnt turn on, but it came on quicker than it usually does.

i had to hit the back of it, the past week or so its taken a good 5 minutes of me booting and hitting the back of it before it actually comes on.

it worked first hit this time though ;)

it just annoys me how it was perfectly fine for the 30 days i had to send it back, and then straight after starting going haywire.

i might take it apart and just unplug the touch screen, i never use it and it seems to be the source of most of the problems i think.

so jealous of my friend right now who came to my house on friday and spent a grand and a half on a pretty nice computer.

he got a G19 :(

Well, i bought one (Lycosa Mirror) a week ago or so, but had to return it because it was defect.

It had all the problems the early batch had (led flashing, random keys stop working, touch pad don't work).

My keyboard was a 'new batch' KB (serial started with MT09), and it's a shame that Razer still have some bad Lycosa keyboards in production.

I've send it back now, and will hopefully get a refund.

After a detailed explanation to the online-shop i bought it from, they refunded the money 2 days later.

I like Razer's mice, but i will never touch their keyboards again.

Now i have an apple wired instead (i wanted a keyboard without all the extra mediakeys and all that bs)

The G19 is crazy, a keyboard that uses a power adapter is going too far.

holy ****, i didnt know it needed it's own plug :| lmao

i thought itd just be normal USB.

come to think of it, it has a screen.

i feel quite silly now for not realising USB cant power a screen.

After a detailed explanation to the online-shop i bought it from, they refunded the money 2 days later.

I like Razer's mice, but i will never touch their keyboards again.

Now i have an apple wired instead (i wanted a keyboard without all the extra mediakeys and all that bs)

same, i do quite like their mice, but i also will never be going near a razer keyboard again.

and ill try to make sure my friends dont ethier.

saitek's keyboards are pretty reliable though.

i had one for YEARS, and gave it away when i got this razer and its still going on my friend's computer.

another freind bouht a saitek one aswell and it seems alot tougher and more sturdy.

my I and G keys just died, had to unplug it and plug it back in and beat it before theyd work again :crazy:

I have the same keyboard they've had problems from the start, the first batch of lycosas they released had a lot of problems but they were supposed to have been fixed so I went and bought one and the touchpad doesn't even work, the problem is it's not worth the money sending it back just to get the touchpad fixed, luckily razers drivers are quite good so I bound all the media keys to the keypad.

When I reported the problems I got a response back the next day, Razers always been pretty fast to respond, still it's the last time I buy any thing from Razer, shame I liked their mice.

Definitely WOULDN'T recommend buying one

Hmm....I bought my Mirror Edition when it first came out and I've never had any problems with it. Typing on it right now...

  • 4 months later...

While it's a somewhat old thread, I feel people should know that the problems STILL persist. A few days ago I bought the MT09 series of the non-mirror and within 12 hours had issues of keys not responding and requiring a reboot or replug to work. I've already contacted Razer about the issue and after pointing out how their canned responses are of no help, they finally agreed that RMA is the best option.

  • 1 year later...

While it's a somewhat old thread, I feel people should know that the problems STILL persist. A few days ago I bought the MT09 series of the non-mirror and within 12 hours had issues of keys not responding and requiring a reboot or replug to work. I've already contacted Razer about the issue and after pointing out how their canned responses are of no help, they finally agreed that RMA is the best option.

I had the same issues. However I made sure all new drivers were installed (v3 I think it is now). Just make sure you leave the task bar icon running (don't disable it), also there's an option that disables hotswitching.

No problems for 3 weeks now.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!