Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Random but Linked to NTOSKRNL Failure

02 Sep 2014   #1
traderyoda

W7 Pro 64 w/SP1
 
 
BSOD Random but Linked to NTOSKRNL Failure

Greetings,

...and thanks in advance for the support.

My PC is custom and I built it up a few years ago; it's been like a rock until a few months ago. I started to get a few BSODs, so I tried rolling back Windows - that didn't help. I tracked things to some memory issues, so I ran Memtest86+ and found one stick with a few errors on Test #8. Rather than take a chance I just replaced the memory with 4 new 2GB Corsair sticks - I tested each of the new sticks with Memtest before installing and they all passed. I thought I had the problem licked until I got another BSOD. Using BlueScreenView the fault is either a '0A' or a '50' almost always traced to ntoskrnl.exe. I tried to search for typical causes and did things like turn off Firewire in BIOS, remove some software people suggested were problematic, etc. - no change. The BSODs seem to occur when the PC has been running awhile. If I leave the PC running all night about 1/2 the time I'll wake up to a BSOD. Finally I bit the bullet and reloaded Windows 7 Pro 64 and all my software for a fresh start- a major pain, but I was getting desperate. A few days later and another BSOD. I'm getting nervous that this is a hardware problem. This PC is not overclocked and runs cool, and I can't find any evidence of a board problem. Power supply checks out perfectly. So I'm about out of ideas and could use a hand.

I've attached a snippet from BlueScreenView and the ZIP file from the diagnostic tool.

Cheers,
TY


My System SpecsSystem Spec
.
04 Sep 2014   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

ntkrnlmp.exe is not the reason behind the BSOD but it is the kernel on which the crash takes place. When the crash dump recording mechanism fails to detect any reason behind the BSOD, it blames the kernel itself. As it happens with you.
Code:
BugCheck 50, {fffff80022ee91af, 8, fffff80022ee91af, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+448c6 )

Followup: MachineOwner
---------
A stop ox50 BSOD is PAGE_FAULT_IN_NONPAGED_AREA. As per Carrona.org,
Quote:
Usual causes: Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS
Your BIOS is very old.
Code:
BiosVersion = 2301   
BiosReleaseDate = 07/10/2009
But it is the latest one.

Let us check the other possibilities, one by one.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest86+ for at least 8 consecutive passes.

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
04 Sep 2014   #3
traderyoda

W7 Pro 64 w/SP1
 
 

Thanks Arc...

Yes, nothing much I can do about the BIOS - that was my first stop in the hunt, but no dice.

I'll go back and test the RAM again, stick by stick. I've read that Memtest86+ Test #8 is the most challenging, and before I replaced my RAM with the 4 new 2GB sticks it only faulted on that test. I did test the new sticks (Test #8) and they all passed. But it's worth repeating. I'll run the entire series of tests and post back.

Question: how can you tell whether the RAM is bad or it's a memory controller problem on the hardware side?

BEST,
TY
My System SpecsSystem Spec
.

04 Sep 2014   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by traderyoda View Post

Question: how can you tell whether the RAM is bad or it's a memory controller problem on the hardware side?
Do the test first with all the RAM modules attached. If failures are detected, then we will see how can we dig further.
My System SpecsSystem Spec
05 Sep 2014   #5
traderyoda

W7 Pro 64 w/SP1
 
 

Greeting Arc

Memtest86+ ran through 9 passes with all RAM in and all tests - no errors. So it appears I do not have a RAM or memory controller error. Anything else I need to do before running the driver monitoring program?

Cheers,
TY
My System SpecsSystem Spec
05 Sep 2014   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

You may disable the Epson entries in the startup.
My System SpecsSystem Spec
05 Sep 2014   #7
traderyoda

W7 Pro 64 w/SP1
 
 

Will do - will get to it now!

THX
TY
My System SpecsSystem Spec
05 Sep 2014   #8
traderyoda

W7 Pro 64 w/SP1
 
 

Arc - ran with Driver Verifier enabled per directions. It ran perfectly doing my normal office work and such. I was done with the machine for awhile and I decided to transfer a large block (over 200 gigs) of music to a blank harddrive figuring it would put some stress on the system. Got a BSOD very quickly. The dump file is attached.

This is pretty much what I've experienced before... I seem to get a BSOD when I have the machine loaded up, or when I leave it transferring large files overnight. Maybe it's a heat related problem, although it's run for many years configured as it is now.

Thanks again for hangin' in there with me!

Cheers,
TY
My System SpecsSystem Spec
06 Sep 2014   #9
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

The verifier enabled crash dump reports memory failure.
Code:
BugCheck A, {fffffa860117eb0a, 2, 0, fffff80002ef7537}

Probably caused by : memory_corruption ( nt!MiPfnShareCountIsZero+77 )

Followup: MachineOwner
---------
Is the blank HDD is one of your removable discs? In that case it might be associated with some chipset (USB) issue. Though the manufacturer does not have any update listed, you may try the Intel® Driver Update Utility from https://downloadcenter.intel.com/default.aspx .

Sometimes the antivirus also may cause blockage to storage filters. Uninstall Avast using Avast Uninstall Utility. Just on a test basis. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.

Then try to replicate the issue, with DV disabled. Let us know the result.
My System SpecsSystem Spec
06 Sep 2014   #10
traderyoda

W7 Pro 64 w/SP1
 
 

Hmmm... memory problem. I naively assumed I had a RAM problem and swapped out RAM, maybe unnecessarily.

I'm in the process of taking each of these steps.

The blank harddrive was a recently reformatted internal SATA WD 750GB Green Drive. I use it as a backup storage device for music.

As soon as I get this done I'll give it another large transfer, see what happens and report back!
My System SpecsSystem Spec
Reply

 BSOD Random but Linked to NTOSKRNL Failure




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Random BSODs, often 109s, usually linked to ntoskrnl.exe
Hi all, A friend built me a gaming computer three years ago (most of the specs should be in my profile) and it crashes every so often. Sometimes a few times in a single day, sometimes once a month. This can happen in the middle of a game, when browsing the Internet or when the computer is...
BSOD Help and Support
BSOD on shut down (linked to USB device/driver failure)
Hello, I recently started having issues with my USB wifi stick. In irregular intervals (several times a day, especially, but not exclusively, when I'm running resource intensive programs) it will stop working completely as if it had been disconnected from the computer and it won't resume...
BSOD Help and Support
Random BSOD possibly linked to Chrome
Ok, this is my first time here, so I hope I have done everything right. Attached is the zip file from the SF diag tool. In it are the errors for 3 crash dumps. Here is my story: I've always got blue screens since I built this computer about 8 months ago. It was very rare, we are talking less...
BSOD Help and Support
BSOD possibly Google Chrome linked, error 0x000000f4 ntoskrnl.exe
I have been experiencing BSODs about once a day for more than a week, as far as I can remember it's always when using Google Chrome (though I almost always have Chrome open, so it might not be related). The BSOD occurs seemingly randomly, often after hours of using the computer without any...
BSOD Help and Support
Random BSoD, Driver Power State Failure, reports blame ntoskrnl.exe
Hello and thanks for letting me post on this awesome forum!!!! I am fixing a family members computer and it has stumped me. I have tried everything that I can find online related to my problem outside of reinstalling but I think it could be a hardware (power or memory) issue from what i read and...
BSOD Help and Support
Random BSOD : ntoskrnl.exe (nt+0x7CC40) Driver Power State Failure
Hi XPS L502x : 2nd generation Intel Core i7-2720QM processor 2.20 GHz with Turbo Boost 2.0 up to 3.30 GH 8Gb Ram Windows 7 64 bit Have been having repeated BSODs lately. Used to get them about once or twice a week but its now a few times a day that it happens. Have attached the zip...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 17:32.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App