![]() ![]() Tried all the usual swapping around for troubleshooting (easier when you have two very similar setups sitting side by side), psu's, memory, slots, tried the cpu's in each motherboard to see if that made any difference, etc.Įnded up returning both motherboards thinking that was the issue, picked up gigabyte ud4's. The other started for all of 10m, crashed out and then gave the 1/2 second twitch with fans and led on power up. One glitched all over the place with the sata ports, having a 1/5 chance of booting into windows without hd related errors, and even when it did boot in, it wasn't smooth sailing. Both picked up 2600k's with asus p67 boards. I and a friend both went through a shockingly similar situation in our recent sandy bridge builds, both from microcenter. Asus has been a very good company and I'd hate to see them start going downward. But now I'm going to have to rethink that for future purchases. I've had 2 previous systems running Asus mobos in the past 3 years and they have been solid and reliable. I will do some stress testing tonight as well as trying to get up to 4.2Ghz and hopefully whatever the cause of the failures were was just because of poor Asus quality. So far been running the GD65 for a few hours and have not had any issues (knock on wood). I didn't even want to risk a possible 4th trip (40 mile drive each way). I was too pissed off to try another P8P67 Pro and without knowing what the cause of the failures were. Only this time I got the MSI GD65 instead. So now my 3rd time back to Microcenter to replace the mobo and cpu. CLR RTC and remove battery with no success. Within the first 10mins of using it, it shuts down unexpectedly again. I turn it off to run out to do some errands. Stock turbo mode and no stress testing, just watching a movie. Get into windows used it for 2 hrs, all running at stock settings. Put the cpu into the mobo, first boot, success. CLR RTC and removing the battery did nothing. Nothing on the display and it would go into an infinite boot up loop. Put the cpu in the replacement mobo and this time, the fans and everything would come on, but the cpu led is on solid red this time. So I took the mobo back to Microcenter for replacement. Used only a single stick of ram and putting it in each slot to try and powerup and got nothing. ![]() Pulling the cord from the outlet and then plugging it back in and pushing power, the fans twitched and the cpu led would blink once for a split second and then nothing. so I thought.ģ days later, just running 3Dmark vantage at 4.1Ghz with 1.19V, the computer shuts off unexpectedly in the middle of it. The form factor is nice, but it really isn't worth the headache of dealing with support for an under-performing system that can't be upgraded.I bought the 2500K and P8P67 Pro bundle deal from Microcenter a week ago. I suggest you return the system while you still can. This makes high resolution + high refresh rate monitors hit or miss, I personally had issues running a 4k / 165hz. There is also this where a Corsair employee admitted that they are using HDMI 2.0 / DisplayPort 1.2 extensions internally. They are overpriced for the hardware that you get, and due to cooling the CPUs under-perform compared to a decent air cooler. I love the form factor of this machine, but Corsair doesn't properly support these machines. I ended up selling the refurbished as I don't need this headache in my life. What I got back was a completely different machine, without the updated BIOS. When they got the machine, they said that there were replacing the cooler and SSD. In order to RMA my machine for a BIOS update, I had to build a completely new machine so that I could continue to work. This post pretty much sums up my experience during the year I owned this machine. Meanwhile iCUE will be slowly baking your hardware to death. ![]() I had to connect my fan to the motherboard header and run it at 100% to ensure adequate cooling of both the CPU and GPU.Ĭorsair support is absolutely horrendus, it will take months to try and get this fixed. The bug still exists in both iCUE3 and iCUE4, it was never fixed. They said they needed to message the iCUE team and marked my issue as resolved. I opened a support ticket for it, and it took 2 months for me to get them to understand the issue and that it wasn't weather related. This same thing happened to me a few weeks after I bought my a100 last year. When coolant temps fall below 60c control is returned to iCUE which will then turn off the fan. When they hit 60c, hardware protection kicks in and ramps up the fan to 100%. Basically iCUE turned off your fan, so the coolant temps skyrocketed. This is a bug in the iCUE software that has gone unresolved for over a year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |