Kernel-Power 41 Random Crashing

Hi guys, I had this problem about a month ago.

I updated all my drivers and did a few other things which solved it.

Whenever my computer crashes it just stops, no BSOD just a strange noise on the speakers sometimes, and completely unresponsive so I have to reset the computer manually via the button.

When the reset happens my keyboard loses it back lighting.

I have been keeping track of time, last one was 7:33 this morning, then checked the Event Viewer and again (like usual) It says ' Event 41 Kernel - Power'

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 have already done the solutions on the Mircrosoft website, atleast I did the 3rd solution (unticking the restart button)

Much help is appreciated
(here is everything attached the results are inside the ZIP File)
Attachment 169338

Also, I just remembered, after the initial crash, it seems to run fine until the next time I turn it off and back on, it then crashes once then is fine...

redfox2020 said:

Hi guys, I had this problem about a month ago.

I updated all my drivers and did a few other things which solved it.

Whenever my computer crashes it just stops, no BSOD just a strange noise on the speakers sometimes, and completely unresponsive so I have to reset the computer manually via the button.

When the reset happens my keyboard loses it back lighting.

I have been keeping track of time, last one was 7:33 this morning, then checked the Event Viewer and again (like usual) It says ' Event 41 Kernel - Power'

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 have already done the solutions on the Mircrosoft website, atleast I did the 3rd solution (unticking the restart button)

Much help is appreciated
(here is everything attached the results are inside the ZIP File)
Attachment 169338

Also, I just remembered, after the initial crash, it seems to run fine until the next time I turn it off and back on, it then crashes once then is fine...

No DMP files included in upload please try this method

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

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 the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.


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.

Ah, okay I will upload it again when i'm home, thank you for the quick reply

Hi

I've attached the required folder, when I was my computer reset and came up with a quick BSOD, but then went black and restarted. So hopefully it won't reset again tonight...!

Thank you again

Crashed again today. It seems to... crash once when I turn it on (after 15-20 minutes) then after the reset, its fine until next time I turn it on. (Next day)

I just had another reset, checked the tim 6:15, then checked the event viewer...

File System Filter 'Avgmfx64' (6.0, ‎2011‎-‎03‎-‎01T13:25:15.000000000Z) has successfully loaded and registered with Filter Manager.

Googled that, came back to this site...

https://www.sevenforums.com/crashes-d...es-freeze.html

So now I'm uninstalling AVG and seeing it that works!

Will update either way.

redfox2020 said:

Hi

I've attached the required folder, when I was my computer reset and came up with a quick BSOD, but then went black and restarted. So hopefully it won't reset again tonight...!

Thank you again

Memory corruption probably caused by a driver. please run these two tests



1-Memtest. Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.

Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.



2-Driver verifier

I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Hi,

Removing AVG seemed to stop the problem, but now I have another;

Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
Feature: Behavior Monitoring
Error Code: 0x80004005
Error description: Unspecified error
Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

And again a few more times,

here is a crash report;


Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 15/08/2011 07:29:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081511-17674-01.dmp
This was probably caused by the following module: luafv.sys (luafv+0x1F2)
Bugcheck code: 0xFC (0xFFFFF880041AD1F2, 0x80000002AC380963, 0xFFFFF88003C85A40, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\Windows\system32\drivers\luafv.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: LUA File Virtualization Filter Driver
Bug check description: This indicates that an attempt was made to execute non-executable memory.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. There is a possibility this problem was caused by a virus or other malware.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Sun 14/08/2011 19:38:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081411-17799-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF88004932233)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 12/08/2011 17:14:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081211-14164-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0xD1 (0x11, 0x2, 0x0, 0xFFFFF88005DBD23E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Tue 09/08/2011 17:28:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080911-37783-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7FD00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800035A26F9, 0xFFFFF8800DB0AE60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.