Nintendo Comments On 3DS Error Screen

I haven't had the screen yet. I always have Wi-Fi turned off, but I've played Monkey Ball, Rayman 3D and Rabbids 3D, so three "dangerous" titles, if I understand this correctly?
 
bigswords said:
Try it with Wifi off for Monkey Ball if you have the chance.

Monkey Ball is only about 3 hours long. It only crashed once in the time it took me to beat and I have no idea how I'd go about trying to replicate it to see if it's wifi causing the problem. The second time through the level it didn't lock up at all.
 
Saterium said:
Monkey Ball is only about 3 hours long. It only crashed once in the time it took me to beat and I have no idea how I'd go about trying to replicate it to see if it's wifi causing the problem. The second time through the level it didn't lock up at all.

Well only if you want to test it all the way through without wifi, I didn't know the game was so short. Or try out Ghost Recon that's a "dangerous' title. I turned wifi off (or sit infront of the router) and so far so good
 
Yoshi said:
I haven't had the screen yet. I always have Wi-Fi turned off, but I've played Monkey Ball, Rayman 3D and Rabbids 3D, so three "dangerous" titles, if I understand this correctly?

Yes, all is good then. You will need to turn on Wifi and have a connection setup where you at.

But I'm guessing it's due to weak wifi signalling or something like that.
 
drtomoe123 said:
You don't have a cracked hinge, you have one that is in the process of cracking. When the hinge actually cracks, the top screen flops around, you can't get it to stay in it's normal position, and then, worst case scenario, the top screen disconnects from the bottom part of the system.

Oh shit, I didn't know it was that bad! I thought everyone was just complaining about the cosmetic effect on the hinge... I guess mine didn't fully crack since I have stopped using it long ago and now I only turn it on briefly once in a blue moon.
 
Unless people here have been consistently getting errors, I'm talking over and over again not just a couple of times, testing with and without wifi is not going to prove anything. It could all just be coincidence, the same can be said for regarding a game as "dangerous" at this stage.
 
I can confirm you get errors even after the update and after not getting it for a few days, I got 2 back to back, wifi on.

1st time while playing Ghost Recon, 2nd time while in the Mii Maker or Mii Plaze right after the 1st crash.

I haven't gotten one since.
 
GJS said:
Unless people here have been consistently getting errors, I'm talking over and over again not just a couple of times, testing with and without wifi is not going to prove anything. It could all just be coincidence, the same can be said for regarding a game as "dangerous" at this stage.
I have yet to see anyone say that they had wi-fi turned off when getting the error; which suggests that the wi-fi chip/software is likely to be the culprit.
 
AndyMoogle said:
I have yet to see anyone say that they had wi-fi turned off when getting the error; which suggests that the wi-fi chip/software is likely to be the culprit.
It could also suggest that those who care enough to post online just haven't encountered the error with wifi off yet.

All these anecdotal posts are not conclusive evidence of anything, take me for example; I've experienced the error only once on the first day I got the 3DS(24th) and have not replicated it since yet my usage has not changed.

It is too early at this stage to be deciding what the cause is until people start exclusively testing the units over a longer period trying to replicate it, there might not even be a single root cause.
 
GJS said:
It could also suggest that those who care enough to post online just haven't encountered the error with wifi off yet.

All these anecdotal posts are not conclusive evidence of anything, take me for example; I've experienced the error only once on the first day I got the 3DS(24th) and have not replicated it since yet my usage has not changed.

It is too early at this stage to be deciding what the cause is until people start exclusively testing the units over a longer period trying to replicate it, there might not even be a single root cause.
This is obviously no proof, but until I see someone saying that they got the error when the wi-fi was turned off, I'm going to consider it very likely that the wi-fi is somehow part of the problem.
 
Got the error while playing Ghost Recon. Wifi was on and I was putting the 3ds in and out of sleep mode a couple of times before that.
 
The only error I've had with my 3DS is the other day my 3DS wouldn't connect online. Also, when loading the home menu, if the wireless switch was on, the lower screen was s tuck on a Home splash screen of some sort. It would stay on that screen until I turned off the wireless. The home menu would then load, and i could re-activate wireless, but still could'nt get online.

The issue didn't fix when I deleted and re-entered the connection settings in my 3DS, but it did stop when I restarted my router. It's almost like the 3DS and my router were stuck in the handshake offering phase.
 
the two times i got the error was with wifi on, but i was sat within a few feet of my router... so... go them back to back launching the same game (rayman) haven't had any problems other than that.
 
I've had the error pop three times on Ghost Recon, nothing on Pilot Wings, Steel Diver, or SSFIV, but then Ghost Recon has been taking up the bulk of my time. Wifi was on for all three instances. May not be definitive, but I guess I'll try playing with Wifi off for the foreseeable future and see what happens.
 
GJS said:
It could also suggest that those who care enough to post online just haven't encountered the error with wifi off yet.

All these anecdotal posts are not conclusive evidence of anything, take me for example; I've experienced the error only once on the first day I got the 3DS(24th) and have not replicated it since yet my usage has not changed.

It is too early at this stage to be deciding what the cause is until people start exclusively testing the units over a longer period trying to replicate it, there might not even be a single root cause.

I agree, but as AndyMoogle replied, the wifi looks like the most likely suspect. It may not fix everyone's problem. But at least we are narrowing it down.
 
Day 5 of owning it. It's never been off (except to put stuff on the SD card) and Wifi has always been on.
No error screens yet.
I wonder if some of the WiFi cards are faulty or if it's actually people's routers sending signals the 3DS can't handle?
 
AceBandage said:
Day 5 of owning it. It's never been off (except to put stuff on the SD card) and Wifi has always been on.
No error screens yet.
I wonder if some of the WiFi cards are faulty or if it's actually people's routers sending signals the 3DS can't handle?

I do hope it's the latter and it's the routers are at fault.
 
I got this again earlier. I had just got 10 Wanderes for the quest and as soon as I hit 'Venture forth' got the error screen. Pissed me off because I lost all those guys (20 coins worth)
 
I got the screen of death while playing Ghost Recon last night. This the second time this happened.
 
Got the black screen 3 times today while playing ghost recon w/ wifi on. Turned wifi off and no black screen yet. I also have pilotwings and steel diver, no black screens there.
 
I have had 3 errors with my 3DS this week since thursday (Aus launch unit)

All errors have been post-update
All errors during Ghost Recon or on the home menu shortly after

1 error was when both screens faded to black and system required a hard reset
The other 2 errors were system lockups and also needed hard reset

Not sure why, havent been able to replicate it but havent had as much time with my other games yet (Ridge and PES).

Oh and also had a crash on the friend list section when deleting a request.
 
No errors yet, but I've only been playing Pokemon White on it.
Wifi is turned off. I played a few of the included mini games once or twice, but for about 5 minutes.
I don't have any 3DS games yet, I only got the system to replace my old DS Tank until some games I want are released.
 
I got my first and only BSOD today after taking several pictures and being haphazard with sleep mode and suspend software. (edit - long after my launch day update)
 
angelfly said:
Out of curiosity is this happening at all on JP systems? It was out a month earlier in Japan but so far I haven't seen any complaints but on day one for EU and NA this pops up. Although Ghost Recon hasn't been released there yet Monkey Ball came out shortly after launch.

Not seen any mention of it in Japan, no. Anyone else?

(Brief search of JP game sites has lots of references to 'overseas 3DS Black Screen of Death' but nothing about it happening on domestic units)

I wonder if it's to do with certain western routers. Although it seems like a very severe reaction to be something so superficial.

I guess we'll find out in time.
 
So, I was using my Wii to download the Okamiden demo onto the 3DS, and the Nintendo Channels wouldn't load.
And I remembered, this happened a lot when it was hooked up to the internet, where channels would just sit at a black screen forever.
So, yeah, I'm definitely thinking it's something to do with routers. Hasn't effected my 3DS yet, but my Wii got it every now and then, even when loading up a game.
 
Got my second one playing ghost recon this morning. Got one yesterday playing ghost recon. wifi was on and I hadn't turned it off since I got the error yesterday.
 
It's happened to me many times playing Ghost Recon. Wifi on.

It's not that bad for GR considering I save the game often.

However it'll suck if Zelda OoT has not quick save and I lose my progress.

Should I look to replacing mine or just wait for Nintendo to patch it out?
 
robut said:
It's happened to me many times playing Ghost Recon. Wifi on.

It's not that bad for GR considering I save the game often.

However it'll suck if Zelda OoT has not quick save and I lose my progress.

Should I look to replacing mine or just wait for Nintendo to patch it out?

Chances are any unit they give you will suffer from the same problem. And like some said it seems mostly connected to wifi and Ghost Recon/Monkeyball.
 
AceBandage said:
So, I was using my Wii to download the Okamiden demo onto the 3DS, and the Nintendo Channels wouldn't load.
And I remembered, this happened a lot when it was hooked up to the internet, where channels would just sit at a black screen forever.
So, yeah, I'm definitely thinking it's something to do with routers. Hasn't effected my 3DS yet, but my Wii got it every now and then, even when loading up a game.
My Wii used to shut down the internet in my entire house when I used it online. I had to powercycle my router to get it working again. Maybe this is related.
 
robut said:
It's happened to me many times playing Ghost Recon. Wifi on.

It's not that bad for GR considering I save the game often.

However it'll suck if Zelda OoT has not quick save and I lose my progress.

Should I look to replacing mine or just wait for Nintendo to patch it out?
Turn off the wi-fi while playing single player games.
 
richiek said:
I got the screen of death while playing Ghost Recon last night. This the second time this happened.

Try turning your wifi off and see whether this helps it, I'm at Chapter 7 with no crashes and my wifi is off.

@heringer

Formatting the SD card to FAT 32 , helped some people who are having just black screens (no error messages of any sort) when the system is turned on. A different issue altogether.
 
RandomVince said:
I have had 3 errors with my 3DS this week since thursday (Aus launch unit)

All errors have been post-update
All errors during Ghost Recon or on the home menu shortly after

1 error was when both screens faded to black and system required a hard reset
The other 2 errors were system lockups and also needed hard reset

Not sure why, havent been able to replicate it but havent had as much time with my other games yet (Ridge and PES).

Oh and also had a crash on the friend list section when deleting a request.

Is your wifi on by any chance while playing games? If you need to use the online functionality go closer to your router or manually configure your ip address and dns address.
 
bigswords said:
Is your wifi on by any chance? If you need to use the online functionality go closer to your router or manually configure your ip address and dns address.

Yes my wifi has been on all the time. Ive read this thread since posting above a number of times, but didnt think to report back. Ill see how it goes with wifi off for the next week.
 
This isn't really the right topic for it I guess, but I'm having a lot of crashes with LEGO StarWars on 3DS. The screen just turns black, with no error message. It happens during loading between acts or when loading a savegame. Fortunately it hasn't corrupted my savegame yet, that'll happen when I almost finish the game I think.

Are more people experiencing these problems? I had one error-message during Monkey Ball, but Pilotwings and SFIV are error-free.
 
RandomVince said:
Yes my wifi has been on all the time. Ive read this thread since posting above a number of times, but didnt think to report back. Ill see how it goes with wifi off for the next week.

Cool and thanks, update when you can. Also try to manually configure your ip address and dns server if you need to use the online stuff.

Sigh I wished Nintendo had a error message "you internetz has failed" or something like that, this generic message just makes people uneasy.
 
Notorious_Roy said:
This isn't really the right topic for it I guess, but I'm having a lot of crashes with LEGO StarWars on 3DS. The screen just turns black, with no error message. It happens during loading between acts or when loading a savegame. Fortunately it hasn't corrupted my savegame yet, that'll happen when I almost finish the game I think.

Are more people experiencing these problems? I had one error-message during Monkey Ball, but Pilotwings and SFIV are error-free.


Try turning off wifi and playing your 3DS without the SD card.

If turning off wifi works , then put back the SD card

If you are still getting crashes then copy the Nintendo folder out and reformat the SD card to FAT 32. And copy the folder back.

Does your AR games and face raider and cameras all ok?
 
sonikokaruto said:
i've been playing street fighter 4 online for the whole week, no screen.


maybe it's just that ghost recon is shitty rushed code?


Could be, but I have been playing Ghost Recon for 18 hours and no crashes so far, this is with my wifi off. Hopefully theres a firmware update that either changes the error message or fix this weird issue
 
Kevitivity said:
I paid $18 today @ Amazon...

Looks like I have to send my 3DS in as well as I'm getting the BSoD error... :(

Is your wifi on by any chance? Try turning it off first to see whether you are still getting the bsod error.
 
Cat in the Hat said:
This is usually the way to go with every console launch ever.
My first 360 and ps3 still work fine, as does my snes, ps2, dreamcast, n64, gamecube, wii and various handhelds.

It's inevitable that systems will break it doesn't matter what version of the system it is, slim 360s break, slim ps3s break etc.
 
Kryptonic said:
Just reporting that I haven't had anymore black screen errors since turning my wifi off in ghost recon.

Thanks :) Are you usually far away from your router when you play with your 3DS?
 
Wow, interesting error, haven't come across it. I don't own the two games that seem to be causing this but I've had nothing here outside of a small OS freeze. Basically it didn't seem to recognize any DS carts I was using so I just powered the machine down. When I turned it back on no problems, worked with every DS (domestic & import) and 3DS game I had on me.
 
I've just gotten the error for the first time tonight playing Ghost Recon with the wifi on. I was mid mission and lost all my progress in that mission, argh. Remind me to save more often or turn the wifi off.
 
So, I guess we have a strong suspect. I have Ridge Racer and not a single lockup or BSOD. I always play with wifi ON. Heck, in fact I think I have never turned it off.
 
Top Bottom