Jump to content
Corsair Community

Search the Community

Showing results for tags 'bluescreen'.

  • 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
    • English Support
  • PRODUCT DISCUSSIONS
    • CORSAIR Software
    • 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

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


Location


Interests


Occupation


Optical Drive # 1


Homepage


ICQ


AIM


Yahoo


MSN


Skype

Found 3 results

  1. Hallo, Ich habe mir vor ca. 3 Monaten 2x 8 GB Corsair Vengeance RGB Pro zur Aufrüstung geholt damit ich 32 GB habe (Sind beide identisch). Nun habe ich seit dem häufiger Probleme mit Bluescreens und Crashes. Also habe ich die Neuen ausgebaut und mit Windows-Arbeitsspeicherdiagnosetool die Alten überprüft und es war kein Fehler ebenso mit den neuen, sobald ich alle 4 einbaue kommt das ein Hardwareproblem gefunden wurde, weiß nicht woran das liegt. RAM : Corsair Vengeance RGB Pro 3200 MHz Liebe Grüße
  2. Hallo, ich habe mir im März 4x8GB Vengeance Pro zugelegt und seither Problemlos genutzt. Seit gut 2 Wochen habe ich allerdings massive Probleme, die mich langsam aber sicher zur Verzweiflung bringen. Angefangen hat es mit 1 Riegel der sich nicht mehr mehr per iCUE ansteuern lies, mehrere Restarts und Updates später liesen sich alle 4 nicht mehr Ansprechen und iCUE zeigt nur noch ein rotes Ausrufezeichen auf dem RAM an. Quasi gleichzeitig kamen unmengen an Bluescreens und Freezes, teilweise mehrmals hintereinander. Habe Windows mehrmals neu aufgesetzt, mehrmals alte und neue iCUE Versionen probiert. Ohne iCUE, sämtliche Treiber gecheckt. BIOS Update und Reset. Das Mainboard auf korrekten Anschluss aller Kontakte geprüft. Keine Veränderung. Habe dann meinen alten RAM testweise eingesetzt und siehe da, keine Bluescreens oder Freezes. Also den RAM reklamiert und gestern direkt den neuen eingebaut. ->Gleiches Spiel, Freezes und Bluescreens alle paar Minuten: driver_irql_not_less_or_equal Watchdog Violation iCUE zeigt ein Rotes Dreieck mit Ausrufezeichen auf dem RAM und teilweise verschwindet der RAM sogar komplett aus der Anzeige. Ich bin absolut ratlos. Bitte um Hilfe.
  3. 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!
×
×
  • Create New...