We got it working. It seems that the expansion ROM was enabled. It works fine after disabling it. Thanks @Margaret Bloom.
Answer from Vinu Chandran on Stack OverflowHello, I got 2x SuperServer E300-9D-8CN8TP with X11SDV-8C-TP8F motherboards from my work place. I found some AC adapters that power on the device and now am troubleshooting them. They startup and go to "DXE - BIOS PCI Bus Enumeration" with a code of 92, it stays there and then reboots. I plugged in the ethernet cable to the IPMI port in hopes that I could do something from there. The BMC got the ip 192.168.1.152. If anymore information is needed I will provide it to the best of my abilities. Thank you.
tldr: Does anyone know how I could get passed DXE - BIOS PCI Bus Enumeration Code 92 on a X11SDV-8C-TP8F?
After this part the system will restart. The right label is IPMI, when I go to 192.168.1.152 it asks for a username and password. I put the username as ADMIN and the password as 002590B8FDE9 but that doesn't work. I don't see any other place that lists a password for IPMI. Top down view of the E300-9D-8CN8TP with X11SDV-8C-TP8F motherboardEdit: So I got 32GB DDR4 ECC RAM and with that I was able to boot and get into bios. There are other issues involving code 79 but that will have to be a different issue.
Thank you for your help!
x86 - BIOS Stuck after PCIe Enumeration - Stack Overflow
[SOLVED] PC restarts a few minutes after boot up?
My computer hangs on post with debug code 92. - Republic of Gamers Forum - 128188
Window 10 pc won't boot. Getting error code 92 on screen.
-
Graphics card: RX 480
-
MSI 970 GAMING DDR3 2133 ATX AMD Motherboard
-
AMD FX-6300 Vishera 6-Core 3.5 GHz
-
Windows 10, current version
So here's what happened. I had just downloaded that new game Elex on steam. I play for about 2 minutes and start to think the game looks really shitty. Very lo-res textures and such. Then it gets to a point in the opening cut scene where it just freezes. I force quit back to the desktop and the tops of all the windows are discolored and the minimize/maximize/close buttons are covered by black boxes and not functional. This hasn't happened before. Go to restart and it won't boot back up. All I'm getting is a "92" on the screen.
I looked up error code 92 for MSI mobos and found this info from a forum post, but no solution.
92 = PCI Bus initialization is started (your computer is starting the PCI expansion card slots communications lines between the slots to the chipset on your board)
I'm guessing this means there may be a problem with the GPU since since it's connect via the PCI bus and I experienced those graphical anomalies before I attempted a restart. But how would it be able to use the GPU to send that code to the screen without the GPU?
I've also tried resetting the BIOS and checking the RAM sticks one by one, but still getting that error 92.
Has anyone experienced a problem like this before? Thanks for any help you can provide.
Gigabyte Aorus X399 Gaming 7
Gigabyte Aorus Extreme 1080 ti
64 gb gskill memory
Samsung 1Tb M.2
Last night I got complacent and decided to install the Windows 10 Fall Creators update, 1809. Downloaded, updated, when it went to reboot I'm getting nothing on the screen, seems to be stuck in a loop on boot up. Does not respond to F12 or Del key on bootup. I made a video of the onboard LED and went through it, frame by frame, trying to capture the codes:
48 Reserved
A4 SCSI initialization is started
64 CPU DXE initialization started
61 NVRAM initialization
6A IOH SMM initialization
3F Reserved
D5 Can't load boot option.
D8 Flash update has failed.
92 PCI Bus initialization Started
D1 IOH initialization error.
14 Reserved
15 Pre-memory North Bridge Initialization started
19 Pre-memory South Bridge initialization started
14 Reserved
15 Pre-memory North Bridge Initialization started
66 CPU DXE initialization started
68 PCI host bridge initialization started
c0 Reserved
D3 Some of the architectural Protocols are not available.
C1 Reserved
C6 Reserved
B5 PCI Device hot plug
67 Reserved
6D Reserved
67 CPU DXE initialization started
11 PEI Core is started
48 Reserved
A5 Issue reset during SCSI initialization process
89 Reserved for OEM use
B4 USB device hot plug-in
02 ???
88 Reserved
B4 USB device hot plug-in
D5 No Space for Legacy Option ROM initialization.
92 PCI Bus initialization Started
9A USB initialization started
D1 IOH initialization error.
14 Reserved
19 Pre-memory South Bridge initialization started
15 Reserved
19 Pre-memory South Bridge initialization started
14 Reserved
15 Pre-memory North Bridge Initialization started
BE Reserved
60 Issue reset during SCSI initialization process
C0 Reserved
88 Reserved
D3 Some of the architectural Protocols are not available.
C1 Reserved
I resisted the urge to immediately panic and start flailing about changing things. Going to start trying to fix the problem this evening. So, I'm thinking the first step is to disconnect everything and take the graphics card out of it, hook up my monitor to the integrated graphics display. Is it even possible for a windows update to corrupt the bios?
Any suggestions are welcome.
Edit: Forgot there's no integrated video, woops. Took the 1080 out and stuck in an old card I had lying around. Apparently same behavior, although I did no detailed comparison of codes. Edit: It seems that I am not receiving power to USB devices, keyboard, mouse. I just wanted to try Windows dark mode. My pc is dark, alright. I’m convinced the mobo is kaput, how that was accomplished from a simple Windows update, I don’t know. Co-worker also reported issues with displays and user profiles and is apparently locked out after 1809 update. If I have to buy a new mobo, I’m not inclined to buy the same model as the one that just let itself get T-boned by a Windows update. Unfortunately, the others are E-ATX and I would need a new case too. Edit: The cpu led comes on immediately on power up, stays on solid, a flicker as it refreshes periodically, I guess as it loops. Reset cmos, no change. I’m just reporting things as I notice them after some reading. So now I don’t know whether it’s the cpu, mobo, or the suspiciously timed windows update. Build has been running for almost a year w no problems.
Edit: removed all 4 memory sticks, then put the first one back into slot 2. Booted into bios screen! Yay, right? Screen said cmos had been cleared, but i don’t remember the changes I had made, so i exited w/o saving, it booted into windows, all my stuff is there. Powered down added second stick to slot 4, would not boot. I then tried swapping each of the remaining 2 sticks into slot 4 w same results. Then I tried each of them alone in slot 2, no luck. Got back around to putting the stick that worked back into slot 2, now it does not work. Wtf fiddlesticks!
So, cpu, mobo, or memory? I still lean toward mobo, but more confused than ever.