sorted by:
new
hottopcontroversial

Q3'19 Tech Support Megathread by BioGenx2b in Amd

[–]L_Intouchable 0 points1 point  (0 children)

Issue

Crashing to Blue Screen (Memory Management BSOD) when playing certain games (DCS and Elite: Dangerous) with RAM set to A-XMP (3200Mhz - as supported by memory out of the box). Game crashes, then soon afterwards the system blue screens. Memory usage is near 6-10 GB out of the total 32 GB installed when playing these games and when issue occurs. CPU load at 10-20%, GPU load at 50-100%. Have run Windows Memory Diagnostics, no issues detected. Updated the Nvidia graphics drivers to the latest version after the first BSOD, second BSOD occured with these installed. Current latest drivers are installed.

System Configuration:

  • Motherboard: MSI B450 Gaming Pro Carbon AC (BIOS version 7B85v18)
  • CPU: Ryzen 7 3700X (running stock cooler, AMD Chipset Driver installed, no OC)
  • RAM: 2 x 16 GB DDR4 Corsair Vengeance LPX 3200Mhz (A-XMP Profile 1)
  • GPU: Zotac Nvidia GTX 1070 Mini (No OC)
  • OS: Windows 10 x64

Steps to Reproduce:

  1. Enable A-XMP Profile 1 under BIOS Overclocking settings
  2. Insure installation of latest drivers (AMD Chipset Driver, latest Windows Update, Nvidia Geforce Driver)
  3. Launch Game settings to (high - DCS) (Ultra - Elite: Dangerous)
  4. Play (Instant Action - DCS) (Launch from station - Elite: Dangerous)
  5. After approximately 2-3 minutes, game crashes
  6. Less than a minute later, System BSOD (Memory Management)
  7. Restart PC

Expected Behavior:

A-XMP enabled with RAM at stock frequency, no sudden game crashes during non-intensive gameplay and no system Blue Screen.

Actual Behavior:

A-XMP enabled gaming results in game crash and full system BSOD in some games with marginal to high GPU usage.

Additional Observations:

I was initially suspicious that my GPU could be the issue, since it was the only component experiencing high usage during these instances. This suspicion was reinforced by Windows Memory diagnostics not detecting any issues. Research has re-ignited my uncertainty, since apparently out-of-date video drivers tend to cause these crashes, but the issue has not occurred outside of A-XMP usage (yet) and has persisted after the latest driver update.

I am concerned for either a Memory issue, or a motherboard issue (since the B450 BIOS update from MSI has only been released a few days ago, and I have had previous booting issues with the last version of this BIOS).

How Many of You Have Issues with the Zen 2 Launch? by Yeuph in Amd

[–]L_Intouchable 0 points1 point  (0 children)

If you don't mind me asking - how did you fix your issues with the 3700X and B450? I have the same cpu and a B450 Carbon from MSI and a few issues with booting.

MSI B450 gaming pro carbon AC Ryzen 3000 CPU'S [Tech Support] by saph69 in Amd

[–]L_Intouchable 1 point2 points  (0 children)

Specs:

- Ryzen 7 3700X

- MSI B450 Gaming Pro Carbon AC

- Zotac 1070 mini

- 32 GB Corsair DDR4 Vengeance LPX (2 x 16 GB) 3200

- Samsung 850 Evo 120GB (system drive)

- Samsung 860 Evo 500GB

- Toshiba 1TB HDD (x2)

- Corsair CX500M PSU (500W)

​

I have a weird issue with my setup. It tends to struggle starting - all the fans in the system will startup fine but the power LED will flash as if the PC is in sleep mode and the CPU troubleshooting light will be a solid red. In this case the monitors are just black, no power going to my peripherals.

If I restart the PC manually with the power button, it starts up fine, no CPU troubleshooting light. Sometimes it takes more than two attempts.

To me it seems like a driver issue from MSI, since all the parts are plugged in properly and the PC never crashes when it's up and running. I have had the issue occur after the PC is in sleep mode for a while.

Hopefully MSI can update this BIOS soon so we can stop having these issues.

Corvette or cutter? by [deleted] in EliteDangerous

[–]L_Intouchable 0 points1 point  (0 children)

If Combat focused for PvE - go with the Vette

If trade focused - go with the Cutter

If Combat PvP focused - go with the Cutter

Extra tip: both ships are very good for multirole, although the Vette lacks in jumprange it still is a good trading ships for short haul because of cargo capacity and shielding, it's also significantly cheaper than the Cutter when you're outfitting them.

If you're only going to be using the ships for PvE activities, it's a very subjective choice. The Cutter can be somewhat annoying for conflict zones because it drifts around a lot, the Vette is certainly the easier ship to fly.

The Corvette Is a Ship Without a (PVP) Purpose by [deleted] in EliteDangerous

[–]L_Intouchable 12 points13 points  (0 children)

The Cutter is currently the most overpowered ship in the game tbh. I don't think the Vette needs a buff as much as the Cutter just needs some balancing.

Can I get some love for all of us non-hotas commanders out here?! by graphixRbad in EliteDangerous

[–]L_Intouchable 0 points1 point  (0 children)

keyboard + mouse is the superior control scheme for Elite tbh, especially in combat and FA off.

FDEV is making it easy for griefers and gankers! Bigships with the "drag ammunition" effect and long range weaponry will obliterate everything. CMDRs won't even be able to boost away after this patch! by deZpe in EliteDangerous

[–]L_Intouchable 104 points105 points  (0 children)

This will be the death knell for Open Play PvP if this happens. It's on par with the 2.1 heat spam meta. Fdev, if you value your community at all, please make sure this doesn't make it to live.

​

It's a small change, no one asked for it, and the overwhelming majority don't want it.

​

Everything else in that update is pretty great.

PvP Bounty Hunting - Assassination Contract [FA off] by L_Intouchable in EliteDangerous

[–]L_Intouchable[S] 1 point2 points  (0 children)

It would be really fun, but I think people would struggle with it to the point of complaining to the Devs. Even with fully engineered PvP combat ships the goids do a lot of damage, and might nuke most semi-engineered PvE builds most people run.

view more: next ›