Lots of BSOD problems 1A 3B 0A 50 1E C4 BE 4E

Page 3 of 5 FirstFirst 12345 LastLast

  1. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #21

     nVidia Driver

    Your nVidia driver has been flagged. Download the previous version from here and save it to your desktop. Then follow NVIDIA Drivers - Avoid Problems for the cleanest possible install.
    Code:
    fffff880`0b88b268  fffff880`04990d81Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x109d81
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`04887000 fffff880`052bf000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Apr 08 21:32:37 2015 (55259065)
        CheckSum:         009F7AE7
        ImageSize:        00A38000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     SFC /SCANNOW

    Open an elevated command prompt and type in or copy and paste sfc /scannow and hit enter. Post back with the results.
      My Computer


  2. Posts : 2,781
    Windows 10 Pro x64
       #22

    Hm, it's still blaming memory corruption. Have you tried 8 passes on each stick(take all the other sticks expect one and take the test for 8 passes and switch and do the samething?)
      My Computer


  3. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #23

    Thanks for the replies again guys.

    Boozad, I'd already used DDU to get rid of all traces of NVIDIA drivers, and reinstalled the latest. Just gone through what you suggested and installed the version previous to this one but it's still crashing.

    Laith, I ran MemTest for about 48 hours straight with no errors, so far I must have done about 40 passes and haven't seen a single error yet.
      My Computer


  4. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #24

    If you've run MemTest86+ for that many passes with no errors there's nothing wrong with your RAM. Memory Management doesn't necessarily mean there's a problem with your physical memory, it could be a bad driver passing through virtual memory or trying to alter the kernel by passing bad info into kernel mode. It could be accessing an address that's just simply bad or doesn't exist.

    Having said all of that, follow the procedure outlined below. Make sure you've read and understood it all before proceeding.




    Diagnostic Test

     DRIVER VERIFIER


    Driver Verifier will stress your drivers and cause BSODs if any fail. Follow this tutorial to enable/disable it. Driver Verifier - Enable and Disable

    Enable Driver Verifier but only enable these options:

    • Standard settings and IRP logging step 3.
    • Don't enable Force Pending I/O Requests

       Warning
    Make a System Restore point before enabling Driver Verifier.

       Note
    Your system will act very sluggishly while DV is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.


    Post any resulting dump files.

    We'll look at other possibilities after ruling out drivers.
      My Computer


  5. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #25

    I've already run driver verifier for a while, some of the dump files are from when I was running that, but I can stick it on again if you think that would help and then post another set of logs once it's BSOD'd a few more times?
      My Computer


  6. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #26

    It's hard to pick the DV ones out from your logs unfortunately as there are so many dumps, the chances are they're the ones blaming the nVidia driver. I'll have another browse through and see if I can pick then out, hold fire on that for now. What you can do in the meantime is stress test your GPU. Perform the test below and make a not of your GPU temperatures at idle and under load. I know you've already done it but the temperatures would be handy.

    Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

       Note
    Run Furmark for around 30 minutes.

       Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them, if the temperature continues to rise steadily once it has reached 80°C be prepared to stop the test so as to not damage your GPU.
      My Computer


  7. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #27

    Have you run any of the diagnostics provided by Samsung on your SSD?
    Code:
    7: kd> !pool fffffa80098f0130
    GetPointerFromAddress: unable to read from fffff80003316100
    Pool page fffffa80098f0130 region is GetUlongFromAddress: unable to read from fffff800033161c0
    Nonpaged pool
    GetUlongFromAddress: unable to read from fffff80003284a38
    Unable to get pool big page table. Check for valid symbols.
    fffffa80098f0000 is not valid pool. Checking for freed (or corrupt) pool
    Bad allocation size @fffffa80098f0000, zero is invalid
    
    ***
    *** An error (or corruption) in the pool was detected;
    *** Attempting to diagnose the problem.
    ***
    *** Use !poolval fffffa80098f0000 for more details.
    
    
    Pool page [ fffffa80098f0000 ] is __inVALID.
    
    Analyzing linked list...
    [ fffffa80098f0000 ]: invalid previous size [ 0x80 ] should be [ 0x0 ]
    [ fffffa80098f0000 --> fffffa80098f0060 (size = 0x60 bytes)]: Corrupt region
    
    
    Scanning for single bit errors...
    [ fffffa80098f0000 ]: previous size [ 0x80 ] should be [ 0x0 ]
    
    7: kd> !poolval fffffa80098f0000
    Pool page fffffa80098f0000 region is Nonpaged pool
    
    Validating Pool headers for pool page: fffffa80098f0000
    
    Pool page [ fffffa80098f0000 ] is __inVALID.
    
    Analyzing linked list...
    [ fffffa80098f0000 ]: invalid previous size [ 0x80 ] should be [ 0x0 ]
    [ fffffa80098f0000 --> fffffa80098f0060 (size = 0x60 bytes)]: Corrupt region
    
    
    Scanning for single bit errors...
    [ fffffa80098f0000 ]: previous size [ 0x80 ] should be [ 0x0 ]
      My Computer


  8. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #28

    Thanks for the replies again.

    First I'm attaching some more logs just in case, the first 4-5 will be with DV.

    Second I did actually run FurMark a short while ago but just ran it again for about 35 minutes. Resting temp is about 32, stress temp is 67, didn't go any higher than that.

    Third I've run Samsung Magician (not sure if there's anything else?), firmware is updated, drive shows as good, also used Seagate SeaTools which came up with no errors on any of my drives.
    Last edited by beardo; 01 May 2015 at 19:33.
      My Computer


  9. Posts : 2,781
    Windows 10 Pro x64
       #29

    Boozad, i certainly know that. But WinDBG blames memory corruption.
    As it turnes out the 2 latest BSODs are caused by my enemy, BAD_POOL_HEADER.
    Almost all the latest blames the kernel, one still thinks its memory corruption and 1 blames the hardware.
    Run IntelBurnTest.
    CPU - Stress Test Using IntelBurnTest
      My Computer


  10. Posts : 20
    Windows 7 Ultimate x64
    Thread Starter
       #30

    Thanks for the reply again!

    I ran the Intel burn test, but it stopped after 2 passes with an error message. I've attached screenshots of the message and the window, as well as the HWiNFO window...
      My Computer


 
Page 3 of 5 FirstFirst 12345 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 12:09.
Find Us