Unsolved

1 Rookie

 • 

13 Posts

2302

September 1st, 2020 07:00

17 R1, recently started to switch off for no reason

Couple of weeks ago I was playing and during the game laptop just turned off, without any signs of lag or any sounds. Just off as electricity was off and no battery inside (but it was inside). Then I was not able to turn it on, so I unplugged and plugged in the battery connector and after this it turned on. Same thing repeated after 20-30 minutes. Then I tried to work in it by removing battery. Same thing with shut down happened after 10-20 minutes of just showing me Desktop. I made all possible diagnostics of hardware and some showed me issues with battery. I purchased new one, today I tried to turn it on with new battery and same shut down happened when Windows was just loading. After this I can’t turn it on again. I don’t know what can it be, but definitely not a battery as I understand. What else I can do to find a problem? I am planning to visit repair shop, but I don’t wanna pay for diagnostics, I am a poor student.

Thanks in advance.

7 Practitioner

 • 

1.7K Posts

 • 

8.3K Points

September 1st, 2020 15:00

I'm having a similar issue with an M17x R4 that I have been working on. It will just hard shut down as though all power has been pulled. Unfortunately for me it seems that the motherboard has a power issue (probably in a MOSFET or capacitor) as I have swapped out every single part including using a different power adapter but it keeps doing it. It sounds a lot like your issue but hopefully it isn't.

Things you can try are - in no particular order

1. Remove all the RAM and try running on one stick at a time, in different RAM slots (there are 2 slots under the keyboard)

2. Remove the GPU and test (not possible if you have the 3D 120Hz display)

3. Try another power adapter if you can find a compatible one

4. Swap your main HDD/SSD over to the other drive bay

5. Repaste your CPU and GPU 

6. Try a power drain. Remove the power adapter, battery and RAM and hold the power button down for 60 seconds

 

Moderator

 • 

27.6K Posts

 • 

19 Points

September 2nd, 2020 01:00

We tried reaching you on a private message but did not receive a response. Please feel free to reply to the private message whenever you are available.

1 Rookie

 • 

13 Posts

September 2nd, 2020 02:00

I wasn’t able to find an original battery 2F8K3. So I had to buy it from amzn. I did a battery report with my old battery, and it showed that all OK, though Dell SupportAssist pointed that battery needs replacement. My laptop was always with plugged-in AC adaptor.

1 Rookie

 • 

13 Posts

September 2nd, 2020 02:00

Hi, thank you with advices. I tried numbers 5,6 already. 4 is not possible, but will try the rest.

9 Technologist

 • 

6.1K Posts

September 2nd, 2020 02:00

Hi @Sorpa  laptops are designed to shut off if not plugged into mains and battery power output drops below its battery use threshold. Please create a Win10 battery report to determine if the main battery is charging correctly. Check that the new main battery is a Dell replacement, it should say Dell on its label. Check that charger port inside laptop is not damaged. 

1 Rookie

 • 

13 Posts

September 2nd, 2020 06:00

@crimsom 

I somehow turned on laptop. So I performed Win10 battery report and don't see any issues there.

 

I tried to work without battery already and it shut down after 20 min approx. I am not sure if doing the same with a new battery would make any difference.

 

The event records shows only one critical error with code 41. Maybe that's the thing I should look for, didn't check it yet.

Thanks for trying to help me and your time

 

 

9 Technologist

 • 

6.1K Posts

September 2nd, 2020 06:00

Hi @Sorpa you did not mention conducting Win10 Battery Test on your new battery. There are reports of Dell laptops being very particular about what replacement battery it will work with.

Please disconnect the battery and connect the charger to see if 17 R1 shuts down on mains power. 

Use the Win10 Administrative Tools to see if there is a forced shutdown event recorded in Component Services and/or Computer Management. The event report should also tell you what triggered the shutdown. If it gives you an error code, search the internet for solution because Microsoft's error reporting text can be very obscure. 

9 Technologist

 • 

6.1K Posts

September 2nd, 2020 06:00

Hi @Sorpa please share an image of your code 41. Thanks. 

1 Rookie

 • 

13 Posts

September 2nd, 2020 07:00

@crimsom 

I am not sure if you meant to screenshot this part. I am not an advanced user, so I may misunderstand you. Also my system is in Russian, but I guess all look the same.

 

22222.png11111.png

9 Technologist

 • 

6.1K Posts

September 2nd, 2020 16:00

Hi @Sorpa  thank you for sharing the image of event 41. 

Event ID

Description

41

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

1074

Logged when an app (ex: Windows Update) causes the system to restart, or when a user initiates a restart or shutdown.

6006

Logged as a clean shutdown. It gives the message "The Event log service was stopped".

6008

Logged as a dirty shutdown. It gives the message "The previous system shutdown at time on date was unexpected".

 

The typical shutdown event IDs are 41, 1074, 6006, 6008. Win10 can search on these event IDs in the event viewer by selecting "Filter Current Log" in the drop down menu and search for 41, 1074, 6006, 6008. 

Your image says 0x8000400000000002 error code. Now try to fix what triggered the Kernel Power 41 Critical Error. The Steps to fix Kernel Power 41 error in Windows 10 are:-

Update your drivers
Disable duplicate audio drivers
Uninstall your antivirus
Change your power settings
Turn off Fast Startup
Update your BIOS
Check your hardware
Uninstall recent updates
Disable Auto-restart in the Advanced System settings 

9 Technologist

 • 

6.1K Posts

September 2nd, 2020 16:00

Hi @Sorpa  the quick and easy option is to rollback Win10 to a time that it was working. Have a look to see if Win10 created a system restore point that predates the 17 R1 switching off for no reason. 

This option takes your PC back to an earlier point in time, called a system restore point. Restore points are generated when you install a new app or driver, and when you create a restore point manually. Restoring won’t affect your personal files, but it will remove apps, drivers, and updates installed after the restore point was made.

  1. In the search box on the taskbar, type control panel, and then choose it from the list of results
  2. In the Control Panel search box, type recovery.
  3. Select Recovery > Open System Restore.
  4. In the Restore system files and setting box, select Next.
  5. Select the restore point that you want to use in the list of results, and then select Scan for affected programs.
  6. You'll see a list of items that will be deleted if you remove this restore point. If you're OK with the deletions, select Close> Next > Finish.

Notes

  • If you don’t see the restore point that you want to use, select the Show more restore points check box to see more restore points.
  • If you’re not seeing any restore points, it might be because system protection isn’t turned on. Here’s how to check:
    1. In the search box on the taskbar, type control panel, and then choose it from the list of results.
    2. In the Control Panel search box, type recovery.
    3. Select Recovery > Configure System Restore > Configure and see if the Turn on system protection option is selected.
      • If the Turn on system protection option is not selected, system protection isn’t turned on and there aren't any restore points. In this scenario, you won't be able to recovery your PC using a system restore point and will need to use one of the other recovery options. 
      • If the Turn on system protection option is selected, Win10 rollback should have fixed the problem. 

1 Rookie

 • 

13 Posts

September 3rd, 2020 02:00

@crimsom  Thank you very much for your efforts. I will try it out.

7 Practitioner

 • 

3.1K Posts

 • 

13.7K Points

September 4th, 2020 15:00

Also try using the sfc /scannow command to see if the system files are corrupt.

0 events found

No Events found!

Top