Solved Random BSOD in WIndows 7 Kernel-Power Event ID 41

[DrillHead]

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]

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.
___________________________________

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

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

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

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

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

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

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


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

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

 

[DrillHead]

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]

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

 

[Arc]

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

 

[DrillHead]

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...
:huh:

 

[Arc]

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

 

[DrillHead]

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]

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]

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.

 

[DrillHead]

Disabled verifier and everything seemed to be working just fine. Shut the computer down this morning before going to work and it hung on the "shutting down" screen. No record of it in event viewer at all and no minidump files???

I guess I'll hope for no "next time" and if it does I'll upload the log files.

 

[DrillHead]

Hello again. Got another BSOD today. I've made 1 change since my last post. I updated my mouse drivers (Logitech MX518). I had noticed the USB connect and disconnect noise a few times for what seemed like no reason. Then my pointer disappeared and reappeared. I double checked and Windows was using the default driver instead of the Logitech driver. SO I updated hoping that might solve the problem for good. No dice.

Here is the log. Thanks in advance.

 

[DrillHead]

Bump. The error this time was BAD_POOL_HEADER. First time I've seen that...

A little help please. Thanks!

 

[Arc]

Bump. The error this time was BAD_POOL_HEADER. First time I've seen that...

A little help please. Thanks!

Sorry, I was not able to come online for a few days.

As you said you experienced a new BSOD, can you upload the files again?

 

[DrillHead]

can you upload the files again?

Thanks. I understand. Check the post before my "bump" Those are the files.

 

[Arc]

Can you plan to update the BIOS? Apparently it is the same version, but the update date is newer.

Suggested BIOS update: Driver Details | Dell US

View attachment 325787

Your BIOS info:

BiosVendor = Dell Inc.                
BiosVersion = 2.5.3 
BiosReleaseDate = [COLOR=Red]11/22/2007[/COLOR]
SystemManufacturer = Dell Inc.                
SystemProductName = Dell DXP061

Let us know if it is any helpful.
_________________________________________

BugCheck 19, {22, 200700ebdc000, 0, 0}

GetPointerFromAddress: unable to read from fffff80003913100
GetUlongFromAddress: unable to read from fffff800039131c0
GetUlongFromAddress: unable to read from fffff80003881a38
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+72e6 )

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

 

[DrillHead]

I updated the BIOS as requested. I had considered that before but didn't notice the update version was different only saw that it was the same version number so I did not go through with it. This time I flashed it with the newer update.

I noticed something odd today as well. I had left the computer on while away and it went into powersaver mode and had shut off the hard drives. When I woke it up my second partition on one of my drives (where my XP OS resides) would not respond. First partition (where the actual XP OS is) on the same drive was active and accessible as was everything else. I decided to reboot to see if it came back online and the system went to the "shutting down" screen and would not go ahead and reboot. After waiting for quite some time I went ahead and shut it off manually. Waited for a bit and then booted back up. Checked my boot sequence and checked my XP install that is on that other drive. XP still runs like a dream when I boot into it. I rebooted again and went back into Windows 7 and everything came up fine. I noticed the event log showed that Windows 7 had "rebooted without cleanly shutting down" in the critical events section. There were also numerous occurrences on the following error:

IaStorV, Event ID = 9. And the details show this:

The device, \Device\Ide\iaStor0, did not respond within the timeout period.

Could this be causing/contributing to the problems?

 

[DrillHead]

I also disabled my Iomega 750MB drive in Windows 7. I only use this drive in XP so I figured it couldn't hurt to disable it under 7. I figured it could only help if this was causing my issues.

I know that making multiple changes can make it more difficult to isolate the actual cause of the problem but since I don't use it under 7 there was no need to have it enabled then anyway. One less factor in troubleshooting.

Good idea? Bad idea? I'm open to any input.

Most of the time everything seems to run flawlessly but the occasional BSOD and the occasional hang up when shutting down is irritating me. I have had such a clean running system for so long that I've become a bit OCD about these issues. I really want 7 to run as flawlessly as my XP OS always did and still does. I haven't experienced any such issues with my XP install... ever.

 

[DrillHead]

7 days and no crashes. So far so good Arch. Thanks for the help. I'll update again in 7 more days just to be sure.

 

[Arc]

OK, take your time to observe the situation.