Solved BSOD while idle - Kernel Power Event ID 41

[CactusBomb]

I had played Skyrim a few hours prior to this happening. The system had been idle for a bit after that. I have had this happen to my system once each month for the last 4 months. Any suggestions?

Thanks

 

[HarriePateman]

Welcome to SevenFoums,

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="Red"]MEMORY_MANAGEMENT [/COLOR]([COLOR="blue"]1a[/COLOR])
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, [COLOR="Blue"]A page table page has been corrupted.[/COLOR] On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8000a19be0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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

As we can see something has corrupted a page table, so there are a few tests i would like you to perform.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+​

If there is no error, enable Driver Verifier to monitor the drivers.

Driver Verifier - Enable and Disable
​

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

 

[CactusBomb]

Ok, just finished running a 20-hour memtest. The results look good. I had run this a few weeks ago when I installed 6GB more of RAM into my mobo so I'd be running 12GB but it turns out the new RAM was faulty. Found errors within the first 2 hours of the test. So at least the RAM I have currently installed is working fine.

Now to run the dreaded DV...

 

[HarriePateman]

Ok, just finished running a 20-hour memtest. The results look good. I had run this a few weeks ago when I installed 6GB more of RAM into my mobo so I'd be running 12GB but it turns out the new RAM was faulty. Found errors within the first 2 hours of the test. So at least the RAM I have currently installed is working fine.

Now to run the dreaded DV...

Thats a good sign

 

[CactusBomb]

Ok, so I almost went the full 24 hours running DV without a BSOD until this morning, after it had slept all night, I woke up the computer and it gave me the BSOD within 15 seconds. Then rebooted and tried to disable DV and got another BSOD, and then tried again and got another BSOD. So I restarted in Safe Mode and was able to disable DV. Looking into the event veiwer it's still the same Kernel-Power Event ID 41 error.

Attached is a photo of the BSOD I was getting this morning. Where should I go from here? It looks like it's a driver issue.

 

[HarriePateman]

Can you upload the new DMP files please.

 

[CactusBomb]

Yep, not a problem.

Thanks, for the quick response!

 

[HarriePateman]

Okay this BSOD, gives us a different output.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffffa8006e9eeca, 8, 0, fffff8800108d356}

*** WARNING: Unable to verify timestamp for [COLOR="red"]jraid.sys[/COLOR]
*** ERROR: Module load completed but symbols could not be loaded for [COLOR="Red"]jraid.sys[/COLOR]
Probably caused by : jraid.sys ( jraid+4356 )

Followup: MachineOwner
---------

jraid.sys is used for creating the DMP Files, is your windows fully upto date?

 

[CactusBomb]

I just checked, it says it's updated but then had 6 other update installations recommended so I'm currently installing those as well.

nVidia Graphics Adapters WDDM1.1 WDDM1.2 and WDDM1.3, Acer Display HDMI up date, and updates for Windows 7 for x64 based systems KB2709981 KB2830477 KB2592687 and KB2574819 (which I am running)

 

[HarriePateman]

Okay let me know when there done.

 

[CactusBomb]

All set and rebooted.

Should I run the dm log collector again?

 

[HarriePateman]

Try it again yes

 

[CactusBomb]

Here's the latest!

 

[HarriePateman]

Okay same error, can you download this driver please: ftp://driver.jmicron.com.tw/SATA_Controller/Windows/JMB36X_WinDrv_R1.17.62_WHQL.zip

Then restart and tell me how it goes.

I was able to find this link from another post within the Forum.

 

[derekimo]

Ok, so I almost went the full 24 hours running DV without a BSOD until this morning, after it had slept all night, I woke up the computer and it gave me the BSOD within 15 seconds. Then rebooted and tried to disable DV and got another BSOD, and then tried again and got another BSOD. So I restarted in Safe Mode and was able to disable DV. Looking into the event veiwer it's still the same Kernel-Power Event ID 41 error.

Attached is a photo of the BSOD I was getting this morning. Where should I go from here? It looks like it's a driver issue.

The cause of the BSOD in this picture is Avast,

BugCheck C4, {e3, fffff8800402854f, 6e0010, 0}

Unable to load image \SystemRoot\system32\drivers\aswSP.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSP.sys
Probably caused by : aswSP.sys ( aswSP+2854f )

Followup: MachineOwner

For the time being, uninstall your Anti-Virus,

AV Uninstallers

And Install Microsoft Security Essentials which we know doesn't cause BSOD's.

 

[CactusBomb]

Ok, I installed the driver and it it seems to be firing on all cylinders. No BSOD yet.

I also uninstalled avast! and installed MSE. I ran a quick scan and found no issues.

Here is the latest dm log collector.

 

[HarriePateman]

Glad to hear that you have not had another BSOD, there will be no more DMP Files unless there is a BSOD.

The file you uploaded are the same

Any more problems give us a shout!

 

[CactusBomb]

Great! Thanks for your help!