Reply to thread
GBAtemp.net - The Independent Video Game Community
Search
Search titles only
By:
Search titles only
By:
Reply to thread
GBAtemp.net - The Independent Video Game Community
Home
Log in
Terms & Rules
Donate
Forums
New posts
Search forums
Groups
Public Events
New
New posts
New resources
New blog entries
New profile posts
New blog entry comments
New threadmarks
Latest activity
Cheats
Cheat Codes Add and Request group
The Legend of Zelda: Tears of the Kingdom cheat codes
Pokémon Legends: Arceus cheat codes
Xenoblade Chronicles 3 cheat codes
Fire Emblem Engage cheat codes
Request a cheat...
Tutorials
Nintendo Switch tutorials
Nintendo 3DS tutorials
Nintendo Wii U tutorials
Reviews
Overview
Official reviews
User reviews
Downloads
Latest reviews
Search resources
Blogs
New entries
New comments
Blog list
Search blogs
Chat
Top chatters
Search
Search titles only
By:
Search titles only
By:
Log in
Register
New posts
Search forums
Log in
Register
Home
Forums
PC, Console & Handheld Discussions
Nintendo Wii U
How I fixed 160-0103 system memory error
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="SDIO" data-source="post: 10094858" data-attributes="member: 636278"><p>After I flashed back the SLC and it began working again with the 32GB card, I put the 64GB card back and it still didn't work. When I looked at the logic analyzer I saw that the Wii U gave up after querying the status, it didn't even attempt a read from the SDXC card, so it doesn't matter what was on it.</p><p>The strange thing is, the SDXC card is working fine in the normal SD Slot of the Wii U, so the Cafe OS should be able to handle it.</p><p></p><p></p><p>Nintendo used different eMMC chios from different Vendors. My failed eMMC is a Hynix H26M64002BNR 228A.They probably had a bad batch or something together with the Cafe OS, wich seems to be write heavy (because it is also known for killing USB sticks) it was just a bad combination in my case. Also the Wii U was unused for many years. Flash can also loose it's content over time just sitting there.</p><p>I assume the reason I didn't see a performance difference is the SLC cache doing it's job. With redNAND you don't have the SLC cache.</p><p>I would also assume eMMC should be better in general. But here it seems to really be a bad batch of eMMC chips. Also a current SD card from a good brand should last for some time. I am using a Sandisk, but that's just my personal preference as I will never trust Samsung again with anything containing flash (They are also known for many eMMC bugs, like on the Galays S2 and S3 and Nexus 7 and also the 840 Evo (which I own one) has a few known problems). So it's Sandisk for me, never had problems with them. But I also had a HTC HD2, where I was running Android from an Samsung SD card for a long time. Back then I never had Problems with the SD card. But it is the same SD card I used for the comparison. When I made an Backup of the old card before overwriting it with the Wii U MLC I also saw some bit rod there (some blocks needed a few attemps, but it seems the controller was able to correct them finally). Or maybe the contacts where just oxidized and reinserting it a few time scratected them clean...</p><p></p><p>Yes, but it's not only affecting old SSDs. I would even assume old SLC SSDs are more robust. It is a general problem of flash and it only get's worse the finer the structures get and the more bits you have in a cell. Over time the electrons are migrating out of the Gate in the flash cell, The question is just how long it take till enough cells are corrupted so the ECC can't fix it. It also can happen to BIOS chips (butnot as often, as they are not pushing the limits) and SD cards, CF Cards and the SSD in your computer. Depending on how smart the controller is, it might not be doing a scrub on it's own and only detects errors when reading. I would add to your suggestion, that in addition to powering on it's also a good Idea to do a NAND backup, so every block gets read and the controller can detect the error, while it's still correctable.</p><p></p><p></p><p>Yes in my case it was a Hynix.</p><p>I am not sure what caused my emmc to fail completely over time, if it was bitrod over time or if the cells died from too much writing, so it was running out of reserve blocks. Maybe it was also a combination of the two.</p><p>In this German Forum (you don't need to understand the text, just look at the pictures), where I first described the Problem the user nino postet a picture on how to connect the pins: <a href="https://forum.wii-homebrew.com/index.php/Thread/59635-Brick-nach-Speicherfehler/?postID=715489#post715489" target="_blank">https://forum.wii-homebrew.com/index.php/Thread/59635-Brick-nach-Speicherfehler/?postID=715489#post715489</a> I don't want to repost it because of copyright. The only thing I would different is cutting the clk trace between the pads and then tie the clk on the emmc side to GND. Also having the pad there gives you the chance to reconnect the emmc if you ever want to.</p><p></p><p></p><p>Good to know, I also only knew the method of looking at the size. I guess I have to see what this tool has to say about my SD Card.</p><p></p><p></p><p>Maybe. From what I know the Wii U writes cheap usb sticks to death when launching games from them. So that would indicate that you would move wear from the eMMC to the USB device. It would be interesting to see what is causing the writes. Maybe someone who knows more about the Firmware could insert some debug code to log all writes to serial or something like that.</p><p></p><p></p><p>When I scrolled through my NAND dump in a hex editor, it doesn't seem like the Wii U is discarding unsued blocks. So from the perspective of the eMMC everything, except some blocks at the end are used. But it was really just a very quick look and I was mostly interested in the part, that didn't fit on the SD card.</p><p>Maybe I will take a look again, but not today.</p><p></p><p>To add a little to your answer: it seemed that in my case the FTL got corrupted and running the discard allowed the eMMC to clear and rebuild the FTL. Also it could be possible that the eMMC is returning I/O errors if it is degraded to much. Mine didn't (but it should have instead of returning random data). When you rewrite the eMMC the I/O errors are gone, which might help IOSU not crashing (but it also could make it worse).</p><p></p><p>I also saw a few videos from Voultar, maybe I should try to contact him.</p><p></p><p></p><p></p><p>I just use dd for my USB stick. But that would also save the unused space, which isn't much in my case. Together with the otp.bin and the seeprom.bin you can also extract it in the PC and copy it back over FTPiiU (but it takes a long time). I had to do this, because I did a Factory Reset at some point, which changed the USB key in the seeprom and I am to afraid of bricking to write the old seeprom back.</p><p></p><p>I now bought a broken Wii U from ebay. The seller said it just died, which also seems to be a common problem. Maybe I can figure something out. May 'hopeÄ is that it is also the MLC, but I think thats unlikely.</p></blockquote><p></p>
[QUOTE="SDIO, post: 10094858, member: 636278"] After I flashed back the SLC and it began working again with the 32GB card, I put the 64GB card back and it still didn't work. When I looked at the logic analyzer I saw that the Wii U gave up after querying the status, it didn't even attempt a read from the SDXC card, so it doesn't matter what was on it. The strange thing is, the SDXC card is working fine in the normal SD Slot of the Wii U, so the Cafe OS should be able to handle it. Nintendo used different eMMC chios from different Vendors. My failed eMMC is a Hynix H26M64002BNR 228A.They probably had a bad batch or something together with the Cafe OS, wich seems to be write heavy (because it is also known for killing USB sticks) it was just a bad combination in my case. Also the Wii U was unused for many years. Flash can also loose it's content over time just sitting there. I assume the reason I didn't see a performance difference is the SLC cache doing it's job. With redNAND you don't have the SLC cache. I would also assume eMMC should be better in general. But here it seems to really be a bad batch of eMMC chips. Also a current SD card from a good brand should last for some time. I am using a Sandisk, but that's just my personal preference as I will never trust Samsung again with anything containing flash (They are also known for many eMMC bugs, like on the Galays S2 and S3 and Nexus 7 and also the 840 Evo (which I own one) has a few known problems). So it's Sandisk for me, never had problems with them. But I also had a HTC HD2, where I was running Android from an Samsung SD card for a long time. Back then I never had Problems with the SD card. But it is the same SD card I used for the comparison. When I made an Backup of the old card before overwriting it with the Wii U MLC I also saw some bit rod there (some blocks needed a few attemps, but it seems the controller was able to correct them finally). Or maybe the contacts where just oxidized and reinserting it a few time scratected them clean... Yes, but it's not only affecting old SSDs. I would even assume old SLC SSDs are more robust. It is a general problem of flash and it only get's worse the finer the structures get and the more bits you have in a cell. Over time the electrons are migrating out of the Gate in the flash cell, The question is just how long it take till enough cells are corrupted so the ECC can't fix it. It also can happen to BIOS chips (butnot as often, as they are not pushing the limits) and SD cards, CF Cards and the SSD in your computer. Depending on how smart the controller is, it might not be doing a scrub on it's own and only detects errors when reading. I would add to your suggestion, that in addition to powering on it's also a good Idea to do a NAND backup, so every block gets read and the controller can detect the error, while it's still correctable. Yes in my case it was a Hynix. I am not sure what caused my emmc to fail completely over time, if it was bitrod over time or if the cells died from too much writing, so it was running out of reserve blocks. Maybe it was also a combination of the two. In this German Forum (you don't need to understand the text, just look at the pictures), where I first described the Problem the user nino postet a picture on how to connect the pins: [URL]https://forum.wii-homebrew.com/index.php/Thread/59635-Brick-nach-Speicherfehler/?postID=715489#post715489[/URL] I don't want to repost it because of copyright. The only thing I would different is cutting the clk trace between the pads and then tie the clk on the emmc side to GND. Also having the pad there gives you the chance to reconnect the emmc if you ever want to. Good to know, I also only knew the method of looking at the size. I guess I have to see what this tool has to say about my SD Card. Maybe. From what I know the Wii U writes cheap usb sticks to death when launching games from them. So that would indicate that you would move wear from the eMMC to the USB device. It would be interesting to see what is causing the writes. Maybe someone who knows more about the Firmware could insert some debug code to log all writes to serial or something like that. When I scrolled through my NAND dump in a hex editor, it doesn't seem like the Wii U is discarding unsued blocks. So from the perspective of the eMMC everything, except some blocks at the end are used. But it was really just a very quick look and I was mostly interested in the part, that didn't fit on the SD card. Maybe I will take a look again, but not today. To add a little to your answer: it seemed that in my case the FTL got corrupted and running the discard allowed the eMMC to clear and rebuild the FTL. Also it could be possible that the eMMC is returning I/O errors if it is degraded to much. Mine didn't (but it should have instead of returning random data). When you rewrite the eMMC the I/O errors are gone, which might help IOSU not crashing (but it also could make it worse). I also saw a few videos from Voultar, maybe I should try to contact him. I just use dd for my USB stick. But that would also save the unused space, which isn't much in my case. Together with the otp.bin and the seeprom.bin you can also extract it in the PC and copy it back over FTPiiU (but it takes a long time). I had to do this, because I did a Factory Reset at some point, which changed the USB key in the seeprom and I am to afraid of bricking to write the old seeprom back. I now bought a broken Wii U from ebay. The seller said it just died, which also seems to be a common problem. Maybe I can figure something out. May 'hopeÄ is that it is also the MLC, but I think thats unlikely. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
PC, Console & Handheld Discussions
Nintendo Wii U
How I fixed 160-0103 system memory error
General chit-chat
Help
Users
Settings
Notifications
Miscellaneous
Inverse message direction
Display editor on top
Enable maximized mode
Display images as links
Hide bot messages
Hide statuses
Hide chatter list
Show messages from ignored users
Temporarily disable chat
Receive mention alerts
Sound notifications
Normal messages
Private messages
Whisper messages
Mention messages
Bot messages
Desktop notifications
Normal messages
Private messages
Whisper messages
Mention messages
Bot messages
Options
Options
View top chatters
Xdqwerty
Loading…
what are you looking at?
K3Nv2
Loading…
BigOnYa
Loading…
@
wiihackZlol
:
hey anyone here?
Yesterday at 10:46 PM
@
PandaPandel
:
heyo
Yesterday at 10:59 PM
@
K3Nv2
:
Wii experts at your service we can Abracadaba anything made by Nintendo for your piracy needs
+1
Yesterday at 11:02 PM
@
Psionic Roshambo
:
Now your playing with power!
+1
Yesterday at 11:03 PM
@
K3Nv2
:
Guys five unmarked black vans with red letters just pulled up at my house
Yesterday at 11:07 PM
@
BigOnYa
:
Ancientboi called FBI on you. You better flush your stash.
Yesterday at 11:08 PM
S
@
salazarcosplay
:
how are you
@BigOnYa
Yesterday at 11:10 PM
@
BigOnYa
:
Good, been lazy. Been inside playing games for last few days, too hot outside, was 97 degrees F today. It was so hot outside, I seen a dog chasing a cat, and they both were walking.
Yesterday at 11:12 PM
S
@
salazarcosplay
:
@BigOnYa
which games?
Yesterday at 11:13 PM
@
BigOnYa
:
Fallout4, pubg, Starfield, Forza, Still wakes the Deep, just to name a few
Yesterday at 11:16 PM
@
K3Nv2
:
It's just ancientboi left me his laptop
+1
58 minutes ago
@
BigOnYa
:
Who are/ were they?
54 minutes ago
@
K3Nv2
:
Some Nintendo execs wanted to give him a promotion
51 minutes ago
@
Sicklyboy
:
party van
+1
49 minutes ago
@
K3Nv2
:
Get in the van
46 minutes ago
@
Sicklyboy
:
5 day weekend starts now
+1
46 minutes ago
@
Sicklyboy
:
Have off tomorrow for Juneteenth, then took thursday and Friday off to make the most out of the mid-week day off lol
46 minutes ago
@
K3Nv2
:
5 days of straight fap
+1
46 minutes ago
@
Sicklyboy
:
enter the goon cave
45 minutes ago
@
K3Nv2
:
Ancientboi likes the goonies
45 minutes ago
@
BigOnYa
:
Good week to take time off, so damn hot! You can catch up on some gaming While staying in the AC, or do like ken does, fap all week.
44 minutes ago
@
Xdqwerty
:
im back
18 minutes ago
@
BigOnYa
:
The wut boy is back.... and you know he can never be whack.
+1
12 minutes ago
@
K3Nv2
:
How dare you say wut hell yawn you into a lawsuit
+2
10 minutes ago
@
Xdqwerty
:
@K3Nv2
, what
2 minutes ago
Submit
@
Xdqwerty
:
@K3Nv2, what
2 minutes ago
Chat
3