Jump to content

Search the Community

Showing results for tags 'corsairservice'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CORSAIR COMMS DEPARTMENT
    • Community Rules & Announcements
    • Live Event Announcements
    • New Product Releases
  • COMMUNITY DISCUSSIONS
    • Non-CORSAIR Tech, Benchmarks, and Overclocking
    • Games & Gaming
    • Battlestation and Build Showcase
  • TECHNICAL SUPPORT & CUSTOMER SERVICE
    • iCUE Software Troubleshooting
    • Build Hardware Troubleshooting
    • Gaming Peripherals & Audio Troubleshooting
    • Furniture and Ambient Lighting Troubleshooting
    • CORSAIR Pre-Built Systems Troubleshooting
  • PRODUCT DISCUSSIONS
    • CORSAIR iCUE
    • Build Hardware
    • Gaming Peripherals
    • Audio Devices
    • Battlestation Hardware: Ambient Lighting, Furniture, etc.
    • CORSAIR Pre-Built Systems
    • CORSAIR Technologies Q&A
  • Alternative Languages
    • Deutscher Support (German Support)
    • French Support
    • Spanish Support
  • LEGACY TOPICS
    • Corsair Enthusiasts Section
    • Corsair Product Discussion
    • Alternate Language Support
    • Customer Service

Categories

  • System Build Inspiration
  • Memory
  • Cases
  • iCUE CONTROLLERS
  • Maximizing Performance
  • Peripherals
  • Storage
  • Liquid Cooling
  • Gaming Mice
  • News and Events
  • How-tos and DIY
  • USB Drives
  • Extreme OC Mods
  • Gaming Keyboards
  • Power Supply Units
  • Gaming Headsets
  • Uncategorized

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Interests


Occupation


Optical Drive # 1


Homepage


ICQ


AIM


Yahoo


MSN


Skype

Found 2 results

  1. The title pretty much says it all.. the issue started after updating windows to version 2004 and is still here after updating to 20H2 as well. It's impossible to recreate the problem, since it's completely random. It happens whenever it wants. The error message appears for a brief moment right before the computer shuts off and says about an exception in a memory address I think. Also I've noticed one more thing: When the system boots up if I go in the event viewer there's always a Windows Error Reporting event related to Corsair.Service. DisplayAdapter.exe.. only when there hasn't been an error window during the last shutdown. Every time I get the error when shutting down, the next time I start the system there's no Windows Error Reporting event related to DisplayAdapter. Very strange behaviour... This is a widespread issue Corsair, please try and fix it or at least give us the option to disable this service.
  2. As the title is noted, the Corsair Service seems to be leading to BSODs at least once a day, it seems to be related to the CPU-Z .sys module that you guys are using. I would suggest you upgrade to cpuz147_x64.sys module instead of using 146 which is pretty outdated (and causing consistant BSODs). Sys Info OS: Windows 10 x64 Pro v1803 -- Latest Updates CPU: AMD FX 6350 GPU: NVIDIA GTX 760 RAM: 8GIG BSOD Dump files -- https://mega.nz/#!FAdxgLzB!53TIsYd_Iqvw2KwepCVydmjhyiNBqLeVk-KYAv2Jhew https://mega.nz/#!tRUXFbLZ!mMH5xt2X7A5FW4armAGiBqroxduuRJOroNbKe2jsnYw
×
×
  • Create New...