locked
event id:41 RRS feed

  • Question

  • my pc configuration is 

    {

    OS Name Microsoft Windows 7 Ultimate
    Version 6.1.7600 Build 7600
    System Manufacturer Gigabyte Technology Co., Ltd.
    System Model G31M-ES2L
    System Type X86-based PC
    Processor Intel(R) Core(TM)2 Duo CPU     E7400  @ 2.80GHz, 2800 Mhz, 2 Core(s), 2 Logical Processor(s)
    BIOS Version/Date Award Software International, Inc. F8, 2/5/2009

    Installed Physical Memory (RAM) 2.00 GB

    Total Physical Memory 2.00 GB

    Available Physical Memory 397 MB

    Total Virtual Memory 4.00 GB

    Available Virtual Memory 1.47 GB

    BIOS Version/Date Award Software International, Inc. F8, 2/5/2009
    SMBIOS Version 2.4

    }

    log name: System

    source: Kernel-Power

    level: Critical

    task category : (63)

    key word:  (2)

    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    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] 2013-04-05T11:28:04.754012800Z
    EventRecordID 9960
    Correlation
    - Execution
    [ ProcessID] 4
    [ ThreadID] 8
    Channel System
    Computer Prashanth-PC
    - Security
    [ UserID] S-1-5-18
    - EventData
    BugcheckCode 278
    BugcheckParameter1 0x85f58168
    BugcheckParameter2 0x91b258a4
    BugcheckParameter3 0x0
    BugcheckParameter4 0x2
    SleepInProgress false
    PowerButtonTimestamp 0


    m.vamsi krishna

    Friday, April 5, 2013 3:09 PM

Answers

  • Hi,

    Meanwhile, you can take a look at this link:

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

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


    Alex Zhao
    TechNet Community Support

    • Marked as answer by Cloud_TS Friday, April 19, 2013 7:48 AM
    Tuesday, April 9, 2013 1:59 AM
  • You also need to install Service pack 1


    "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    BugCheck 116, {85f22510, 8f1118a4, 0, 2}

    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+f88a4 )


    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    • Marked as answer by Cloud_TS Friday, April 19, 2013 7:48 AM
    Wednesday, April 10, 2013 6:31 PM

All replies

  • Event ID 41 simply means that the last shutdown was unexpected.  If you had a Blue screen follow these

    We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.
    If you are overclocking stop.  (chances are if you dont know if you are, you are not)a
    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.  We need at least 2 DMP FILES to diagnose and confirm


    The procedure:

    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button. (if available on  your site, MS doesnt have this)
     *Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.
    Link for how to  upload below.
    http://www.wikihow.com/Use-SkyDrive

    To ensure minidumps are enabled:

    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
    * OK your way out.
    * Reboot if changes have been made.

    Please also run MSinfo32 and upload the output as well.
    To run MSinfo32 please go to start>run>MSinfo32
    Go to "file" "save" and upload the saved file with the DMPS
    (Instructions for XP, Vista, Win 7, Win 8)
    System specs are often useful so include whatever you know


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    Friday, April 5, 2013 4:27 PM
  • Hi,

    Meanwhile, you can take a look at this link:

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

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


    Alex Zhao
    TechNet Community Support

    • Marked as answer by Cloud_TS Friday, April 19, 2013 7:48 AM
    Tuesday, April 9, 2013 1:59 AM
  • You also need to install Service pack 1


    "It's not a true crash, in the sense that the Blue Screen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

    Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OS's like XP to crash.

    As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
    If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.


    If playing with video driver versions hasn't helped, make sure the box is not overheating.
     Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
     Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.


    If so, it might be as simple as dust buildup and subsequently inadequate cooling.

    I would download cpu-z and gpu-z (both free) and keep an eye on the video temps

    BugCheck 116, {85f22510, 8f1118a4, 0, 2}

    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+f88a4 )


    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.


    Wanikiya & Dyami -Team-ZigZag. www.ZigZag3143.com email Admin@zigzag3143.com

    • Marked as answer by Cloud_TS Friday, April 19, 2013 7:48 AM
    Wednesday, April 10, 2013 6:31 PM