Jump to content
Corsair Community

Search the Community

Showing results for tags 'bsod'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


    • Community Rules & Announcements
    • Live Event Announcements
    • New Product Releases
    • Non-CORSAIR Tech, Benchmarks, and Overclocking
    • Games & Gaming
    • Battlestation and Build Showcase
    • iCUE Software Troubleshooting
    • Build Hardware Troubleshooting
    • Gaming Peripherals & Audio Troubleshooting
    • Furniture and Ambient Lighting Troubleshooting
    • CORSAIR Pre-Built Systems Troubleshooting
    • 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
    • Corsair Enthusiasts Section
    • Corsair Product Discussion
    • Alternate Language Support
    • Customer Service


  • iCUE

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me




Optical Drive # 1







Found 16 results

  1. Running a Ryzen 7 3700X with a Gigabyte X570 Ultra and 5700XT GPU, 2x 16GB CMW32GX4M2C3200C16 and a 850 Corsair PSU. Issue is that I can not get my system to run stable when I enable the XMP in BIOS. System runs great at 2133 but as soon as I enable XMP to get the 3200 speed I get random BSOD, sometimes when powering down or when watching YT. MemTest86 shows well over 200 errors after only 2 minutes! - Did a clean Win install, with latest AMD drivers etc. - Tried all different memory slots and combinations on the mainboard - Used 2 another same set of ram sticks - RMA'd the mainboard and memory - Tried entering the memory timings by using the Ryzen DRAM calculator (every which way that I found on the www) - Used the Corsair How-To-Guide for memory overclocking - Enabled XMP manually set the Multiplier to 32 and Voltage to 1.35V - Tried the above with High frequency support to Level 1 - Tried it in a number of different variations and suggestions in various forums - Tried most of the above on BIOS with AGESA 1003 ABBA, AGESA 1004B and AGESA 1004B & SMU 46.54.0 Nothing did result in any 100% improvement with the constant occurring BSODs So I reached out to on the Gigabyte Discord and got help from a user with the same issue :cool: The following settings solved his issue: - Enable XMP - Set DRAM voltage manually to 1.35V - Set RAM multiplier to 32x - Set the first five subtimings manually to 16-18-18-18-36 (the same as XMP would) important! - Set the sixth timing (tRC) to 56 instead of 54 as XMP would important! Memory slots used: A2/B2 And it also worked for me! System runs stable on 3200 without any BSOD. Did a overnight MemTest86 and zero errors! I believe it has something to do that the CMW32GX4M2C3200C16 is optimized for Intel and that maybe there is an issue with the XMP, that the values don't work with an AMD system. Would like to hear if anyone using CMW32GX4M2C3200C16 on an AMD Ryzen build has similar issues and if the above fix solved any potential BSOD issues. Update: Latest BIOS Update from GB 10c did not resolve the issue with the XMP profile and BSOD if the timings are not entered manually. Running stable on 10c with Win 10 v1909, overnight MemTest86 showed zero errors.
  2. For a while now, ICUE has been causing the irql not less or equal BSOD. Ive tried everything - different ICUE versions, clean installations and even bought a new SSD but the problem persists. Has anyone managed to find a solution?
  3. The only things I found on Windows Reliability monitor are a lot of faults related to: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\Corsair.Service.exe This not necessary cause a BSOD but maybe. There is anyone with similar problem? In any case, please, can you check on your Windows Reliability Monitor if you have similar issues? Many thanks
  4. Make no mistake, I didn't think it was possible for a headphone stand to have said effect on a system, which is why it's been "years of" issues. I have always had regularly random BSODs with my system from a certain point in time. It's an aging motherboard, modded for some new tech, so there is expected to be some discomfort at times. Growing pains, if you will. I will be upgrading soon, but this machine is still fast and responsive, as a result of tweaking and tweaking the tweaks for many years. And the board is a very solid board for its age. Anyways, on to the problem, and efforts I've given (also randomly and sporadically as life doesn't make such investigations a smooth process) in trying to assess the factors responsible for every sort of random crash, or make system adjustments to fix it. So, I have flashed the mobo bios with mods, and updated on board chip firmware, I have laced through the BIOS changing different settings, I have ran diagnostic tests on everything. I have solid quality components, and I have always built my own rigs, as well as building custom gaming rigs for others. I repair cell phones, tablets, electronics, etc so I have enough experience to be able to assess issues, and over time I can usually narrow things down to the heart of the issue. There has always been the thought in the back of my mind that the headset stand was a possible factor, but I didn't think that by being plugged in and not used for anything but holding up my headphones and displaying synced RGB lighting, that it would cause regular crashes. And I mean on every OS I've tried from every release of Windows since I received the stand, which have been many because after several BSODs, my solution is to start fresh and pay attention to when the BSODs start kicking in, and draw similarities until they point somewhere vague or specific. Also several Linux gui distros, ubuntu debian and arch based. Modified versions of Windows, as well. But the issue being so random and sporadic but regular, that I knew they were coming, yet no regularity so as to indicate anything specific... EXCEPT the times for whatever reason I had the headphone stand unplugged, and I would think everything was going great and decide to make sure everything was plugged in and working, and oh.. the stand right let's plug it in and get it set up too. Then usually not immediately, but still soon enough that thinking back I could start to see a peripheral timing association with the stand being plugged in.. but still stubbornly believed it wouldn't have that effect. Especially since the BSODs occurred at times when there were no obvious functions involving the stand going on - wasn't plugging or unplugging anything into the usb ports - in fact, it never happened when I was doing those things. The only thing is that I noticed there was a difference in functions between the usb port on the top near the upright base, and the one on the right side of the base. Almost as if one functioned as USB2.0 and the other as USB3.1 despite the fact they are both blue, which should indicate USB3.0/3.1 functionality. I did however, end up thoroughly checking the hub it was sometimes plugged into, thinking it was the hub and not the stand. lol yep. Anyways, this last install of 20H1 crashed on me a few times and I finally decided (who knows what finally triggers us to jump off that cliff, after standing on the edge of it looking down for so long - idk ask Freud) that the stand might be the issue and I needed to finally try specifically testing. Well I have had it unplugged for several days, and no issues with my system, no glitchy things happening, no random slower than normal boots, and NO BSODs... so far. Hopefully I don't get a red herring BSOD, and end up getting thrown off the stand focus, although this thread might assist in keeping from that possible eventuality. Ultimately, I'd like to see if anyone else might have similar issues. I couldn't find many in relation to this in a search, and the times I did, the user seemed to feel it was other issue with the stand, like the USB ports on the stand causing the BSODs, and I mean the 2 extra ports, not the main power port for the stand - which is a possibility. Anyways, I wanted to give my specifics and see if it triggered anyone else's memory or realizations of past or present experiences with the ST100 stand. Perhaps I can get some confirmation, or a nudge in a different direction, but still related to the stand, as I am positive that is the device causing the issues. And answering why would be the ultimate goal, although with computer tech - many why's go unanswered as an accepted loss. In any event, hopefully I can get some help here, or better yet help others. Thanks for the interest, and my most sympathetic apologies for the length of the... meandering type of explanation. Hopefully it was somewhat clear.
  5. Dear all, I started getting BSODs SYSTEM_SERVICE_EXCEPTION - ntfs.sys, on my system since I got the corsair CMSX16GX4M1A2400C16 on my Lenovo Y520. I ran some diagnostics: - Windows memory diagnostics - Memtest86 Both report issues with the corsair memory. When running tests with memtest I did the test with 2 memories in the following order: mem stick 1: SKHynyx - 8gb 2400T SA1-11 alone on slot 1 mem stick 2: the 16gb CMSX16GX4M1A2400C16 Test 1: both sticks in - many errors Test 2: only stick 1 on slot 1 - no errors during tests Test 3: only stick 2 on slot 1 - many errors (results are in memtest_results.jpg attached file). Why is the corrsair reporting so many errors :(. It is less than an year old. From what I see it is compatible with the PC configuration. Any advice will be appreciated! System specs: Motherboard: Intel Sunrise Point HM175, Intel Kaby Lake-H Processor: QuadCore Intel Core i5-7300HQ, 3300 MHz (33 x 100) Memory (part number): CMSX16GX4M1A2400C16 Video Card # 1: nVIDIA GeForce GTX 1050 Video Card # 2: Intel HD Graphics 630 Hard Drive # 1: Kingston SA2000M8500G Hard Drive # 2: ST1000LM035-1RK172
  6. I have built a new setup couple weeks ago. Yesterday while playing some games, i got a BSOD and then my PC rebooted, after that, I noticed the windows was not booting anymore! After turning everything off for a while and back on again I noticed that my motherboard (which has a debugging led feature) was accusing the my DRAM was faulty. I removed the two DRAM and noticed that one of them is not working. I can boot my PC while using one of them, and can't boot while using the two and the other that I assume is fried. What can I do? It is very strange that everything was working pretty fine till yesterday. - 16Gb Vengeance Pro RGB 3200 (CMW16GX4M2C3200C16) - MSI MPG Z390 Gaming Pro Carbon - i9 9900k
  7. Hey, so before stating anything I would just like to say that I’m not an expert in any way so please bear with me on this one. So ever since I built my new computer and installed the iCue software to control my 3 LL120 rgb fans and 3 ML120 that I have noticed something weird. Whenever I launched the app the computer started to throttle, the screen would start dimming and returning to normal, and the refresh rate also seemed affected, with the frame rate dropping from 144hz to what seemed like 20. There wasn’t even any other app running, nor game, but the performance hit was very noticeable. But I assumed it wasn’t really a problem and moved on from it since once I closed iCue the computer would return to its normal state. However yesterday I bought and installed 4 RGB strips (all connected together and plugged in to commander) and the performance hit when using iCue increased even more. I then started to get many BSOD with the error message “WATCHDOG VIOLATION”. Removing and unninstaling iCue has seemed to solve the problem has I have not gotten any single BSOD since then. I have tried unninstaling iCue multiple times and nothing seems to be working, I would very much like to have this software since it enables me to control all the RGB functionalities I have paid for aswell as controlling the fan speeds, which are now running almost max speed constantly. Any help is appreciated and I can surely give any information if needed! Thanks and sorry for any case of bad english or bad pronounciation :)
  8. Well i got my PC 2 years ago, in my budget i could only afford a single 8GB ram and i choose a Corsair LPX Vengeance(CMK8GX4M1A2400C16R), The PC did well since day 1 and stills running fine to this day, 2 weeks ago i decided that it was the right time to get another stick of RAM since 1 or 2 of my games are started to lag when my RAM is running low. As i said i already have a single 8GB Corsair LPX Vengeance (CMK8GX4M1A2400C16R) so i decided to get another one to avoid possible issues, then i got the new stick and installed it on the 1st of Friday, the RAM wasn't recognized at first but the PC was doing fine, my motherboard only has 2 RAM slots, A1 & B1, i had the old stick on A1 and put the new one in B1, then i ask around for a solution and they recommended me to switch the RAM, put the new stick in A1 and the old stick in B1, the issue starts here, my PC got into a boot loop boot my motherboard did recognize both sticks of RAM. I switched back the RAM, The old stick in A1 and the new one in B1, still the PC didn't boot so i choose to reinstall Windows, after the reinstall everything worked find till i got a BSOD, the PC restarted and after some hours i got another BSOD, i got BSODs pretty much everyday, i decided to try Memtest86 to test both RAM sticks and it came with no errors, then i decided to do the test on the new stick alone and 0 errors too, im running the PC with the new stick now and so far no issues but i want to use BOTH sticks of RAM, any ides of what could be happening? TL:DR: i have 2 sticks of RAM i use the old stick in the A1 slot and the newer one in B1, it that causes BSODs after a couple of hours, but if i trade the new stick to A1 and the older to B1 the PC doesnt boot.
  9. Hey Folks, Just got a new Corsair One Elite delivered 3 days ago. Amazing machine! Beautiful, quiet, very solid & compact piece of computing machinery. Love the design! One thing that concerns me: I've had two BSOD events in the last 3 days, both while playing graphically intensive games (one on HTC Vive Pro, one Sniper Elite 4, max settings.) The machine just suddenly shows a blue screen, then reboots. Looking at the event viewer, I see two critical errors listed at the time these happened that say: "Kernel-Power". I've tried to monitor graphics card temps, and they don't seem to go over ~ 73 Deg C. That said, the fan sounds like its running full speed. A related concern I have is that (I think) the One Elite has a 500W power supply, but nVidia recommends minimum 600W PSU (per the GTX 1080 Ti user guide.) Could this be a possible cause? Running DisplayPort 2560x1600 monitor (just one), have latest nVidia drivers, and latest Win 10 updates. Have not updated any BIOS or other MoBo stuff (a little reluctant to do that, have read posts about dead video after update.) Stock out-of-the-box Corsair One Elite. Should I be worried? Should I submit a ticket? Hate to part with this thing so soon. - Kevin
  10. 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
  11. Hallo Community :), ich hab jetzt aktuell das VOID PRO RGB Wireless Headset, aber jedes mal wenn ich das Headset vom PC trenne entsteht ein BSOD mit Treiberfehler. Habe den Treiber vom Headset bereits mehrmal gelöscht und neuinstalliert(Firmware auch), hab schon verschiedene Kabel getestet. Das Headset selbst wie auch der USB Anschluss ist/sind nicht beschädigt. Bin da momentan auch ein bisschen ratlos ... MfG, AcrimEX :D
  12. Hi all Since building a new rig from parts sourced on Black Friday I have encountered non stop bsod with a few different error codes. Mainly memory_management irql_not_less_or_equal kernel_security_check_failure I am normally pretty good with being able to diagnose and repair bsod but this one had me stomped for ages. I tested all hardware with no fails. RAM and all storage was fine. Drivers also came back fine. BOIs was flashed at cpu install all chip set and relevant mobo drivers installed and up-to-date and yet bsod still appears. I did everything I could think of until I reinstalled windows. At this point I realised the one app/driver I had yet to install was Corsair link/H100i GTX cooler but my windows was the most stable it has been since being built. Device manager flags "H100iGTX cooler" as no drivers detected. Upon reinstalling Corsair link as Admin and load up a game...... bsod. Then every time I restart, enter pin for windows and get to desktop.... bsod. I've tried installing and rebooting with disabled signature signing and still bsod. After removing Corsair link I can now restart, log into windows and game effortlessly with 0 bsod. Is there a fix/work around for this? Can I just continue without the drivers? Thanks in advance for your time and patience. :D:
  13. About a year ago, I was experiencing random BSODs for two years straight. Found out it was a stick of RAM with a set of burned out contacts. Memtest86 didn't find anything, Windows RAM test found nothing. Suffice to say, I was absolute infuriated with this problem that seemed to have no solution. I replaced the bad stick of RAM and ended the BSODs. A couple of days ago, I started getting BSODs, again. I was beyond levid. Not wanting to experience another lengthy period of time of hardships, I set about finding the root of the problem. Downloading a program called blue screen viewer yielded some insanely useless results. http://i.imgur.com/eMZC0hK.png Here, you can see some generic errors like PAGE_FAULT_IN_NONPAGED_AREA and KMODE_EXCEPTION_NOT_HANDLED, or even no stop code text at all. All the dumps indicated some error with the Microsoft Kernel, which I doubted was the source of the problem. Then, in my 12 entire years of using Windows, I discovered a new program on Windows, called Driver Verifier. Take a guess what it does. After some configuring, I was able to produce the following BSOD: http://i.imgur.com/7zk34BW.png I am now immediately uninstalling Corsair Utility Engine, and, for the foreseeable future, I am not installing another piece of Corsair software for the following reasons: To begin with: I frankly don't understand why keyboard software has to take up 200mb of my disk. Secondly: The interface is clunky, slow, and full of many unneeded graphics to make it appear flashy and comprehensive. Thirdly: The interface changes so frequently that never once have I ever been able to open the application and actually know what I'm doing in the two years that I've owned this keyboard (K70 RGB.) Fourthly: I don't know if this is true now, as I've downloaded CUE about three weeks ago, so, for all I know, CUE has now been updated to be a dating simulator, but, in my version, I don't know why, but CUE requires me to create an entire "lighting effect" if I want to light a certain set of keys with a certain color. Why, in previous versions, am I allowed to create one lighting zone with multiple colors, and now I am not, is a little painful. Fifth, and lastly: Going to corsair.com/downloads, pressing the download button, pressing "skip this step and download" because I don't want my personal info. to be sold by Corsair is a painful process, if, I want to stay up to date with the latest version of a keyboard software that doesn't crash my computer. I'm hoping that updating could be implemented into the actual program itself rather than having the user to update manually. Overall, not happy. The keys do make the nice clickety clack sounds. And in some long forgotten version of CUE, I was able to flash my lighting preset to the keyboard, so I always have my favorite lighting profile. But I do hope that in the near future, something as basic as a keyboard driver doesn't crash my computer.
  14. Today I received my new Corsair VOID Wireless headset, plugged it in, updated its firmware and all was well. I then noticed a notification to update the CUE software from 2.4.66 to 2.5.66. Half way through the install process, my PC crashed into a sound loop and then BSOD with the error code IRQL_NOT_LESS_OR_EQUAL. Now my PC is stuck in an endless boot loop. I managed to cure it by disconnecting all my corsair devices and using my Win10 usb drive to run a system repair which just did a system restore. (and which i just realized deleted Forza Horizon, so thats 50Gb to re-download :(: ) I downloaded CUE 2.5.66 from Corsair's site, it does install, but will not open! :evil: I tried removing and re-installing, but still have this issue. I'd rather not have to do a clean Win10 install :(: Anyone experienced the same? Any advice would be greatly appreciated :)
  15. Hello! In short: My current problem is that I get intermittent BSODs of type 'MEMORY_MANAGEMENT' and others, general system instability, and some spontaneous reboots. This prompted a memtest, which resulted in over 400k errors, which in turn made me attempt to test each stick of memory by itself, but no configuration other than the initial one will boot. Could this be a motherboard issue, or is it a memory issue? The full story with more detail: The issues started while playing relatively demanding fullscreen games a couple of weeks back. My displays would suddenly go dark, the sound would glitch out and/or loop, and the system itself would (apparently) hardlock. After some research, I marked this down to unrecoverable display driver crashes, and tried disabling SLI. No dice. Then I tried actually disabling the card in slot #1 (the 780Ti SC) in my device manager, thus also disabling SLI completely, and plug both my screens over to the second card. This seemed to work without issues, except for a huge hassle on reboot, as I would have to plug one screen back to (the disabled) card #1 to be able to get into windows, then re-enable card #1 and reboot, THEN plug the screen back to #2 and disable #1 again. Whew. At any rate, this worked without crashing for about a week. Then weird stuff started happening. Chrome tabs would crash or fail to load, dropbox and google drive would crash on startup, and the system would occasionally just reboot spontaneously. Figuring this might be because of my ‘unconventional’ GPU setup, I removed the card in slot #1, and replaced it with the card from slot #2, taking the #1 card out completely. This is when the BSODs started happening. To test whether or not card #1 was, in fact, broken, I ran some 3Dmark stress tests on card #2 (now in slot #1). They ran fine, but as soon as I attempted to run a regular benchmark, the system crashed with a MEMORY_MANAGEMENT stop error. Upon reboot I was greeted by another identical bluescreen about 5-10 seconds after logging into windows. These bluescreens have been popping up intermittently since then. Because of the memory-related error message, I figured I might as well try a Windows Memory Diagnostic and see if any errors popped up, but the test came out clean after 2 passes. Believing this had to be a mistake, I ran Memtest from a USB stick. Memtest would consistently crash on test #1 or #2 with an error saying it couldn’t start CPU 0, so I had to disable the first two tests to get it to run at all. I ran the remaining tests for 4 passes, and was presented with a little over 400,000 errors. You can take a look at the memtest log itself here. Being fairly confident in that I’d narrowed this down to a memory issue, I then started the process of testing each stick on its own to isolate the faulty module, but no configuration of memory sticks other than my initial configuration would boot at all. Here are my test results in more detail: Orig config (rotated 90 degrees clockwise): DIMM Slot A1 - Serial No. 348325 DIMM Slot A2 - DIMM Slot B1 - Serial No. 348324 DIMM Slot B2 - CPU SOCKET DIMM Slot D2 - DIMM Slot D1 - Serial No. 348322 DIMM Slot C2 - DIMM Slot C1 - Serial No. 348323 (This is the config ASUS recommends for this mobo) Test 1: A1 - 348325 A2 - B1 - B2 - D2 - D1 - C2 - C1 - Result: PC reboots after 20~ seconds, no display output at all. No beeps. Loops endlessly. Test 2: A1 - A2 - B1 - 348324 B2 - D2 - D1 - C2 - C1 - Result: Same as test 1 Test 3: A1 - A2 - B1 - B2 - D2 - D1 - 348322 C2 - C1 - Result: Same as test 1 Test 4: A1 - A2 - B1 - B2 - D2 - D1 - C2 - C1 - 348323 Result: Same as test 1 Control test because wtf: A1 - 348325 A2 - B1 - 348324 B2 - D2 - D1 - 348322 C2 - C1 - 348323 Result: Normal boot to windows without issues. Test 5: A1 - A2 - B1 - 348324 B2 - D2 - D1 - 348322 C2 - C1 - 348323 Result: Same as test 1 Test 6: A1 - A2 - B1 - 348324 B2 - D2 - D1 - C2 - C1 - 348323 Result: Same as test 1 Test 7: A1 - A2 - 348325 B1 - B2 - 348324 D2 - 348322 D1 - C2 - 348323 C1 - Result: No reboot, but no display output. No beeps. No response to any kb+m input. ## I reset the CMOS at this point ## Test 8: A1 - A2 - 348325 B1 - B2 - 348324 D2 - 348322 D1 - C2 - 348323 C1 - Result: Same as test 7 Control test 2: A1 - 348325 A2 - B1 - 348324 B2 - D2 - D1 - 348322 C2 - C1 - 348323 Result: Normal boot, but since the BIOS is back to defaults, the system will not pass POST because it can’t find the CPU Fan (what). Setting the CPU fan to manual 100% fixes this error. (This error has not happened before BSODs started happening.) And now I’m here. I’m sort of at a loss at this point. I’m reasonably certain that the problem lies either with the memory or the motherboard, but I don’t know how to proceed to narrow it down further. Any help would be appreciated!
  16. Hello. I got a newly build dedicated streaming pc (see dropdown). It worked fine for like 2 days after the build, but then bsod's and crashes came. For example i've had bad_pool_header, IRQL_not_less_or_equal, driver overran a stack buffer etc. i've re-installed windows 10 6 times, and windows 7 3 times.. both are legit copies. I've checked all the drivers on my computer from driver management and with 2 different programs, and ran a memtest.. can't seem to get rid of the problem.. Please help :)
  • Create New...