Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

I'm scratching my head on this one...

 

My Mobo is a gigabyte aorus gaming 7 v1.0 with the original bios installed. I bought it October ish 2017.

I upgraded from corsair vengence RAM (16GB 2x8GB DDR4 3000 MHz 1.35v)

to...

G.SKILL ripjaws V (32GB 2x16GB DDR4 3200 MHz 1.35v)

When I put in the new sticks, the PC wouldn't post with a C1 error code. All it would do was cycle on and off.

I switched out each new stick of RAM and put in its place an old stick. When I did this, it posted. I was able to go through this process to find that one stick would consistently be a problem. 

I thought, ok, this sucks but I will just go back to microcenter and get a new set of RAM.

Well, here's what's puzzling. I put both new sticks back in just to see if it would screw up again. It didn't, it's been running fine so far.

My BIOS also reset it's self to factory defaults on it's own.

I will do windows 10 memcheck when I get home in a couple of days. 

Do you guys think that the sticks truly weren't seated in properly? Or do you think I actually have a bad stick of RAM and right now things are running ok but in the short term, things will degrade very quickly?

Also, I never set the XMP profile to DISABLED before putting the new RAM in. So I guess the Mobo was trying to POST with an improper xmp profile from the old sticks. Do you have to do that? 

Why did my BIOS reset itself? I have to do my entire OC again. Oh well.

 

What are y'alls thoughts?

FAA: ATP-ME, 737 CA, enough time in the 757/767 to be dangerous 🤠

Matt Kubanda, 7950X3D, 64GB RAM, RTX 5090@4k, MSFS 2024

 

 

 

A badly seated card is always a possible explanation of a RAM issue, or more likely, a dirty contact or some dirt or other foreign debris in the slot.

Some overclocking mobos are designed to fail-safe back to default/auto values if they fail to POST as configured...that might explain your resets.

The Win 10 memory test is really hit and miss--I'd suggest downloading the free Memtest 86+ utility and creating a bootable USB stick using the supplied program.  Boot into that and run it for 8-12 hours (e.g. overnight).

Motherboards aren't always super-accurate on the voltages actually being supplied to the DIMMs.  Sometimes if the memory is teetering on the ragged edge of stability, adding just a little voltage can get it over the hump...e.g. 1.35v to 1.36v or 1.365v. 

As far as the XMP settings, if you have the BIOS set to automatically use XMP, then it should use whatever XMP profile is written into the installed DIMM's SPD.  If it was manually set using the XMP profile, then it will use whatever you last set in the BIOS.  The exact terminology and settings vary with the BIOS.

 

Bob Scott | President and CEO, AVSIM Inc
ATP Gulfstream II-III-IV-V

Sys1 (MSFS20+24/XPlane12+11): AMD 9800X3D, water 2x240mm, MSI MPG X670E Carbon, 64GB GSkill 6000/30, nVidia RTX4090FE
Alienware AW3821DW 38" 21:9 GSync, 2x4TB Crucial T705 PCIe5 + 2x2TB Samsung 990 SSD, EVGA 1000P2 PSU, 12.9" iPad Pro
Thrustmaster TCA Boeing Yoke, TCA Airbus Sidestick, Twin TCA Airbus Throttle quads, PFC Cirrus Pedals, Coolermaster HAF932 case

Sys2 (P3Dv5/v4): i9-13900KS, water 2x360mm, ASUS Z790 Hero, 32GB GSkill 7800MHz CAS36, ASUS RTX4090
Samsung 55" JS8500 4K TV@60Hz,
3x 2TB WD SN850X 1x 4TB Crucial P3 M.2 NVME SSD, EVGA 1600T2 PSU
Fiber link to Yamaha RX-V467 Home Theater Receiver, Polk/Klipsch 6" bookshelf speakers, Polk 12" subwoofer, 12.9" iPad Pro
PFC yoke/throttle quad/pedals with custom Hall sensor retrofit, Thermaltake View 71 case, Stream Deck XL button box

Sys3 (DCS/P3Dv4/ATS/ETS): AMD 7800X3D, MSI MPG X870E Carbon, Noctua NH-D15S, 64GB GSkill 6000/30, EVGA RTX3090
Alienware AW3420DW 34" 21:9 GSync, Corsair HX1000i PSU, 4TB Crucial T705 PCIe5 + 2TB Samsung 970Evo Plus,
TM TCA Officer Pack
, Saitek combat pedals, TM Warthog, TM RS300 FF wheel/pedals, Coolermaster HAF XB case

It's a Gigabyte that is perfectly normal. It is just verifying the timings of the new ram, now that its up and running make sure you have enabled the XMP profile and it is running at 3200.

I have a Gigabyte board and just upgraded my corsair ram to some faster 4000mhz stuff and it did the same thing. Took about 3 self restart before it was ready to boot up.

I don't recommend doing this but if you were to mess with the timing and frequency settings and get to aggressive it will do the same thing again and restart till it gets to a safe setting again and finally boot up.

Flight Simulator's - Prepar3d V5/MSFS | Operating System - WIN 11 | Main Board - GIGABYTE X870E Aorus Elite WIFI7 | CPU - AMD 9800X3D | RAM - CORSAIR 64GB 6600Mhz | Video Card - EVGA RTX3090 FTW3 Ultra Monitor - DELL 38" Ultrawide | Case - CORSAIR 750D Full Tower | CPU Cooling - CORSAIR H170i Elite LCD 420mm Push/Pull | Power Supply - EVGA 1000 G+ | Sound System - Definitive Technology ProMonitor 600 w/subwoofer

On ASUS motherboards you have a MemOK button you press after boot when new memory is fitted this will then put the MB in resetting the memory timings.

 

Raymond Fry.

PMDG_Banner_747_Enthusiast.jpg

Is the memory on the Motherboard's memory qualified vendor list?

Gigabyte x670 Aorus Elite AX MB; AMD 7800X3D CPU; Deepcool LT520 AIO Cooler; 64 Gb G.Skill Trident Z5 NEO DDR5 6000; Win11 Pro; P3D V5.4; 1 Samsung 990 2Tb NVMe SSD: 1 Crucial 4Tb MX500 SATA SSD; 1 Samsung 860 1Tb SSD; Gigabyte Aorus Extreme 1080ti 11Gb VRAM; Toshiba 43" LED TV @ 4k; Honeycomb Bravo.

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.