locked
Windows 7 crash and reboot automatically kernel-power error (Part 1)

    Question

  • Hi,
    I'm Andrea from Italy, I've installed windows 7 on my Toshiba NB100, Windows 7 RC Build 7100.
    Since I've installed it the pc crashed every 30 minutes or less, without any screen, only black screen and reboot.
    I tried to:

    remove the tick on "automatically restart" -> nothing
    remove firefox (because I noted that crashes happened with it) -> nothing
    remove ms office (same as firefox) -> nothing
    update drivers, with device manager -> nothing
    update bios from toshiba website -> nothing
    do check disk -> nothing
    defrag -> nothing

    this is the last critical error event

    - <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="2009-06-17T19:30:31.510422900Z" />
      <EventRecordID>4917</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Andrea-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>



    So, I don't know what to do (and I hope to resolve the problem, because I like very much win7), someone has some ideas?

    NOTE: This thread has been locked due to length and continued here.

    Wednesday, June 17, 2009 9:23 PM

Answers

  • hi for those in here check for speed step in bios if enabled try turing off as i turned off yesterday and to test for shutdown i was playing tf2(the game that gave random shutdowns) for 3 hours rebooted played again no issues and even booted in to game with out playing overnight with no shutdown if you have intel and have speedstep turn it off

    Edit: so it appears most people on this site have intels if this is true then it would either be c-state or speedstep causing the issue if you guys turn these off and the issue stops happening please reply with it worked or not and ur pc or laptop specs mobo cpu ram video card and os  like this

    Cpu: Intel® Pentium™ Dual Core T4400 (2.2GHz/800Mhz FSB/1MB cache)
    Mobo: Dell MotherBoard
    H277K(studio 1537 laptop)
    Ram: 4GB Shared Dual Channel DDR2 at 800MHz
    Video Card: Intel Graphics Media Accelerator 4500MHD
    Operating System: Windows 7 Ultimate Edition
    Resolved issue by turning off Intel SpeedStep
    Tuesday, November 24, 2009 8:18 PM
  • Hi,

    To address this issue, Microsoft has published a knowledge base (KB) article:

    Windows Kernel event ID 41 error in Windows 7 or in Windows Server 2008 R2: "The system has rebooted without cleanly shutting down first".

    Click the following link to view the article in the Microsoft Knowledge Base:

    http://support.microsoft.com/kb/2028504

    Regards,

     


    Magon Liu - MSFT
    Tuesday, June 08, 2010 3:02 AM
    Moderator

All replies

  • Hi Andrea,

    Sounds like the PC is spontaneously rebooting.  This could be an indication of a hardware problem or a driver problem.  Are you able to run manufacturer diagnostics on the system?
    • Proposed as answer by bits8mybytes Thursday, March 25, 2010 2:33 AM
    Thursday, June 18, 2009 1:47 AM
  • How can I do that?

    Actually, following other forum idea, I've disabled the sleep mode and other in the power settings, putting all to "do nothing", and it seems to work, but so I don't have screen saver, power saving and so on...
    I think win7 has not to work by this way without some functions.....
    Thursday, June 18, 2009 7:42 PM
  • Unfortunately the idea does not work!
    The PC work for more time than before, but this morning it restarts two times during 5 hours of work, less but same as before.
    Please help me...thanks
    Friday, June 19, 2009 12:51 PM
  • Do you have any manufacturer diagnostics?  Check Toshiba's site for diagnostic utilities that you can download and install or create bootable media with.  Also consider pressing F8 while booting, and selecting to run the Windows Memory Diagnostic.

    Ensure there is adequate ventilation - blow out any dust, etc. from accessible areas with a can of compressed air.  Also consider ensuring that connections (RAM, HD, cards, etc.) are clean, clear, and snug.
    Friday, June 19, 2009 1:02 PM
  • - <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="2009-06-19T10:58:28.806823400Z" />
      <EventRecordID>5947</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Andrea-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>

    that was the last restart this morning...

    after that I follow you advice and I've done:
    windows memory diagnostic -> no problem detected
    toshiba diagnostic tool -> no problem detected

    I think is not a computer-machine problem, because on this computer I've a dual boot with ubuntu netbook remix, and with this OS the computer work without any problem.

    Any other ideas to solve the problem?
    Friday, June 19, 2009 6:47 PM
  • The system is not shutting down cleanly.  It is spontaneously restarting.  Either something in kernel mode is being Very Bad, or there is a hardware problem.

    The behavior begins immediately after installing the Windows 7 RC, before installing any other software including drivers from Toshiba?

    Are you able to selectively eliminate hardware from the equation (e.g. if you have multiple RAM modules, take one or more out and try each individually)?
    Friday, June 19, 2009 7:25 PM
  • Hi.

    I has the same problem, and I resolved as follow:

    Go To ->

    Contol Panel
    System and Security
    Administrative Tools
    Schedule Tasks

    Under the Active Tasks panel, I had a task named "RacTask" scheduled to run 1 hour after the power on.
    I noticed when the time to start that task comes, my computer reboout...

    So I disabled that task, and my computer don't reboot anymore now.

    Seems a joke that the RAC service who is the responsible to check the reliability of the system, was the cause of the reboot :)

    Hope this help,
    Eugenio Serrano.
    Solid Quality Mentors
    NDSoft Consultoria y Desarrollo
    Saturday, June 20, 2009 1:57 PM
  • Hi Eugenio,
    It's more than just a reboot, though - a reboot is at least graceful.  An unexpected / spontaneous reboot is not - it can lead to FS corruption, data loss, etc...

    So it sounds like disabling the RacTask is a workaround, which is of course better than nothing, but not the actual cause (which, if triggered by software, would suggest some buggy kernel module)...
    Saturday, June 20, 2009 5:23 PM
  • because first thing after installing I've update drivers.
    In the interest of trying to get some indication as to what step in the initial setup / configuration process this occurs, I'd suggest not installing the updated drivers..
    I cannot eliminate hardware because the PC is a Toshiba Netbook
    If the system has multiple RAM chips, it seems you could at least attempt to isolate them.
    as I've written before with ubuntu netbook remix the pc works very well, the problem of restarting appear only in windows 7, so I don't think there is a physical hardware problem
    The Netbook Remix may not exercise all of the functionality of all of the devices the same way that Windows does.  And, the drivers are of course different.
    but all diagnostics said all si ok....
    Unfortunately, all that really means is that diagnostics were not able to find a problem. It does not mean that a problem will not exist. :-(
    but is there a build after the 7100
    Sure, but not officially provided by Microsoft for the "general public".


    One other thought to try involves running SFC /SCANNOW from an elevated CMD prompt.
    Saturday, June 20, 2009 5:29 PM
  • Hello, I joined this discussion because I have the exact same problem with my computer. With a bit of googleing easily finding this post.

    Had 4 Bsod's in aprox 24 hours

    EDIT: Started new thread, problem is different:
    http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/dbe8f3dd-41f7-4d87-9e47-9c66b251b6e7
    ----------------------------------

    My specs: Gigabyte GA-EX38-DS5 with F4 bios, Intel C2D E8400 @3000Mhz, 2x2Gb DDR2 Mushkin 1066Mhz Ascent (@800Mhz), Asus Ati Radeon 3870 512Mb DDR4,  Maxtor 160gb sata(games), Western Digital Caviar 16 500Gb (system) , new WD Caviar Freen 1Tb(storage), Antec HE550 modular PSU.

    • Edited by zan_laurin Sunday, June 21, 2009 7:31 PM off-topic
    Saturday, June 20, 2009 7:12 PM
  • Hi zan_laurin,

    Had 4 Bsod's in aprox 24 hours
    This differs from the report discussed here; in this thread, the problem can pretty much be described as "spontaneous reboots".  If you're getting bugchecks, please post some details (the hex codes, etc.) or put the minidumps in a password-protected ZIP file and upload it somewhere.

    You might also consider starting a new thread, since (from your description, at least) your problem is different...
    Saturday, June 20, 2009 7:21 PM
  • I just goggled 3 parameters that I found in the event log and I thought that maybe its related to my issue:

    Microsoft windows kernel power , event ID 41, Task 63.


    I'll start a new thread on this. Thank you
    Saturday, June 20, 2009 7:27 PM
  • I've formatted and reinstalled win7, but nothing, this morning he had a spontaneous reboot.
    I tried all....if there are no other ideas, I think I'll try with toshiba guarantee, maybe something is wrong in the netbook...
    Monday, June 22, 2009 3:07 PM
  • Presumably, you did not install any driver packages - you just installed Win7, began using the netbook, and encountered the reboot?
    Monday, June 22, 2009 3:24 PM
  • Yes, I did not install any driver packages but the netbook restart!!!
    Monday, June 22, 2009 6:10 PM
  • Can you use Win7 in Safe Mode for a while, to see if you experience the problem?
    Monday, June 22, 2009 6:42 PM
  • I get the exact same thing on my new Gateway Core i7 , X58 chipset  64 bit Win7.
    - <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="2009-07-04T05:16:41.031250000Z" /> 
      <EventRecordID>10130</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="4" ThreadID="8" /> 
      <Channel>System</Channel> 
      <Computer>MK-PC</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="BugcheckCode">122</Data> 
      <Data Name="BugcheckParameter1">0x20</Data> 
      <Data Name="BugcheckParameter2">0xffffffffc000009d</Data> 
      <Data Name="BugcheckParameter3">0xfffffa80079947c8</Data> 
      <Data Name="BugcheckParameter4">0x0</Data> 
      <Data Name="SleepInProgress">true</Data> 
      <Data Name="PowerButtonTimestamp">0</Data> 
      </EventData>
      </Event>
    For me this happens always when i re-awake the PC by giggling the mouse.. .I notice that the screen goes haywire for a split second and then the BSOD appears.  Has anyone found a way to fix this?
    Saturday, July 04, 2009 5:29 AM
  • Hi flabbygums,

    Bugcheck 122 is "WHEA_INTERNAL_ERROR" - "This bug check indicates that an internal error in the Windows Hardware Error Architecture (WHEA) has occurred. "

    That doesn't sound good.  But... Since this behavior occurs when the PC is asleep, one may consider that the problem is likey related to power-managment, etc.  I've read that this functionality in Windows 7 leaves some to be desired, and that one can hope for better results with a newer build of Windows 7 (or the  RTM). So, you might consider updating drivers, etc. to ensure you're running the latest version.  You may also consider disabling various power-saving features in anticipation that the problems will be addressed in some new build of 7. 
    Sunday, July 05, 2009 8:28 PM
  • I installed Win 7 32bit on a clean system yesterday. And I just got a spontaneous reboot after only some browsing/downloading, nothing harsh on the system. But it's the same EventID. Installed a few apps and 1 game, 1 video card driver for my x1950 which isnt supported anymore by AMD on Win 7, and thats it.
    I already noticed a weird stutter, where the system would just freeze a second every 10 seconds, for a couple of minutes, it stopped, and another couple of minutes later it crashed.

    Minidump @ http://www.mediafire.com/?ojzmyt9bh3l pass: minidumpspar


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

        EventID     41   

        Version     2   

        Level     1   

        Task     63   

        Opcode     0   

        Keywords     0x8000000000000002   
       
    -     TimeCreated   
       
        [ SystemTime]     2009-07-07T20:39:49.610416000Z   
       

        EventRecordID     1715   
       

        Correlation
       
       
    -     Execution
       
       
        [ ProcessID]     4
       
       
        [ ThreadID]     8   
       

        Channel     System   
       

        Computer     spars-PC
       
       
    -     Security
       
       
        [ UserID]     S-1-5-18
    -     EventData

       
        BugcheckCode     209

       
        BugcheckParameter1     0x2bf87585

       
        BugcheckParameter2     0x2

       
        BugcheckParameter3     0x8

       
        BugcheckParameter4     0x2bf87585

       
        SleepInProgress     false

       
        PowerButtonTimestamp     0

    Was my first and only spontaneous reboot so far btw. Well, I had another one this afternoon when I was burning Win7 64bit, it failed and just rebooted, my DVD drive freaked out and started spinning continuously, plus it wouldnt even eject. I had to reinstall the DVD drivers driver for it to give me my CD back, but thats not really related to this I guess.
    Tuesday, July 07, 2009 9:41 PM
  • Hi spa-rood,

    Looks like a DEP violation.  L1E62x86.sys (whatever that's for?? - check your system for it...) seems suspect...
    Tuesday, July 07, 2009 10:38 PM
  • Searched for it, and it's the driver for my network adapter/onboard LAN card or whatever we call it these days.

    I'll try to uninstall it, and install the drivers from asus.com instead of the Win7 drivers.
    Wednesday, July 08, 2009 12:03 AM
  • OK - curious to hear how it goes... :-)
    Wednesday, July 08, 2009 2:23 AM
  • Havent had a spontaneous reboot yet. Will try to start some downloads like I did yesterday when crashing, but it seems good. Also seems like I rolled back drivers, Win7 had L1E62x86.sys, now I have L1E60X86.sys (latest drivers from asus.com). But as long as its not crashing, Im happy.
    Wednesday, July 08, 2009 8:15 AM
  • Do you expect you would have encountered a bugcheck by now?
    Wednesday, July 08, 2009 9:30 AM
  • No not really actually, already tried downloading some files and no crash so far.
    Wednesday, July 08, 2009 2:16 PM
  • At what point do you think you will be satisfied that changing the driver has addressed the issue? (How frequent were the bugchecks, etc.?  Seems you didn't have 7 installed for a very long time, so it will likely take some usage before you're able to feel comfortable with it...)
    Wednesday, July 08, 2009 2:32 PM
  • I just installed Win7, and I got that error within a day. But so far I had only 1 of those errors, I'll be satisfied in a few weeks. Still not sure though, Ive overclocked my CPU and RAM too and have a +4 year old hard-drive so it might be hardware messing about, but I think I wouldve noticed something before I installed Win7. Already diagnosed the HD, gonna run memtest tonight plus some torture tests to be absolutely sure.
    Wednesday, July 08, 2009 4:57 PM
  • I have been having a similar issue with my newly constructed computer, and I would be very curious if there has been a solution fleshed out.

    The error seems to happen more frequently when exercising the 3D hardware (e.g. playing games). I've updated the motherboard firmware and drivers, video card drivers, and integrated sound / ethernet drivers in an attempt to fix this problem, which has so far been fruitless.

    Interestingly, the spontaneous reboots only started occurring after I updated my motherboard firmware to the latest version (as the version that comes with the Gigabyte GA-m790XT-U4DP doesn't recognize Phenom II x4s by default, and sets their frequency to 800Mhz rather than the 3.2Ghz the chip is supposed to be running at). 7

    I have about a dozen of logs mostly identical to the one below modulo the time at which they occurred. I've attached the most recent one in hopes that it provides someone else more edification than I've had.

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          7/12/2009 5:26:10 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      Stalwart
    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.
    Event Xml:
    <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="2009-07-13T00:26:10.607219300Z" />
        <EventRecordID>4872</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Stalwart</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>
    Monday, July 13, 2009 1:06 AM
  • having the same issue with a core i7 920 MSI x58 platinum sli, gtx 275, OCZ Gold 4 gb DDR3 1600(PC3 12800) Ram, Western Digital WD25000AAJS SATA with windows 7 x64.  It started as restarting and now it just shuts down.  I played around with drivers for the components but it still happens.   I have seen some vista 64 bit issues that are similar but still the problem is not resolved.  If anyone with my similar setup was able to resolve this issue and how please post.

    Tuesday, July 21, 2009 3:33 PM
  • I have been having the same issue for the last few days. It originally started with Windows XP x64 Ed. Then with Windows 7 x86 edition.

    Spontaneous reboots. Microsoft-Windows-Kernel-Power error.

    I can post more system details later today. I just wanted to up this thread as there doesn't seem to be a solution posted...


    Also, is everyone using a Gigabyte mother board here? Could that be the cause?






    • Edited by ackynet Tuesday, August 25, 2009 3:26 PM
    Tuesday, August 25, 2009 3:07 PM
  • Motherboard: Gigabyte (GA-EP45-DS3L S775 P4)
    CPU: Intel Core 2 Quad - Q9550
    Ram: Corsair 4GB DDR2-1066
    Power Supply: OCZ Modxstream pro 500W




    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          8/25/2009 10:58:18 PM
    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.
    Event Xml:
    <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="2009-08-26T02:58:18.370022600Z" />
        <EventRecordID>1066</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>clutch2k9</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">126</Data>
        <Data Name="BugcheckParameter1">0xc0000420</Data>
        <Data Name="BugcheckParameter2">0x828f67ef</Data>
        <Data Name="BugcheckParameter3">0x8f5c7bc8</Data>
        <Data Name="BugcheckParameter4">0x8f5c76f0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Wednesday, August 26, 2009 3:37 AM
  • Do you have a minidump for that one, ackynet?  If so, can you put it in a password-protected ZIP file, upload the ZIP file somewhere, and privately provide the details (my email address is in my profile)?

    126 = 0x7E = SYSTEM_THREAD_EXCEPTION_NOT_HANDLED; 0xc0000420 = STATUS_ASSERTION_FAILURE: "An assertion failure has occurred.".
    Wednesday, August 26, 2009 9:35 AM
  • Hi No.Compromise,

    I have sent the minidump files this morning.

    Wednesday, August 26, 2009 5:38 PM
  • Sorry to tell you that the vast majority of the dump files indicate a hardware memory error.  The rest indicate memory corruption, which may be caused by faulty drivers, or faulty hardware.  So, things are pretty much pointing to this being a hardware memory issue...

    Check your RAM with e.g. Windows Memory Diagnostic, and / or selectively test the modules by removing some of them and seeing if you can repro the problem with a specific module or set of modules.  Also check connections to ensure they're snug, etc.
    Thursday, August 27, 2009 10:31 AM
  • Thank you. That's what I was leaning towards as well. I overclocked the RAM yesterday morning and it went 24 hours without a crash. However, it just crashed again now.

    Luckily the RAM is new, so I should be able to have it replaced.


    Lastest error.

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          8/27/2009 7:19:48 AM
    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.
    Event Xml:
    <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="2009-08-27T11:19:48.516815800Z" />
        <EventRecordID>848</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer></Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">26</Data>
        <Data Name="BugcheckParameter1">0x8886</Data>
        <Data Name="BugcheckParameter2">0x84c93e28</Data>
        <Data Name="BugcheckParameter3">0x84d72ae8</Data>
        <Data Name="BugcheckParameter4">0x602</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Thursday, August 27, 2009 11:55 AM
  • Bugcheck 26 (0x1a) indicates a severe memory management error occurred, right in line with the other bugchecks.
    Thursday, August 27, 2009 12:08 PM
  • I've been dealing with a similar problem for a couple of weeks. Random crashes that result in spontaneous reboot or having to power down/up to restart. I have a MSI K9N2 sli Platinum nForce 750a Socket AM2+ Mobo with AMD Phenom X4 9500 processor - not overclocked. Memory are 2 Corsair PC6400 DDR2 800 MHz DHX 2048MB modules. HD is WD Caviar 500GB Serial ATA HD. Display is Galaxy GeForce 8400 GS 256MB PCIe w/DVI.

    Have updated BIOS, all drivers, and run the memory checks from windows and memtest86. Was getting occasional errors on Windows Memtest but not memtest86. Corsair says the memtest86 is more thorough. Pulled one stick of memory out yesterday and reran Windows memory check with no errors. Computer ran rest of the day and all night with no crashes. Put the stick back in this morning but in swapped position and Windows memory check ran with no errors. Have been running since with no crashes.

    I'll attach some of the diagnostics I have cut from earlier crashes. Why would swapping the two sticks make any difference? Is there anything I can do to further troub leshoot this?

    Drivers in crash stack:
    HDAudBus.sys    HDAudBus.sys+16d03    0x908e3000    0x90902000    0x0001f000    0x49ee93c0    4/21/2009 11:49:20 PM    Microsoft® Windows® Operating System    High Definition Audio Bus Driver    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\drivers\HDAudBus.sys   
    HdAudio.sys    HdAudio.sys+d6c4    0x90973000    0x909c3000    0x00050000    0x49ee93f2    4/21/2009 11:50:10 PM    Microsoft® Windows® Operating System    High Definition Audio Function Driver    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\drivers\HdAudio.sys   
    ntkrnlpa.exe    ntkrnlpa.exe+6f6ea    0x82a02000    0x82e11000    0x0040f000    0x49ee8b4e    4/21/2009 11:13:18 PM    Microsoft® Windows® Operating System    NT Kernel & System    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\ntkrnlpa.exe   

    Drivers in crash stack:
    ataport.SYS    ataport.SYS+6e87    0x8b6fb000    0x8b71e000    0x00023000    0x49ee8a3a    4/21/2009 11:08:42 PM    Microsoft® Windows® Operating System    ATAPI Driver Extension    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\drivers\ataport.SYS   
    CLASSPNP.SYS    CLASSPNP.SYS+43b9    0x8bb9c000    0x8bbc1000    0x00025000    0x49ee8a3b    4/21/2009 11:08:43 PM    Microsoft® Windows® Operating System    SCSI Class System Dll    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\drivers\CLASSPNP.SYS   
    ntkrnlpa.exe    ntkrnlpa.exe+59443    0x82a10000    0x82e1f000    0x0040f000    0x49ee8b4e    4/21/2009 11:13:18 PM    Microsoft® Windows® Operating System    NT Kernel & System    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\ntkrnlpa.exe   

    Drivers in crash stack:
    aswMonFlt.sys    aswMonFlt.sys+1392    0x9522d000    0x95244000    0x00017000    0x4a8147b5    8/11/2009 6:28:05 AM    avast! Antivirus System    avast! File System Minifilter for Windows 2003/Vista    4.8.1351.0    ALWIL Software    C:\Windows\system32\drivers\aswMonFlt.sys   
    halmacpi.dll    halmacpi.dll+5ba9    0x82a1f000    0x82a56000    0x00037000    0x49ee8a2e    4/21/2009 11:08:30 PM    Microsoft® Windows® Operating System    Hardware Abstraction Layer DLL    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\halmacpi.dll   
    ntkrnlpa.exe    ntkrnlpa.exe+3b7bb    0x82a56000    0x82e65000    0x0040f000    0x49ee8b4e    4/21/2009 11:13:18 PM    Microsoft® Windows® Operating System    NT Kernel & System    6.1.7100.0 (winmain_win7rc.090421-1700)    Microsoft Corporation    C:\Windows\system32\ntkrnlpa.exe   

    Bugcheck at failure:
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          8/26/2009 10:54:59 AM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      MSI01
    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.
    Event Xml:
    <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="2009-08-26T14:54:59.437500000Z" />
        <EventRecordID>17107</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>MSI01</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">26</Data>
        <Data Name="BugcheckParameter1">0x1236</Data>
        <Data Name="BugcheckParameter2">0x852f9780</Data>
        <Data Name="BugcheckParameter3">0x852f97a0</Data>
        <Data Name="BugcheckParameter4">0x1137e</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>

    Bugcheck at Failure:
    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          8/26/2009 10:05:26 AM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MSI01
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000008e (0xc0000005, 0x8bba03b9, 0x8d89a904, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 082609-16328-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-08-26T14:05:26.000000000Z" />
        <EventRecordID>16986</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>MSI01</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x0000008e (0xc0000005, 0x8bba03b9, 0x8d89a904, 0x00000000)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">082609-16328-01</Data>
      </EventData>
    </Event>
    • Proposed as answer by Farrukh 2010 Sunday, March 28, 2010 1:17 AM
    Thursday, August 27, 2009 4:38 PM
  • Hi Harleydls,

    You're potentially encountering memory corruption, given the variety of the bugchecks.  Depending on the frequency, Driver Verifier may be an option, but if any memory diagnostic program is indicating that the memory is bad, I'd immediately be suspicious.  (And even if a memory diagnostic did not indicate memory is bad, it doesn't mean the memory is "good" - it just means that the diagnostic didn't detect memory problems.)


    Why would swapping the two sticks make any difference? Is there anything I can do to further troub leshoot this?
    Moving hardware when there may be a bad connection may have the effect of improving the connection. Or, perhaps dust was disturbed such that what had previously been a heat problem will cease to arise... for a while. Etc. I'd suggest systematic testing with the memory modules - run with as few modules as you can for a while and once you're certain you would have encountered the problem under normal conditions, try a different module.
    Thursday, August 27, 2009 5:33 PM
  • O.K. NC, Thanks and I will continue along those lines. I am very suspicious of the memory too, as this system ran 7 for over two months with no crashes and then all of the sudden, I get them frequently. As soon as I play with the memory modules themselves, it seems to be better. The dust may also be an issue as I blew some out of the box yesterday when changing the modules out. I'll report back if I get any more glitches and also have requested Corsair replace the modules. We'll see where that goes.

    Thanks again
    Thursday, August 27, 2009 6:03 PM
  • I have the same problem as Harleydls   and  thousands of people. I made a new thread about it without any solution. I am so freaking mad when I read that "I might be your memory or hardware problem" " Do you have the latest drivers" " latest BIOS" 

    How the ____ could my hardware be broken when the same hardware runs 100% perfect on XP,Vista 32 and 64 and as soon I installed WIN7 RTM the ____ broke loose... One more thing WIN7 BUILD 7100 worked great :)

    So my conclusion is that WIN 7 RC/RTM is broken/ or bad drivers for WIN7 RC/RTM... I see lot's of ppl on different forums  that have the same Kernel-power event 41 error!



    /Pasch
    Friday, August 28, 2009 7:44 AM
  • Hi Pasch,

    You abandoned your thread and hijacked this one.  x_X

    EventID 41 is a generic message loosely indicating an ungraceful reboot.  You can't lump them all together, because they are likely caused by different things.

    Seems strange that you would get mad, when someone tries to help you when you post about a problem.  The reason the stated items are often suggested is because they are often involved in resolving the type of issue reported.   Whether or not you like them is not relevant.  You were even given an explanation for some of the items back in your thread, yet you continue to bring them up here.

    Without further details, as requested in your original thread, it will be rather difficult to assist you.

    Friday, August 28, 2009 10:18 AM
  • Hey ppl... Been getting a similar problem...I've had win7 RC on my pc for abt a month and it worked fine. On thursday, what happened was like someone just pulled the plug on the machine, that is to say, no BSOD, just going from in windows to a black screen. It does not even reset itself. Once i push the power button it comes back up and i get the  error below. At first i ignored it but it happened 3 times again that day.. I did a fresh install of win7 RC and just installed apps like microsoft office and photoshop. i did not install any of my games to check it out... It worked well for a day, then happened again on friday night.... Worked well whole day saturday (yesterday) and this morning same problem... Below is what i got from event viewer... Thanks for the future help....

    - <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="2009-08-29T07:46:26.187600000Z" />
      <EventRecordID>1420</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Jason-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>

    Did a memory test, no problems reported...
    Sunday, August 30, 2009 1:33 PM
  • Yesterday, I upgraded my HP 6516B laptop to Win 7 Pro - it's been running XP without problem for 1 year or so.

    Today, the laptop has frozen twice, and the only way I've been able to get it back working again is a forced power down and restart.

    The event log shows the kernel-power 41 entry - what would people suggest I look at to find the source of this problem?

    Phil C

    Tuesday, September 22, 2009 3:34 PM
  • All sorted - it was Winamp that was causing the problems. Uninstalled it and the laptop's been perfect ever since.

    Phil C
    Friday, September 25, 2009 5:19 PM
  • Hi Andrea.

    I have the same porblem with my new pc. its a core 2 quad with a mother intel dp45sg and 3 hard disk 1 video card xfx 9800 and 1 dvd liteon, i think that the solution could be a fix made by microsoft so far we need it. In my case i think its the power suply i got a powersuply to all my stuff inside my pc its 500W that isn´t to eficently so i think that if i buy a new one like thermaltake of 850 or 750 watts but i suspect that coud be this.

    I think the problem might be this:
    the PC is restarting alone when i be sailing without generating activity with the mouse, and as i knew, if not detacta mouse movement from the familiar Windows interface that puts to rest the pc. With windows xp although I never had this problem but that Windows Vista is the same problem. Factor hardware does not think it's because the pc was already running other operating systems without any problem. In my case when I relaunch the application was when i had watching a video online or playing something that requires energy. For me the problem in Windows 7 is with energy management. So i think that a fix or a SP could have the solution for this.

    Sorry if i do not be clear but i speak better english no write it im from argentina.
    Saturday, September 26, 2009 3:08 PM
  • So are we still all without a solution?

    Everytime I play a game (and i've tried about 4 different games), I get a spontaneous reboot

    event viewer shows eventid 41 as the culprit

    i've tried adjusting power saving settings, but to no avail

    this seems a pretty widespread W7 issue - no solution out there yet?
    Saturday, September 26, 2009 6:37 PM
  • I've the same error , kernel power error 41 in Windows 7. I've tried to make various test, memory, cpu, etc..., adjusting power settings and scheduled task, I've eliminated from hardware the Matrox Rtx2 Card for Video Editing, but seems that the System  spontaneous reboot anyway.


    Monday, October 19, 2009 7:46 AM
  • What are the details of the event log message?
    Monday, October 19, 2009 9:56 AM
  • Sadly not a solution, but I have the same problem.

    This is a weird problem, as it does not occur during gaming and high intensity applications. It only seems to happen during web browsing and genral pc usage.

    It happens to me once every day, but at different times. So its hard to track down a specific program which could be causing it.

    Critical 20/10/2009 10:44:36 Kernel-Power 41 (63)
    Critical 19/10/2009 09:29:20 Kernel-Power 41 (63)
    Critical 18/10/2009 22:29:44 Kernel-Power 41 (63)
    Critical 18/10/2009 18:53:31 Kernel-Power 41 (63)

    Heres my error details.


    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          18/10/2009 18:53:31
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      PongoBongo-PC
    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.
    Event Xml:
    <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="2009-10-18T17:53:31.660412500Z" />
        <EventRecordID>8494</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>PongoBongo-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>

    Its my opinion, that this is a software problem because it seems to happen across many different hardware systems - which had not had power problems before installing WIN 7.

    Can anyone point me in the direction of some debugging tools, as I would like to investigate a bit deeper into the problem. Is there any software I could run which would log running process before a critical event. Maybe I could see if a process started just before the crash, and have some clues to a potential cure.

    Tuesday, October 20, 2009 2:22 PM
  • I'm getting the same spontaneous reboot except mine happens every hour almost like clockwork.  This is a fresh install, no extra driver software installed and i have office 2007 and firefox installed but this happened before i installed firefox.


    Critical    10/20/2009 11:23:28 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 10:23:57 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 9:23:39 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 8:23:23 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 7:23:05 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 6:22:47 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 5:22:29 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 4:22:12 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 3:21:54 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 2:21:36 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 1:21:20 AM    Kernel-Power    41    (63)
    Critical    10/20/2009 12:20:44 AM    Kernel-Power    41    (63)
    Critical    10/19/2009 11:20:24 PM    Kernel-Power    41    (63)
    Critical    10/19/2009 5:54:18 PM    Kernel-Power    41    (63)
    Critical    10/19/2009 3:19:11 PM    Kernel-Power    41    (63)




    BODY{font:x-small 'Verdana';margin-right:1.5em} .c{cursor:hand} .b{color:red;font-family:'Courier New';font-weight:bold;text-decoration:none} .e{margin-left:1em;text-indent:-1em;margin-right:1em} .k{margin-left:1em;text-indent:-1em;margin-right:1em} .t{color:#990000} .xt{color:#990099} .ns{color:red} .dt{color:green} .m{color:blue} .tx{font-weight:bold} .db{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;border-left:1px solid #CCCCCC;font:small Courier} .di{font:small Courier} .d{color:blue} .pi{color:blue} .cb{text-indent:0px;margin-left:1em;margin-top:0px;margin-bottom:0px;padding-left:.3em;font:small Courier;color:#888888} .ci{font:small Courier;color:#888888} PRE{margin:0px;display:inline}
    - < 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 =" 2009-10-20T17:23:28.625000000Z " />
      < EventRecordID > 2614 </ EventRecordID >
      < Correlation />
      < Execution ProcessID =" 4 " ThreadID =" 8 " />
      < Channel > System </ Channel >
      < Computer > Matt-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 >
    Tuesday, October 20, 2009 5:54 PM
  • Im getting windows 7 pro in a couple of days. I hope the retail version has solved all these problems. Good luck to all! :D
    Tuesday, October 20, 2009 6:17 PM
  • Hourly reboots are a sign that you're using the expired beta version of Win7.  What build are you using?
    Wednesday, October 21, 2009 9:48 AM
  • That there is no bugcheck code suggests that the system is either spontaneously rebooting, or that there is perhaps an issue with power at the location.  Is the system a laptop or a desktop?  Is there a UPS attached to the system?  When did the behavior start?  Can you use system restore to restore the system to a point in time before the behavior started?
    Wednesday, October 21, 2009 9:50 AM
  • HI, MY LAPTOP HAVE A CRASH APP, having a blue screen eventid 41 or kernel-power critical error. my laptop is acer aspire 4736. can you help how can i solve this blue screen or anything i can do not to happen it again.
    Friday, October 23, 2009 8:10 AM
  • What are the details from the "41 event"?
    Friday, October 23, 2009 9:50 AM
  • Hi Andrea,

    I had a similar problem that I found. As someone else has posted, it appears to be in the power settings. I had set mine to never hibernate or power down and found that the machine was rebooting for what appeared to be a power issue. I later found in the full power settings that the disk was still set to power down with 10 minutes of no activity. It seems to me that if you have no power down or hibernate that these lower settings should be ignored or set to never. Anyway once I set that to never the system works fine. BTW the thing would reboot even when it was doing a backup. (I think that would count as activity??).

    John C
    Friday, October 23, 2009 12:16 PM
  • Had the same issues with kernal power.  I got 3 BSOD's in the first 24 hours.  Action center had me download a new driver for my power management.  So, far so good.  It's been a few days, now.

    It's odd, though, so many are having issues with kernal power issues.
    Saturday, October 24, 2009 6:55 PM
  • i wish someone could solve it, as i have installed my new windows 7 64 bit professional edition on a clean install, on a new computer... every 10 or so minutes, i get is a blue screen error flashing some sort of STOP error code such as Bad_config, IRQL not equal or less etc... and 3 seconds later it reboots...

    the event logger has stated the same as everyone elses on this forum; event 41 (63) critical with Kernal-power being the problem...

    i've scowled the internet searching for a solution, and everyone states hardware failure or driver failure, both which i checked.... does anyone have a true answer?
    Sunday, October 25, 2009 4:34 AM
  • hi all i am having the same issue see below this only seems to happen when i use steam or play certian games like team fortress 2 however when i play unreal tournament or other games i can run for hours with out a sudden loss of power total shut down but when trying to play any game in steam i get a sudden shut down after 1-5 mins my laptop does not seem to be over heating and i have run a 2 day stress test and full hardware check on it with no errors or problems
    this is what event log shows any help or info would be greatly appreciated
    - System
    - Provider
    [ Name ] Microsoft-Windows-Kernel-Power
    [ Guid ] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
    EventID 41
    Version 2
    Level 1
    Task 63
    Opcode 0
    Keywords 0x8000000000000002
    - TimeCreated
    [ SystemTime ] 2009-10-25T09:42:38.490028100Z
    EventRecordID 6045
    Correlation
    - Execution
    [ ProcessID ] 4
    [ ThreadID ] 8
    Channel System
    Computer JJforever-PC
    - Security
    [ UserID ] S-1-5-18
    - EventData
    BugcheckCode 0
    BugcheckParameter1 0x0
    BugcheckParameter2 0x0
    BugcheckParameter3 0x0
    BugcheckParameter4 0x0
    SleepInProgress false
    PowerButtonTimestamp 0
    Sunday, October 25, 2009 10:11 AM
  • Same problem here, it seems to occour on some games more than others, i.e painkiller more than world of warcraft which has only rebooted once. Hasnt happend to me whilst not playing a game.

    - System
    - Provider
    [ Name ] Microsoft-Windows-Kernel-Power
    [ Guid ] {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
    EventID 41
    Version 2
    Level 1
    Task 63
    Opcode 0
    Keywords 0x8000000000000002
    - TimeCreated
    [ SystemTime ] 2009-10-25T01:21:21.962823700Z
    EventRecordID 1741
    Correlation
    - Execution
    [ ProcessID ] 4
    [ ThreadID ] 8
    Channel System
    Computer Holley-PC
    - Security
    [ UserID ] S-1-5-18
    - EventData
    BugcheckCode 0
    BugcheckParameter1 0x0
    BugcheckParameter2 0x0
    BugcheckParameter3 0x0
    BugcheckParameter4 0x0
    SleepInProgress false
    PowerButtonTimestamp 0
    Sunday, October 25, 2009 8:27 PM
  • Hi may i know what driver particular for power management that you download.. coz i got also error of BSOD due to kernel power
    Tuesday, October 27, 2009 8:49 AM
  • Here is the details: (What should i fo for it... advance thanks)

    - <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="2009-10-25T15:07:20.159613500Z" />
      <EventRecordID>31716</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Kapogi-PC</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="BugcheckCode">25</Data>
      <Data Name="BugcheckParameter1">0x20</Data>
      <Data Name="BugcheckParameter2">0xfffff8a0088e1810</Data>
      <Data Name="BugcheckParameter3">0xfffff8a0088e18b0</Data>
      <Data Name="BugcheckParameter4">0x50a0081</Data>
      <Data Name="SleepInProgress">false</Data>
      <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
      </Event>

    Tuesday, October 27, 2009 8:51 AM
  • hello i have actually gone in and as of oct 26 i had new video drives available have installed these and my problem with random shutdowns during games stopped so i may suggest this
    Wednesday, October 28, 2009 9:25 PM
  • I have the same problem with my pc and kernel power 41 crash....

    My config :
    QuadCore q9400
    Ati Radeon 4890 vapor-x
    Alim Corsair 650W
    Asus P5QC with sound integrated Realtek high audio definition

    All my drivers and my bios are updated ....

    Helpp please
    Tuesday, November 03, 2009 4:47 AM
  • Hi Zan_laurin, i have the same problem with my PC too, and i only started after i got my new Graphics card, Radeon 3870 512mb ddr4... sound familiar?
    I think this problem may be due to a graphics card error.  just a thought.
    Thursday, November 05, 2009 1:32 AM
  • Hello ,my problem is:

    - <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="2009-11-04T20:42:37.800812800Z" />
      <EventRecordID>11493</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Gab-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>


    My config:
    E8400, Gigabyte EP45-DS3, HD4850

    Any idea or solution to what could be wrong?
    Thursday, November 05, 2009 1:25 PM
  • Maybe I found a solution for me.

    Hi, I've made a memtest on my 2 x 2Gb Kingstone RAM Memory and discovery an error in one of bank.
    I've  removed the memory bank RAM damaged.
     
    Now I work only with one of them (2Gb), waiting to buy the second memory. Windows 7 hasn't had no more automatic reboot issue (kernel power error).
    I think in my case the problem was the faulty memory that caused reboots. I hope so!

    Thursday, November 05, 2009 5:52 PM
  • Ok, I have the same issue.  Using a Thinkpad X60s; have run memory diagnostics several times; run Lenovo's diagnostics from a bootable cd & now from within the OS.  Memory is fine.  Am dual booting, with Win XP on one partition (original OEM install, fully updated).  XP runs just fine and event log has zero instances of Event ID 41 or 6008.  However in Win 7  Event ID 41 & Event ID 6008 surface when trying to resume from hibernate (when relying on battery or when plugged in).   Event log details are pasted below:

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          11/5/2009 12:40:59 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      X60s
    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.
    Event Xml:
    <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="2009-11-05T17:40:59.115244900Z" />
        <EventRecordID>155218</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>X60s</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">true</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>

    and

    Log Name:      System
    Source:        EventLog
    Date:          11/5/2009 12:41:14 PM
    Event ID:      6008
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      X60s
    Description:
    The previous system shutdown at 10:22:24 AM on ‎11/‎5/‎2009 was unexpected.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="EventLog" />
        <EventID Qualifiers="32768">6008</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-05T17:41:14.000000000Z" />
        <EventRecordID>155213</EventRecordID>
        <Channel>System</Channel>
        <Computer>X60s</Computer>
        <Security />
      </System>
      <EventData>
        <Data>10:22:24 AM</Data>
        <Data>‎11/‎5/‎2009</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>31301</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Binary>D9070B00040005000A00160018008A02D9070B00040005000F00160018008A023C0000003C000000000000000000000000000000000000000100000004F70000</Binary>
      </EventData>
    </Event>

    What to do now?  It is quite annoying to have to deal with the error each time one resumes from hibernate (system reboots and then asks me to go into safe mode). 

    Thanks to everyone for your help in advance.

    Yogesh
    Thursday, November 05, 2009 8:38 PM
  • Solution of my problem: disable the catalyst control center.
    Friday, November 06, 2009 7:50 PM
  • Good morning,

    I had (repeat had ) exactly the same problem. reference_by_pointer (which for me was "abacadabra" ) and codes : 41 and 63
    Could not restart or shut-down the PC without blue screen.
    Tried several things, without success.
    System information : motherboard ASUS P6T DeLuxe, processor Intel I7, mem 6GB, used Vista Ultimate 32-bit, changed to Windows 7 Ultimate 64-bit.

    During installation, Win 7 looks for driver updates and afterwards I checked via Windows update. So, I expected all drivers were OK.
    In the end I checked all drivers with the programm DriverGenius ( I don't receive commission ). DriverGenius found several newer drivers for Intel and Ralink components.
    The programm installs the new found drivers by himself.
    Be carefull; in 1 case a driver found by DriverGenius was older than the one installed, but the programm warns you before installing.
    Before, I did check the Intel site myself, but the site was too confusing for me.

    In the end, after DriverGenius finished the job, "Halleluhja ", I could immediately restart and shut down the PC without any problems.

    I hope this solution will help everybody with the same problem. Let me know by replying or at russgol@wxs.nl

    Jan        the Netherlands           73 years old.

    Saturday, November 07, 2009 7:16 AM
  • Go back to the original OS and wait for Windows 7 Service Pack 1.  Windows 7 has serious problems that maybe will not be fixed anytime soon.
    Tuesday, November 10, 2009 6:08 PM
  • Greetings

    Just had the exact same issue (log file below) Except I was saving a Word document to a thumb drive I've used a dozen times before, and used it on another PC after the crash without issue. This was the first time I've had this problem, and the system has been working quite well up until this. Have made no modifications to the PC; during the BSOD it indicated the error was with a CDBUF.sys (?) file; not sure as it was on screen for only a few seconds so I'mnot sure if that was the driver that was displayed. After I post this I'm going to try and reopen the word doc and save it to see if the same thing happens.

    CapWx


    Log Name:      System
    Source:        Microsoft-Windows-WER-SystemErrorReporting
    Date:          11/10/2009 9:41:21 PM
    Event ID:      1001
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      MARK-PC
    Description:
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000008e (0xc0000005, 0x8ac22d39, 0x9557b824, 0x00000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111009-44569-01.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-11-11T03:41:21.000000000Z" />
        <EventRecordID>5135</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>MARK-PC</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x0000008e (0xc0000005, 0x8ac22d39, 0x9557b824, 0x00000000)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">111009-44569-01</Data>
      </EventData>
    </Event>

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          11/10/2009 9:41:10 PM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      Mark-PC
    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.
    Event Xml:
    <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="2009-11-11T03:41:10.206800000Z" />
        <EventRecordID>5136</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>Mark-PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">142</Data>
        <Data Name="BugcheckParameter1">0xc0000005</Data>
        <Data Name="BugcheckParameter2">0x8ac22d39</Data>
        <Data Name="BugcheckParameter3">0x9557b824</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Wednesday, November 11, 2009 4:20 AM
  • Greetings

    This is just an update to my post from last evening. The same event occurred when I tried to save a Word doc on my 1 GB SanDisk Cruzer thumb drive. Been suing the drive for a few years under various iterations of Windows and have not had a problem til yesterday evening. The only thing I can think of was the PC had been on for 3 days straight without a reboot - overheat? Not too likely as it's in a cool basement. Plus, I'd put an extra fan on the box to increase air flow. It's a home built, just over a year old, and originally I installed Vista Home Premuim; upgraded to Win 7 Home Premium 2 weeks ago.

    My question is, since this is hosted on the MicroSoft site, I presume MVP's or actual MS techs/engineers are looking into this? From the various posts I've seen across the web it *could* be related to a variety of issues from faulty drivers, to power surges, to overheating,etc. I'm using an APC UPS; the PC is "cool" os I'm note sure what is next.

    Comments?

    CapWx
    Wednesday, November 11, 2009 7:26 PM
  • Same problem here.

    As with CapWx, I built my own CPU about 2 months ago. Running AMD Phenom(tm) II X4 955 Processor 3.20 GHz With 4.0 GB RAM - 32 bit OS. Installed W7 Professional on 10/24/09. Had approx. 7 BSOD reboots. Event viewer looks pretty much the same a everyone else. Memory check reports no errors. Like everyone else I'm at a loss. There is no way this many problems are related to hardware or driver issues. Has anyone talked to or had a live chat with microsoft tech support? It would interesting what they have to say.

    - <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="2009-11-08T15:01:07.061201900Z" />
      <EventRecordID>4981</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>ScottBrown-PC</Computer>
      <Security UserID="S-1-5-18" />
      </System>
    - <EventData>
      <Data Name="BugcheckCode">78</Data>
      <Data Name="BugcheckParameter1">0x7</Data>
      <Data Name="BugcheckParameter2">0x9a17f</Data>
      <Data Name="BugcheckParameter3">0x865fe</Data>
      <Data Name="BugcheckParameter4">0x0</Data>
      <Data Name="SleepInProgress">false</Data>
      <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
      </Event>
    Thursday, November 12, 2009 2:07 AM
  • The "Microsoft-Windows-Kernel-Power" and associated Event ID 41 are generic items that are encountered whenever there us an unexpected reboot, essentially.  Not all are caused by the same thing, but the causes are varied enough that this is not an uncommon thing to encounter.  Bad drivers and bad hardware are what causes bugchecks. Event ID 41 with a bugcheck code of 0 seems essentially to be a spontaneous reboot - really, really bad drivers, or faulty hardware, or a power-cycle, or bad power, or loss of power, etc.

    The varying bugcheck codes indicate different problems.  In your case, it appears that you have a bad driver that is playing badly with memory.  Standard procedure for dealing with this is to enable driver verifier on all non-MS drivers...
    Start->verifier.exe, create custom settings, next;enabled predefined settings, standard settings, next; Select driver names from a list, next;sort by provider, check the box for all non-Microsoft drivers, click Finish, reboot, and wait for the next bugcheck to occur; hopefully it will have additional details about the driver that caused the problem.  In the event your system won't boot with the verifier settings enabled, boot into safe mode, run verifier.exe again, and choose to delete existing settings and reboot...
    Thursday, November 12, 2009 12:57 PM
  • My Code is: i hope you can say somthing about it

    <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="2009-11-12T17:25:58.168820500Z" />
        <EventRecordID>4069</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>DevilBook</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">194</Data>
        <Data Name="BugcheckParameter1">0x7</Data>
        <Data Name="BugcheckParameter2">0x1097</Data>
        <Data Name="BugcheckParameter3">0x40d0006</Data>
        <Data Name="BugcheckParameter4">0xfffffa8005ababe0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Thursday, November 12, 2009 5:56 PM


  • Hi!

    Same herre!  Unexpected crashes and I do not have any idea - what the reason is!

    <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="2009-11-11T17:52:48.187500000Z" />
        <EventRecordID>1411</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>PC</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">209</Data>
        <Data Name="BugcheckParameter1">0x0</Data>
        <Data Name="BugcheckParameter2">0x2</Data>
        <Data Name="BugcheckParameter3">0x0</Data>
        <Data Name="BugcheckParameter4">0x0</Data>
        <Data Name="SleepInProgress">false</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>
    Thursday, November 12, 2009 8:03 PM
  • OK NC. Tried what you suggested had to take the second route and boot in safe mode and delete existing settings. Based upon your information and some that I received from a friend of mine, I believe this is driver related. Here's what I can tell you. As I did a fresh install of W7 the system crashed twice during installation. I was able to install W7 of the third try. I attempted to install a audio driver from a CD I got with my sould blaster audio card. System crashed twice. I uninstalled that audio driver and let windows update find and install a driver for that device. I thought the driver on the CD was not compatible with
    W7. Let me ask this. My friend indicated this was software/driver related otherwise the system would not reboot if there was a hardware conflict. Is that true? If there was a hardware conflict what would that be? As I mentioned before, this CPU is two months old and every component in it has a one year warranty.

    Antoher thing that I failed to mention previously, I've had IE error messages that IE has stopped working. I've also had applications freeze which I had to end using task manager. I don't believe the is an overheating problem. I have a fan in the side of my CPU the size of a sub woofer as well as one in the back. I could start uninstalling one driver at a time and let windows update find and re-install but I'm not sure this is the solution.

    Can I give you any other information that would be helpful to resolve these problems? I'm sure others above are just as frustrated as I am. At the point, I'm not sure where this leaves me.
    Friday, November 13, 2009 1:18 AM
  • 0xc2 (194) is another form of memory corruption.  Same suggestion - driver verifier...
    Friday, November 13, 2009 12:04 PM
  • Bad IRQL - again, try driver verifier (Force IRQL Checking, one of the standard tests IIRC).  May also be memory corruption (code at 0 tried to read from address 0 at IRQL 2).
    Friday, November 13, 2009 12:06 PM
  • Hardware conflicts can result in odd behavior, as the experience could depend on how drivers react.  

    Can you upload the minidump (from %systemroot%\minidump, e.g. c:\windows\minidump) for the crash you got when you tried booting with verifier enabled?

    Freezing applications may or may not be related to a bad driver.  Crashing applications may or may not be related to a bad driver.  Hard to say - best bet is to work on one thing at a time, I think, and see what progress can be made with the bugchecks...
    Friday, November 13, 2009 12:11 PM
  • Hi,

    My system is always rebooting spontaneously.

    System info: Windows 7  Processor Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz, 2670 Mhz, 4 Core(s), 4 Logical Processor(s)
     

    I called the distribiutor and he told me to downgrade to windows XP. What should I do?

    BCLR
    Friday, November 13, 2009 12:21 PM
  • Here my dump files sry i have some problems with SkyDrive i uploadet them on my space i hope this is okay.

    http://www.wbblite2.de/091109-20217-01.dmp
    http://www.wbblite2.de/111209-25022-01.dmp
    Friday, November 13, 2009 2:41 PM
  • I've been fighting this problem for 3 days! Finally figured it out.
    The problem is your system drive is slow to recover from a sleep state.  I switched out my 

    HITACHI Deskstar for a Western Digital Caviar Black WD1001FALS 1TB

    Sometime after sleep the drive totally disappears!!! This is a known problem at Western Digital.

    A work around is to set the drive power down time to never in POWER options.
    But this leads to a noisy sleep.

    Oh, and the other solution is to make the Hitachi the boot drive again. That's what I did!!
    • Edited by ArnieAZ Saturday, November 14, 2009 12:23 AM
    Friday, November 13, 2009 5:12 PM
  • Got nearly the same Problem.

    Changed my OS from Vista 32 bit to W7 64 bit. Only Changed my Hd from an (ols) ATA to a new WD sATA. System had been superstable under Vista 32 bit.

    Installed W7 2 Weeks ago - ran till 3 days ago absolute normal.

    Restarted the System one next mornig and shortly after the W7 loading screen appeared a bluescreen and reboot. Afterward System went in repairmode with no real result.

    Systemreport gives me the kernel power problem....

    This happend several times afterwards... ...but never when System was up and operating - only while booting W7!

    Set System back to a backuppoint shortly after Installation when the error didn't occure - same Problem...

    Changed from ide legacy to ahci in BIOS - first that seemed to work. But today again the System hang at bootup - no BS but hang until I had to switch off power supply.

    Now diabled the sleepmode of my WD-HD.


    I'm dissapointed about W7 and hope it'll get a fix. Why did the System ran the first 2 Weeks stable? Did a W7 Update caused the Problems?
    Friday, November 13, 2009 7:59 PM
  • @jc_ing

    If those dumps were from before verifier was enabled (the filename indicates that is the case), then please enable verifier as indicated, and post dumps that are gathered after enabling verifier.
    Saturday, November 14, 2009 12:45 AM
  • Hi NC, I have seen ur response on so many occasions in this forum. I dont' have much idea about the system settings. So I need brief steps to follow in order to solve the frenquent system shut downs with a blue screen and automatic restart after that. I brought a laptop before 15 days. System details are compaq persario cq40, AMD, Dual Core, 3 GB RAM, 320 GB hard disk.



    Critical

    I am getting the following when ever the system gets shutS down unexpectedly as said by other members of this forum, BUT NO ONE IS GAVE THE RIGHT SOLUTION

    1. Kernel-Processor-Power

    - System

      - Provider

       [ Name]  Microsoft-Windows-Kernel-Processor-Power
       [ Guid]  {0F67E49F-FE51-4E9F-B490-6F2948CC6027}
     
       EventID 26
     
       Version 0
     
       Level 4
     
       Task 4
     
       Opcode 0
     
       Keywords 0x8000000000000000
     
      - TimeCreated

       [ SystemTime]  2009-11-15T11:14:56.026852400Z
     
       EventRecordID 12315
     
       Correlation
     
      - Execution

       [ ProcessID]  4
       [ ThreadID]  48
     
       Channel System
     
       Computer raparthi-PC
     
      - Security

       [ UserID]  S-1-5-18
     

    - EventData

      Group 0
      Number 1
      IdleStateCount 1
      PerfStateCount 2
      ThrottleStateCount 0
      IdleState 01
      PerfState 34080000640000001A04000032000000

    2. Source: Kernel-Power

    Details[General]: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost

    power unexpectedly.

    Full Details:

    - System

      - Provider

       [ Name]  Microsoft-Windows-Kernel-Power
       [ Guid]  {331C3B3A-2005-44C2-AC5E-77220C37D6B4}
     
       EventID 41
     
       Version 2
     
       Level 1
     
       Task 63
     
       Opcode 0
     
       Keywords 0x8000000000000002
     
      - TimeCreated

       [ SystemTime]  2009-11-15T11:14:53.296841000Z
     
       EventRecordID 12313
     
       Correlation
     
      - Execution

       [ ProcessID]  4
       [ ThreadID]  8
     
       Channel System
     
       Computer raparthi-PC
     
      - Security

       [ UserID]  S-1-5-18
     

    - EventData

      BugcheckCode 26
      BugcheckParameter1 0x41201
      BugcheckParameter2 0xc03b08c0
      BugcheckParameter3 0x5dfac005
      BugcheckParameter4 0x85e5ba68
      SleepInProgress false
      PowerButtonTimestamp 0

    NEED HELP. AWAITING QUICK RESPONSE. PLEASE ADVISE.

     

    Sunday, November 15, 2009 1:06 PM
  • Having the same problems.

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         14-11-2009 2:24:59
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-14T01:24:59.401222700Z" />
        <EventRecordID>4431</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         12-11-2009 10:50:19
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-12T09:50:19.742825000Z" />
        <EventRecordID>4173</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         10-11-2009 16:02:26
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-10T15:02:26.900423500Z" />
        <EventRecordID>4005</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         10-11-2009 13:05:19
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-10T12:05:19.696024900Z" />
        <EventRecordID>3906</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         9-11-2009 15:07:15
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-09T14:07:15.306024200Z" />
        <EventRecordID>3518</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         7-11-2009 18:33:32
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-07T17:33:32.934820100Z" />
        <EventRecordID>3184</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         3-11-2009 9:16:17
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-11-03T08:16:17.340420800Z" />
        <EventRecordID>2148</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</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>

    Logboeknaam:   System
    Bron:          Microsoft-Windows-Kernel-Power
    Datum:         31-10-2009 8:26:35
    Gebeurtenis-id:41
    Taakcategorie: (63)
    Niveau:        Kritiek
    Trefwoorden:   (2)
    Gebruiker:     SYSTEM
    Computer:      slurp
    Beschrijving:
    Het systeem is opnieuw opgestart zonder eerst correct te worden afgesloten. Deze fout is mogelijk veroorzaakt doordat het systeem niet meer reageert of is vastgelopen of doordat de stroom is uitgevallen.
    Gebeurtenis-XML:
    <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="2009-10-31T07:26:35.324820800Z" />
        <EventRecordID>1572</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>slurp</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="BugcheckCode">244</Data>
        <Data Name="BugcheckParameter1">0x3</Data>
        <Data Name="BugcheckParameter2">0xfffffa8008b02b30</Data>
        <Data Name="BugcheckParameter3">0xfffffa8008b02e10</Data>
        <Data Name="BugcheckParameter4">0xfffff80002dd1240</Data>
        <Data Name="SleepInProgress">true</Data>
        <Data Name="PowerButtonTimestamp">0</Data>
      </EventData>
    </Event>




    This is really starting to be a problem, since this machine is powering my home mediacenter and I cannot rely on it. So an answer would be nice.


    Sunday, November 15, 2009 2:07 PM
  • Apparently I am having similar issues. My comp runs perfect until I open up a game. Sometimes I am able to play for a couple hours before it restarts, sometimes only for a few mins.

    MOBO: EVGA NVIDIA 780i SLI
    Processor: Intel Core 2 Quad Q9300@2.5GHz (OC'd to 3.0GHz)
    Ram: 8 Gigs
    OS: Windows 7 Home Premium (64 Bit)
    Video: EVGA NVIDIA 8800 GT x2

    Log Name:      System
    Source:        Microsoft-Windows-Kernel-Power
    Date:          11/15/2009 10:50:21 AM
    Event ID:      41
    Task Category: (63)
    Level:         Critical
    Keywords:      (2)
    User:          SYSTEM
    Computer:      DREAMMACHINE
    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.
    Event Xml:
    <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="2009-11-15T15:50:21.069200000Z" />
        <EventRecordID>7274</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="8" />
        <Channel>System</Channel>
        <Computer>DREAMMACHINE</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>


    Any Help would be appreciated
    Sunday, November 15, 2009 4:35 PM
  • i,

    I have a custom build PC that ran vista 64bit solidly for two and a half years, I never ever had any problem, but now three times this week I've had a restart of the computer when unlocking the PC on Windows 7 64 bit, and once whilst I was out the machine rebooted itself.

    Spec is
    - Core 2 Duo E6550
    - Gigabyte P35-S3 Motherboard
    - 4GB DDR 2 Ram
    - 2x Samsung 320GB Serial ATA Hard Drives
    - 450W Power supply
    - X1550 Graphics Card

    It happens randomly and windows 7 event viewer is worse than useless, and when the computer restarts there is nothing about the computer having recovered from an erorr like I've seen on windows vista machines that crash

    All I have in event viewer each time is
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    I've checked all the temperatures and everything and everything looks healthy. Needless to say I'm not impressed by the fact I've had more trouble with Windows 7 than I had with Vista from release day. The PSU has been checked and is fine.
    Sunday, November 22, 2009 8:52 PM
  • Everyone posting here,  can you have a look in your Motherboard BIOS and see if you have a INTEL C-STATE option.  If you do, try DISABLING it and see what effect it has.

    The ONLY way I could get my system to even install Win7 64bit was to disable the Intel C-State within the BIOS.  This C-State setting is part of the Processor frequency and power control.  By disabling it all you are doing is making the processor run at full frequency, thus full power all the time. 
    Monday, November 23, 2009 3:33 AM
  • Aleady tried that, never had any issues with installing at all, everything was smooth until this silly restarting which is really starting to annoy me.

    The irony is that for all the bad rep Vista got, I'm having trouble keeping 7's uptime higher than 4-5 days, when on Vista I only rebooted when I absloutely had to, and would frequently clock up months at a time.
    Monday, November 23, 2009 10:11 AM
  • hi for those in here check for speed step in bios if enabled try turing off as i turned off yesterday and to test for shutdown i was playing tf2(the game that gave random shutdowns) for 3 hours rebooted played again no issues and even booted in to game with out playing overnight with no shutdown if you have intel and have speedstep turn it off

    Edit: so it appears most people on this site have intels if this is true then it would either be c-state or speedstep causing the issue if you guys turn these off and the issue stops happening please reply with it worked or not and ur pc or laptop specs mobo cpu ram video card and os  like this

    Cpu: Intel® Pentium™ Dual Core T4400 (2.2GHz/800Mhz FSB/1MB cache)
    Mobo: Dell MotherBoard
    H277K(studio 1537 laptop)
    Ram: 4GB Shared Dual Channel DDR2 at 800MHz
    Video Card: Intel Graphics Media Accelerator 4500MHD
    Operating System: Windows 7 Ultimate Edition
    Resolved issue by turning off Intel SpeedStep
    Tuesday, November 24, 2009 8:18 PM
  • Ok, I got around my issue (I will not say fixed as that implies it is gone - it is still there a and I shouldn't need to turn C-STATE off).

    CPU: Intel Xeon X5550 x 2 (2.66GHz/1333Mhz FSB/8MB Cache)
    Mobo: Supermicro X8DA3
    Ram: 6 x 4GB Crucial Reg ECC 1333Mhz
    Video Card: ATI Radeon HD 5870
    OS: Win 7 Ultimate 64 bit
    Resolved by disabling Intel C-STATE
    Wednesday, November 25, 2009 6:08 AM
  • Got around my issue by changing power settings as others suggested, but it just a band-aid solution. Don't like running at full power all the time unless I shut down...

    Cpu: AMD Athlon™ II X4 620 Quad-Core Processor 2.6GHz/4000MHz FSB/2MB L2 Cache
    Mobo:  NVIDIA MCP78V

    Ram: 6GB Shared Dual Channel DDR2 at 6400MHz
    Video Card: NVIDIA GeForce 9100 Motherboard Integrated
    Operating System: Windows 7 Home Premium Edition
    Resolved issue by disabling sleep mode, and in Power Options, Processor Power Management, set minimum processor state to 1% and maximum to 100%

    3 days with no bsod after 2-3 every 6 hrs or so while multi-tasking down/uploading files to FTP, e-mailing, and working with Adobe Illustrator

    Note that I'm running AMD - it's not just those with Intels with the problem....
    Wednesday, November 25, 2009 5:00 PM
  • yes i actually did some looking around seems amd and intel have powernow! and speedstep or c-state its the same thing different names its to speed up slow down processor try setting power settings to min cpu state 100% and max to 100% seems to be something with the processor state being flux from speedstep or power now its something that needs to be fixed but atleast it can be fixed for now
    Wednesday, November 25, 2009 7:46 PM
  • OK, The problems everyone is describing sound similar to mine. I am trying to add Ram to my PC but every time I start up after adding the second stick  my PC shuts down and restarts with similar BSOD as mentioned above. I have now tried 3 different sticks( I thought they must have been bad so i returned them to the store and got new ones) yet I am still having the same problems. I can switch each stick and trade slots but my problem still exists. When I only use one stick my pc works fine. When I add the second stick it crashes. Any ideas? I am running Windows 7 and Im starting to believe the MAC commercials......Im losing faith.Please help.
    Wednesday, November 25, 2009 11:45 PM
  • sounds like u actually have a hardware problem with the 2nd ram slot on ur mobo not the os if ur able to swap to other bank n run fine then that would point to hardware fail maybe get ur pc checked
    Saturday, November 28, 2009 6:06 AM
  • Thank you for the reply. I can place the ram in either slot and it works fine so I don't think it is the MB. It only crashes when i use a second stick in either slot. Any more ideas?
    Saturday, November 28, 2009 6:29 AM
  • To all above,

    Its been a while since I have responded. I see that other are logging in to report similar problems. I have fixed my problem. NC had indicated that I had a bad
    driver playing badly with my memory. Turns out that is right. I downloaded  the chipset driver compatible with Win7 and installed. So far so good. No BSOD

    since. Hope this info is useful to all.
    Saturday, November 28, 2009 6:21 PM
  • Hey!

    Unfortunately I have encountered similar problem. My notebook crashes and turns off, but in my case only while playing games. I wouldn't mind if the games were uber hi-tech, advanced mumbo-jumboes, but my computer crashes on games which are 4 and more years old. So my guess is, that this is not happening due to overheated CPU or actually any part of the hardware. I have to add, that my win 7 pro x64 (build 7600) is only a week old. I had win XP x64 beforehand and never encountered any similar problems at all. 
    Things I've done so far:
    - memory checked
    - bios updated
    - all drivers are up to date (also checked them with verifier.exe)
    - set up the power options to high performance

    I havent tried the solution with speedstep, because I dont have it in my BIOS setup (which kinda bothers me).
    I repeat: I don't have any problems during normal/moderate usage of my computer!

    Games I tried: Wolfenstein: Enemy Territory and Guild Wars. Every time I end up with random power shutdown, independent of anything which is actually happening on the screen. (The CPU usage widget shows around 20% od CPU usage while GW is in windowed mode)

    The crashes are not generating minidump files, only usual logs same as stated above:
    - <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="2009-11-30T11:29:45.660412600Z " /> 
      <EventRecordID>7738</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="4 " ThreadID="8 " /> 
      <Channel>System</Channel> 
      <Computer>Seb</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>

    It seems to me, that my OS is dealing with some power management issues which cause crashes...
    Any ideas?
    Monday, November 30, 2009 12:47 PM
  • POSSIBLE SOLUTION:
    I may be able to add some good insight into this problem having had spontaneous shutdowns of Windows 7 since June of '09 when I started testing the beta version. It is now Almost December and I have had great luck in figuring out this problem. I am now on 6.1.7600 release version of Win7. I do believe this issue is a memory-related issue and not a power management issue. Yes, it is possible that power management may still be a small minor problem occationally to spontaeously reboot a computer but under the stresses of a high-end game (and having the power options disabled), if it occurs, its most likely something else.

    I bought premium memory from Corsair the Dominator model (2 sticks of 2GB). I use my PC mostly for high-end, maxxed-graphics gaming which requires my PC to be very well tuned and responsive 100% of the time and reliable 100% of the time with no exception. Any deviation of this is unacceptable. I do not overclock anything. If you buy good components you will not need to.

    Let me deviate for one paragraph to explain how I got to believing is was a hardware issue and not software/OS. I have a dual-boot machine. C: drive is WinXP Pro SP3 and D: drive is Win7 release. Two physically separate drives. I had the beta version of Win7 on a 3rd drive even, but now its not even connected at all since I started using the release version. I could go into either XP or Win7 and test various software and how it worked. After the stability of my games/apps met my stringent tests, I ported all my applications to Win7 drive and finally after so many years of running XP (probably 6 or more, I skipped the whole buggy Vista ordeal), reformatted my XP drive after successful app ports and reinstalled it clean. I reinstalled some key games/apps just to have as a backup in case some drastic problem with Win7 surfaced down the road. I started to notice some key games and apps I would run under XP to spontaneously reboot the machine! Holy cow, I thought only Win7 was doing this! After having a stable non-rebooting XP drive after a clean reinstall of XP the same issue started happening under XP. This is why many ppl are saying its not happening under Vista/XP, when was the last time they did a clean reinstall of their old OS? Yes, its possible XP and Win7 are using similiar device drivers or whathaveyou but my gut feeling was there was a hardware issue. So my hardware testing began. I am a former paid bug tester so my testing process for hardware/software is pretty methodical yet creative enough to overcome or expose bugs. I knew I could find the answer to this with testing and extensive internet research. Now back to our program...

    I do feel this issue is somehow tied in with the timing of the memory chips, how the processor handles these memory chips and how the chipset of the motherboard interacts with the other 2. These 3 CORE components are absolutely crucial to being tuned exactly to accommodate the stresses and burden in a timely and responsive fashion. Heat is not an issue in my rig as I have a Coolermaster High Air Flow (HAF 932) that keeps everything at least 10C degrees cooler then normal. Its a beautifully engineered case and I highly recommend it. The memory I have is specced to run at 1066mhz, however I have noticed that even when running the memory faster (hotter) at 1066, it becomes more stressed over time because the motherboard is actually not able to have the correct timings on it. The timings of the memory i have is 5-5-5-15 2T @ 2.1 volts (for either 1066 or 800mhz). No matter how directly I set these timings and then boot into my Memtest86+ tester CD the timings always test at 5-5-5-18 @1066mhz!!! This slight deviation can have catastrophic consequences under stress in an OS. Either OS, XP or Win7. The bios has them set correctly and they display correctly in the BIOS and even in the OS diagnosis packages but when u run a beefy memory tester the reveal their true nature as having incorrect timings. Hence all the spontaneous reboots I have been having and hence all the frustrations. Don't use the built-in Win7 memory tester to diagnose your problem. Yes, it will tell u have a problem but its extremely basic and you will never know what timings its testing at for certain. Had I only went by the basic Win7 tester it would never have revealed to me the true timings of the memory under stress.

    This is where the processor comes in. I strongly feel that these memory modules require a processor that has ECC on it (Error-correcting control) the ECC works in relation to the memory to circumvent any potential memory errors before the motherboard interacts with the memory. My current processor does not have ECC but I will be getting one within 1 week at most, that does. To reduce this stress I have taken the modules down to 800mhz 5-5-5-15 2T @ 2.1 volts. These are manufacturer settings for either mhz level not my own. I do not overlock my PC at all just use premium components and tune everything softwarewise but never overclock. Stability is extremely important to me versus speed.

    Bumping this memory down has revealed an extremely stable system at the expense of a tad slower memory and the spontaneous reboots (even when the OS was running idle overnight) have stopped. I diligently check Win7 for Event errors after I wake up from leaving my system running overnight. Since the computer is to autoreboot after a shutdown I may not catch it in my sleep but the event viewer does. These shutdowns have stopped in-game and when the system is idle completely. Memtest86+ shows them testing now correctly at 5-5-5-15 @800mhz with no errors and not 5-5-5-18 @1066mhz with voluminous errors. This is a very good thing!

    My motherboard is a very reliable Gigabyte motherboard and I love it. It can accommodate the memory at 1066mhz, my chips are specced for 1066 but this motherboard loves them at 800mhz moreso. My motherboard can run the memory at 1066mhz for days then once in a while, due to stress i put it under, BAM, spontaneous reboots happen sequentially back-to-back in rapid succession. Every motherboard has its own preference for identically-specced memory chips. Its like a marriage it seems. There are many pretty girls but only one is just right =) My next step in this success is to get a fully ECC-capable Phenom II processor within 1 week, bumping the memory back to 1066 and doing extensive memory overnight burn-in tests to reveal if errors occur. Each memory stick resides in its own channel not both in the same channel. It is running ungauged as the motherboard manufacturer recommends. I follow manufacturer recommended settings for every component by calling their tech support to verify BIOS settings. This creates a very reliable and stable gaming RIG.

    I just want to point out that I have tried now 3 identical memory module sets from Corsair and the first 2 tested with some errors where is the 3rd set running at 800mhz tests perfectly overnight. Occasionally I run an overnight test to re-verify they are remaining stable. An ECC-capable processor should be able to handle an occasional error or 2. Not having this I am forced to lower the memory to stabilize it. My memory modules, because they are premium are of better quality then the motherboard is. I have to put the voltage to +0.03 volts to get them to 2.1 volts and this is in the red area in the BIOS. So the memory is a better brand then the motherboard BIOS is. I am at max voltage in the BIOS to run them at manufacturer recommended specs. This is probably the reason why the first 2 sets started failing by my being too cautious and undervolting them @ 2.0 volts to keep them out of the "WARNING" red area of the BIOS setting. I now follow strict manufacturer recommended settings of the component regardless of the warnings of the BIOS. The techs at Corsair told me on several occasions, that undervolting can physically damage the memory just as overvolting can. This was news to me as i have never heard of this before when it came to memory modules.

    So to wrap up:
    1) I strongly recommend downloading the freeware memory tester @ www.memtest.org and running an overnight test to check for errors. Memory is extremely volatile component and must be monitored. Any deviation and error can spontaneously reboot or crash or lockup the system.

    2) Verify the timings of your memory are exactly as set in your BIOS and they are testing at this timing settings exactly, no deviation is acceptable.

    3) Verify you have a processor with ECC on it to accommodate occasional errors that may come up over prolongs periods of computer use. 1-3 errors over a period of a week are an acceptable amount and the ECC can accommodate these but anymore and the system will crash.

    I hope this this helps someone out there and Happy Gaming under Windows 7 (THANK YOU MICROSOFT, for finally after 20 years of OS's creating a beautiful and reliable OS!!!)

    Monday, November 30, 2009 2:21 PM
  • Passionfly1, you have pointed out some very importatnt matters!
    However as a laptop user I find my BIOS settings severly simplified and I'm unable to adjust such things as memory voltage etc.
    Monday, November 30, 2009 4:14 PM
  • Passionfly1, you have pointed out some very importatnt matters!
    However as a laptop user I find my BIOS settings severly simplified and I'm unable to adjust such things as memory voltage etc.

    Well, the good news is if u run Memtest86+ off of a CD it will tell you the timings that its running at. All you have to do is find out what the correct timings are and make sure that they coincide with what a dedicated memory burn-in tester (Memtest86+ but there are others I'm sure) is saying they are testing at. The 2 should match identically. If the memory chips you have in the laptop are supposed to be at those timings and voltage then your ok, if not it may be time to contact your laptop manufacturer and let them know a dedicated memory tester is revealing incorrect timings for the memory modules that they themselves have specified should be on those memory modules. But before you get ahead of yourself make sure its not failing first with correct timings THEN worry about how in the heck your gonna get the BIOS to set them correctly. Don't cross that bridge until you have to. You may not even need to, tbh.

    If the memory tester reveals incorrect timings based on your research the manufacturer will be stuck in a no-win situation and have to take action. If they don't release a BIOS update then the timings they specify are invalid and if the timings are valid then they must release a BIOS update to correct this. It's possible you have correct timings but this is just a worst case scenario if you do encounter it.

    Laptops are proprietary computers meaning they can't have everything inside replaced with some aftermarket item off the shelf (some parts can be but most can't and need specific manufacturer parts) but you have to go directly to the source who made your laptop and find out the timings of the memory. You can always just ask what specific memory module is inside this laptop and then contact via phone the manufacturer of this memory to find out from them based on PART NO not MODEL no. of the memory module timings they should be at. A PART no. determines what point in the time the like modules where created together and a MODEL No. is just a fancy way to tell different specced components apart from each other.

    The rule of thumb I go by is the smaller a computing device is the more proprietary it is and doesn't have the luxury of swapping out parts or having robust information on it. A good example of this is iPhone or your Cell phone/PDA. Which are in a sense are little tiny computers in the palm of your hand that just happen to excel at telephony applications. But nonetheless they are little tiny computers or sublaptops if you look at them.
    Tuesday, December 01, 2009 6:35 AM
  • Timings and voltage checked, everything is as it's supposed to be.
    I've decided to check if all of my drivers are really up to date, so I have downloaded driver-helper-sort of program ("DriverMax"). It stated that my chipset and couple of other drivers are old, so I updated all of them to the newest versions showed by the program.
    Unfortunately this also didn't do the job. Plus I had the same kernel power error while streaming video from the Net (new situation).
    I'm starting to get irritated, because nothing seems to work and I loose my time on pointless struggle with drivers, clean boots and so on.
    Are there any software programs which can be used to adjust te voltage level for hardware components? Except BIOS of course...
    Wednesday, December 02, 2009 3:10 AM
  • Well there are software out there that handle power regulations and such but if you say they checked out and you have the correct timings by calling the memory manufacturer or checking their website then external software to control timings will be irrelevant at this point. Your also trying to solve a hardware issue with software. That's cheating, you can't do it that way. lol

    I can point you in a correct direction however. Since I have no clue on your system specs I'm going to be general and let you determine how to solve this best.

    In order for a sudden shutdown to stop occurring one thing has to be certain. Your motherboard, processor and memory need to have the correct specs to be able to run together at the desired speed. I'll give you an example. If you have 800mhz memory and your processor is say 2.4-2.8 Ghz processor and you want to run the memory at say 1066mhz (which they are designed to run at) and the motherboard will run at you MUST have a processor that will accommodate this speed. 2.4-2.8 Ghz will not be enough to run them at 1066mhz.....UNEQUIVOCALLY. What is the spec of the processor? This is something the motherboard manufacturer can only tell you. Are you starting to see how all 3 are interrelated to each other?

    If in the above example, you are running your memory at 1066 mhz, and the motherboard is specced to be able to, you need to call the motherboard manufacturer's tech support and ask them a simple question. Can the processor I have (give them your processor type and model) run my memory at 1066mhz (or whatever speed you are running them at now)?

    You may be pleasantly surprised that it may or may NOT be able to accommodate the memory at this speed without overclocking the processor, therefore you will need to either A) overclock the processor (which I do not recommend) and risk frying it or B) get a processor to accommodate the memory at the 1066mhz speed. A processor must be at certain minimum limits in Ghz and other factors to run memory at specific speeds unequivocally. Only the mobo manufacturer can give you these specs. I can not since I have no clue what you have and if I did I'm not a tech for that specific part to know its full tolerances. That means you can run them now but to avoid sudden restarts they must be set exactly. Sudden restarts are due to a lack of anyone of the 3 CORE components not being synced with each other. Most motherboard makers have a compatible listing of acceptable processors for your motherboard. Check this first, but ALWAYS call their tech support and get it from the horses mouth.

    I'll give you another example. Every SINGLE/DUAL CORE processor from AMD CAN NOT unequivocally run memory at 1066mhz. They must be triple or quad core to support memory at 1066mhz or higher. Will the memory run in your PC at 1066 with a dual core, YES! Will it do sudden shutdowns because they are dual and not tri or quad core, YES!!! This is the reason you must call them and ask for their technical advice on choosing the correct processor for the memory you have and the speed you want to run them at. The specs for your motherboard will show it supports 1066 mhz memory, the mobo will support dual-core processors but they will not be recommended to work TOGETHER . This one of the oldest marketing tricks in the book. To beef up the specs on components to make it look like it can support just about anything but put together they fail and you crash and you get frustrated and you want to kill something. Its not so much the number of cores the will be looking at to tell you this its the other specs like channel speed, caches sizes, etc. of the processor you are asking about that determine how fast (how hot) a memory module can go and be reliable so as not to cause a sudden restart. Every DUAL core processor I've seen has inferior specs to meet 1066+ mhz memory requirements. I don't care if its DDR2 or DDR3 memory. Only when you start to look at TRI and QUAD core processors do the specs start to ramp up sufficiently to run them hot.

    All you have to waste is time since most tech support have 800 numbers and you can ask them questions for a long time since you were probably waiting up to 15 mins to connect with them. They do want to help and are a tremendous wealth of knowledge and information that you for FREE when you buy their products. This is what they are there for, to help you!

    Every mobo, memory and processor all have tolerances of what they can support for the other 2 components that are rarely if ever revealed blatantly on the box you bought them in or the website. You must be diligent and do your homework by actually calling each of the 3 tech support to see if the other 2 components are support and will work in conjunction with one another. You can go by specs all you want and realistically this should be enough but you will be incredibly surprised what a tech tells you and what you read from specs somewhere else. The disparity of what is written on a website and what you hear a tech say to you can be the exact opposite in some cases!
    Wednesday, December 02, 2009 5:57 AM
  • Hi,

    My newly built PC running Windows 7 64-bit is also rebooting spontaneously.  Sometimes when I am trying to launch an app, and sometimes when I am doing nothing at all.  It started with locking up for no reason and now my system prefers to spontaneously reboot.  Event viewer shows the kernel-power failure error.  

    My system is a Core i5 running 4GB of DDR3.  It is not over-clokced and I am not having system overheating issues.  I ran windows memory diagnostic twice and it found no errors both times.  I initially had Intel speed-step disabled and I re-enabled it after I started getting this error, though it made no difference.  I have run various malware detection programs and no malware/spyware/or other viruses are present.

    EDIT: I am also running a Sapphire Radeon 5770 HD graphics card.  I have disabled the Catalyst Control Center as someone recommended, although I have the latest drivers so I do not understand why that would be the problem.  I also set the power settings to never turn off the monitor or computer as someone else suggested.  If the problem truly is either of these I would be surprised and it would suggest a compatibility issue that could be remedied with a later software update on the part of ATI or Microsoft.

    The event viewer log is here:

    - <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="2009-12-02T14:49:11.952018300Z" />
      <EventRecordID>13079</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Grant</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>

    Wednesday, December 02, 2009 3:56 PM
  • Awe ____!  It rebooted again after I tried all of the things from this thread >:(

    I don't want to lose my data to corruption. Someone please help!  This is making working on my desktop impossible!

    More info, my power supply is a brand new Corsair 650TX, so it shouldn't be the problem.

    I don't know what a minidump is or how to find that file.  Would someone please walk me through the process so that I can post it for you if that will help.  I am at my wits end about what to do about this issue (as many of you here may be as well). 

    EDIT: Side note that I find interesting.  The problem (reboot) doesn't happen when my wife or I are streaming audio from any of numerous online radio stations.  I am able to consistently operate my dektop for hours as long as I am listening to radio online.  The same thing goes for Hulu and other streaming video formats. :/ ???? Curious.
    Wednesday, December 02, 2009 5:26 PM
  • Awe ____!  It rebooted again after I tried all of the things from this thread >:(

    I don't want to lose my data to corruption. Someone please help!  This is making working on my desktop impossible!

    More info, my power supply is a brand new Corsair 650TX, so it shouldn't be the problem.

    I don't know what a minidump is or how to find that file.  Would someone please walk me through the process so that I can post it for you if that will help.  I am at my wits end about what to do about this issue (as many of you here may be as well). 

    Based on your earlier response you did not do what I recommended in my earlier post:  "I ran windows memory diagnostic twice and it found no errors both times." Run Memtest86+ from www.memtest.org not the built in windows memory tester. I clearly stated above to do this and not the ridiculously simple and uninformative Windows memory tester. Burn the ISO onto a CD and run the CD from boot. When the test is running, verify the timings you see in the upper part of the Memtest screen with the correct timings you need to have from the memory manufacturer. Call the memory maker tech support and ask them the correct timings you need for the speed the are running at. For example, if you are running at 800mhz make sure the settings are 5-5-5-15 and 2T at 2.1 volts. This is just an example as mine run at, not what yours can be. The BIOS settings needs to have the timings set to match the Memtest86+ (version 4.00 is  out now) testing timings EXACTLY . If you set in the BIOS 5-5-5-15 2T and Memtest is showing them testing out at 5-5-5-18 2T, you will have a disparity which will cause sudden restarts.

    Verify by actually calling the motherboard maker tech support, that the processor you have is enough to run the memory at 800 mhz (in this example, it may be different on your system). If the processor is too weak to run memory at the speed you are running at it will cause sudden restarts. If you are running a dual or single core processor and you are running memory at 1066 mhz or faster this will cause sudden restarts. You need the specs of a processor that come in the TRI and QUAD core flavors only to run memory that hot or hotter. Its not how many cores the processor has that's the key its the specs that quad and tri cores have that allow memory to run that much hotter, with stability.

    Your 650w Power supply is adequate for your system. This is not the problem. Your software updates are adequate. This is not the problem. You can reinstall XP clean and run some intense app and it will also start to have sudden restarts. So Windows 7 is not the problem. The problem you are having is HARDWARE in nature to cause sudden restarts. You have some sort of unbalanced configuration between the memory, processor and motherboard being out of sync of each other. THIS IS THE PROBLEM. One of these 3 components will need to be replaced or upgraded or even downgraded to allow the other 2 to run them efficiently together. Any disparity in one of these 3 component settings or specs and your computer will have sudden restarts.
    Wednesday, December 02, 2009 6:38 PM
  • Okay, I will try getting the RAM specs and running memtest86+, however I am not convinced it is the memory. I found that it did lock up once while I was streaming radio, though I was running sfc /scannow with an elevated command prompt, so that might have choked the system. It was able to complete sfc /scannow in safe mode without detecting any integrity issues.

    I have an ASUS P7P55D LE motherboard that is designed to run both the processor and the RAM I have installed.

    My processor is an Intel Core i5 750 which is a quad core and therefore not likely the same problem as the gentleman with the Core 2 processor.

    My  RAM, brand I forget but I will look up, is 4GB (2x2GB) PC3 12800 DDR3 1600MHZ DIMM 240PIN.
    I ran CPU-Z and the following screen shot shows my memory stats:

    http://i61.photobucket.com/albums/h45/natetheblade/Memoryinfo.jpg Btw: Is there a way to show images on this board?
    • Edited by njrgrant Wednesday, December 02, 2009 7:08 PM
    Wednesday, December 02, 2009 7:01 PM
  • Okay, I will try getting the RAM specs and running memtest86+, however I am not convinced it is the memory.

    I have an ASUS P7P55D LE motherboard that is designed to run both the processor and the RAM I have installed.

    My processor is an Intel Core i5 750 which is a quad core and therefore not likely the same problem as the gentleman with the Core 2 processor.

    My  RAM, brand I forget but I will look up, is 4GB (2x2GB) PC3 12800 DDR3 1600MHZ DIMM 240PIN.
    I ran CPU-Z and the following screen shot shows my memory stats:

    <a href="http://s61.photobucket.com/albums/h45/natetheblade/?action=view&current=Memoryinfo.jpg" target="_blank"><img src="http://i61.photobucket.com/albums/h45/natetheblade/Memoryinfo.jpg" border="0" alt="Photobucket"></a>

    your processor only supports 1066 and 1333 mhz only, not 1600 mhz, are you running them at 1600 mhz? This may be your problem. Who is the memory chip maker of your RAM? Different chip makers can have diff timings for identically specced RAM.

    Lawl, "I have an ASUS P7P55D LE motherboard that is designed to run both the processor and the RAM I have installed." typical marketing trap ppl fall into. Yes, they are specced to run these components individually, but not necessarily TOGETHER at the same time. My mobo can run memory at 1066, my mobo can run an Athalon X2 processor but if I run both at the same time I get a sudden restart because the processor can not handle memory running that hot.

    What did the motherboard tech support say to you after u talked to them as a recommended processor to have to run memory at 1600 mhz? I bet you anything it wasn't an Intel Core i5 750.
    • Edited by passionfly1 Wednesday, December 02, 2009 7:18 PM
    Wednesday, December 02, 2009 7:08 PM
  • Holy cow! You're right. Thank you for your help passionfly1. What a novice move on my part, though this is the first PC out of several I have built where I have run into this issue.

    I changed it and so far it is working, but I am obviously not an expert.

    Do you think that I can change the DRAM frequency to 1333Mhz in the BIOS and have it run alright???
    Wednesday, December 02, 2009 7:17 PM
  • Holy cow! You're right. Thank you for your help passionfly1. What a novice move on my part, though this is the first PC out of several I have built where I have run into this issue.

    I changed it and so far it is working, but I am obviously not an expert.

    Do you think that I can change the DRAM frequency to 1333Mhz in the BIOS and have it run alright???

    take a look at the specs here http://ark.intel.com/Product.aspx?id=42915 It clearly shows in the Memory Specifications if only supports 1066/1333 mhz. If the timings are set correctly as per the tech support of the memory manufacturer @ 1333 your system should run just fine. Your timing settings can be different for 1066 then for 1333 tho. Its best to just call them and get it from them directly. If you go off a timing value off some website it may wrong and inaccurate since the website has no knowledge of other components in your system to take into consideration to get exact memory timing settings. Yes, the timings for 1066, 1333 and 1600 can all be slightly different but not necessarily so. I've seen them slightly different for diff speeds but that's based on how they are made and vary from one manufacturer to the next.

    Notice even tho your processor is a quad core it still can not support these higher end 1600 (very hot) memory speeds. I'm pretty sure only the quad i7's are capable of doing this. But again call the mobo tech support and get it from them directly. The 3 CORE components play tug of war with each other. If you pull too hard with one (1600mhz) the other 2 react and STRONGLY!
    Wednesday, December 02, 2009 7:20 PM
  • Problem solved for me and...I pity the fool, which is myself. Win7 puts more stress to hardware, thus it gets hotter than on XP. I've checked the temperatures during gameplay and wow, my gpu reached 100 celsius degrees. Needless to say the notebook shutted itself down just seconds after. The problem was stupidly simple - dust got into my cooler and some components and proper ventilation was impossible. I can't believe I forgot to check that before.
    To all notebook users - remember to clean the dust from your hardware regularly, we are far more voulnerable to overheating!
    Thursday, December 03, 2009 7:31 AM
  • Problem solved for me and...I pity the fool, which is myself. Win7 puts more stress to hardware, thus it gets hotter than on XP. I've checked the temperatures during gameplay and wow, my gpu reached 100 celsius degrees. Needless to say the notebook shutted itself down just seconds after. The problem was stupidly simple - dust got into my cooler and some components and proper ventilation was impossible. I can't believe I forgot to check that before.
    To all notebook users - remember to clean the dust from your hardware regularly, we are far more voulnerable to overheating!

    I'm not so sure if this is entirely true. I have been monitoring my temps from when I was using XP from June and back and when I switched over to Win7 beta in Early July and now under Win7 when it was released. I have an extensive record of my temp settings I have preserved for a long period and It does seem to me my system is running much cooler now. How it may be affecting notebooks may be different under Win7 then XP but from a desktop POV I'm actually running overall about 5 degrees C cooler now over a long period of monitoring temps.

    But again you may be correct when it comes to notebooks. I'm not compiling data on those types of PC's
    Thursday, December 03, 2009 8:35 AM
  • I can quite categorically say it is nothing to do with memory in my situation - it most certainly is to do with how Win7 interacts with the CPUs.

    I have 2 Xeon X5550 on a Supermicro X8DA3 running Crucial memory at 1333mhz - all in accordance with the specifications of manufacturer PLUS it is ECC Registered RAM.  I even ran MemTest for 24hrs continuous on this system without a single fault. I also happened to install Ubuntu 9.10 without a problem, and guess what OpenSolaris 6.2009 installed perfectly and ran perfectly as well.
    Which OS didn't Win7 64bit.

    Initially with the two physical CPU's installed Win7 would net even install - it would get to a differing point each time (and believe me I tried MULTIPLE installs) and just power down ie completely shutoff, just like pulling the plug.

    Now what did work was REMOVING a cpu - now with only one Physical CPU I could get it to install and run.  As soon as the second CPU was put back in - back returns the power down issue.  Booting into Safe Mode allowed the system to boot cleanly with NO power downs - and before you ask - not a single third party or other software was installed - this is the bare initial MS install from the DVD - so ALL Microsoft software!

    I have 2 x 4 cores + 2 x 4 hyperthreads total from the two XEON X5550's.  So while in safe mode I set the number of CPUS available to the system as 15 ie one less than total and rebooted.  What happened next - it works, but not with 16!! Explain that one.

    So I then knew it is CPU related and thus systematically (by disabling every BIOS option available to do with the CPUs) re-instated each one in turn.  The one that was causing the issue was the Intel C-STATE value.

    The question that needs asking is WHY is Win7 unable to correctly handle or interact correctly with power states of the latest CPU's? Top the extent of not even installing?
    Thursday, December 03, 2009 10:13 AM
  • This may be of interest, 'Intel support community'

    John
    Thursday, December 03, 2009 11:57 AM
  • It's got nothing to do with Intel as far as I am concerned, as it's happening on a Turion X2 64 bit 2.2Ghz CPU machine for me as well as my Intel Desktop.

    No bluescreens, just reboots - meantime I've upgraded to Vista which has been solid on both machines for a couple of weeks now, for sure not my hardware.

    For me Windows 7 has been far far more of a pain in the enck than Vista ever was,
    Thursday, December 03, 2009 1:12 PM
  • Thank you for your help.  Getting in touch with the company I got the RAM from and getting the proper timing settings really did the trick.  I have been running the computer for several hours, even stressing it with games, and I have not had a single re-boot.  Lesson: next time double check the RAM and motherboard to make sure every spec is compatible so that I don't have to play with these settings.  Somehow I must have gotten 1066 and 1600 confused.  Give passionfly1 your vote!
    Thursday, December 03, 2009 6:30 PM
  • I can quite categorically say it is nothing to do with memory in my situation - it most certainly is to do with how Win7 interacts with the CPUs.

    I have 2 Xeon X5550 on a Supermicro X8DA3 running Crucial memory at 1333mhz - all in accordance with the specifications of manufacturer PLUS it is ECC Registered RAM.  I even ran MemTest for 24hrs continuous on this system without a single fault. I also happened to install Ubuntu 9.10 without a problem, and guess what OpenSolaris 6.2009 installed perfectly and ran perfectly as well.
    Which OS didn't Win7 64bit.

    Initially with the two physical CPU's installed Win7 would net even install - it would get to a differing point each time (and believe me I tried MULTIPLE installs) and just power down ie completely shutoff, just like pulling the plug.

    Now what did work was REMOVING a cpu - now with only one Physical CPU I could get it to install and run.  As soon as the second CPU was put back in - back returns the power down issue.  Booting into Safe Mode allowed the system to boot cleanly with NO power downs - and before you ask - not a single third party or other software was installed - this is the bare initial MS install from the DVD - so ALL Microsoft software!

    I have 2 x 4 cores + 2 x 4 hyperthreads total from the two XEON X5550's.  So while in safe mode I set the number of CPUS available to the system as 15 ie one less than total and rebooted.  What happened next - it works, but not with 16!! Explain that one.

    So I then knew it is CPU related and thus systematically (by disabling every BIOS option available to do with the CPUs) re-instated each one in turn.  The one that was causing the issue was the Intel C-STATE value.

    The question that needs asking is WHY is Win7 unable to correctly handle or interact correctly with power states of the latest CPU's? Top the extent of not even installing?
    I have to totally agree with you here Windows 7 has issues in 2 areas I have noticed, autoplay and thumb drives and power states in any flavor they come in whether its C states or sleep mode or power down mode and waking up. There is something seriously wrong with Windows 7 and how it handles power states. Now that I've got my hardware stability under control my next problem to tackle with Windows 7 is drilling them on figuring out what in the heck is going on with the power states with Windows 7.

    I also have to agree that Win7 is interacting with the CORE 3 components way more aggressively then previous OS's. This may be a 64-bit versus 32-bit OS issue. I am wondering if running processes with the "*32" designator may somehow be causing strange occurrences to happen in whats supposed to be pure 64-bit OS. Its almost impossible to not run some 32-bit software in Windows 7 since so many developers have yet to come out with pure 64-bit code for their drivers, applications.

    Its sad that the hardware we have available is completely outpacing the software we have to run on these modern machines. Software developers are going to have to start writing aggressively to catch up to all these new hardware speeds.
    Thursday, December 03, 2009 7:27 PM
  • This may be of interest, 'Intel support community'

    John

    2 posts caught my eye in this thread:

    "It's not just Win 7 that has problems, it's XP x64 and Linux as well."

    and

    "I've googled quite a bit of stuff on this problem, and I've found that at least Gigabyte boards have the same issue.   I haven't heard back from intel on the issue I reported yet.   Bleeding edge technology is always the same.  At least I'm stable with EIST off...http://forums.tweaktown.com/f69/ga-p55-ud3-i5-750-windows-7-x64-rtm-very-unstable-34410"

    I've had power state problems happen under XP a few times and I have had issues with the power states with most of the Gigabyte motherboards I've owned. I'm a Gigabyte, Corsair and AMD fan and have had great success working with them to resolve issues within the CORE 3 components. Windows 7 is definately having an issue with coming out of power state like Sleep mode or BSOD after idle.

    My friend Google and I are going to start tackling this new area and I have to ramp up my knowledge on power states first before I start posting any definitive answers as to why or what is the root causes of these problems.

    Turning off any power states in the BIOS or control panel obviously avoids this problem but if you forget to shut off you PC before you go to bed a few times each month your gonna get hit with an exuberant electricity bill. These functions MUST work correctly or else.
    Thursday, December 03, 2009 7:39 PM
  • Mr. passionfly1,

    I have auto-rebooting problem with my windows 7 - 32 bit.  I might be related to RAM frequency discrepancies.  I have power Kernel Auto-rebooting at random times and the critical error event (41) is followed by 4 "kernel-power-processors" event (63).

    Here are my system Specs:

    -Asus P5B Green (*Memory RAM 800/667/533MHz, LGA 775)
    -Intel Quad Core Duo Q9550 2.83Hz
    -Graphics: Sapphire ATi 5570 
    -Actual RAM on Mobo: four exact chips on all four slots --> SAMSUNG 1GB 2Rx8 PC2-5300U-555 -12-E3
    -PSU Cooler Master 600W 


    Here is my most recent reading of my MemTest86+:

    "Intel Core 2 2829MHz
    L1 Cache:   64 K  46374 MB/s
    L2 Cache: 6144K  19782 MB/s
    Memory : 4095M    3567 Mb/s
    Chipset  : Intel P965/C965  - FSB :332MHz  -  Type DDR- II
    Settings: RAM : 332 MHz (DDR665) / CAS :5-6-6-15 / Dual Channel "

    Here is the story.  My friend donated me the Asus P5B Green and 4 Samsung 1 GB RAMs that were already attached to it (all four slots!).  He gave me the Mobo box and manuals, but he never gave me the RAM boxes (due to the fact that he is messy when it comes to organization with PC hardware, and he lacks PC knowledge).  Without the Sumsung RAM boxes, I do not have a clue what the actual frquencies of the RAM chips are, I assume they are 555MHz Max.

    So my processor frequency in BIOS last night says 333MHz and the RAM frequency cannot go over 333MHz.   Is this frequency just too low for Windows 7 in general?  I can just change the entire Motherboard to a DDR3 and give it 4GB worth of DDR3 memory that goes up to 1333MHz, but can I just take out all of the Sumsung chips and replace it with two 2GB DDR2 800MHz chips so I don't have to dole out so much cash for a new MOBO?

    It makes sense to toss out all the 4  1GB Sumsung chips and replace it with two  2 GB DDR2 memory chips because making 4 GB with two chips is more energy efficient am I right?

    Hope you can reply soon.

    Monday, December 14, 2009 7:33 PM
  • Mr. passionfly1,

    I have auto-rebooting problem with my windows 7 - 32 bit.  I might be related to RAM frequency discrepancies.  I have power Kernel Auto-rebooting at random times and the critical error event (41) is followed by 4 "kernel-power-processors" event (63).

    Here are my system Specs:

    -Asus P5B Green (*Memory RAM 800/667/533MHz, LGA 775)
    -Intel Quad Core Duo Q9550 2.83Hz
    -Graphics: Sapphire ATi 5570 
    -Actual RAM on Mobo: four exact chips on all four slots --> SAMSUNG 1GB 2Rx8 PC2-5300U-555 -12-E3
    -PSU Cooler Master 600W 


    Here is my most recent reading of my MemTest86+:

    "Intel Core 2 2829MHz
    L1 Cache:   64 K  46374 MB/s
    L2 Cache: 6144K  19782 MB/s
    Memory : 4095M    3567 Mb/s
    Chipset  : Intel P965/C965  - FSB :332MHz  -  Type DDR- II
    Settings: RAM : 332 MHz (DDR665) / CAS :5-6-6-15 / Dual Channel "

    Here is the story.  My friend donated me the Asus P5B Green and 4 Samsung 1 GB RAMs that were already attached to it (all four slots!).  He gave me the Mobo box and manuals, but he never gave me the RAM boxes (due to the fact that he is messy when it comes to organization with PC hardware, and he lacks PC knowledge).  Without the Sumsung RAM boxes, I do not have a clue what the actual frquencies of the RAM chips are, I assume they are 555MHz Max.

    So my processor frequency in BIOS last night says 333MHz and the RAM frequency cannot go over 333MHz.   Is this frequency just too low for Windows 7 in general?  I can just change the entire Motherboard to a DDR3 and give it 4GB worth of DDR3 memory that goes up to 1333MHz, but can I just take out all of the Sumsung chips and replace it with two 2GB DDR2 800MHz chips so I don't have to dole out so much cash for a new MOBO?

    It makes sense to toss out all the 4  1GB Sumsung chips and replace it with two  2 GB DDR2 memory chips because making 4 GB with two chips is more energy efficient am I right?

    Hope you can reply soon.

    Its not that 333mhz is too low for Win7 its that its too low for that motherboard. Here are the specs for your motherboard I got from Asus website (I am assuming this is it since I did not find a "Green" flavor of the P5B listed there):

    4 x DIMM, max. 8GB, DDR2 800 / 667 / 533 MHz, non-ECC, un-buffered memory

    from http://usa.asus.com/product.aspx?P_ID=YwIVDOTcvIMHZdTy

    their qualifying memory they have tested with the P5B Mobo is listed here: http://dlsvr04.asus.com/pub/ASUS/mb/socket775/P5B/P5B_QVL.pdf

    Since I do not know the actual part/model number of the memory I can not tell you the top speed they can potentially run at (but Samsung can if you call them). If your Mobo is incapable of getting memory at faster then 333mhz then you need to either get memory that can run at a minimum of 533 like the specs for the Mobo say it must be at or get a Mobo that can accommodate the slower 333mhz memory you have. Either case its quite evident the Mobo and the memory you have do not like each other =(

    If the memory you have is capable of running at 533 or even faster and you can not set it faster in the BIOS then I would call Asus and ask them whats up? May need a BIOS update if that's the case but my gut feeling is that memory is not possible to run with that Mobo.

    Samsung's website lists stuff by part number not model number and we already know what the model is (1GB 2Rx8 PC2-5300U-555 -12-E) but their website is not very informative. If I was you I would go with more predominant memory makers like Kingston or Corsair or OCZ to name a few. Get one of their memory in the 800mhz flavor like say 2x4GB to run them in ungauged "faster" modes. Mem Modules running in pairs tend to run faster then a single module due to the way the memory architectures alternates between the 2 modules. Try and buy memory in "EVEN" number of modules (2,4,6,8) rather then buying them in "ODD" number of modules (1,3,5,7). The evens will run faster in your system then the odds. How many modules you want is all determined by how much total RAM you want to have. I would recommend at least 4GB for now and in about 1 year I'm pretty sure 6 or 8GB will be more preferred. Try and stick with the same BRAND of memory modules. Go with all Corsair or all OCZ not 1 or 2 OCZ and 1 or 2 Kingston for instance. Different brands can have identical specs and cause problems in your PC that's so small but can lead to major issues like sudden restarts or whatnot.

    You can't go wrong with that recommended list of memory Asus has its memory that's been tested and works with it.

    Another quick thing I noticed is the timing you say the are set for ("C
    AS :5-6-6-15 / Dual Channel") and the the actual model number ( SAMSUNG 1GB 2Rx8 PC2-5300U-555 -12-E3 ). If I am correct they actually built the timings into the model number as 5-5-5-12 and your timings are 5-6-6-15. Are you seeing the problem? That 555-12 does look like a genuine timing sequence number if you look at it.
    Tuesday, December 15, 2009 3:39 AM
  • Hi all,

    i'm having the same issue, and the exact same log as andrea. My system specs are:

    Gigabyte GA-MA785G-UD3H
    AMD Phenom II X4 940 / 3 GHz
    Kingston HyperX Dual Channel Kit - 4 GB ( 2 x 2 GB ) - DIMM 240-pins - DDR2 - 1066 MHz / PC2-8500
    Sapphire RADEON HD 4850 X2
    WD Caviar Black WD6401AALS
    Antec TruePower New 650 watt

    Windows 7 Ultimate build 7600

    And in my post screen I saw my memory was rolling at 800 MHz, I tried to change this along with memory voltage and timings. Then, windows wouldn't boot up. So I had to remove my bios battery to reset these settings, then its running fine, beside crashes. When I ran memtest86+, it showed me that my memory was running at 200MHz ! I mean W T F! I've already contacted Gigabyte and they are processing it right now.

    And lately it only restarts when playing games. At first it crashed even when I was doing nothing at all, but that seems gone.

    I hope some Windows developer is looking into this.

    What could be the cause of these problems?
    Wednesday, December 16, 2009 3:19 PM
  • Hi all,

    i'm having the same issue, and the exact same log as andrea. My system specs are:

    Gigabyte GA-MA785G-UD3H
    AMD Phenom II X4 940 / 3 GHz
    Kingston HyperX Dual Channel Kit - 4 GB ( 2 x 2 GB ) - DIMM 240-pins - DDR2 - 1066 MHz / PC2-8500
    Sapphire RADEON HD 4850 X2
    WD Caviar Black WD6401AALS
    Antec TruePower New 650 watt

    Windows 7 Ultimate build 7600

    And in my post screen I saw my memory was rolling at 800 MHz, I tried to change this along with memory voltage and timings. Then, windows wouldn't boot up. So I had to remove my bios battery to reset these settings, then its running fine, beside crashes. When I ran memtest86+, it showed me that my memory was running at 200MHz ! I mean W T F! I've already contacted Gigabyte and they are processing it right now.

    And lately it only restarts when playing games. At first it crashed even when I was doing nothing at all, but that seems gone.

    I hope some Windows developer is looking into this.

    What could be the cause of these problems?

    I am having the same problems with my Gigabyte GA-MA78GM-US2H Mobo, I can not for the love of me get my system to run memory @ 1066mhz with perfect timings and everything set i the BIOS with Corsairs support. I am starting to feel this POS Mobo needs to be replaced with a differant brand. I have been trying since June of this year to get my Premium Dominator Corsairs to run at 1066 on this board, even went so far as to get a new Phenom II processor to power these and still its reboots the system once they modules are set for 1066. I freaking hate Gigabyte and their POS Mobo's atm >.<

    The Dominators run fine @800mhz but that the heck is the point of running your memory gimped if the Mobo is specced to support 1066 and even 1200mhz memory speeds!

    I set the timing exactly as my modules require in the BIOS @ 5-5-5-15 2T @ 2.1v (If u notice these are EXCELLENT timings for these modules) and still this da mn motherboard shows them running in the OS (CPUZ or Blackbox 2.0) or Memtest86+ as either 8-5-5-15 or sometimes 5-5-5-18. I am like WTF IS GOING ON!!!!! Stupid Gigabyte!

    DO NOT BUY GIGABYTE motherboards if you want to run memory faster then @1066mhz or faster!!! THEY SUCK!

    The cause of this is that Gigabyte motherboards for all their hoopla are incapable of retaining the memory timings you set for them in the BIOS with the actuality of what they truely run at once you are past POST. This is the reason for this issue. I can blatantly see I set the timings in the BIOS to 5-5-5-15 and it shows up in CPUZ once the OS is loaded as either 8-5-5-15 or 5-5-5-18. When i set it for a "5" it should stay as a freaking "5" not an "8"!!!!!
    Wednesday, December 16, 2009 3:32 PM
  • I'm having these minidumps after a bsod, maybe it has to do something with it?:

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa8005209028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000f2384000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000185, Low order 32-bits of the MCi_STATUS value.

    Debugging Details:
    ------------------


    BUGCHECK_STR:  0x124_AuthenticAMD

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    STACK_TEXT: 
    fffff880`02f6ba88 fffff800`035f6903 : 00000000`00000124 00000000`00000000 fffffa80`05209028 00000000`f2384000 : nt!KeBugCheckEx
    fffff880`02f6ba90 fffff800`0318d513 : 00000000`00000001 fffffa80`0500ec50 00000000`00000000 fffffa80`0500eca0 : hal!HalBugCheckSystem+0x1e3
    fffff880`02f6bad0 fffff800`035f65c8 : 00000000`00000728 fffffa80`0500ec50 fffff880`02f6be30 fffff880`02f63100 : nt!WheaReportHwError+0x263
    fffff880`02f6bb30 fffff800`035f5f1a : fffffa80`0500ec50 fffff880`02f6be30 fffffa80`0500ec50 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`02f6bc80 fffff800`035e9e8f : 00000000`00000000 00000000`00000001 fffff880`02f6beb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`02f6bcc0 fffff800`030777ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
    fffff880`02f6bcf0 fffff800`03077613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`02f6be30 fffff880`03fa87f2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`02f8bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : amdppm!C1Halt+0x2


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

    BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

    Followup: MachineOwner

    Thursday, December 17, 2009 2:51 PM
  • I think i solved my problem by updating my BIOS. Now my pc is very smooth. I hope this helps for people with the same error.
    Sunday, December 20, 2009 2:37 PM
  • Hi!

    My system is always rebooting spontaneously.

    Kritikus 2010.01.05. 8:26:09 Kernel-Power 41 (63)
    Kritikus 2010.01.05. 8:22:01 Kernel-Power 41 (63)
    Kritikus 2010.01.04. 21:05:16 Kernel-Power 41 (63)
    Kritikus 2010.01.04. 20:41:16 Kernel-Power 41 (63)
    Kritikus 2010.01.04. 18:25:34 Kernel-Power 41 (63)
    Kritikus 2010.01.04. 15:29:11 Kernel-Power 41 (63)
    Kritikus 2010.01.03. 22:27:52 Kernel-Power 41 (63)
    Kritikus 2009.12.30. 15:59:53 Kernel-Power 41 (63)

    Kernel-Power 41
    (61)
    - System

      - Provider

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

       EventID 41

       Version 2

       Level 1

       Task 63

       Opcode 0

       Keywords 0x8000000000000002

      - TimeCreated

       [ SystemTime]  2010-01-04T20:05:16.128413300Z

       EventRecordID 30166

       Correlation

      - Execution

       [ ProcessID]  4
       [ ThreadID]  8

       Channel System

       Computer AMD

      - Security

       [ UserID]  S-1-5-18


    - EventData

      BugcheckCode 0
      BugcheckParameter1 0x0
      BugcheckParameter2 0x0
      BugcheckParameter3 0x0
      BugcheckParameter4 0x0
      SleepInProgress false
      PowerButtonTimestamp 0

    --

    - <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-01-04T20:05:16.128413300Z" />
      <EventRecordID>30166</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>AMD</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>

    Config.:

    Gigabyte MA-770DS3 rev. 1.
    AMD X2 6400
    CSX 4 Gbit Kit Overclocking (800 mhz, 2x2048MB)
    ASUS 450W A-45GA Aktív PFC ATX2 12cm
    Gainward ATI 4850 512
    Windows 7 64

    Bios, chipset and drivers up to date. What is the problem?
    Tuesday, January 05, 2010 8:03 AM
  • Hi, I need help really badly.  For about 1 week now, my computer has been resetting and if it doesn't reset and starts up, within 3-10minutes it immediately goes into hibernation and I cannot restart it besides turning off the computer and turning it back on.  Most of the time it doesn't even start up just goes straight into hiberation.

    I also checked the event log and I got - Kerner Power Failure, event id 41 category 63 ,

    I have Windows 7-  Gigabyte Card 2.38 ghz card.

    If I try to go in the Bios system by hitting F1-F2, F4, computer freezes and nothing happens.

    I also tried to change the power plan settings to turn hibernation off and again when I go into power settings computer goes into hibernation before giving me the option.

    I recently upgraded to Win 7, for about 3-4 months with no issues, nothing new and this has been happening all of a sudden.

    Please help! Could it be the power strip? Overheating? I never overclocked my machine and maybe it has been set to this way automatically? I'm not sure. What do  I do? I am not too tech savy.

    Haril79@gmail.com - Any help would be highly appreciated.
    Sunday, January 10, 2010 11:31 PM
  • Hi, I need help really badly.  For about 1 week now, my computer has been resetting and if it doesn't reset and starts up, within 3-10minutes it immediately goes into hibernation and I cannot restart it besides turning off the computer and turning it back on.  Most of the time it doesn't even start up just goes straight into hiberation.

    I also checked the event log and I got - Kerner Power Failure, event id 41 category 63 ,

    I have Windows 7-  Gigabyte Card 2.38 ghz card.

    If I try to go in the Bios system by hitting F1-F2, F4, computer freezes and nothing happens.

    I also tried to change the power plan settings to turn hibernation off and again when I go into power settings computer goes into hibernation before giving me the option.

    I recently upgraded to Win 7, for about 3-4 months with no issues, nothing new and this has been happening all of a sudden.

    Please help! Could it be the power strip? Overheating? I never overclocked my machine and maybe it has been set to this way automatically? I'm not sure. What do  I do? I am not too tech savy.

    Haril79@gmail.com - Any help would be highly appreciated.

    CPUID has a great free temp monitor you can d/l called hwmonitor (Google it). If you can't even go into the BIOS then you have a hardware issue so I would start by eliminating all extra cards in any PCI slots first. Get the comp as dumb as possible by unplugging just the bare necessaries like 1 ram chip inserted not 2, 3 or 4. unplug the hard drive and use the built-in video (if you have it) on the mobo instead of a dedicated video card then go into the BIOS. If you can get into it start by reattaching all your devices back again with a quick reboot between re-attachments to see if the problem surfaces.

    My hunch its either a faulty memory module, incorrect timings for that memory module or a problem with clean power for the system (your PSU aka Power Supply Unit). But I'm winging it here cause I have limited information about your system.

    A bad power supply or one that's dying will start shutting a computer down or cause it to go into hibernate mode. Hibernate mode is a primarily laptop ability to conserve the battery power that has been ported into OS's and desktops. If a laptop was running low on power it would hibernate as fast as it could to preserve the data from getting lost. Seems like you are having this sort of issue but on a desktop. Not enough power and the desktop starts to shut itself down to preserve a fatal crash.

    HWMonitor also has a voltage monitor you can see if the PSU voltages are fluctuating wildly when not under load. Make sure they are within the tolerances in the monitor as they are printed on the side of the PSU or you may have a dying PSU issue.

    The more stuff you unplug from the computer the less power it will draw at a loss of that devices use of course. This will ease the burden on your PSU and allow it to run better but then it may reach a threshold where that last CD or hard drive you plug into the mobo makes it do crazy things like power down suddenly. It may not be the device itself you are plugging/unplugging but the actual strain on the PSU pushes it over the edge and the whole PC starts acting crazy.
    Monday, January 11, 2010 2:34 AM
  • Got the same problem with my Acer Aspire 5670 laptop since I've installed win7 x86
    I did upgrade my RAM with 2x1GB of Kingston memory. I'll keep monitoring my memory
    and core temperatures and keep trying possible solutions posted here. If I find anything
    that works for me I'll let you know.
    Wednesday, January 13, 2010 2:18 PM
  • Hey all, I did some crazy things to solve this problem but none of them worked. So I contacted Gigabyte, en after a view conversations they said I should return the motherboard to where I bought it, so I did. Later I got an email from them saying my motherboard is faulty, now I'm still waiting for my new one.

    Hope this solves the problem.
    Wednesday, January 13, 2010 4:39 PM
  • I too am having thed same event but have a blue screen. I believe it is a problem that occurs when the computer is trying to enter sleep. Try shutting down media player if on or exploriers player if on before sleep is entered. Try changing the power settings to prevent sleep and enter hibedrnate or turn off computer on time setting. It appears to be a management issue of CPU by the OS. Microsoft should be aware of the problem and I bet they are working on a solution.
    Wednesday, January 13, 2010 6:37 PM
  • Hi.

    I has the same problem, and I resolved as follow:

    Go To ->

    Contol Panel
    System and Security
    Administrative Tools
    Schedule Tasks

    Under the Active Tasks panel, I had a task named "RacTask" scheduled to run 1 hour after the power on.
    I noticed when the time to start that task comes, my computer reboout...

    So I disabled that task, and my computer don't reboot anymore now.

    Seems a joke that the RAC service who is the responsible to check the reliability of the system, was the cause of the reboot :)

    Hope this help,
    Eugenio Serrano.
    Solid Quality Mentors
    NDSoft Consultoria y Desarrollo

    Thank you for this information. I will be monitoring this task very closely from now on. You may be on to something in regards if 2 criteria are met:

    1) Your PC is in a lowered powered state when away from it yet not completely logged off or shutdown and
    2) This task run at its scheduled time.

    This will to promote the devastating rapid shutdown and restart of the computer.

    I do believe based on what you are saying that if both these conditions are true it may be possible due to errant code in the RAC scheduled task a shutdown could occur. I will continue to monitor this task closely over a period of a week to see if it is true.

    Thank you very much for bringing this to my attention.
    • Proposed as answer by passionfly1 Saturday, February 27, 2010 6:49 AM
    Thursday, January 14, 2010 1:22 AM
  • Hi there,
    I'm impressed of how many people seems to have the same problem. Recently I bought completely new hardware:

    Mainboard: ASRock M3A785GMH/128M (BIOS updated manually to newest version 1.40)
    Memory: 2 x 2GB DDR3-10666 OCZ OCZ3P1333LV4GK, running at 1333 MHz, 1.65V
    CPU: AMD Phenom II X2 550 (3.1 GHz)
    HDD: WD640AAALS

    I installed Windows 7 64 Home Premium without any problems. After a few days of stunning fast Windows experience, I got different BSODs (SYSTEM_SERVICE_EXCEPTION, MEMORY_MANAGEMENT etc.) In the event list I found some "Windows-Kernel-Power" issues. After many crashes, it seems like registry was corrupted. Windows wasn't stable any more, so I decided to make a fresh install. But the problem repeated: System was running perfectly for days, then bluescreens appeared.

    Thinking of memory issues, I loaded bios defaults: no effect
    Running memtest 4.0 for 72 (seventy two!) hrs. showed not a single error.
    Running Windows Memory test: no errors found
    Maybe a problem of the mainboard itself, I thought. I freshly installed Win7 and run the newest release of prime95 stability test for 48 hrs.:  not a single error occured. Note: Prime95 is a very reliable hardware testing tool. Even if there are minimal hardware issues, it crashes. But this wasn't happening with my machine.
    Next day I booted Win7 and did nothing for about 1 hour. What happened: the system crashes with BSOD! Kernel-Power-Management issue in the event list.

    I installed Windows XP Professional SP3. It was running for days without any problems, not a single error in the system event list.
    I installed Debian Linux 5 (lenny) 64-Bit with gnome GUI. It was running for day without any problems.

    I installed Windows 7 Home Premium 64 Bit: After 2 days freaky BSODs appeared.

    Driver issue? I only installed original AMD system drivers (ATI all in one chipset drivers and ATI catalyst drivers, each the newest release). If these where buggy, I think, many people would have issues with them but this doesn't seems to be the case.

    I have no more idea WTF is wrong with the system...

    Sunday, January 24, 2010 11:51 AM
  • To All:
    I noticed that there are a lot of people experiencing Kernel-Power errors, especially when moving to Windows 7 64-bit version. I had similar problems and it was driving me nuts until I finally figured out the issue. I'm not saying this will be the same for everyone but it is another angle to look at.

    I bought a brand new computer from a local retailer 12 months ago. They put it all together for me and ensured the system was properly burned in. The original specs were as follows:

    CPU:                       AMD Athlon 64 X2 6000+ 3.0 GHz

    Mainboard:           XFX nforce 750a AMD SOCKET 940 DDR2
    PSU:                        Ultra LS600 Lifetime Series 600W Power Supply
    Memory:               4 x OCZ DDR2 PC2-6400 / 800MHz / 2GB Module (8GB total)
    OS:                          Windows XP Pro 32-Bit
    Video:                    GF 9600GSO 580M 768MB DDR2 DUAL DVI TV PCI-E

     

    For the first 8 months, the system ran fine with XP pro 32-bit and never gave me any issues. It wasn't until I October when I received my copy of Windows 7 64-bit that all my problems arose. I would receive random reboots and BSOD and when looking in the system log it said that it was a Kernel-Power error. This was a freshly installed system, all firmware and driver updates completed and running into these problems. I ran a TON of tests on the system to try and determine the problem, Including running MenTest86 to see if RAM was the culprit. I opened a long email thread with XFX support and after two months it was determined that my CPU was incompatible with my motherboard. AMD actually manufactures two 6000+ cpu's, one that draws 89W and the other that draws 125W.

                    AMD Athlon 64 X2 6000+ 3.1 GHz @ 89W                    

                    AMD Athlon 64 X2 6000+ 3.0 GHz @ 125W

     

    As it turns out, my particular motherboard can only handle a cpu up to 95W and the CPU that was sold was the  125W version. The problem went undetected for 8 months because even though the CPU installed was 125W, it was only running in 32-bit mode and only using 3.5GB of the available 8GB of RAM. This kept the overall power draw down to an acceptable level for the motherboard and thus no problems. As soon as I went to the Windows 7 64-bit, the CPU is now running at full capacity, and now that it is using all 8 GB of RAM, it was simply too much for the board causing Kernel-Power errors.  Knowing that the CPU/Mobo combo that was sold to me was incompatible and having the email thread from the manufacturer in hand, I went back to the original place of purchase, explained their mistake and had them replace the CPU at no charge to me with one that was compatible. Since I was worried about potential damage to the motherboard, I had them increase the warranty for another 60 days to be safe and ensure the problems were gone.

     

    My system is now running Windows 7 64-bit without any issues for over a week whereas previously I couldn't go more than a day. The CPU that is now installed is:

                    AMD Phenom X3 8750 2.4GHz, 3.5MB Cache, 1800MHz Triple-Core @95W

     

    It sucked that it took so long to find the problem but it's just one of those things and I ended up getting a significantly faster CPU out of the deal. I post this because it was a simple mistake that anyone could have made that will cause all the same problems you are experiencing. I also went down the path of checking drivers, making sure the most recent were installed and the problem in the end was related to power because the CPU was sucking too much juice. While your CPU/Mobo combo's may be correct, it is very possible that you could still have true power related issues if your power supply is undersized.

     

    Anyway, that was my experience that I wanted to share in case it helps others.

     

    -Sean

     

    Sunday, January 24, 2010 7:36 PM
  • No.Compromise and Passionfly1 are right!

    I slowed the ram down and the problem disappeared. It seems the problem is indeed memory corruption but not due to faulty hardware (which explains why memtest didn't find any errors).
    Monday, January 25, 2010 12:23 AM
  • No.Compromise and Passionfly1 are right!

    I slowed the ram down and the problem disappeared. It seems the problem is indeed memory corruption but not due to faulty hardware (which explains why memtest didn't find any errors).

    ATTENTION: Wall of text, incomming! lol

    I am absolutely certain that Windows 7 has a serious issue with how the memory and the processor interact with each other beyond the 800mhz range that a lot of memory chips run at. I do not know which driver or process or task is the root cause but I will find this dang thing. It has become my life quest, lol Once you start running memory at 1066mhz or faster, Windows 7 starts rebooting randomly whereas XP does not. I have upgraded my processor from a single core AMD 7850 to a triple core 720 black edition to even allow for the memory to run at the 1066mhz speed its supposed to be running at and still occasionally it does random reboots. Corsair, AMD and Gigabyte all 3 have verified that those 2 pieces of components should be able to run together to make the memory run at 1066mhz (Corsair Dominator memory modules, of which I went through 3 different sets already). Yet it can't! This new Black Edition CPU is fully capable of overclocking to amazing heights but I needed a good CPU cooler to accomplish that first.

    I have recently purchased a Corsair CWCH50 Liquid-cooled self-contained CPU cooler (seen here http://www.zipzoomfly.com/jsp/ProductDetail.jsp?ProductCode=10010633&prodlist=froogle ). The cost was $54 (with free shipping!) from ZipZoomFly.com with rebate, a very good price for this technology. The price has recently went back up to around $70 so I was fortunate to find it back in early January when it was so cheap. To be able to further overclock my processor to accommodate running my memory at the true 1066mhz they are SUPPOSED to be able to run at, I had to buy this product. I am trying to incorporate the push-pull double fan system (seen here http://blog.corsair.com/?p=987 ) attached to the little radiator but with a hitch. Corsair does not sell an additional identical fan so I had to get some nice identically-specced (Corsairs specs, not CoolerMaster's) CoolerMaster fans (seen here http://www.amazon.com/gp/product/B0026ZPFCK/ref=oss_T15_product ) to be able to mount the both of them to the radiator. With yet another hitch! I have to get an identical set of screws that are deep enough to mount the second fan to the other side of the radiator, from Corsair. They are in the process of sending me these 2nd set of screws to accomplish this.

    The 3rd hitch is the CWCH50 does not come with the AMD brackets the newer CWCH50-1 kit does have the brackets inside. The mounting bracket is free from Corsairs website, but this of course caused another delay in implementing this solution. If you do buy the CWCH50 make sure you get the -1 version of the kit and not the "CWCH50" model if you use AMD CPU's. I think there is an equivalent kit for the Intel side but I am not sure about this since I don't use or like Intel. Although I must say Intel's XMP memory architecture and Corsairs new Dominator GTX1 memory implementation is starting to attract me (http://blog.corsair.com/?p=1420#more-1420 ). ZipZoomFly had the older kit without the bracket and in hindsight I was aware of this, but I wanted to jump on this lowered (and rebated) price fast! Since the bracket was free from Corsair (even shipping!) it was just a matter of waiting to get it.

    I want to wait until I have everything together before installing this complete push-pull Corsair cooler, instead of piecemeal with one fan. I like to install stuff all at once and not have to fiddle with internal system components like a surgeon over and over. I like to install it correctly and then forget about it.

    If after all this is accomplished and I am able to overclock my Black Edition 720 to a level that far exceeds what is normal and run this CPU stabily AND I still can not run my premium Corsair Dominator memory modules at 1066mhz, I will rip Microsoft a new like I have never done as to why the OS is still crashing if it does. For those of you that may think, in my previous posts, that I am a Microsoft worshipper or fanboy with complete consistency, will be in for a rude awakening, lol  I have been dealing with this random crash/freezing issue since 3 days after Win7 came out and to some extent during beta (although the crashes were not so evident and more rare during beta). I just thought after all its "beta", of course its gonna crash! But I have now been dealing with this specific freezing issue since June of '09 when I first started using Win7 beta. THAT'S 7 MONTHS of this one specific and horrific issue.

    My system atm is extremely stable and does not crash running my memory at 800mhz . But this is NOT good enough. If XP can not crash with memory running at 1066mhz, other users report Linux 64-bit and Vista 64-bit, running stably, then Windows 7 has a SERIOUS flaw in some driver or task or something embedded within it to cause it to freeze like this. These modules are premium memory modules and I fully stand behind Corsair in them being reliable and usable at the 1066mhz range because XP has shown me it is possible to run them as such, but Windows 7 has not. Not only that but I have gone through 3 sets of them. Poor Corsair =( I made it up by buying yet another good Corsair product and am here to tell you you should too! This CWCH50 is one of the best engineered CPU coolers that uses a self-contained water-cooling system to be able to run CPU as low as 15 degrees C (as some review sites purport to run the CPU at) with push/pull implementation. Even Corsair's own link has a Core i7-870 running at 70 degrees C under load. This is easily about 10-15 degrees C less then a comparable liquid cooler @ 3x the price on a different site can run this processor under load. Amazing technology!

    You will never have to deal with an actual accessible water reservoir with this product. Its all self-contained. If I can persuade anyone out there to try this CPU cooling solution, which has been verified on numerous review sites (and I have read a TON of them before making my purchase) as being the cheapest, coolest and best overall, then I will have gone beyond having to return 2 perfectly good sets of memory modules which in hindsight I am positive was not Corsair's fault the crash was occurring. I firmly stand by this and Corsair.

    You can tell by the length of this thread (and the one similar to it) that there is soooooo many ppl that are having freezing problems and this is not good!

    Microsoft, if after Overclocking my CPU to an astronomical level to accommodate the memory to be able to run it at 1066mhz your OS still crashes or freezes, due to inability to perform reliably with memory running at this speed, you will have a malestorm of venomous hate-speech coming forth from me onto this forum and many many others to have to devote so much time from my life to this frigging ridiculous issue. I will probably get kicked off this board. I can foresee it lol

    But that time is not yet, there is still testing to be done...

    Monday, January 25, 2010 2:24 AM
  • No.Compromise and Passionfly1 are right!

    I slowed the ram down and the problem disappeared. It seems the problem is indeed memory corruption but not due to faulty hardware (which explains why memtest didn't find any errors).

    Out of curiosity, what memory timings did Memtest show the memory was testing at before you lowered the memory speed and were these identical timings you entered in the BIOS for that accelerated speed? eg.: did the 2 areas (the BIOS and Memtest) show identical memory timings when you ran the memory modules hotter/faster?
    Monday, January 25, 2010 3:03 AM
  • Hi there,
    I'm impressed of how many people seems to have the same problem. Recently I bought completely new hardware:

    Mainboard: ASRock M3A785GMH/128M (BIOS updated manually to newest version 1.40)
    Memory: 2 x 2GB DDR3-10666 OCZ OCZ3P1333LV4GK, running at 1333 MHz, 1.65V
    CPU: AMD Phenom II X2 550 (3.1 GHz)
    HDD: WD640AAALS

    [...]

    I have no more idea WTF is wrong with the system...

    Update: I installed Windows 7 again. Because of the Kernel-Power-Thing I switched the ACPI HPET mode to enabled in the BIOS setup. In some forums I read that the HPET mode supplies better system stability. But after nearly 2 days of running at its best windows crashed again. But now without bluescreen, it just freezed. After resetting, the windows memory diagnostics was to run. And it told my that there were some memory related problems (I was testing the system for two weeks but this was the first time, windows memory diagnostics said that there were problems.) Now I'm running memtest86 4.0 again since 2 ours without error. The RAM timings shown by memtest86 are 8-8-12-30. I've no experience with over- or underclocking. In which ratio I should lower the timings? Would anyone recommend me to lower them? I can hardly believe that the RAM memory is defected because memtest haven't shown any errors since the beginning of this oddysee - and I tested much.
    Monday, January 25, 2010 7:16 PM
  • Hi there,
    I'm impressed of how many people seems to have the same problem. Recently I bought completely new hardware:

    Mainboard: ASRock M3A785GMH/128M (BIOS updated manually to newest version 1.40)
    Memory: 2 x 2GB DDR3-10666 OCZ OCZ3P1333LV4GK, running at 1333 MHz, 1.65V
    CPU: AMD Phenom II X2 550 (3.1 GHz)
    HDD: WD640AAALS

    [...]

    I have no more idea WTF is wrong with the system...

    Update: [...]
    Update 2: Spent half a day reading forums about windows 7 RAM issues. Many times I read about issues with high speed RAM. So I switched the sticks from 1333 (667) MHz to 1066 (533) MHz. Windows 7 installed successfully like on all other tries. Having installed some software I decided to let the system run idle in the morning. When I came back in the late evening, system has crashed completely. Windows 7 wasn't even able to start anymore. Some files are corrupted. Hard disk surface tested but without any error. Now I installed Windows 7 again but with only one stick of RAM (2 GB). Installation runs like ever bevore - superb. No problems with installing drivers, software or windows updates. I'll let the system run idle again and see whether it is death or not tomorrow morning.
    Tuesday, January 26, 2010 7:08 PM
  • Hi there,
    I'm impressed of how many people seems to have the same problem. Recently I bought completely new hardware:

    Mainboard: ASRock M3A785GMH/128M (BIOS updated manually to newest version 1.40)
    Memory: 2 x 2GB DDR3-10666 OCZ OCZ3P1333LV4GK, running at 1333 MHz, 1.65V
    CPU: AMD Phenom II X2 550 (3.1 GHz)
    HDD: WD640AAALS

    [...]

    I have no more idea WTF is wrong with the system...

    Update: I installed Windows 7 again. Because of the Kernel-Power-Thing I switched the ACPI HPET mode to enabled in the BIOS setup. In some forums I read that the HPET mode supplies better system stability. But after nearly 2 days of running at its best windows crashed again. But now without bluescreen, it just freezed. After resetting, the windows memory diagnostics was to run. And it told my that there were some memory related problems (I was testing the system for two weeks but this was the first time, windows memory diagnostics said that there were problems.) Now I'm running memtest86 4.0 again since 2 ours without error. The RAM timings shown by memtest86 are 8-8-12-30. I've no experience with over- or underclocking. In which ratio I should lower the timings? Would anyone recommend me to lower them? I can hardly believe that the RAM memory is defected because memtest haven't shown any errors since the beginning of this oddysee - and I tested much.
    ITS NOT YOUR MEMORY! Windows 7 has a core issue somewhere, I do not know where specifically that makes the system crash/freeze if the memory you are running is set to run higher then 800 mhz. That means ALL computers that run memory @ 1066, 1200, 1333, 1666, 1800, 2000, 2200 and higher can POTENTIALLY be affected by this core software bug that is inherent in this operating system. I have been extensively testing this theory but this is my hunch. If you can drop your system memory speed to 800mhz and run it stably for 1 week then I am correct in my theory. Obviously this theory is hard to prove atm for me but all indicators point to this.

    Don't return your memory
    . I went through 3 sets of premium grade Corsair memory chips and still had my system crash once the memory was set to 1066mhz. Its very hard to predict when it will crash because its very dependent on which register of the bank the memory hits when its running @ 1066 or faster to cause this situation. Hence the randomness of the freezes. Every poster that is having this problem is running @ 1066 or faster memory speeds. The other trend i notice is ppl with one stick of ram (even at faster then 800mhz speeds) do not have this freeze as opposed to ppl with 2 or more sticks of memory in their system. Try and find this pattern in any post you read. I think I am on to something very tangible with my theory.

    Yes, there are other issues that can cause a freeze but this is the MAIN issue that Windows 7 is having in terms of freezes.
    Wednesday, January 27, 2010 7:31 AM
  • There is a new Windows Critical update out: http://support.microsoft.com/?kbid=977074

    Specifically it fixes the issue of:
    • On a computer that is running Windows 7, you configure the Screen Saver Settings to display the logon screen on resume. Additionally, you configure the computer to go to sleep. However, the computer may not go to sleep after the screen saver starts. Instead, a black screen is displayed. This problem causes the operating system to stop responding. You must restart the computer by holding down the power button.
    Wednesday, January 27, 2010 8:18 AM
  • I have tried many of the fixes listed above and I can still reproduce my particular rebooting error.

    My PC reboots after playing DOW2 of COH for more than 1-2 minutes.

    So far i have turned off power saving options on my CPU ( I7-920), lowered my ram frequency from 1066 to 800hmz (6gb pc12800 Corsair XMS C8), disabled RACTask, checked all power cables connected to my video card (GTX 275) and updated my video and mainboard drivers (GB EX58-UD3R Mainboard).

    All new hardward bard; HDDs,OP drives and PSU running Win 7 Pro 64bit.

    Still no love for me, ive read a few posts from people with the same issue as me no one else had any luck since there last post?


    Tmr i will test my ram modules 1 by 1 and see how that goes...


    kap

    Wednesday, January 27, 2010 10:43 AM
  • I had the same issue, I had an AMD PhenomII 940 X4 3.0Ghz, changed it with my brother's which is: AMD Athlon 64 X2 ...Ghz. Now running for up to 2 days without crashes. Anyway, it wasn't the memory of 1066Mhz.

    Hope this helps someone.
    Wednesday, January 27, 2010 3:15 PM
  • ITS NOT YOUR MEMORY! Windows 7 has a core issue somewhere, I do not know where specifically that makes the system crash/freeze if the memory you are running is set to run higher then 800 mhz. That means ALL computers that run memory @ 1066, 1200, 1333, 1666, 1800, 2000, 2200 and higher can POTENTIALLY be affected by this core software bug that is inherent in this operating system. I have been extensively testing this theory but this is my hunch. If you can drop your system memory speed to 800mhz and run it stably for 1 week then I am correct in my theory. Obviously this theory is hard to prove atm for me but all indicators point to this.

    Don't return your memory
    . I went through 3 sets of premium grade Corsair memory chips and still had my system crash once the memory was set to 1066mhz. Its very hard to predict when it will crash because its very dependent on which register of the bank the memory hits when its running @ 1066 or faster to cause this situation. Hence the randomness of the freezes. Every poster that is having this problem is running @ 1066 or faster memory speeds. The other trend i notice is ppl with one stick of ram (even at faster then 800mhz speeds) do not have this freeze as opposed to ppl with 2 or more sticks of memory in their system. Try and find this pattern in any post you read. I think I am on to something very tangible with my theory.

    Yes, there are other issues that can cause a freeze but this is the MAIN issue that Windows 7 is having in terms of freezes.

    Running Windows 7 with only one stick @ 1066 MHz. Since I installed it freshly on monday night there was no BSOD or freeze. But I cannot be sure. At the very first try (2 sticks @ 1333 MHz) it has crashed first after one full week.
    Second thin I did is not to install any drivers which are not missing after windows installation. Maybe the chipset driver (AMD 785G) or the graphics driver (ATI 4200HD) are buggy. Why Microsoft provides drivers for AMD 785G and ATI 4200HD by itself? Doesn't they trust the hardware developers?
    Wednesday, January 27, 2010 7:34 PM
  • ITS NOT YOUR MEMORY! Windows 7 has a core issue somewhere, I do not know where specifically that makes the system crash/freeze if the memory you are running is set to run higher then 800 mhz. That means ALL computers that run memory @ 1066, 1200, 1333, 1666, 1800, 2000, 2200 and higher can POTENTIALLY be affected by this core software bug that is inherent in this operating system. I have been extensively testing this theory but this is my hunch. If you can drop your system memory speed to 800mhz and run it stably for 1 week then I am correct in my theory. Obviously this theory is hard to prove atm for me but all indicators point to this.

    Don't return your memory
    . I went through 3 sets of premium grade Corsair memory chips and still had my system crash once the memory was set to 1066mhz. Its very hard to predict when it will crash because its very dependent on which register of the bank the memory hits when its running @ 1066 or faster to cause this situation. Hence the randomness of the freezes. Every poster that is having this problem is running @ 1066 or faster memory speeds. The other trend i notice is ppl with one stick of ram (even at faster then 800mhz speeds) do not have this freeze as opposed to ppl with 2 or more sticks of memory in their system. Try and find this pattern in any post you read. I think I am on to something very tangible with my theory.

    Yes, there are other issues that can cause a freeze but this is the MAIN issue that Windows 7 is having in terms of freezes.

    Running Windows 7 with only one stick @ 1066 MHz. Since I installed it freshly on monday night there was no BSOD or freeze. But I cannot be sure. At the very first try (2 sticks @ 1333 MHz) it has crashed first after one full week.
    Second thin I did is not to install any drivers which are not missing after windows installation. Maybe the chipset driver (AMD 785G) or the graphics driver (ATI 4200HD) are buggy. Why Microsoft provides drivers for AMD 785G and ATI 4200HD by itself? Doesn't they trust the hardware developers?

    DO NOT install the drivers that Microsoft recommends from their Windows Update, go to the source and get the drivers (manufacturer), Never install those POS drivers from Microsoft. I can count about 40 times those Windows Update drivers always gave me problems. The source drivers are always more current and work better and more stable.
    Wednesday, January 27, 2010 9:17 PM
  • I had the same issue, I had an AMD PhenomII 940 X4 3.0Ghz, changed it with my brother's which is: AMD Athlon 64 X2 ...Ghz. Now running for up to 2 days without crashes. Anyway, it wasn't the memory of 1066Mhz.

    Hope this helps someone.

    Ok, in order to have memory running @ 1066 mhz or faster your processor needs to be the correct speed once the memory speed starts to ramp up. By downgrading your processor AND increasing your memory speed makes me know something is not right here. Thats like saying your running your computer submerged in the bathtub and it runs just fine. I find this incredibly hard to believe.

    1066 and faster requires minimum Phenom (or Phenom II of course) for just about any AM2+/AM3 motherboard out atm to run faster then 800mhz. I can not even comprehend how this is even possible by what you did.

    Only the Mobo maker can give you the minimum processor speed they recommend for the memory you want to run at. When the X2's were out the top speed was around 400-600mhz for memory. This just seems impossible.
    Wednesday, January 27, 2010 9:22 PM
  • Well I tested all of my ram mods 1 by 1 and the problem persisted with each one so i played around with ram timings and frequencys backing them all the way off to no avail.

    So i dont think my problem is related to RAM.

    Another test i tryed was hooking up all my HDDs and OP drives to a 2nd PSU, lowering the power load, to see if it was a under power supply issue and that made a huge difference. I was able to run the performance test in DOW2 succesfully as before it was crash within 15 seconds of starting the test. My PSU is a 550w Antec true power and I am going to buy a new PSU asap, hopefully that solves my issue.

    anyone else having rebooting issues while running games or other intense aps, not at all during browsing or just running basic aps, you may want to try a new PSU...


    kap
    Thursday, January 28, 2010 9:00 AM
  • Hi,
    I have a retail version of Windows 7 and this happens every hour of everyday!

    - <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-01-12T11:09:45.602424700Z" />
      <EventRecordID>194032</EventRecordID>
      <Correlation />
      <Execution ProcessID="4" ThreadID="8" />
      <Channel>System</Channel>
      <Computer>Tierney-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>

    I have tried the above solutions, as a noob I have paid over £120 for regcheck programs, driver update programs and bios update programs. nothing works.
    I have praised windows 7 since I installed the retail version about 2 months ago. This crashing began a week ago and has not stopped.
    I am completely frustrated with microsoft. When I do what is asked by windows checks my computer is working 100%.
    When I send in my 'event log online help' there are no records in nettech about this. But when I do a search there are loads of people here having problems.
    Tell us MS what are you doing about this?
    Do you even recognise there is an issues?

    Sorry to vent but I have worked with windows since 3.1 ( how old am I :-) ) and every upgrade since.

    Help out a loyal customer here please

    Geo

    Thursday, January 28, 2010 10:04 AM
  • Nevermind, my last post was hasty. Slowing the memory down from 1333Mhz to 1066 seems to have improved stability (or it's pure luck) but not resolved the problem. I will lower to 800Mhz and report back as per passionflys suggestion.

    To be continued...

    Thursday, January 28, 2010 11:49 PM
  • My PSU is a 550w Antec true power and I am going to buy a new PSU asap, hopefully that solves my issue.

    I have a Corsair 650W PSU and my system shouldn't use more than around 300W so I don't think it's the PU. Also, strangely, my system never crashes while gaming as long as I keep moving. It only crashes if I don't touch the mouse / keyboad for about 30s. In other words, when the load should be lower. It seems to me some kind of timer kicks in after a few seconds, which does something that causes the system to crash.

    It's quite reliable. Don't touch the mouse for around 30s and..... reboot. Quite stressful but it keeps you working. ;)
    Friday, January 29, 2010 11:11 AM
  • Hello Everyone,

    I have been reading this for a while and trying the various fixes or so-called fixes. None of them have helped my situation. I started getting the reboots a couple of weeks ago and have tried most of the items on here. The one thing I haven't tried yet is to disable the RAC task. Has anyone tried this yet and is there any negative impact to doing this?

    I strongly believe that this is not a hardware issue, but more of some type of task or power management issue. I'm not 100% sure yet (still testing) but I think it has something to do with waking up from sleep. I have disabled sleep this morning and will monitor to see if this could be the issue, maybe the RAC task kicks in after waking from sleep?

    I have run all the diagnostic tests and passed, disabled speed step, scan disk, troubleshooter, removed ccc, etc. I am about to try installing windows 7 on a different drive to make sure it has nothing to do with the WD 150 gb velociraptor 10,000rpm drive I just installed. if that doesn't work I'm going back to XP.

    Has anyone tried to use windows 7 32 bit instead of 64 bit?

    Does anyone know if Microsoft has acknowledged this as a real problem yet and are planning to fix soon?

    I can't work from home because of fears of losing data!!!!

    Friday, January 29, 2010 12:01 PM
  • upgrade my power supply to a 900watt and now its perfectly stable. kap
    Friday, January 29, 2010 10:48 PM
  • Running Windows 7 with only one stick @ 1066 MHz. Since I installed it freshly on monday night there was no BSOD or freeze. But I cannot be sure. At the very first try (2 sticks @ 1333 MHz) it has crashed first after one full week.
    Second thin I did is not to install any drivers which are not missing after windows installation. Maybe the chipset driver (AMD 785G) or the graphics driver (ATI 4200HD) are buggy. Why Microsoft provides drivers for AMD 785G and ATI 4200HD by itself? Doesn't they trust the hardware developers?

    DO NOT install the drivers that Microsoft recommends from their Windows Update, go to the source and get the drivers (manufacturer), Never install those POS drivers from Microsoft. I can count about 40 times those Windows Update drivers always gave me problems. The source drivers are always more current and work better and more stable.

    Update 3: The problem seems to be solved! (Well, just only in my specific case, but I think I should publish my solution here). System is running since monday evening without a single occurence of BSOD or freeze. Why do I believe that the issue is gone? First I thought memory or - more specific: memory speed was the cause of the BSODs. Switching memory speed down to 1066 MHz brought no change. BSODs again. Then thought it would be better to run the system with only one stick of RAM at 1066 MHz. Second thing I did was not to install the ATI chipset drivers (All-in-One). After that changes my fresh installed Win 7 was running stable for nearly two days. On wednesday afternoon I installed the second stick of RAM again and turned speed up to the original value of 1333 MHz. No problems happened since that time, system is running 24 hours each day. My main suspicion is now the ATI chipset drivers package. This is the only part I changed. Another possibility (which seems unplausible to me) is that the fact of installing Win 7 with only one stick of memory at 1066 and add the second stick later is influencing the result.
    Saturday, January 30, 2010 9:47 AM
  • Hello Everyone,

    I have been reading this for a while and trying the various fixes or so-called fixes. None of them have helped my situation. I started getting the reboots a couple of weeks ago and have tried most of the items on here. The one thing I haven't tried yet is to disable the RAC task. Has anyone tried this yet and is there any negative impact to doing this?

    I strongly believe that this is not a hardware issue, but more of some type of task or power management issue. I'm not 100% sure yet (still testing) but I think it has something to do with waking up from sleep. I have disabled sleep this morning and will monitor to see if this could be the issue, maybe the RAC task kicks in after waking from sleep?

    I have run all the diagnostic tests and passed, disabled speed step, scan disk, troubleshooter, removed ccc, etc. I am about to try installing windows 7 on a different drive to make sure it has nothing to do with the WD 150 gb velociraptor 10,000rpm drive I just installed. if that doesn't work I'm going back to XP.

    Has anyone tried to use windows 7 32 bit instead of 64 bit?

    Does anyone know if Microsoft has acknowledged this as a real problem yet and are planning to fix soon?

    I can't work from home because of fears of losing data!!!!


    I disabled the RAC task on my dads PC since he was having this BSOD issue, he hasn't had a single problem since, and that was last weekend. Longer than he has ever made it without a BSOD since installing Windows 7.
    Saturday, January 30, 2010 2:05 PM
  • Well, I have new info. I started to notice that before the each kernel power creash I got another error, not critical. It was related to AVG free 9.0. I read on other boards that they uninstalled it and it worked fine. I tired this and it also removed my Security Processor Loader Driver. So I am starting to think that it may have been avg the whole time. I'm going to do a fresh install of windows 7 and I will report back.
    Saturday, January 30, 2010 3:33 PM
  • I have the same problem, worse in 3D games, but happens less often elsewhere. I have tried stopping all power reduction and sleep modes as well as addressing stopping applications running under administrator. All hard disks are checked and clear (4) and the WIN 7 system is running under a dual processor AMD chip with 3 Gig of memory. I am at a loss of what is wrong.
    Saturday, January 30, 2010 7:11 PM
  • All drivers checked and okay, sleep modes and hibernate cleared , administrator apps closed and still get a quick reboot under 3D games and to a lesser sense under regular operations. Hard disks (4) checked and fine, running under a dual AMD processor with 3 gig of memory. Error code is 41 Kernel power loss 41.
    Saturday, January 30, 2010 7:14 PM
  • Tried this solution and doesn't work...still a hard reset after changing administrator tools and checking all drivers and hard disks(4). AMD dual processor with 3 gig of memory.
    Saturday, January 30, 2010 7:16 PM
  • Any solutions? I have gotten rid of all sleep/hybernate modes using full power..got rid of all administrator runs, and still the problem with error 41. Checked the hard drives, drivers, and system is clean. Running on a WIN 7 with AMD dual processor with 3 gig of memory.
    Saturday, January 30, 2010 7:20 PM
  • Solution yet? I have the same reoccuring problem , mostly3D games, but elsewhere. Checked all the disks (4) and drivers up to date along with now power reduction or power sleep/hybernate. Running AMD dual processor with 3 gig of ram.
    Saturday, January 30, 2010 7:23 PM
  • At my wits end, will try this selection and see if it is a reseat or memory module problem. Done the stopping of power sleep/hybernate, done comple disk checks and driver clearences and stopping all administrator control programs. Happens most frequently with 3D programs to a much lesser extent with regular programs. Running AMD dual processor with 3gig of memory.
    Saturday, January 30, 2010 7:28 PM
  • Memory collection errors even with posted error 41, loss of Kernel power? Have checked hard drives, dropping all sleep/hybernate modes, dropped administrator programs...still get error 41 especially running 3D games, programs. Running AMD dual processor with 3 gig of memory.
    Saturday, January 30, 2010 7:30 PM

  • Update 3: The problem seems to be solved! (Well, just only in my specific case, but I think I should publish my solution here). System is running since monday evening without a single occurence of BSOD or freeze. Why do I believe that the issue is gone? First I thought memory or - more specific: memory speed was the cause of the BSODs. Switching memory speed down to 1066 MHz brought no change. BSODs again. Then thought it would be better to run the system with only one stick of RAM at 1066 MHz. Second thing I did was not to install the ATI chipset drivers (All-in-One). After that changes my fresh installed Win 7 was running stable for nearly two days. On wednesday afternoon I installed the second stick of RAM again and turned speed up to the original value of 1333 MHz. No problems happened since that time, system is running 24 hours each day. My main suspicion is now the ATI chipset drivers package. This is the only part I changed. Another possibility (which seems unplausible to me) is that the fact of installing Win 7 with only one stick of memory at 1066 and add the second stick later is influencing the result.

    Problem is not solved at all. Just five minutes ago the system crashed into BSOD. It was running idle, I did nothing. The event list shows me that there was a problem with windows defender update but. The BSOD event was - like all time before - event 41: kernel power. This is the detail view of the event:


    - <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-01-30T22:53:11.899207600Z" /> 
      <EventRecordID>4641</EventRecordID> 
      <Correlation /> 
      <Execution ProcessID="4" ThreadID="8" /> 
      <Channel>System</Channel> 
      <Computer>buero</Computer> 
      <Security UserID="S-1-5-18" /> 
      </System>
    - <EventData>
      <Data Name="BugcheckCode">30</Data> 
      <Data Name="BugcheckParameter1">0xffffffffc0000005</Data> 
      <Data Name="BugcheckParameter2">0xfffff800028c4e39</Data> 
      <Data Name="BugcheckParameter3">0x0</Data> 
      <Data Name="BugcheckParameter4">0xffffffffffffffff</Data> 
      <Data Name="SleepInProgress">false</Data> 
      <Data Name="PowerButtonTimestamp">0</Data> 
      </EventData>
      </Event>

    Does anybody know something about this bugcheck code?
    • Edited by Seven_s Saturday, January 30, 2010 11:35 PM edit
    Saturday, January 30, 2010 11:26 PM
  • so, i had the EXACT same problem as most here.

    brand new system, two days old:
    i7 920 @ 2.67
    6GB OCZ Gold 1600
    ATi 5850 HD
    2 1TB harddisks
    Gigabyte GA-EX58-UD5
    550w OCZ PSU
    Lite-on DVD drive
    Antec p182 case

    so, installing Win7 was a terror! two blue screens even before i got to the install screen.
    after that, it was freezing (black screen, HDD light would turn off) when ever i did anything intense, like, test the hardware, play a game, run photoshop.
    so, i checked out this thread...
    I underclocked my ram to 1066

    played COD MW2 for 30 minutes, no problem.
    opened a huge file in photoshop and played around in lightroom... no problem...
    it stayed on all night, no problem.


    hmm?
    Monday, February 01, 2010 1:18 AM
  • Ok, I'm reporting back. The last thing I worte was I uninstalled AVG 9.0 free and it crashed my system. I reinstalled windows 7 again right on top off the old installation I did not format the drive. It installed well! I created restore points along the way (which I can't see all of them, but that's another issue) and backed up onto other drives. Knock on wood and my fingers are crossed so far so good. I installed MSE instead of AVG and have not had the random reboots. The only issue so far was coming out of sleep the hardrives came on but the monitor did not. Hard reboots did not help, I had to unplug the monitor at the power source to get it to come back on. When it did I noticed I only had a generic pnp driver for the monitor so I updated to a newer samsung driver and all is well. I hope I didn't just jinx myself!!!!! This is far from fully tested it has only been 2 days free of the random reboots. If you have AVG free 9.0 uninstall it, but google or look on the avg site for the uninstaller, doing it through windows crashed my system. I hope this helps some of you out there.
    Monday, February 01, 2010 11:12 AM
  • Same problem since i installed W7 x64
    HP Elitebook 8530w

    - System
       
    - Provider
          [ Name] Microsoft-Windows-Kernel-Power
          [ Guid] {##############################}
       
      EventID 41
       
      Version 2
       
      Level 1
       
      Task 63
       
      Opcode 0
       
      Keywords 0x8000000000000002
       
    - TimeCreated
          [ SystemTime] 2010-01-31T23:09:43.482419300Z
       
      EventRecordID 54783
       
      Correlation
       
    - Execution
          [ ProcessID] 4
          [ ThreadID] 8
       
      Channel System
       
      Computer  
       
    - Security
          [ UserID] S-1-5-18
    - EventData
        BugcheckCode 209
        BugcheckParameter1 0x30
        BugcheckParameter2 0x2
        BugcheckParameter3 0x0
        BugcheckParameter4 0xfffff88004073394
        SleepInProgress false
        PowerButtonTimestamp 0
    Monday, February 01, 2010 5:06 PM
  • Slowing memory down to 800Mhz did not resolve the problem.
    Monday, February 01, 2010 11:51 PM
  • Well, I jinxed myself! It worked fine for 2 days now it's rebooting again. One thing I have noticed is I have 2 HD audio drivers installed one in location 0 and one in location 2. Location 2 is the hard drive that windows 7 is installed on, location 0 is the old hard drive that had xp on it that I have not formated yet, but I am not dual booting either. Could these drivers be the cause? Should I delete the one in location 0?

    Tuesday, February 02, 2010 11:46 AM
  • have you guys tried disabling the ATI/AMD external events utility service. first stop this service and then disable it in its properties and then reboot.
    Tuesday, February 02, 2010 2:14 PM
  • Heey,

    Yesterday i Had the same thing, I was Playing a pc-game when al of the sudden my pc rebooted out of nowhere,
    and windows-event-list said it was a critical error in Kernal-power, ID-41 catogorie:63 proces-id:4 & threat-id:8

    and then i checked Bios (F1-DEl or whatever at firts screen) and checked H\w Monitor and her it was i saw somthing rateter diffrent than normal,
    i check this bios settings often so i know wat it use to say : that the temprature op my processor is aboud 60-70 degrees but now i had a temprature reading op 107degrees !!!!
    so there was a problem with cooling my cpu - and i checketed it, it was coverd in DUST !!! - i cleand it en restartet my pc and now i am keeping a eye on the temratures :)

    so be warned if you have the same problem , check your pc for DUST !!!!

    P.s
    Sorry for the poor english hope you understand it

    Greetz
    Wednesday, February 03, 2010 8:48 AM
  • have you guys tried disabling the ATI/AMD external events utility service. first stop this service and then disable it in its properties and then reboot.

    Are you speaking with some sort of authority to what this service does or functions with? And know what this affects? Cause I am not turning off services I do not understand or know about just cause some person on a forum says "turn it off" willy nilly...

    Please provide more information how specifically this service affects the Kernel-power error then we can follow it. Just saying for ppl to turn something off is not good enough. Thanks
    Wednesday, February 03, 2010 9:08 PM
  • have you guys tried disabling the ATI/AMD external events utility service. first stop this service and then disable it in its properties and then reboot.

    Are you speaking with some sort of authority to what this service does or functions with? And know what this affects? Cause I am not turning off services I do not understand or know about just cause some person on a forum says "turn it off" willy nilly...

    Please provide more information how specifically this service affects the Kernel-power error then we can follow it. Just saying for ppl to turn something off is not good enough. Thanks
    AMD external events utility is the hotkey-poller, only hotkeys.
    I am not a microsoft representative im just a guy like u ppl who is suffering from the same issue, I read bout this on AMD forum and thought I should post it here just for helping someone, Im not forcing u to do something.
    and I think the way you addressed me could have been a little less rude.
    Wednesday, February 03, 2010 9:44 PM
  • I did stop that service and it didn't work. Thanks!
    Here is something new and really wierd, I plugged a sandisk micro drive into the usb port and the system shutdown, it did it also upon removing...now here is where it gets wierd. It also happened when I touched the usb port with my finger...MY FINGER just touch the port and the system reboot, I was about to give in and buy a new PSU but now I don't really know what it can be? It didn't happen just once with my finger it happened 3 out 5 times. HELP!!!!!!
    Thursday, February 04, 2010 1:29 AM
  • hello i am also getting the problems with my intel quad 9750 processor and x64 w7 system and i read on the asus support forum and w7 forum the following:
    My computer is crashing with the following error: “INTERNAL_POWER_ERROR (a0) The power policy manager experienced a fatal error.” What can I do about this?
     
     

    This error is caused by the hibernation file size being is too small for the current memory requirements of the computer. To fix this problem,
    increase the size of the hibernation file by following these steps:

    1.Click the Start button.
    2.In the search box, type command prompt. (cmd)
    3.In the list of results, right-click Command Prompt, and then click Run as administrator.
    4.In the Command Prompt window type:
    powercfg /hibernate /size <size%>
    where <size%> equals the size of the hibernation file in percentage of total physical memory.
    The default size is 75% and can be increased to 100% with:

    powercfg /hibernate /size 100 

    hope it will help some peeps with this problem!greets barrylaros@live.nl

    Thursday, February 04, 2010 8:18 PM

  • Problem solved (this time for real it seems, no crashes for several days!)

    Problem

    Windows spontaneously reboots but gets stuck at the first stages of booting (unsure exactly where). In order to start the computer I have to switch off the main power supply at the PSU for a few seconds and then turn the computer on.

    This happens more frequently when gaming then otherwise, but oddly never while being active. That is, reboots only happen if I'm in a game but I don't touch the controls for a while (around 30s).

    System

    Windows 7, 64-bit
    Athlon II X4 620
    2GB DDR3 1333Mhz

    Did not work
    - Slowing ram down to 800Mhz
    - Updating drivers
    - Disabling power saving options in windows and / or switching off cool 'n' quiet support in bios.
    - Probably a bunch of stuff I forgot and that never made sense anyway.

    Seems to be working

    After a whole lot of googling I've found several prople claiming it's a problem with audio drivers. Apparently some have successfully solved the problem by upgrading the drivers. At least one who had several audio devices had disabled all but one. I disabled ATI HDMI output and Realtek digital output and kept Realtek high definition audio (for headphones) and my Logitech USB speakers (which have a build in sound card of sorts). So far it seems to be working.

     

    Friday, February 05, 2010 1:08 PM

  • Problem solved (this time for real it seems, no crashes for several days!)

    Problem

    Windows spontaneously reboots but gets stuck at the first stages of booting (unsure exactly where). In order to start the computer I have to switch off the main power supply at the PSU for a few seconds and then turn the computer on.

    This happens more frequently when gaming then otherwise, but oddly never while being active. That is, reboots only happen if I'm in a game but I don't touch the controls for a while (around 30s).

    System

    Windows 7, 64-bit
    Athlon II X4 620
    2GB DDR3 1333Mhz

    Did not work
    - Slowing ram down to 800Mhz
    - Updating drivers
    - Disabling power saving options in windows and / or switching off cool 'n' quiet support in bios.
    - Probably a bunch of stuff I forgot and that never made sense anyway.

    Seems to be working

    After a whole lot of googling I've found several prople claiming it's a problem with audio drivers. Apparently some have successfully solved the problem by upgrading the drivers. At least one who had several audio devices had disabled all but one. I disabled ATI HDMI output and Realtek digital output and kept Realtek high definition audio (for headphones) and my Logitech USB speakers (which have a build in sound card of sorts). So far it seems to be working.

     

    this is what I am starting to think too its the audiodg.exe (the go-between file between the OS and your sound card drivers to ensure system stability is actually causing MAJOR system instability) I have many posts in these forums about this file and either disabling (like you did) many audio drivers/features to prevent this file from triggering or leaving them enabled like I have done and actually controlling the audiodg.exe memory use with clever light-weight processes/task memory utilities. The thing to note is that the faster your RAM chips run at (hence my previous recommendations at lowering your memory speed to 800mhz), the more likely this weird instability is likely to trigger.

    I use Minimem 1.3 (freeware), Cleanmem 1.4.0.2 (freeware) and Smartram (by IOBit, freeware) to manage this file specifically (and the OS as well) and prevent it from allocating more memory then it is reasonably supposed to use. I have seen on my system in games this file hogging up to 1GB of system commit memory. By either not releasing it once used or leaking it (not sure which). These 3 small utilities keep this process in check. Cleanmem runs as a scheduled task actually at 5 min intervals reallocating back to the system memory that is not being relinquished back. This is a very clever utility and you should look into it at how it maintains clean memory usage in the system as a whole, not just audiodg.exe. It uses Microsoft's own internal calls to keep memory misallocation from happening on your system. Its a very cleverly done lil app.

    Here are some good links to read about it and corroborating articles:

    http://www.pcwintech.com/cleanmem

    additional info:
    http://smallvoid.com/article/winnt-system-cache.html
    and
    http://blogs.msdn.com/ntdebugging/archive/2007/11/27/too-much-cache.aspx
    and
    http://technet.microsoft.com/en-us/sysinternals/bb897561.aspx
    and
    http://msdn.microsoft.com/en-us/library/ms682606(VS.85).aspx
    and
    http://msdn.microsoft.com/en-us/library/ms686234(VS.85).aspx
    • Proposed as answer by passionfly1 Friday, February 05, 2010 3:59 PM
    Friday, February 05, 2010 3:00 PM
  • I did stop that service and it didn't work. Thanks!
    Here is something new and really weird, I plugged a sandisk micro drive into the usb port and the system shutdown, it did it also upon removing...now here is where it gets weird. It also happened when I touched the usb port with my finger...MY FINGER just touch the port and the system reboot, I was about to give in and buy a new PSU but now I don't really know what it can be? It didn't happen just once with my finger it happened 3 out 5 times. HELP!!!!!!
    ok, you need to contact Microsoft Technical support for this asap. This problem is EXTREMELY disturbing for me to understand why its doing this. Very peculiar behavior for a system board and OS to cause this effect.
    Friday, February 05, 2010 3:29 PM
  • have you guys tried disabling the ATI/AMD external events utility service. first stop this service and then disable it in its properties and then reboot.

    Are you speaking with some sort of authority to what this service does or functions with? And know what this affects? Cause I am not turning off services I do not understand or know about just cause some person on a forum says "turn it off" willy nilly...

    Please provide more information how specifically this service affects the Kernel-power error then we can follow it. Just saying for ppl to turn something off is not good enough. Thanks
    AMD external events utility is the hotkey-poller, only hotkeys.
    I am not a microsoft representative im just a guy like u ppl who is suffering from the same issue, I read bout this on AMD forum and thought I should post it here just for helping someone, Im not forcing u to do something.
    and I think the way you addressed me could have been a little less rude.

    that's all I was asking for is clarification on why it should be disabled. I still do not see a specific link to the kernel-power shutdowns and this service based on your information. I'll keep mine running for now since my system is stable and god only knows what other effect turning off this service will cause to create more problems.

    I was not talking about forcing anyone to do anything but telling ppl to turn off services and not providing information why or how this is related is just bad information or incomplete information at least. We need to have "reasonable" justifications to turn off services that does not create further instability in an already unstable system setting is all. Don't take it personal, as it was not meant to be. =)
    Friday, February 05, 2010 3:35 PM
  • Slowing memory down to 800Mhz did not resolve the problem.

    how much memory is the audiodg.exe process using in peak times when playing a game, viewing movies or using any sound-intensive application?
    Friday, February 05, 2010 3:37 PM
  • Well, I jinxed myself! It worked fine for 2 days now it's rebooting again. One thing I have noticed is I have 2 HD audio drivers installed one in location 0 and one in location 2. Location 2 is the hard drive that windows 7 is installed on, location 0 is the old hard drive that had xp on it that I have not formated yet, but I am not dual booting either. Could these drivers be the cause? Should I delete the one in location 0?


    don't delete anything until you are certain its the right thing to do and always have a backup of your data before doing anything drastic and never listen to anyone telling you to compromise the latter. Its always best to have a backup plan in case "deleting" something causes you to loose all your HD data. Plan for a worst case scenario and you won't be screaming at ppl who may give u misinformative info. Just my 2 cents.

    Make sure you have a verified backup of any important HD stuff you have then it would be safe to say you can delete anything you wish. But again the choice is yours to make. No one can tell u with definitive certainty to go ahead and delete anything, only you can make that decision. That's why its hard to tell you to "go ahead and delete" anything like you are asking us to do, lol
    Friday, February 05, 2010 3:45 PM