Posted: 8/15/2010 12:03:35 AM EDT
|
Enpower EN660 Laptop. Intel T7100 4gb RAM Windows 7 64bit Home. Fresh install last week. Anyone running Vista or Windows 7 run across this problem? This computer has run flawless until this fresh install. Prior to this install, I was running the same version of Windows from the same disk with no issues. The event view calls it a Event 41 Kernel Power. I did a search of this problem. According to several forums, It's happening to all kinds of computers running Vista and/or Windows 7. I cannot find a pattern. It's hitting Intel and AMD Processors. Laptops, desktops, 32bit, 64bit, it doesn't matter. I think it's either a driver issue or a faulty Windows update. The BSOD only shows up for a split second. Not enough time to record the failure. The computer makes a strange noise, shuts down, reboots and runs like normal for the rest of the day. Any of you Windows experts seen this problem? My ability to translate the log entries is lacking. Until I can get a handle on this, I'll be running Mint 9x64 KDE as much as I can. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>2</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords> <TimeCreated SystemTime="2010-08-15T04:31:36.520012300Z" /> <EventRecordID>4478</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>ZM-PC</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">false</Data> <Data Name="PowerButtonTimestamp">0</Data> </EventData> </Event> Thanks in advance ZM |
|
Quoted: First thing to do is disable "reboot on error" so it stops and shows you the error.Enpower EN660 Laptop. Intel T7100 4gb RAM Windows 7 64bit Home. Fresh install last week. Anyone running Vista or Windows 7 run across this problem? This computer has run flawless until this fresh install. Prior to this install, I was running the same version of Windows from the same disk with no issues. The event view calls it a Event 41 Kernel Power. I did a search of this problem. According to several forums, It's happening to all kinds of computers running Vista and/or Windows 7. I cannot find a pattern. It's hitting Intel and AMD Processors. Laptops, desktops, 32bit, 64bit, it doesn't matter. I think it's either a driver issue or a faulty Windows update. The BSOD only shows up for a split second. Not enough time to record the failure. The computer makes a strange noise, shuts down, reboots and runs like normal for the rest of the day. Any of you Windows experts seen this problem? My ability to translate the log entries is lacking. Until I can get a handle on this, I'll be running Mint 9x64 KDE as much as I can. - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" /> <EventID>41</EventID> <Version>2</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000002</Keywords> <TimeCreated SystemTime="2010-08-15T04:31:36.520012300Z" /> <EventRecordID>4478</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>ZM-PC</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="BugcheckCode">0</Data> <Data Name="BugcheckParameter1">0x0</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">false</Data> <Data Name="PowerButtonTimestamp">0</Data> </EventData> </Event> Thanks in advance ZM How did you get the details if it's too fast? Is that someone elses' data set? You need YOURS. Errors that appear to have no sense to them, are often general "we forgot to program an error error". So, what the device spits out when it doesn't know what to say about what is wrong, resulting in the same error showing up for all sorts of things. Without further information, we are just guessing here, my guess is it's a heat related problem and you have an item dislodged or dust in the case. Try sticking it in a high air flow situation (maybe a box fan on it's side and laptop on top) and seeing if the error comes back. |
|
Quoted: is this during a fresh install? do you have your recovery cd? can you boot into safe mode? It crashes, reboots and seems to run fine afterwards. About heat. I thought about that also. I blew it out after the first BSOD. There wasn't much of a dust buildup anywhere. It gets blown out once a month. Historically this computer has never has a heat problem. It sits on a board that allows positive airflow. However, I'll pull the cover and check again. That data you see is directly from my event viewer. There are two programs that were hanging up after the install. Spybot and Musicmatch. They were not on the previous install and have been removed. Update: I installed a CPU temp program. It's running 52C on both processors with a 25% load. I'm watching the Colts-Niners game on Veetle using two monitors. 52 degrees C is about right for this computer. I run the Balanced setting in the Windoze 7 settings and limit the max CPU load to 95% No issues so far. |
|
Quoted: you aren't using tea timer are you with spybot? I don't think so. It's been awhile since I used Spybot. If I recall, Tea Timer gave me problems. I think I didn't use it on this install of Spybot. It did it again about 10 minutes ago. Right in the middle of the football game. Totally unacceptable. I switched out the hard drives. I want to see if it does it again with a different hard drive. I keep a backup HD just for special occasions like this. The event log findings are in the original post. Monday or Tuesday I'll wipe the offending drive clean and reinstall Windoze. |