Atmosphere won't boot - Error code: 2101-0001 (0x265)

  • Thread starter Thread starter Symbitic
  • Start date Start date
  • Views Views 8,254
  • Replies Replies 14

Symbitic

Member
Newcomer
Joined
Apr 21, 2015
Messages
14
Reaction score
10
Trophies
0
Age
34
Location
Sterling, IL
Website
github.com
XP
129
Country
United States
My Switch won't boot. I woke it up earlier this morning, but before I could press the same button three times, it crashed to the Atmosphere BSoD.
When I tried launching EmuCFW from Hekate, it gives the blue screen with the following message:

Error code: 2101-0001 (0x265)

I tried backing up my existing atmosphere and bootloader dirs and reinstalling Atmosphere, Hekate, and sigpatches.
Now: When I launch CFW emuMMC from Hekate, the screen goes black and I think it powers off. When I launch CFW sysMMC or Stock sysMMC, it goes to the "Switch" boot logo, then freezes there.

Any idea what could be causing this?
 
what else does it say on the screen when it crashes, there should be another line that starts with program.
 
Iirc that error code is related to m92t36 power management ic. If you can't even boot ofw then it doesn't sound good.

Can you check the usb c port for bent pins? Also does it charge normally?
 
Iirc that error code is related to m92t36 power management ic. If you can't even boot ofw then it doesn't sound good.

Can you check the usb c port for bent pins? Also does it charge normally?
No bent pins I can see. Not charging. I recently had to take a Lenovo laptop in for repair because it too had stopped charging. It used the same USB-C charger.
 
Problem is the M92T36 Chip

This error code is generally caused by M92T36. 2101-0001 is an error on the i2c bus. This is a faulty M92 in MOST cases. There are cases where it can be something such as a faulty charging cable, excessive force, or accidental damage when inserting and removing the charging cable. It is not usually an error that will just occur on its own for no reason. Because this is a hardware-related (critical) error code, replacing components is your only option.
 
Not charging. I recently had to take a Lenovo laptop in for repair because it too had stopped charging. It used the same USB-C charger.
Likely the m92t36 was fried by the charger. Also don't use 3rd party chargers with switch.
 
If I'm reading it right, the max is 20V (3.25A)

Well there is your problem, the switch charge only supply 5v and 15v, so that why your chip blown, you supplied the wrong voltage.

If I'm reading it right, the max is 20V (3.25A)

Regarding your laptop, was this charger Lenovo brand?
 
Well there is your problem, the switch charge only supply 5v and 15v, so that why your chip blown, you supplied the wrong voltage.



Regarding your laptop, was this charger Lenovo brand?
No, it was third-party. That's my likliest suspect. The charger did say it could also do 15V, but I've stopped using the third-party one. The official Lenovo charger supports the same 65W and volt/amp ranges. Using the official Nintendo charger is problematic because the cord isn't long enough.
 
  • Like
Reactions: impeeza
Guess that, I am in a similar boat now. I had also used a third party USB C charger which was said to be compatible with Nintendo Switch.

But, I am experiencing the same errors and experience. I cannot boot into OFW.

And get the attached error when launching emunand CFW.

Does anyone have a solution for this??
 

Attachments

  • 7DA79791-FC86-4117-98D8-DC19696C5ED0.jpeg
    7DA79791-FC86-4117-98D8-DC19696C5ED0.jpeg
    1.4 MB · Views: 188

Site & Scene News

Popular threads in this forum