Anthony N Well-known member Joined Jun 13, 2012 Posts 619 Location Michigan, USA Jul 31, 2015 #1 So I get this odd error from my laptop when I turn it on. Any ideas? I've tried multiple restarts with no avail.
So I get this odd error from my laptop when I turn it on. Any ideas? I've tried multiple restarts with no avail.
cluberti Senior Member Staff member Joined Mar 2, 2012 Posts 443 Location Redmond Jul 31, 2015 #2 Does it leave any traces of it happening in the Application event log?
Anthony N Well-known member Joined Jun 13, 2012 Posts 619 Location Michigan, USA Jul 31, 2015 #3 Can you point me in the direction to find that? Also I did a system restore that made the critical error stop but it has made my computer extremely slow and unresponsive.
Can you point me in the direction to find that? Also I did a system restore that made the critical error stop but it has made my computer extremely slow and unresponsive.
cluberti Senior Member Staff member Joined Mar 2, 2012 Posts 443 Location Redmond Jul 31, 2015 #4 The event viewer is where the event logs are. Windows dialog box errors are now pretty "user friendly", but that also means they lack a lot of data that would be useful in troubleshooting. That data mostly goes into the event viewer logs now.
The event viewer is where the event logs are. Windows dialog box errors are now pretty "user friendly", but that also means they lack a lot of data that would be useful in troubleshooting. That data mostly goes into the event viewer logs now.
Anthony N Well-known member Joined Jun 13, 2012 Posts 619 Location Michigan, USA Aug 1, 2015 #5 No traces of anything but a system restore seems to have fixed things up. Seems to have been a driver at fault, I'm still trying to figure out why it's so sluggish yet and I have to get my "n" key replaced.
No traces of anything but a system restore seems to have fixed things up. Seems to have been a driver at fault, I'm still trying to figure out why it's so sluggish yet and I have to get my "n" key replaced.
Maximum Well-known member Joined Jul 30, 2015 Posts 55 Location United States Aug 2, 2015 #6 After doing some research I have found numerous people have been having the same issue as you are (specifically with an upgrade from Windows 8.1 to 10) there are workarounds but it seems like the error keeps coming back after a restart or two. You can try one of these: #1 - Run the 'System File Checker': System file check (SFC) Scan and Repair System Files - Microsoft Community #2: - Create a local admin account, login with it, and remove the old account from the system. If neither of those fixes your issue I suggest writing down your key and doing a clean installation of Windows 10. EDIT: Just realized you fixed the issue, as for it being slugish you can check out this if you'd like - Windows 10: How to fix slow boot-up issues after free upgrade
After doing some research I have found numerous people have been having the same issue as you are (specifically with an upgrade from Windows 8.1 to 10) there are workarounds but it seems like the error keeps coming back after a restart or two. You can try one of these: #1 - Run the 'System File Checker': System file check (SFC) Scan and Repair System Files - Microsoft Community #2: - Create a local admin account, login with it, and remove the old account from the system. If neither of those fixes your issue I suggest writing down your key and doing a clean installation of Windows 10. EDIT: Just realized you fixed the issue, as for it being slugish you can check out this if you'd like - Windows 10: How to fix slow boot-up issues after free upgrade
Anthony N Well-known member Joined Jun 13, 2012 Posts 619 Location Michigan, USA Aug 2, 2015 #7 Thanks maximum, but it's pretty much fixed now it was driver incompatibility. Alls good now
Maximum Well-known member Joined Jul 30, 2015 Posts 55 Location United States Aug 2, 2015 #8 Yeah I noticed that, I accidentally over looked your other post on this thread. Glad its fixed now :)
Yeah I noticed that, I accidentally over looked your other post on this thread. Glad its fixed now :)