Key Takeaways
1. Nvidia is giving away a high-end gaming laptop, the Asus ROG Strix Scar 16, to one lucky winner and a friend.
2. No Terms and Conditions are provided, leaving entry eligibility and country restrictions unclear.
3. There is no specified end date for the giveaway, so it’s best to enter as soon as possible.
4. The laptop features an Nvidia GeForce RTX 5080 GPU, Intel Core Ultra 9 275HX CPU, 16-inch 2.5K display, 32 GB RAM, and 2x 2TB SSDs.
5. Performance reviews highlight impressive gaming capabilities but note that the laptop can be very loud under heavy use.
Nvidia has just launched its newest giveaway, and this time they’re offering something really exciting: a complete gaming laptop! This isn’t just any laptop; it’s a powerful ROG Strix Scar 16 from Asus. One fortunate gamer, along with a friend, has the chance to win this high-end device. To join in on the fun, make sure to check out the instructions on Nvidia’s post on X.
Missing Details
Typically, Nvidia provides Terms and Conditions for their giveaways, but this time they’re not included. This means it’s unclear who can actually enter the giveaway, as many are often limited to certain countries. Additionally, there seems to be no specified end date for the contest, so it’s advisable to enter as soon as possible.
Laptop Specifications
The Asus ROG Strix Scar 16 comes equipped with Nvidia’s GeForce RTX 5080 laptop GPU. While other specs aren’t detailed in the giveaway announcement, a quick look at Asus’ own website shows that it features an Intel Core Ultra 9 275HX CPU, a 16-inch 2.5K mini-LED display with a refresh rate of 240 Hz, 32 GB of DDR5-5600 RAM, and 2x 2TB NVMe SSDs set up in RAID 0 configuration.
Performance Review
In our evaluation of the ROG Strix Scar 16, which had a slightly different setup (using an RTX 5090 GPU instead of the RTX 5080), we were impressed by its colorful OLED screen, outstanding gaming performance, and easy access for upgrades. However, one downside is that the laptop can become extremely loud when under heavy usage, and this issue is likely to be present in various models too.
Source:
Link


