X299 Taichi crash after reboot - bios troubles

Denpepe

Denpepe

2[H]4U
Joined
Oct 26, 2015
Messages
2,269
So in my infinite stupidity I gave destiny 2 another try, game crashed, got a blue screen, pressed reset button, computer reboots, I click on hwinfo64, 20% orso into loading this, I hear some kind of pop and computer freezes. results in me slightly panicking.

I press reset again, does nothing, couple times more, still nothing, me starts freaking out. So at this point, i hold down the power button and after 4 sec, pc turns of, so I turn the pc on again, fans start spinning like crazy, no image, pc shuts down again after 20-30 sec, and restarts only to do the same again a couple of times.

Then in the end some screen popped up with the message "secure backup uefi B -> A"

After that it booted again, I rebooted to check/adjust bios, that went ok, and for the moment my pc seems to be running ok again, but I'm kind of worries now that this might happen again or even get worse, anyone have anything similar happen or have anyadvise?
 
That message was stating the bios was corrupted and it’s copying the backup to main. At least that’s what some of the older ASRock ones stated. I’d still be a bit worried about the pop and back up everything just in case.
 
A cockaroacha or some other unsavory critter stepped across the wrong wires in your PSU and made it mad for a bit.

Start sniffing parts for burnt odors emanating.
 
You can also review windows event logs. The pop could have been tied to sound of speakers not necessarily the system itself. I noticed that when I do a sudden power off my speakers also make a pop sound.
 
deaedius said:
You can also review windows event logs. The pop could have been tied to sound of speakers not necessarily the system itself. I noticed that when I do a sudden power off my speakers also make a pop sound.
Click to expand...

I checked the logs, other then a couple erros due to an unexpected restart I have 167 bitlocker driver errors in less then 2 min but that might have been my raid array that was not set correctly yet due to the bios flash, bios was back to AHCI.
 
Spartacus said:
bitlocker?

There's your problem.
Drive encryption is nothing but trouble.

.
Click to expand...

I don't use bitlocker, like I said I think it's due to the raid that was not set up yet. Anyways, got my bios updated to the latest version 1.70 from a couple days ago and so far the system seems stable again.

Won't try destiny 2 again until they patch the crashes.
 
So any other issues since this event?
I'm shopping for an x299 board.
ASRock looks like the only manufacturer right now that doesn't have horrific RMA experiences the last few years to current.
 
No more issues, pc works fine as long as I don't play destiny 2 but that's afaik a sofware issue, not hardware.
 
Denpepe said:
No more issues, pc works fine as long as I don't play destiny 2 but that's afaik a sofware issue, not hardware.
Click to expand...

Cool, ended up with an MSI ack from here.
A studio I worked at in Santa Monica has MSI x79 boxes still in service.
I'll see how this goes, and a Taichi XE is my backup plan.
We burned thru Gigabyte and Asus x79 & x99 bc they developed problems that would persist thru rma like losing USB ports or dimm slots.
Rma process was unacceptable with those vendors.
 
Scratch that, now I'm on a Gigabyte Gaming 3.
Since it's my box, and I don't have anyone breathing down my neck to keep gear up let's see how it goes.
When I give up and go buy a Taichi XE I'll post here.

Hopefully the Mobo merry go round will stop at the Gigabyte.
 
I made a wee backup pc with a Gigabyte AX370M Gamingf 3 mobo and an AMD 1500X, so far I'm happy with it, my 3200mhz memory works fine after turning on XMP which was a relief after all the stories I read about Ryzen and memory compatability.

I had a spot of trouoble after the latest windows patches with the taichi not waking up correctly but a bios flash with the latest bios fixed that. Guess it had maybe something to do with the updated microcodes in the patch.
 
I always had the best luck with AMD at the end of a product lifecycle.
Stuff tended to either finally work, or it was well documented in forums to stay away from a POS.

I think Threadripper may need more time marinading.
It's difficult to go from a narrow server centric QVL to consumer/gaming.

I'm liking this Gaming 3 so far, it's doesn't have that stupid Asus AIO induced CPU fan error.
You figure Asus would have compensated for that by now.
It lacks polish.

Gigybyte's uefi shell needs a lot of work.
I think MSI X79 boards may actually have the current Gig shell beat.
I wouldn't recommend a person new to overclocking tackle it.
It lacks buddy bumpers and I can see someone getting into the weeds quickly.
 
You must log in or register to reply here.
Back
Top