Minibeats

HighPoint are set to release seven new SSD solutions that offer a myriad of choice to those looking into taking a step into High Speed Mass Storage at an "affordable" price point. http://www.tomshardware.com/reviews/highpoint-ssd7101-ssd,5200.html?utm_source=notification

Original Article By PC Gamer: http://www.pcgamer.com/nvidia-shield-portable-2-prototype-turns-up-in-a-canadian-pawn-shop/?utm_content=bufferd2d06&utm_medium=social&utm_source=facebook&utm_campaign=buffer_pcgamerfb I feel like that this might of been the testing grounds for the tech inside of the Nintendo Switch personally. I don't know how I would of felt if this came to market though... "The Nvidia Shield Portable (originally released as simply the Nvidia Shield) is an Android-powered portable gaming device that looks basically like an Xbox 360 controller with a five-inch LCD screen stuck to it. The handheld debuted in 2013 and was actually pretty okay—powerful, but a little too bulky for gaming on the move. After its release and failure to catch fire commercially, Nvidia moved to a conventional tablet design, but not before whipping up at least one prototype for a planned, but never released, Shield Portable 2—which for some reason was recently discovered in a pawn shop in Canada."

I moused over my used DIMM slots and one DIMM is reading as 2GB in my Task Manager but BIOS is recognizing the full 16GB. So I dunno what is even going on right now.

I tried that just to be sure. Re seating my RAM actually sent me into an F9 cycle on the next boot after. Also yes. They do individually show as 8GB on their own. I have submitted a ticket to Gigabyte Support. Yes I am in Australia and I hope this gets resolved. Worse comes to worse I'm RMA'ing. But if a new BIOS comes out and everything is dandy, then everything is dandy. I really hope I am an isolated case for the sake of the integrity of the BIOS itself. I'd also recommend you don't use Ryzen Master at all even out of curiosity. Cause the BIOS ran fine and I could XMP as I stated before. But now if I alter anything, even do a manual overclock in BIOS I get sent into an F9 cycle. That's also a fair point. I just like the Master Control software cause of how seamless it was. That's also not really a valid point though. Cause it was fine in BIOS F2 and even in F3b

The Story: So. I'm on a Gigabyte AX370 Gaming K7 motherboard. Originally I was waiting on a BIOS update in order to actually OC my RAM, because RAM OC wasn't happening at all on the release F2 BIOS. On the 7th of March, Gigabyte released BIOS F3. I flashed to it, and was stoked to see that XMP worked immediately, 2933 on my Trident Z RGB DIMMs. However, I tried overclocking my CPU with Ryzen master control. This sent my computer into an F9 error code bootloop. (F9 errorcode = No recovery module was found) To break out of the loop, I had to smash my restart button several times until it finally broke past the F9 code. However, I couldn't boot into Windows after this. TO fix this NEW issue. I flashed back into the old F2 BIOS, and flashed back to F3. I am now in windows after a system restore that corrupted my profile and i had to do some nasty regedit stuff just to get back into my profile and out of a temp login. WARNING: AFTER FLASH TO F3 DO NOT USE RYZEN MASTER CONTROL AT ALL. Doing so will botch your BIOS in such a way that XMP will no longer work. At all. even after a reflash. (Still unsure if I've wrecked my board just trying to get back into windows) Additional Findings: Once you have flashed to F3, You can not flash back to F2, and boot into windows. You will freeze on the windows execution screen 100% of the time, no matter what settings you tweak in BIOS or if you load back to Optimized Defaults. In my case, 6GB of my total RAM has also gone missing (I'm supposed to have access to 16GB, I have access to 10GB however). I am still unsure if this is a side effect of the BIOS, or if I've wrecked my board. In the mean time. I'll be waiting on a new BIOS update that hopefully resolves these issues. If it doesn't. I guess I'm RMA'ing this board. I'm pretty sure I'll still be covered under the warranty due to this being a BIOS issue, rather than a hardware issue.