Red screen of death with error “ secure boot rom(s) changed”

[sccarlso]

I’ve loaded a lot of machines but haven’t seen this one before.

Anyone experience this & know how to address it?  Is one of the boot chips bad?
Or some other issue?  This is after a complete wipe & reload that’s never come up before. 

Thanks!

[Chris-socal]

Did you search and look at the conversations on Red Screen?

I found a few and most referred to memory error, mismatch game or needing the reset key.

Here is one conversation recently but the original poster never replied if they found/fixed the problem. It will be interesting to see which scenario fixes your problem.

Chris

https://newlifegames.com/nlg/index.php?topic=43877.msg233197#msg233197

[sccarlso]

Saw that one when searching.  But that's a different error entirely so that wouldn't be it.

Suspecting a battery in the PCI card isn't making contact so on reboot, it loses it's data which I think might cause this.

Going to put a meter on the PCI card to verify it's keeping the memory in the PCI card alive with the power off.

Hoping it's as simple as that. 

Thanks!

[Chris-socal]

Good luck with that. Please update with your results.

[sccarlso]

Well, I checked everything, batteries, boot chips, memory, everything reseated.

Then it wouldn't even post...   

So I pulled a PCI card from another brainbox, replaced the boot chips, no other changes, and it booted, loaded, and functions normally.

Really odd.  Any issue with the PCI card shouldn't cause a failure to post.  It will post with no PCI card plugged in at all.

But, all that matters is it works now.  Just couldn't identify the actual root cause other than something with the PCI card.

[Stayouttadabunker]

I was watching this topic you started. 
Glad you sort of figured it out. 
And yes, I agree...that is a weird "fix".
What made you think of swapping the PCI cards?
I wonder if you swapped it back, would that PCI then work?

[sccarlso]

Well, only error was Secure Boot Rom changed.
Changed!?  lol.  It can’t be changed without a programmer!

And both the boot1 & boot2 chips verify on boot.
So had to be board bios or the PCI card and/or its bios. 

So swapped it all.  Then it would post and not give that error. 

But now one last show stopper came up, about to just use a completely different brainbox!

All my machines have Tito.  And 2 fam20 660 boxes were fine in this G20.  They loaded and configured right away with no problems.

But now that this upgraded 625 boots fine, loads fine.   I set it up like any other, same loader used as with the 660s.  But the stupid Tito keeps charging the ability to take and print vouchers to false!

Right after I set it to do accept/print vouchers in settings.  If I look at the log it shows that print and accept vouchers were set by operator to “true”.   Good.

But right after in the log it shows the SAS1 system changed print vouchers and accept vouchers to false.  So tickets won’t print.   Argh! 

Using the same OS/Ascent loader I’ve used.  Same set of games.  Same OS / Ascent loaders as the 660s.
Only difference is it’s a 625 with the video card added.

Several games also error saying there’s a problem with the standalone progressive on 3 games that didn’t on the 660 boxes.

I’d like this to be a fam20 box.  But might have to just make it a fam14 due to these issues that don’t occur on fam14. 

Crazy since I’m loading the exact same stuff.  Only difference is it’s an upgraded 625 box and not a 660.

Same boot chips.  Same Tito card.  Same settings on initial setup and same games loaded.

Just no idea how or why the Tito SAS always changes printing and accepting vouchers to false anytime I set it to accept and print them in settings. 

It was Halloween.  This box might be haunted!  😂

Will have to ask Brian Hinkley who makes the Tito cards if he’s ever seen this odd behavior.
By all means this “should” be easy and the same as the 660s I loaded in the same machine with the same software & settings. 

[Stayouttadabunker]

I wonder what chip contains your settings that the TITO SAS1 system changes?
Maybe it's an onboard physical chip problem on the PCI, rather than the TITO board?
But yeah...it's something that maybe Brian can check out/verify.
It would be interesting to hear his results.

[sccarlso]

Posted question on FB to him.

He usually replies quick so will see if he’s ever observed this behavior

But same brainbox loaded with fam14 doesn’t do this on the same machine. 

Makes it really odd!  I’m fine with odd, as long as I can fix it!  😂

[sccarlso]

Brian says the Tito doesn't send anything.  It only responds to queries.  Great.

The only flashable chips on the board and PCI card are the boot1 and 2 chips...

So no idea what's causing the system to always disable voucher in/out...

Kind of run out of ideas.  So going to put the fam14 boots back in there and verifiy vouchers work as they should.
If so, this box will remain a fam14.   As something funky is going on that's specific to fam20, and it's certainly not easy to locate!

[sccarlso]

Finally resolved!  Another case of misleading error messages...

While the PCI card issue was not found, replacing it with a known good fixed it.  Wasn't a battery issue, just something not right with that PCI card...


Then, the follow on issue of the inability to cashout was caused by the cashout button being too tighly screwed in on the back.   This held the cashout button down all the time.

Loosening the plastic nut on the cashout switch in the back allowed the buttton to release and press freely.

Tada, no more issues.  Prints the voucher when pressed and no other issues.

Learn something new all the time!