Hello,

I've done a test run without GPU, worked fine until I added the 7900xtx, then, Dr Debug cycle through codes 36/37 (and sometimes 38 - and I've seen one 39 during writing this) for the 20 last minutes.

I've flashed the bios to the latest to day before sitting the CPU. GPU fans are not running, but TUF logo is lighted.

Only 36 & 37 are documented, with CPU SSM INIT and MEM SB INIT respectively, 38 & 39 are undocumented.

Is it really initializing for that long? I've been 20+minutes in, should it be that long?

Edit: After about 50 minutes: I've seen it briefly go up to 44, and then count down to 37. I've not seen 36 in a long time... is this "training percentage"? Why do it count down.

Edit 2: computer has shutdown by itself... is GPU broken?

I had bought a new Ryzen 3700x and installed it yesterday. Went perfectyl fine on my old Taichi x370, updated bios once, installed new cpu, updated bios again to the latest, easy.

I had discovered I was out of propyl alcohol so I ended up scrapping off as much of the old thermal paste and reapplying a new dallop, but there were still some old material left over. Still, everything worked fine, and I was very happy.

Today I had intended to go today to reseat everything completely cleanly, but upon doing so, I'm now having trouble getting my system to post. I am seeing error 36 and b6, which according to the manual is a memory issue, but I don't see how I'm suddenly having trouble today. I reseated everything - memory, cpu, and cmos. Still same error. Freaking out now thinking I might've inadvertedly bricked something, should've just left it be...

I am trying to fix my brothers PC that I built for him about 5 years ago.

The MSI motherboard is showing post code 36. I don’t have a manual as I have no idea where he put it.

He took it to our local Micro Center, they diagnosed a bad GPU. Bought a used 1080 Ti and just installed it. But it is showing posts code 35 or 36. I have no idea what those codes mean.

A little help would be nice. Thanks

Troubleshooting Help:

What is your parts list? Consider formatting your parts list.

CPU - Intel Core i7-4790K Devil's Canyon Processor 4.0Ghz 5.0GT/s 8MB LGA 1150 CPU
CPU Cooler - Cooler Master Hyper 212 Evo Direct Touch 4 Heatpipe Heatsink
Motherboard - Asrock Z97 Extreme4 LGA 1150 Intel HDMI SATA6
RAM - G.SKILL Ripjaws X Series 32GB (4x8GB) DDR3 19200 2400MHz
Storage 1 - PNY CS1311 480GB 2.5” SATA III Internal Solid State Drive
Storage 2 - Seagate Barracuda 1TB 7200RPM 64MB SATA 6Gbps 3.5in Internal Hard Drive
Storage 3 - SanDisk SSD PLUS 1TB Internal SSD - SATA III 6 Gb/s, 2.5"/7mm
GPU - EVGA GeForce GTX 1080 Ti FTW3 Gaming, 11GB
Case - Thermaltake Chaser A31 VP300A1W2N Mid Tower
PSU - EVGA SuperNOVA 750 G2 220-G2-0750-XR 750W
Optical Drive - ASUS 24X SATA DVD Burner DRW-24B1ST/BLK/B/AS
Operating System - Windows 10 64bit

Describe your problem. List any error messages and symptoms. Be descriptive.

I purchased the components and built this PC back in March of 2015, originally with a GIGABYTE GTX 970 and 8GB of G.SKILL Trident X Series (2x4GB). I upgraded the GPU and RAM in November of 2018 to the parts listed above, all bought used from ebay auctions but they seemed to be in good shape when I installed them. Not long after the upgrade (within a week) I started to get beeps from the motherboard on startup and occasionally a failed boot that would sort itself out in a minute or two. It never went away, so I simply avoided restarting the computer for a couple months. Yesterday, I turned it off because it was being rather slow and now I cannot reboot the PC. The mobo is displaying various error codes, including occasionally '55' and most often '36', which I've read indicates an issue with the RAM.

List anything you've done in attempt to diagnose or fix the problem.

I've removed the RAM, moved the sticks around in different slots, tried brand new RAM, etc, and I've cleared the CMOS several times between various RAM configuration changes. Today I also removed the GPU and tried to boot but it still resolves to error code '36' before inevitably showing F2 indicating recovery procedures in process (or so I've read).

Post relevant photos of build/parts here.

N/A

Provide any additional details you wish below.

If anyone knows how to help me fix it, please offer your advice. Otherwise, I'd like to know what my options are for replacement of the motherboard without sacrificing any of the other components. Everything should be in good shape. Not counting the ebay items I recently added, I've owned everything since factory new and always been rather gentle with the PC. I've never overclocked it or run very demanding games at high resolution. I do a lot of 3D modeling and 3D printing, so it gets most of it's miles from that. I believe most of my components should be good to go if I can replace whatever is failing in the system, but a direct replacement motherboard is going for almost twice what I paid for it back in 2015 and would keep me tied to DDR3 RAM for the foreseeable future. If I could, I'd like to move my current CPU to a DDR4-capable motherboard and upgrade to DDR4 RAM while maintaining all of the other components as is. If anyone can recommend a motherboard that would be a good fit for this application please chime in. I'm pretty inexperienced and ignorant with the latest PC tech so please be gentle.

Thank you!

Update: Turns out my partner is infinitely smarter than I am. Rubber duck'd it with her and she pointed out I was looking at the memory slots upside down. I had the one stick of ram in slot A2 not A1 - which caused the F1 error.
Why the manual calls that "PEI_RECOVERY_USER" and not something memory related, I'll never know. But meh. It works now!

---

TLDR: I have an ASRock B650D4U-2L2T/BCM that keeps getting stuck on an F1 POST code and I can't figure out what it actually wants from me.

TSWR (Too short, will read):

So last week I got an ASRock B650D4U-2L2T/BCM. Like a kid on Christmas I was all excited to build my first 8 bay NAS out of it.

Put everything together, tried to power it up. Found out the PSU I had was having trouble with the backplane of my CS382. So it really was just like Christmas. Got the toy, no way to power it.

Ordered another PSU, put it all together again yesterday and got... Nothing. Fans spin at full speed for about 8 seconds, then wind down after the 7 segment on the mobo sticks on F1.

No monitor ouput on VGA, HDMI or display port, no keyboard for input (plugged in but won't even give me the ability to hit numlock). Plugged in the OOB for it, let DHCP assign an IP (as much as it saddens me to have to put the OOB on my normal subnet, but since the OOB subnet has no DHCP and I have no way to set an IP without the machine booting...) and checked in there. No more information than before. Just a post code of 0xf1.
Checked the online manual for the board, it says that 0xf1 is "PEI_RECOVERY_USER"
It doesn't tell me what that means or how to even start fixing it.

So I assume bios is fried, upload a new version through OOB. OOB reports everything should be good, powercycle the machine for it to take effect. So I do just that.
Nothing still.

Pull battery and short the clear cmos pads, still nothing.
Pulled the CPU and memory to see if something else happened and it beeped at me with error codes that I just lobotomised it.

So now I'm here asking for help. What glaringly obvious troubleshooting have I missed?

Hello. I need some help. Suddenly getting wietd codes and can't figure out the reason. Didn't do much to cpu (except reposting). Looks nice and clean. Socket as well. But can't boot. We'll, I can but only with old memory kit (around 4800 iirc). The main one refuse to boot in any slot/configuration Ordered a new one (thought maybe ram was dead) - same issue, can't boot. Usually I see codes 00, 15 or 37. Couple of times we're 0d and the rest are random. The fact that I can normally boot with the old kit (and play) tells me that cpu is fine. Or there is something I didn't think of? I tried to run memtest on old slow kit - all went smoothly (does that imply that controller is also fine?)

CPU is 9800x3d and it plays just fine with slow memory but not with 6000.