My computer shuts down by itself after upgrading

Toggle sidebar Toggle sidebar
T

TheKirk

Distinguished
Mar 10, 2011
46
0
18,530
Hi there.

I recently upgraded from Windows 7 to 8 on my ~6 months old Asus Zenbook UX31E.
I have two main problems after the upgrade:


- Computer shuts down by itself for no particular reason, and with no warning whatsoever.
- It gets quite hot wether I'm sitting with it on my lap or on a table even though I'm just browsing in chrome or doing some other simple task.

I really don't have any clue why, other than it might be because of the heat. The computer did get hot while running Windows 7 too, though, but it never shut down like this before.

I'm not sure if this has to do with anything, but I didn't do a full-automatic upgrade - That is, I didn't keep any of my old Windows 7 settings. This is because I was experiencing some performance issues before upgrading (computer was running slow at times), and I wanted to do a hard reset. This meant that I had to install some of the drivers manually (touchpad, bluetooth etc.).


I hope you'll be able to help me.
 
Sort by date Sort by votes
cool, listen to your computers sound while on battery. Listen to the sound of the fans.
Now plug in AC power and see if the computer is making more sound. I guess that they have software controlled fan speed and the fan is at full speed under AC power and partial speed under battery (or no speed under battery power:BUG)

if this is the case: go to control panel, look for sleep options. compare options for while it is under AC power to the ones for under battery power. In particular you are looking for a option that controls fan speed. I would guess the battery power fan speed is set too low or off.

edit: I looked on my old laptop and found the setting for win7

look in your power options in control panel, under advanced settings
processor power management-> System Cooling policy
it indicates Plugged in: active
and On battery: Passive

you could try changing the passive to active and see if that does the trick.
 
Upvote 0 Downvote


Bummer, well ASUS has rolled out a bunch of new BIOS updates and updated drivers for in the last month for windows 8 upgrade issues. I would use their BIOS update program and flash the current BIOS v 214 dated 10/16/2012
changes are not listed very well just as Firmware updates.

-You could boot into the BIOS screen on battery power and leave it there to see if that overheats. Then you would know it is not the OS.

The ACPI settings from the BIOS ACPI table will must be wrong somewhere or Windows 8 is reading them incorrectly.
A BIOS update will refresh that table.

-It could also be a failure to load one of the device drivers that the OS uses to control the hardware. Start device manager and look for a driver that did not load. Maybe something like SMBus

if the device driver did not load, then it can not control your system correctly.
 
Upvote 0 Downvote
-Does ASUS have any tools that will allow power management control? Do they work?

-Are there settings in the BIOS that override the control or change the ACPI table version? Is there a menu in the BIOS that will show fan speed or various temps of components? Are they working?

- driver/ binary mismatch between 32bit and 64 bit?
- failure of a device on your SMbus, could mess up the control
- or just a bug, in which case ASUS support will be getting a lot of calls by now.

update intel chipset drivers from the intel site ?


don't know what to tell you. I would hit ASUS and Microsoft support up next.

EDIT:
The more I think about it boils down to this: ASUS BIOS is providing false information to the OS.
I would suspect you would only get this if you did a upgrade that included a format of your drive.

-A non format upgrade most likely has a complete set of ASUS drivers for your machine.
-A formatted version of the upgrade will have a mixture of Microsoft generic drivers, the ASUS generic drivers they gave to Microsoft (but not the custom ASUS drivers for your device)
Then it would have any updated drivers you downloaded from the ASUS site.

basically with a mismatch the OS uses the standard meaning of tables to control the power management and has no idea that the table is being incorrectly mapped.

kind of sucks: I would look to ASUS to get this fixed. Not a fun process
 
Upvote 0 Downvote
here is a powershell script to dump the table that your BIOS is handing to the OS. Start Windows powershell ISE
(powershell_ise) as a admin and cut and run these three lines below:


$thelist = get-wmiobject -class Win32_BIOS
foreach ($objItem in $thelist) { write-host "Supported: " $objItem.BiosCharacteristics}
Get-WmiObject win32_bios | Select-Object *


take the output and post the results.

I think any BiosCharacteristic numbered 0-39 are standard, 40-47 are for BIOS vendors
48-63 are for System vendors

 
Upvote 0 Downvote
PS C:\Users\Joseph> $thelist = get-wmiobject -class Win32_BIOS

PS C:\Users\Joseph> foreach ($objItem in $thelist) { write-host "Supported: " $objItem.BiosCharacteristics}
Supported: 7 11 12 15 16 19 23 24 25 26 27 28 29 32 33 39 40 42 50 57 58 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79

PS C:\Users\Joseph> Get-WmiObject win32_bios | Select-Object *


PSComputerName : WORK
Status : OK
Name : BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03
Caption : BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03
SMBIOSPresent : True
__GENUS : 2
__CLASS : Win32_BIOS
__SUPERCLASS : CIM_BIOSElement
__DYNASTY : CIM_ManagedSystemElement
__RELPATH : Win32_BIOS.Name="BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03",SoftwareElementID="BIOS Date: 08/14/12 17:46:21 Ver:
04.06.03",SoftwareElementState=3,TargetOperatingSystem=0,Version="_ASUS_ - 6222004"
__PROPERTY_COUNT : 27
__DERIVATION : {CIM_BIOSElement, CIM_SoftwareElement, CIM_LogicalElement, CIM_ManagedSystemElement}
__SERVER : WORK
__NAMESPACE : root\cimv2
__PATH : \\WORK\root\cimv2:Win32_BIOS.Name="BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03",SoftwareElementID="BIOS Date:
08/14/12 17:46:21 Ver: 04.06.03",SoftwareElementState=3,TargetOperatingSystem=0,Version="_ASUS_ - 6222004"
BiosCharacteristics : {7, 11, 12, 15...}
BIOSVersion : {_ASUS_ - 6222004, BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03, BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03}
BuildNumber :
CodeSet :
CurrentLanguage : eng
Description : BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03
IdentificationCode :
InstallableLanguages : 1
InstallDate :
LanguageEdition :
ListOfLanguages : {eng}
Manufacturer : American Megatrends Inc.
OtherTargetOS :
PrimaryBIOS : True
ReleaseDate : 20120814000000.000000+000
SerialNumber : BAN0AS739002438
SMBIOSBIOSVersion : UX31E.214
SMBIOSMajorVersion : 2
SMBIOSMinorVersion : 6
SoftwareElementID : BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03
SoftwareElementState : 3
TargetOperatingSystem : 0
Version : _ASUS_ - 6222004
Scope : System.Management.ManagementScope
Path : \\WORK\root\cimv2:Win32_BIOS.Name="BIOS Date: 08/14/12 17:46:21 Ver: 04.06.03",SoftwareElementID="BIOS Date:
08/14/12 17:46:21 Ver: 04.06.03",SoftwareElementState=3,TargetOperatingSystem=0,Version="_ASUS_ - 6222004"
Options : System.Management.ObjectGetOptions
ClassPath : \\WORK\root\cimv2:Win32_BIOS
Properties : {BiosCharacteristics, BIOSVersion, BuildNumber, Caption...}
SystemProperties : {__GENUS, __CLASS, __SUPERCLASS, __DYNASTY...}
Qualifiers : {dynamic, Locale, provider, UUID}
Site :
Container :

Thanks
 
Upvote 0 Downvote

cool, here is my list that pertain:
Supported: 4 7 9 10 11 12 14 15 16 17 19 23 24 25 26 27 28 29 30 32 33 36 37 40 42 51 56 57 58 59 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
SMBIOSMajorVersion : 2
SMBIOSMinorVersion : 5

entry 4 indicated ISA cards (but who cares)
Lack of entry 9 indicates your plug and play is not supported
lack of entry 10 indicated APM is not supported Advanced power management
lack of entry 14 indicates no ESCD support
entry 17 indicate my BIOS ROM is in a socket
entry 32 indicated mono/CGA video support (who cares)
entry 36 indicates LS-120 boot support ( Not sure what this is)
entry 37 ATAPI zip drive support( who cares)
entry 39 indicates you have smart battery support
rest are reserved and supported by device drivers from the motherboard maker and bios maker

-main difference is 10 Advance power management looks like it is not supported or turned off.
and your SMBIOS version is 2.6 and custom for UX31E.214 while mine is 2.5 generic

-look at your BIOS setting and see if some power management setting is turned off. the BIOS indicated it does not support and the Windows is ignoring some settings because of it. Does your system even have a fan? I know some of them are pretty small and are underclocked to remain cool.

you have a custom SMBIOS for your machine, It looks like you are running a older version of the BIOS.
not the version 214 dated 10-16-2012. (or ASUS did not update the version numbers before they put it on the web site, that happens also. but check anyway. and use the asus global site not the usa one. I they can be out of sync
http://support.asus.com/download.aspx?SLanguage=en&m=UX31E&p=3&s=369&os=36&hashedid=okyFhGJT4AM8jMkZ
is where I was looking.

EDIT: I downloaded the ASUS ux31eas.214 rom but the format is changed from what my ROM editor expects and I can not decode it correctly.
 
Upvote 0 Downvote
you might want to verify your system files in case there was a file corruption
start cmd.exe as a administrator and

sfc /VERIFYONLY

to see if it finds a bad OS file

just looked at the SMBIOS spec changes between version:


12h + number of BIOS Characteristics Extension
Bytes. If no Extension Bytes are used the Length is
12h. For version 2.1 and 2.2 implementations, the
length is 13h because one extension byte is defined.
For version 2.3 and later implementations, the length
is at least 14h because two extension bytes are
defined. For version 2.4 and later implementations,
the length is at least 18h because bytes 14-17h are
defined.


will have to look at it when I get back from the airport
 
Upvote 0 Downvote
When I installed Windows 8, I did an update from Windows 7 and then I did a remove everything and reinstall Windows option.

As well when I check event viewer, I always get this error when the computer shuts off:

- System

- Provider

[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}

EventID 41

Version 3

Level 1

Task 63


I ran sfc /VERIFYONLY and nothing is corrupt.

When I run the flash program with the newest bios flash it matches revision 214 date 08/14/2012.
 
Upvote 0 Downvote
Ive got windows 8 at the moment and I have this issue as well, im just persisting with it. never had this issue with windows 7, thinking its a combo fault with win8 and the hardware.

issue: plugin, or remove ac power, laptop just powers of. once powered back on, error 41 in event viewer, kernel power issue.

other fault, sometimes dosent wake correctly from sleep.

edit*
forgot to mention, i have a UX31E i7, win8 ent clean install with drivers from asus website.


Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 14/02/2013 08:14:26
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: ******
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
 
Upvote 0 Downvote
Same problem here. I've been running Win 7 x64 without any problem for over an year, after reinstalling with Win 8 x64 sudden Shutdowns while plugging the AC adapter.

BIOS version is 214 from the Asus homepage.
 
Upvote 0 Downvote
I tried many of the proposed fixes listed here and elsewhere for this fault on my UX31E. One of those was disconnecting the internal battery, but I was reluctant, especially while my laptop was within it's warranty period. I got so fed up with failed attempts to fix this; bios & driver updates, power management settings, restores and clean installs, etc. that I mustered the courage.
I followed a tear-down guide and youtube video instructions (which included battery removal) and removed (for a few minutes) and reconnected the battery connection (that's the multi-coloured cable terminal connection (not a ribbon type) on the UX31E, which is best teased up from the board with a plastic tool). So far, I have not had this problem reoccur (on WIndows 8.1). I have even tested it after maxing out the CPU on a game to get the system nice and hot which seems to be one of the driving causes of this fault - i.e. a fail-safe shutdown of the CPU when changing power profiles. So, in my experience this resolves the fault - for now at least!
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom