Kernel Power Critical Error, event id 41

Anonymous

Good afternoon,

I have been having this problem for a little while now and it's incredibly frustrating.

At random intervals my system will restart without warning. I have disabled the automatic restarting in the system protection settings and I have read through the Knowledge Base articale found here: ( http://support.microsoft.com/kb/2028504 ).

I am not overclocking my system and I have run MemTest to check the system memory. My Power Supply is a 500w unit and my usage is far below that as best I can tell (Asus P8Z68-V PRO/GEN3, Intel i5 3450, Corsair 2x8GB RAM, WD 340 GB HD, HP DVD Writer, USB Mouse, Keyboard, Headphone, WebCam, and 5 cooling fans). All my fans are running, operating correctly and free of dust (I blow them out regularly).

Windows is up to date and I have updated all of the drivers (I think) that I can. I have also enabled the kernel dump feature in the system protection settings and, as of yet, no dump file has been created by any of these events (13 in the last 7 days

5 today).

This error occurs at random intervals, even when the system is sitting idle in the middle of the night. I have allowed my system to sit with a Linux Live CD loaded up and have not noticed it rebooting then, so I am guessing it's not a loss of power kind of thing; it very much appears to be some kind of problem with Windows and the software drivers or hardware that I have. This is extremely frustrating and I just want my system to work and not feel like I have to fight with it to do so; dare I say it kind of makes want a Mac (*ducks*).

If anyone has any ideas, please help me out. I'm debating whether to pull my own hair out or throw the computer out the window.

Thanks,

Michael

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

Your last sentence caused me to realise none of your recent unexpected restarts have resulted in the production of a dump file.

Most system failures result in a BSOD (Blue Screen of Death) and a dumpfile report is created providing that the computer has been configured to create reports. In a limited number of system failures no dumpfile is created. A report is generated when the computer is next booted and placed in the System Log in Event Viewer. The report is given an Event ID number 6008 and gives very little helpful information, save that the cause is unknown and that it occurred at the date and time specified. . A further report is placed in the Reliability Monitor with a red orb on the Miscellaneous Failures line and it is recorded as a Critical Failure. Unfortunately the Technical Details for this type of failure reveal no additional information.

The more common causes of this type of failure all relate to power failure.

These can be because:

The user has pressed the Power On / Off button.
A power failure or a loss of supply to home or office where the computer is located. If this has happened it will often be obvious because electric lights are other electrical appliances switch off.
A faulty electrical appliance on the same electrical circuit as the computer or the computer trips the contact breaker or blows a fuse and switches off the supply for safety reasons.
The power cable between the mains power socket and the computer becomes disconnected at either end.
A power surge or lightning strike occurs. Your computer should connect to an uninterruptible power supply unit, which then connects to the mains supply. If an incident occurs you will have to reset the uninterruptible power supply unit. Without one of these units in place a lightning strike or power surge can damage the computer beyond repair.
A faulty power supply unit. The best test here is to remove the existing power supply unit and replace with a known good power supply unit having the same capacity. Most home users do not keep a spare power supply unit to hand.
A damaged or disconnected power cable or motherboard connector within the computer. You can check the cable is properly connected but a damaged motherboard is not easily checked.
If the computer is a laptop check whether the battery can be fully charged, holds the charge and was or was not connected to a mains supply when the failure occurred.

A related Microsoft Knowledge Base Article:

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

0 comments

44 additional answers

Anonymous

2013-02-03T10:22:04+00:00

Michael

Try installing these drivers for your unknown device.

http://www.atheros.cz/atheros-bluetooth-download.php?chipset=57&system=6

Unzip the download and place the contents in a folder on your desktop. Open Device Manager and select the Driver tab for the unknown device. Click on Update driver and Browse my computer for driver software. Browse to the folder where you have placed the extracted files. Then do whatever is necessary.
Was this answer helpful?

0 comments No comments
Anonymous

2013-02-03T09:11:16+00:00

Gerry,

Thank you for the extra information on the 6 and 17 events.

I do have 1 notification in the device manager, it's listed as an 'unknown device', but that could just be the blue tooth that is located on my mother board. I tried to update the driver, but one cannot be found automatically. I will need to see if I can find one on the Asus support page for my mobo.

The error code is Code 28: The drivers for this device are not installed.

Under the details tab I do not see a property listed as 'Device Description'. There is a value for display name that merely says 'unknown device', but the first install date was 1/29/2013 1:07:38 PM; perhaps that might be in the logs somewhere. The Device Instance Path value is USB\VID_0CF3&PID_3000\6&DF2EE03&0&7.

I have several logitech devices on my system ... first is my keyboard and mouse and second are my G930 headphones. The only problem I am having is that the extra buttons on the mouse that are used for back and forward in my browser isn't working and I haven't been able to figure out why; that has never happened before.

Thank you,

Michael
Was this answer helpful?

0 comments No comments
Anonymous

2013-02-03T07:19:42+00:00

Gerry,

As requested, I have updated the system information to my SkyDrive:

https://skydrive.live.com/?cid=62C91C18AE0BDB44&id=62C91C18AE0BDB44%21108

I poured over the system log for a while this evening and have noticed that two notices precede every single one of the event 41 critical errors:

Event 17. mv91xx: "Adapter is detected.".

Event 6 FilterManager: "File System Filter 'MpFilter' (6.2, ‎2012‎-‎08‎-‎23T18:03:14.

Each of the 6 and 17 events are informational events, not errors, but every single time both of these events come in less than 10 seconds before the event 41.

The event 6 item is associated with MS's Malware Tool (installed via Windows Update and te event 17 item is associated with my SATA controller. I am fairly certain that driver up to date, but I'm going to check that again to make absolutely sure.

Thank you again for your help here Gerry. I'm about at my wits end.

Michael
Was this answer helpful?

0 comments No comments
Anonymous

2013-02-03T07:06:24+00:00

Michael

The first of the unexpected restarts occurred on 23 January 2013 at 21.00.29. On 22 January a number of changes seem to have occurred and some seem to have been problematic. I would like to compare what is in your logs to that reflected in your System Information file.

Type System Information in the Search Box above the start Button and press the ENTER key. Select File, Export and give the file a name noting where it is located. Please upload to your Sky Drive, share and post a link here.
Was this answer helpful?

0 comments No comments