| ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 09517 | Crash/Freeze | Critical (emulator) | Always | 4 days ago | 12 hours ago |
| Tester | danylopez123 | View Status | Public | Platform | MAME (Official Binary) |
| Assigned To | Resolution | Unable to reproduce | OS | Windows (x64) | |
| Status [?] | Closed | Driver | |||
| Version | 0.289 | Fixed in Version | Build | x64 | |
| Fixed in Git Commit | Github Pull Request # | ||||
| Summary | 09517: stvbios: Crashes MAME if you pick "C.R.T CHECK" in the ST-V TEST MENU(in factory) | ||||
| Description |
This happens for the ST-V in general, regardless if you have a cart inserted or not. By holding the service menu during bootup, you can access a more extended service menu for the ST-V, mainly to test the different parts of it, things were going fine.. until it tries to get to the C.R.T CHECK PART, over there, it makes MAME crash. If I remember, this didin't happened in a previous MAME version. I've included a screenshot using the Saturnus core from Mednafen (Used in BizHawk) to show what it should be showing if it didin't crashed, this sorta seems to happen when it tried to change resolution but the same thing happened in the "CLK-CHANGE" but it doesn't seem to make MAME crash.. could it be something else that's different in the "C.R.T CHECK"? |
||||
| Steps To Reproduce |
1. Load stvbios, only the BIOS, no cart 2. Hold "Service Mode" (F2 by default) during any ST-V bootup 3. Press "Service 1" (9 by default) 2 times to select C.R.T CHECK 4. Press "Service Mode" 5. MAME Crashes (For some BIOS I think, some survive) |
||||
| Additional Information | |||||
| Github Commit | |||||
| Flags | |||||
| Regression Version | |||||
| Affected Sets / Systems | stvbios | ||||
|
Attached Files
|
This is what it would normally be showing if it didin't crashed
| ||||
 No.24569
Kale Developer
4 days ago
|
Can't reproduce with latest. |
|---|---|
 No.24573
danylopez123 Tester
4 days ago
|
I did tried this in the stable 0.289 but now that I got the latest DEV version, it doesn't seem to crash now. I guess this can be marked as Resolved. |
|
No.24574
danylopez123 Tester
4 days ago
|
No wait.. I was doing this using a different region BIOS and now when I tried this again.. HUH!? Now it's working just fine!? Ugh.. I swear this was crashing on me before.. I must have ended up having some sort of "Curse" on me.. nevermind, mark this as invalid or something if you want. |
|
No.24575
danylopez123 Tester
4 days ago
|
[Sorry for the 3rd note but somehow, I can't edit my previous notes, this one is the final one, I promise] Actually.. I know how I've managed to trigger this, I've altered the steps to reproduce, also it seems that this happened to me with the default Japan BIOS but when I tried another, it was just fine, maybe some BIOS are lucky to survive, I don't know. |
 No.24585
Robbbert Moderator
21 hours ago
|
Unable to confirm. I tried all the bioses (0 to 13) and none crashed. bios 13 is a bit tricky because it only gives a black screen at start, however the trick of holding F2 and hitting F3 still brought up the test menu, like all the others did. |
|
No.24586
danylopez123 Tester
19 hours ago
|
Well.. then I'm not sure, but I SWEAR this is how it happened to me, or at least with my current Windows 10 PC.. oh, I don't know anymore. You can close this issue and mark it as invalid or something, this might just happens at random to me, i don't know. |
|
No.24587
Robbbert Moderator
19 hours ago
|
I'll leave it for a few days. If you get another crash, please post the dump here. No dump == no clues. |
 No.24589
JimCarlTay Senior Tester
12 hours ago
|
Unable to reproduce on release version 0.289 or on build 957db01, closing. |