Hacking USB Loader GX

[Larsenv]

No, I'm using NAND Saves Emulation and NAND Channels Emulation, those use my UNEEK NAND.

I changed some settings and it's now giving me a message saying "The system files are corrupted.".

 

[Cyan]

NAND save emu is for Wii disc games, to save the game on the "emuNAND save" path.
NAND channel NEED to be set to full (I will remove partial option, it's just confusing users)

some games don't work with "full" and need "neek" mode.
I don't know why it worked and it doesn't anymore, like I said : I still don't have enough info.
which game?
did you try to reinstall it?
do you have a save ? did you try to backup/reset the save?
did you played it on cIOS full successfully before ?
did you played it on neek ? before or after it stopped working with cIOS?
which base are you using for cIOS mode?

it's time to go to bed for me, I'm working tomorrow, so you'll have more help from me in 18h from now.
maybe someone else will be able to help you while I'm sleeping/working

 

[Larsenv]

did you try to reinstall it?

No. I didn't think that would help.

do you have a save ? did you try to backup/reset the save?

No.

did you played it on cIOS full successfully before ?

Not sure what you mean.

did you played it on neek ? before or after it stopped working with cIOS?

No.

which base are you using for cIOS mode?

cIOS 249. Latest d2x Version, v11.

I loaded up Arcade Essentials, a random game I never played, and I got that "The system files are corrupted." message again.

Also, before I reset my settings to Default Settings and fixed my Emulated NAND Path, I got the error messages seen here.

 

[ngs428]

you mean that booting into neek without passing through usbloaderGX works?
and booting neek2o from USBGX doesn't? (either autoboot or boot from feature menu ?)

@ngs428:
here the result
I installed random VC and wiiware from different consoles to test.
At the same time, I can tell that my batch wad install works fine
This is the "export game list to csv" mode, but txt works too, (just not aligned nicely)

Spoiler

# USB Loader Has Saved this file
# This file was created based on your list of games and language settings.

"ID","Size(GB)","Name","Type","Console"
"WR9P","0.00","Megaman 9","Channel_EmuNAND","WiiWare"
"NAEE","0.00","Paper Mario","Channel_EmuNAND","VC_N64"
"WKBP","0.00","You, Me and the Cubes","Channel_EmuNAND","WiiWare"
"E6XE","0.00","Altered Beast","Channel_EmuNAND","VC_NeoGeo"
"WOBP","0.00","Art Style : ORBIENT","Channel_EmuNAND","WiiWare"
"PABE","0.00","Bonk's Adventure","Channel_EmuNAND","VC_TurboGraphX"
"C9HE","0.00","Boulder Dash","Channel_EmuNAND","VC_Commodore"
"FC8E","0.00","Castlevania II Simon's Quest","Channel_EmuNAND","VC_NES"
"HABA","0.00","Chaîne Boutique","Channel_EmuNAND","Wii_system_channel"
"HACA","0.00","Chaîne Mii","Channel_EmuNAND","Wii_system_channel"
"JODI","0.00","Homebrew Channel","Channel_EmuNAND","VC_SNES"
"EA4E","0.00","Samurai Showdown III","Channel_EmuNAND","VC_NeoGeo"
"MBEE","0.00","Shining Force","Channel_EmuNAND","VC_Genesis_megadrive"
"WILP","0.00","Tales of Monkey Island Chapter 1: Launch of the Screaming Narwhal","Channel_EmuNAND","WiiWare"
"HCUP","0.00","Wii Menu Electronic Manual","Channel_EmuNAND","Wii_system_channel"
"HCTP","0.00","Wii System Transfer","Channel_EmuNAND","Wii_system_channel"
"HCVA","0.00","Wii U Menu","Channel_EmuNAND","Wii_system_channel"
"LAKE","0.00","Wonder Boy in Monster Land","Channel_EmuNAND","VC_Master_system"
"QABE","0.00","Ys Book I & II","Channel_EmuNAND","VC_TurboGraphX-CD"

HBC is recognized as SNES because it starts with "J"
there are probably other channels which will have incorrect type or console, especially all the unofficial user injects.

I tested only with emuNAND.
it should work with wii, gamecube and NAND too.
I guess only Wii games have a "size" info.
not sure if GC has that info too. if gamecube have the size info, it should be wrong with dual disc games (I never completed the gamecube options and functions).

The CSV output looks great! Just what I requested. R1260 should be a good one, assuming this will be included

Wii and GC both have the size info. Also, yes, the generated report will only contain games displayed in the list.

Good to hear the batch installer is working! Showmiiwads seemed to do an alright job installing, a few wads were for some reason missed and had to be located and reinstalled.

The only other request I mentioned was the addition of the VC and wiiware types in the selection screen. A quick click on or off of the games by console. I have setup categories, but the main selection screen would be ideal. Request was as below:

"Is there a possibility to have on the screen where you check the consoles to display games for, selections for the types of VC games. As in something like this shown below with check boxes before each category such as "VC N64", etc.

Emunand
VC N64
VC NES
VC SNES
VC Sega Genesis
WiiWare
ETC.."

--------------------- MERGED ---------------------------

No. I didn't think that would help.
cIOS 249. Latest d2x Version, v11.

I am not familiar with v11. Is that a compatible release? V8, V10 and V10-alt are common.

 

[Larsenv]

I am not familiar with v11. Is that a compatible release? V8, V10 and V10-alt are common.

Sorry, my bad.

I have d2x cIOS v10, for some reason I thought it was v11 for some reason.

 

[Cyan]

did you try to reinstall it? --> No. I didn't think that would help.
Uninstalling the game also delete the savegame.
if you launched it, it could have a (failed to be created) save file.
Deleting the game will fully delete the savegame too.
deleting/reinstalling could help in such cases.


Did you played it on cIOS full successfully before ? --> Not sure what you mean.
I'm asking if that game already worked without using neek mode.
the USBLoaderGX has two different emuNAND mode : cIOS (partial/full) and Sneek/Uneek/Neek2o (Neek)
did you already played that game succesfully from the loader ?
I want to know if "it used to work but it doesn't work anymore" or if "it never worked and I want to play it"

did you played it on neek ? before or after it stopped working with cIOS? --> No.
ok, so you mean you never tested that "non working" game on Neek at all?
or do you mean that "now the game doesn't work at all even on neek"?

which base are you using for cIOS mode? --> cIOS 249. Latest d2x Version, v11.
That's not a "base", that's a version.
the base is "IOS56" or "IOS57" or "IOS58" or IOS37 etc.
d2x slot[BASE here]
for example d2x 249[56] = base 56 is installed in slot 249.

I guess the easiest way is to post a syscheck log to know what you really have installed in each slots.


I will also want more information on your "reseted config".
why did you reset the settings?
did the game worked before the reset and stopped working after the reset ?
what are your path to NAND ? ... because "DEFAULT" NAND path is sd:/nand/
it's not "Uneek"

Are you sure (like really sure ... really, not "I don't want to verify, it should be because why not?") that your EmuNAND is good dump? good path ? and loader has the good settings (IOS and path) ?


there's no reason that EmuNAND doesn't work.
there's obligatory a wrong setup somewhere.
try a new SD card, a new USB, a new path, etc.
Try things, untill you find something which make it work.

Do loooooooooot of tests to narrow the issue.
don't wait for me to tell you to test things one by one...

Test a different game to see if the issue is the game
test a different EmuNAND path to see if the issue is the path
test a different dump to see if the issue is the dump
test a different SD card to see if the issue is the SD card
test a different USB to see of the issue is the USB
test ... I don't know, Test it!

 

[sideskroll]

@Cyan
I would appreciate your help on an issue I found.
I have a new HDD. (A WD I mentioned earlier, the one I need to set to IOS 58 for it to load) thing is I haven't played any games with it till today (I verified it worked with IOS 58 and that was that) and I found myself in some kind of bug which I'm not sure if it always existed or if it's from a possible corruption of my loader or if it has to do with my HDD.... hell, I'm not even sure if what I'm about to tell you is in fact what triggers it!) but anyway, I'm almost positive that if I plug/unplug my classic controller pro from the wiimote a couple of times WHILE I'm in the loader the loader "freezes". and I write it that way cause I can still navigate with +/-, the pointer is still visible on-screen and I can "click" on channels (but they don't load). In fact nothing loads anymore. I can't access the settings button, I can't use the home button to get out. Nothing.
The led on my HDD stays blinking (which is what is making me doubt if this has to do with the new HDD)
Any ideas on this? Is this perhaps a "known bug" (nothing works but the interface is still "functional". If I click on a channel for instance, it doesn't load but it can't be "clicked again"... I don't know if I'm explaining myself correctly...)
Please tell me that this is a known issue or that you can at least reproduce the bug yourself... I can't take starting from scratch, AGAIN.
Could a sleeping HDD (incompatible HDD maybe) cause this behavior even though the loader is located in the SD card? Is the plugging/unplugging the controller triggering it?
Any help?
If you need more info/specific tests please let me know ASAP as I really NEED to be done with this once and for all.
Thanks!

 

[Clutz450]

The loader only freezes when you plug in and unplug the controller? Am I understanding you correctly? Like if you don't have that controller connected does the loader work like normal?

How big is your hard drive and how many games do you have on it? I have a 4 TB drive with a lot of games on it and it could take quite some time for it to load up and acts kind of like what you were explaining with the loader appearing frozen yet functional and the hard drive light blinking. How long did you let it sit that way? Try letting it get to that point again and then walk away and do something else. When you come back to your Wii after several minutes see if it's still "frozen" or if it seems like it's working again.

Exactly what kind of Wester Digital drive is it? Try and find out if there is a program on their site where you can check for and disable any sleep feature it may have.

That's all I can think of for now. Hopefully Cyan will be able to give you some other advice.

 

[sideskroll]

The loader only freezes when you plug in and unplug the controller? Am I understanding you correctly? Like if you don't have that controller connected does the loader work like normal?

How big is your hard drive and how many games do you have on it? I have a 4 TB drive with a lot of games on it and it could take quite some time for it to load up and acts kind of like what you were explaining with the loader appearing frozen yet functional and the hard drive light blinking. How long did you let it sit that way? Try letting it get to that point again and then walk away and do something else. When you come back to your Wii after several minutes see if it's still "frozen" or if it seems like it's working again.

Exactly what kind of Wester Digital drive is it? Try and find out if there is a program on their site where you can check for and disable any sleep feature it may have.

That's all I can think of for now. Hopefully Cyan will be able to give you some other advice.

More like... if INSIDE the loader I connect and disconnect the CCP from the wiimote a couple of times that happens.
Not big at all, 1TB model WDBUZG0010BBK which is SUPPOSEDLY (according to the compat list) 100% compatible. (although it never mentioned anything about having to use IOS 58 instead of cIOS otherwise it won't boot.
When it first froze up I left it there and went about my day believing that the loader probably had to create the cache fro the banners and whatnot. But 30 minutes later it was STILL "frozen" like I left it so... I don't know, should I give it more time? I highly doubt that since there are only like 200-250 games betweenn GCN and Wii... It shouldn't take that long....
I THINK there's a link for a WD tool over at the compatibility list. I might try it. But I doubt it has to do with that...

 

[Cyan]

first thing, don't connect the HDD at all to exclude the possibility that it's the cause.
boot the loader without HDD, let it go into channel mode.
now try your CCpro connection/disconnection to see if it freezes too.
if it does, then you can stop worrying about the HDD being the cause.

About the Classic controller doing this bug, it's strange.
This issue like you described it is usually happening when the GUI has another active process, like currently opening a new windows, closing it, extracting file in the background and you have to wait for the end of the extract process before exiting a menu or clicking another button.
We try to "freeze" the GUI when such action is done to prevent the user from doing anything else, but maybe some area is not properly "secured".

Though, I don't see why just pluggin the CC on wiimote would freeze the GUI.
the GUI is related to the input as it needs to read if a button is clicked/hover/out/etc., so maybe plug/unplug can become an issue if the cursor is above an item while you plug/unplug?

Sorry, I don't know why it's in a "no input" mode.
Maybe memory issue, not enough memory left to do the requested action or even display an error message.
Memory limit is a big issue and that's why I have less enthusiasm to work on the loader, add new things, etc.
I don't know how to properly check the used/free memory in realtime, debugging it is not easy as it's not a "sources code error" and there's no crash.

 

[Larsenv]

did you try to reinstall it? --> No. I didn't think that would help.
Uninstalling the game also delete the savegame.
if you launched it, it could have a (failed to be created) save file.
Deleting the game will fully delete the savegame too.
deleting/reinstalling could help in such cases.

Yeah, but even if that worked for one game and I'm having the problem for all WiiWare Games that I've tried, what good would that do for me?

Did you played it on cIOS full successfully before ? --> Not sure what you mean.
I'm asking if that game already worked without using neek mode.
the USBLoaderGX has two different emuNAND mode : cIOS (partial/full) and Sneek/Uneek/Neek2o (Neek)
did you already played that game succesfully from the loader ?
I want to know if "it used to work but it doesn't work anymore" or if "it never worked and I want to play it"

It used to work but it doesn't work anymore. Well, for other various WiiWare Games, that is.

The first game I remember not working was WarioWare: D.I.Y. Showcase even though I had a Save File on it.

did you played it on neek ? before or after it stopped working with cIOS? --> No.
ok, so you mean you never tested that "non working" game on Neek at all?
or do you mean that "now the game doesn't work at all even on neek"?

The other day I booted up into the UNEEK NAND and launched a Game from the Wii Menu that wasn't working on USB Loader GX.

It loaded up without any errors.

which base are you using for cIOS mode? --> cIOS 249. Latest d2x Version, v11.
That's not a "base", that's a version.
the base is "IOS56" or "IOS57" or "IOS58" or IOS37 etc.
d2x slot[BASE here]
for example d2x 249[56] = base 56 is installed in slot 249.

I guess the easiest way is to post a syscheck log to know what you really have installed in each slots.

Yes, here's my SysCheck:

Spoiler

SysCheck v2.3.1 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on vIOS58 (rev 6176).

Region: NTSC-U
System Menu 4.3U (v513)
Priiloader installed
Drive date: 12.07.2010
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x11
Console ID: 70323661
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v4
Found 112 titles.
Found 56 IOS on this console. 4 of them are stub.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 16174): Trucha Bug, NAND Access
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 257): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 16174): Trucha Bug, NAND Access
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 16174): Trucha Bug, NAND Access
IOS31 (rev 1037): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 65535): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 16174): Trucha Bug, NAND Access
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 16174): Trucha Bug, NAND Access
IOS51 (rev 4864): Stub
IOS52 (rev 16174): Trucha Bug, NAND Access
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 16174): Trucha Bug, NAND Access
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 16174): Trucha Bug, NAND Access
IOS80 (rev 16174): Trucha Bug, NAND Access
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 65535, Info: hermes-v5.1): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[57] (rev 65535, Info: hermes-5.1): Trucha Bug, NAND Access, USB 2.0
IOS224[37] (rev 65535, Info: hermes-v5.1): Trucha Bug, NAND Access, USB 2.0
IOS231 (rev 1037): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS236 (rev 65535): Trucha Bug, ES Identify, NAND Access
IOS245[37] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS246[38] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, ES Identify, NAND Access
IOS247[53] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS248[55] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21010, Info: d2x-v10beta52): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS252[56] (rev 21010, Info: d2x-v10beta53-alt): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v6
MIOS v10
Report generated on 12/31/2015.

I will also want more information on your "reseted config".
why did you reset the settings?
did the game worked before the reset and stopped working after the reset ?
what are your path to NAND ? ... because "DEFAULT" NAND path is sd:/nand/
it's not "Uneek"

Are you sure (like really sure ... really, not "I don't want to verify, it should be because why not?") that your EmuNAND is good dump? good path ? and loader has the good settings (IOS and path) ?

I resetted the settings because I thought it would fix it.

The games didn't work before or after the Reset.

My path to my NAND is /nands/pl_us/, what UNEEK wants.

NAND Saves Emulation and NAND Channels Emulation are set to Full for me.

This is what it looked like before the Reset:

Spoiler

This is what it looked like after the Reset:

Spoiler

The system files are corrupted.

there's no reason that EmuNAND doesn't work.
there's obligatory a wrong setup somewhere.
try a new SD card, a new USB, a new path, etc.
Try things, untill you find something which make it work.

I doubt my USB HDD is the problem since I've been using it for about a year and a half now.

Do loooooooooot of tests to narrow the issue.
don't wait for me to tell you to test things one by one...

Test a different game to see if the issue is the game
test a different EmuNAND path to see if the issue is the path
test a different dump to see if the issue is the dump
test a different SD card to see if the issue is the SD card
test a different USB to see of the issue is the USB
test ... I don't know, Test it!

Game - No.
EmuNAND - If it's set to the correct Path in USB Loader GX Settings, why wouldn't it work?
Dump - No.
USB - No.
SD Card - No.

So, is there anything else I can try?

 

[sideskroll]

first thing, don't connect the HDD at all to exclude the possibility that it's the cause.
boot the loader without HDD, let it go into channel mode.
now try your CCpro connection/disconnection to see if it freezes too.
if it does, then you can stop worrying about the HDD being the cause.

About the Classic controller doing this bug, it's strange.
This issue like you described it is usually happening when the GUI has another active process, like currently opening a new windows, closing it, extracting file in the background and you have to wait for the end of the extract process before exiting a menu or clicking another button.
We try to "freeze" the GUI when such action is done to prevent the user from doing anything else, but maybe some area is not properly "secured".

Though, I don't see why just pluggin the CC on wiimote would freeze the GUI.
the GUI is related to the input as it needs to read if a button is clicked/hover/out/etc., so maybe plug/unplug can become an issue if the cursor is above an item while you plug/unplug?

Sorry, I don't know why it's in a "no input" mode.
Maybe memory issue, not enough memory left to do the requested action or even display an error message.
Memory limit is a big issue and that's why I have less enthusiasm to work on the loader, add new things, etc.
I don't know how to properly check the used/free memory in realtime, debugging it is not easy as it's not a "sources code error" and there's no crash.

Yes, forgot to mention that I already tried booting without HDD. Sadly, I can't replicate the issue. BUT, after extensive testing (and I do mean EXTENSIVE) I managed to find a "similar" kind of bug... (without the HDD attached) If I unplug and re-plug the CCP, while having the wiimote pointing towards me (meaning that the CCP completely "inherits" the control of the pointer) while the pointer (hand) is over a channel/option or whatever (as long as it displays its name) the pointer disappears and one can no longer have any control over anything (no home button function, no +/- etc) but it resolves after taking out the batteries and reinstalling them.
So yeah, it's not the same issue (in the issue I previously reported you could still see the hand, switch pages and basically select any channel one desires but it wouldn't load, no home menu, no nothing.) Could it be the same issue but applied differently since with an HDD connected it is trying to access the banners or whatever?
Could it be the #$$#%#$&%#&%$& HDD which *supposedly* worked 100% according to whoever decided to add it to the compatibility table? Could the HDD even cause that? I mean, the HDD light blinking would appear to be the loader trying to access the files, right?
At this point I don't know what else to do. Do you have any ideas? Could the banner cache be causing this? Should I leave it alone for more time (more than half an hour I mean)
Thanks and happy new year!

*EDIT*Apparently using the search option triggers the bug (sometimes). Does that help in any way?

 

[GreyWolf]

Can you change the view to list format? That *should* stop it from trying to fill the banner cache. It sounds like the UI thread is locking up to me, though.

 

[sideskroll]

Can you change the view to list format? That *should* stop it from trying to fill the banner cache. It sounds like the UI thread is locking up to me, though.

What about using search? Would that be cause by the cache as well?
BTW, did you get a chance to take a look at the error logs I sent you? (Regarding your GCN tool)
Thanks for replying!
Oh, and happy new year in case we don't get to talk before that!

 

[Clutz450]

The search feature has always cause slight freezing for me to the point that I don't use it anymore. But I have over 1,000 games. For example I want to play Mario Kart so I select M and it "freezes" for a while but then comes back. Then I pick A and again I have to wait. So it takes way longer for me to search for the game I want to play rather than just scroll through 1,000 plus games.

 

[sideskroll]

The search feature has always cause slight freezing for me to the point that I don't use it anymore. But I have over 1,000 games. For example I want to play Mario Kart so I select M and it "freezes" for a while but then comes back. Then I pick A and again I have to wait. So it takes way longer for me to search for the game I want to play rather than just scroll through 1,000 plus games.

Hi. Yeah but in my case at least (when it happens cause it doesnt happen every time) the lockup is permanent. And like I explained above. No freeze or dump. It just stays there and Im unable to load anything or pull up the home menu, settings. Whatever.
In your experience, how long should be long enougjt for the banners to load into cache? Im trying to discard possibilities one by one.

 

[Clutz450]

I've never had to wait 30 minutes like you. Even with over 1,000 games maybe 2 minutes was the longest I've had to wait when booting up USB Loader GX. Never timed it though so that 2 minutes us just a guess. But not long at all.

 

[Duncan Idaho]

Hmmm, @sideskroll do this, fetch first HDD sentinel (get the free version)

second, plug your HDD to the PC and let HDD sentinel give it a look, tell us about it's health, SMART, etc. It could be that the disk is dying or has a shitload of bad sectors., same to @Larsenv

 

[DonsSword]

You mean homebrew emulators? They don't have a title ID so they wouldn't show up on the game list or have an ID to get the art for them.

Forwarders for emulators should show cover art if there's an entry for their ID at GameTDB.com (ex: http://www.gametdb.com/Wii/DSNA)

I assumed they would, but I get nothing for these titles, even though I can find artwork in GameTDB.com.

Is there a custom edit I can make to the text files to force match the art to the files?

 

[sideskroll]

Hmmm, @sideskroll do this, fetch first HDD sentinel (get the free version)

second, plug your HDD to the PC and let HDD sentinel give it a look, tell us about it's health, SMART, etc. It could be that the disk is dying or has a shitload of bad sectors., same to @Larsenv

Hi.
Thanks for replying.
Unfortunately that has nothing to do with it. As I have 2 of the same units (both BRAND new, not even 2 weeks old) and both exhibit the same behavior (if the issue is in fact caused by the HDD)
Good thing (I guess you could call it good) is that at least its not a huge issue as it only seems to happen under specific circumstances and/or after doing something stupid like plugging and unplugging the controller while in the loader.