BSOD Random but Linked to NTOSKRNL Failure

Page 1 of 3 123 LastLast

  1. Posts : 15
    W7 Pro 64 w/SP1
       #1

    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 Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

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



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


  3. Posts : 15
    W7 Pro 64 w/SP1
    Thread Starter
       #3

    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 Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    traderyoda said:

    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 Computer


  5. Posts : 15
    W7 Pro 64 w/SP1
    Thread Starter
       #5

    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 Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    You may disable the Epson entries in the startup.
      My Computer


  7. Posts : 15
    W7 Pro 64 w/SP1
    Thread Starter
       #7

    Will do - will get to it now!

    THX
    TY
      My Computer


  8. Posts : 15
    W7 Pro 64 w/SP1
    Thread Starter
       #8

    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 Computer


  9. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #9

    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 Computer


  10. Posts : 15
    W7 Pro 64 w/SP1
    Thread Starter
       #10

    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 Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
Our Sites
Site Links
About 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 14:35.
Find Us