09-13-2011 04:56 AM - edited 09-13-2011 04:57 AM
I have just bought a new Edge E420.
Recently it has been shutting down with no warning at all. There is no BSOD, no memory dump (although that is because i have not enabled it) and no noticeable pattern.
I have checked event viewer, and sure enough there are several critical errors, all of them being this:
Critical ERROR ID: 41. Kernel Power Task 63.
"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
It's interesting though, as the laptop never reboots. It just simply shuts down with no warning.
I'm beginning to think it's either a driver conflict or a thermal problem, as the system does get noticeably warm after very little use.
I have installed SpeedFan, and the program reports both physical cores sitting at around 59 degrees celcius.
I'm not sure where to go with this. I've reinstalled a fresh copy of Windows 7 Home Premium, and have installed all the required drivers (up to date) though the issue still persists.
10-26-2011 02:13 PM
Same problem here. Couldn't get it to turn back on without unplugging, removing battery, replacing battery, turning back on with battery power.
Now it won't turn back on at all. RIP Lenovo Thinkpad E420, at 4 months.
10-27-2011 02:03 AM
Check out the Community Knowledge Base for hints and tips.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
W520 | 4176-38U | i7 - 2720QM | Quardo 1000M | 8GB RAM | 60GB OCZ Agility 3
05-09-2012 02:24 AM
Hi all, Base on what i gather from the forum here, Best is to start with updating the bios and powermanagement software from lenovo. Its very hard to determind at this point on where the issue may lie. As Jamez Had suggested earlier it would be worth while to to remove any third party ram that has been installed as there are times an incompatible ram could have been inserted that causes the failure.
In the mean time try with the updated and do let me know how it goes. I speak to the respective teams to check what the cause is.