BSOD when running Firefox. SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION


  1. Posts : 17
    Windows 10
       #1

    BSOD when running Firefox. SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION


    Hi

    Current problem: the computer BSODs when I have Driver Verifier enabled and I open Firefox. 100% reproducible every time.

    History of the problem:
    • It started a few weeks ago with my computer freezing when I used Firefox.
    • At this time I tried to diagnose the issue with Firefox by disabling extensions and running in "safe mode". No effect.
    • I eventually switched over to Edge just to get by, however I eventually found that Skype would cause a freeze as well, although much more intermittently.
    • I had a Xonar sound card which was getting quite old so I tried removing that and the problem went away until yesterday.
    • Yesterday my computer froze again while using Firefox.
    • I tried unplugging my graphics card and running onboard graphics. When I did this, the computer no longer froze, but gave a BSOD.
    • I checked the memory dump with WinDbg and saw an old driver in the stack trace. I was unable to remove this driver so I decided to re-install Windows (using the Reset function - "keep files" option).
    • After re-install, I started installing applications again. I foolishly did not install Firefox as the first thing to re-rest and right now I have a bunch of stuff installed.
    • I started reading about diagnosing the issue and found out about Driver Verifier. I ran this and found that Firefox would BSOD within 10 seconds of restoring previous session and loading a few tabs. I checked these memory dumps with WinDbg but the stack traces look clean to me - I don't see any funky drivers.
    • I've tried updating my motherboard network and sound drivers, no effect.
    • I've tried unplugging the RAM chips (2 chips) and testing them individually, and in each slot (all permutations). No effect, still BSODS with verifier active.
    • I've run a Memtest86+ v5.01 and Memtest86 (an older version) for 1 full pass on each and there were zero errors. I will run a longer test overnight.


    I've pretty much exhausted my avenues for diagnosing the problem. I'll try and get hold of a PSU from a friend to test that avenue soon. And I'll try get some alternative RAM chips to test and see if the problem still occurs.

    Any help would much appreciated!

    [edit: attached debug zip]
      My Computer

  2. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #2

    Hi ExtremeUnction,

    Welcome to the 10forums :)

    I would suggest to run the !thread command, it gives information about the last thread.
    The output of the !thread in either of the dumps shows the nldrv.sys possibily causing trouble which belongs to the Netlimiter 4 program, see below.
    Code:
    THREAD ffffd90582c39040  Cid 0004.087c  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
    Not impersonating
    GetUlongFromAddress: unable to read from fffff802f6503924
    Owning Process            ffffd9057de73040       Image:         System
    Attached Process          N/A            Image:         N/A
    fffff78000000000: Unable to get shared data
    Wait Start TickCount      100199       
    Context Switch Count      7237           IdealProcessor: 0             
    ReadMemory error: Cannot get nt!KeMaximumIncrement value.
    UserTime                  00:00:00.000
    KernelTime                00:00:00.000
    Unable to load image \??\C:\Program Files\Locktime Software\NetLimiter 4\nldrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nldrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for nldrv.sys
    Win32 Start Address nldrv (0xfffff80c3fb42260)
    Stack Init ffff8881120b1c90 Current ffff8881120b1720
    Base ffff8881120b2000 Limit ffff8881120ac000 Call 0
    Priority 8 BasePriority 8 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
    Child-SP          RetAddr           : Args to Child                                                           : Call Site
    ffff8881`120b0ef8 fffff802`f63f5865 : 00000000`000000c1 ffff988f`8cc56f98 00000000`00000054 00000000`00000068 : nt!KeBugCheckEx
    ffff8881`120b0f00 fffff802`f6459c79 : ffff988f`8ea90f50 ffffffff`fff1f134 00000000`00000000 00000000`646e444e : nt!MmFreeSpecialPool+0x14d
    ffff8881`120b1060 fffff80c`3bbb17f8 : ffff988f`8cc56f98 00000000`00000000 00000000`00000000 00000000`00000000 : nt!ExAllocatePoolWithTag+0xea9
    ffff8881`120b1140 fffff80c`3bec4319 : ffff988f`8ea90de0 ffff988f`8ea90f50 ffffd905`82ad6570 ffff988f`8ea90de0 : NETIO! ?? ::FNODOBFM::`string'+0x9d98
    ffff8881`120b1190 fffff80c`3bb8fa86 : ffff988f`8ea90de0 00000000`00000000 00000000`00000000 ffffd905`82c39040 : fwpkclnt!FwppInjectComplete+0x59
    ffff8881`120b11d0 fffff80c`3bc9ad8a : 00000000`00000000 ffffd905`80ca5801 00000000`00000000 00000000`00000000 : NETIO!NetioDereferenceNetBufferListChain+0x286
    ffff8881`120b1290 00000000`00000000 : ffffd905`80ca5801 00000000`00000000 00000000`00000000 ffffd905`80ca58a8 : tcpip+0x6ad8a
      My Computers


  3. Posts : 17
    Windows 10
    Thread Starter
       #3

    Hi axe0

    Wow! Thank you! I uninstalled Netlimiter and rebooted and Firefox is now running without issues. I will have to play around with the settings in Netlimiter and possibly log a bug with their tech support.

    Thanks for the tip re: !thread command. It's great to learn something new! I only knew about !analyze -v and then scrolled to the stack trace that it shows, but it seems to be less detailed than !thread. I see now that the clue is not in the stack trace but in the information above the stack which pointed to nldrv.sys.

    Thanks a lot for your help! If any of you guys were to stream your debug process, I would definitely watch :)
      My Computer

  4. axe0's Avatar
    Posts : 14,792
    Windows 10 Pro
       #4
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 10:49.
Find Us




Windows 10 Forums