Random BSOD in WIndows 7 Kernel-Power Event ID 41

DrillHead · 06 Jul 2014

Hello folks.

Need some help here. I installed Windows 7 Home Premium 64bit in April and I am getting BSODs every week or so. Sometimes more frequently. These have been happening ever since the instal. It was a clean install on a new hard drive. I am running a dual boot set up (by switching boot sequence in my BIOS so I can boot to my XP drive to run some of my older Music production software). I have tried updating drivers but cannot seem to resolve the issue.

The most frequent error has been IRQL_NOT_LESS_OR_EQUAL but have also seen MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA.

I have 3 hard drives divided into multiple partitions. I have my Windows 7 partitions hidden from XP so I don't wipe my backup files from 7. I do have some older hardware installed as well that I use for Music production. Such as a 750MB Zip drive.

CPU is an Intel Q6600 at 2.4 Ghz all stock settings nothing is OC. 4 GB of RAM. I ran Memtest86+ through numerous passes with no errors so I the RAM is good. I've tried a few other fixes from reading on the interwebs but nothing has worked.

I used to run Avast but suspected that may be causing the issues so I switched to Microsoft Security Essentials but the problem still exists.

I would very much appreciate some help on this.

I have attached the .zip file from DM Log collector. ALso ran SFC Scannow with no problems found. I'm at a loss...

Many thanks in advance for the assistance.

Arc · 06 Jul 2014

Hi DrillHead.

You are having various bugchecks, and all are referring to memory. Not necessarily the RAM, but may be some drivers are failing.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If it does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

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.

Let us know the results, with the subsequent crash dumps, if any.
___________________________________

Code:

BugCheck 1A, {41790, fffffa8000b1ca80, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+35084 )

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

Code:

BugCheck A, {80, 2, 1, fffff80003696f1f}

Probably caused by : ntkrnlmp.exe ( nt!KeAcquireInStackQueuedSpinLock+5f )

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

Code:

BugCheck 50, {fffffa81512ecb50, 0, fffff800036ecaf8, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MmUnmapViewInSystemCache+1c9 )

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

DrillHead · 06 Jul 2014

Thank you so much for the response.

As I said in my original post: I ran Memtest86+ overnight for numerous passes (12) with no errors already. Are you suggesting I do that again? Or should I just move on with Driver Verifier?

DrillHead · 06 Jul 2014

I am running verifier. No issues yet. If the machine crashes again where do I see the "results" to let you know?

Arc · 07 Jul 2014

Just follow the Blue Screen of Death (BSOD) Posting Instructions. :)

DrillHead · 07 Jul 2014

Okay. I thought I did that already? Do you mean just upload the info again from DM Log Collector?

Sorry but I'm a little new to this kind of assistance. Normally my machines run well and I have no trouble resolving issues as they come up. This one has thrown me for a loop...

Arc · 07 Jul 2014

Every time you report about a BSOD, you need to do it following the BSOD posting instructions. :)

DrillHead · 07 Jul 2014

Thanks Arc. I understand. It's been 24 hours with Verifier enabled. I have attached the log file.

No crashes. Should I disable Verifier now or leave it enabled until I get another BSOD? Awaiting your advice. Thanks.

Arc · 08 Jul 2014

No crashes. That means, the drivers are in safe side; provided driver verifier was properly applied.

Disable verifier now, and see if the BSODs are back.

But, if RAM is not failing, and drivers are not causing the issue too, any further BSOD will be very vital.

DrillHead · 08 Jul 2014

I followed your instructions to the letter regarding Verifier... You didn't mention any way to verify if Verifier was properly applied other that "system is a bit slow and laggy". I haven't noticed much change since enabling it, though I did see such a comment in the linked thread using the command prompt and running the command "verifier \query" without the quotes. This returned a list of drivers and other info related to them. The other thread did not mention what to look for after running the command in order to confirm that it is working properly.

I will disable Verifier and then follow up with another log if the system does in fact crash again.

Thanks again for your help and for your patience with me trying to understand the whole process.