BSOD 64bit 0x1EE408 PFN_LIST_CORRUPT 0x75BC0 MEMORY_MANAGEMENT


  1. Posts : 3
    W7 64bit Home
       #1

    BSOD 64bit 0x1EE408 PFN_LIST_CORRUPT 0x75BC0 MEMORY_MANAGEMENT


    Hi fellow techies!
    This PC I built for a friend for PRO Poker Online, so needs to be rock solid.
    But of course of all my recent builds this is failing randomly, usually from cold start will be sat with chrome open, few tabs and postgres always on in background - bang BSOD.
    Or many poker sites open, camtasia, chrome, postgres, skype all running for 8 hours+ no problem, start to close down/idle - bang BSOD.
    Am hoping not memory as we have tried two different sets and same occurs.
    Have removed various AV we tried, ie. Avast. MSE, no change but less frequent.
    ATM we're running into BSOD every ~1 week.
    I hsve little acces to PC as it is in constant use to a tight schedule, so I cant pull it a apart and re-add at my leisure unfortunately.
    It had a valid key for Windows to get all updates/fixes etc but then that was mine which I needed for others, so he is waiting to purchase after proved. Same occurred with key.
    Hardware is all new; i5 1150, asrock H81M-HDS, Samsung ssd 120gb, intell ssd 40gb, 1tb green WD, corsair or crucial 8gb ram, asus radeon 5450, 500w psu.
    Driver verifier hasnt been run as i am not physically at pc to fix if wont boot!

    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    Hardware: ASRock, H81M-HDS
    CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
    4 logical processors, active mask: 15
    RAM: 8525328384 total

    SF diags and dumps attached

    Code:
    On Sat 03/01/2015 11:17:39 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010315-5865-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x4E (0x99, 0x1EE408, 0x0, 0x1EE488)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Mon 29/12/2014 09:42:14 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122914-5803-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x4E (0x99, 0xC65EE, 0x0, 0xC6AEE)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Wed 24/12/2014 07:59:00 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\122414-5834-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1A (0x41201, 0xFFFFF68000004568, 0x2F400000B052C025, 0xFFFFFA800F59E370)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Wed 17/12/2014 05:01:45 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\121714-7690-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1A (0x41201, 0xFFFFF68000021568, 0x96600001C0349867, 0xFFFFFA800A40CEC0)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Thu 04/12/2014 00:24:18 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120414-6692-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x4E (0x99, 0x1B0329, 0x2, 0x1A9A8)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Sat 29/11/2014 23:23:23 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112914-6552-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x1A (0x403, 0xFFFFF6800002C5E8, 0xF400000052088825, 0xFFFFF680000C6C10)
    Error: MEMORY_MANAGEMENT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a severe memory management error occurred.
    This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Sat 22/11/2014 17:51:51 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\112214-6302-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x4E (0x99, 0xCA4A1, 0x0, 0xC6A21)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Wed 12/11/2014 23:22:30 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\111214-6208-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000314834E, 0xFFFFF880093655E0, 0x0)
    Error: SYSTEM_SERVICE_EXCEPTION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Thu 06/11/2014 07:03:24 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110614-5959-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x4E (0x99, 0xB71BF, 0x0, 0xB723F)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Tue 04/11/2014 19:37:36 GMT your computer crashed
    crash dump file: C:\Windows\Minidump\110414-5709-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) 
    Bugcheck code: 0x4E (0x7, 0x16BD8D, 0x100000, 0x0)
    Error: PFN_LIST_CORRUPT
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Code:
    Microsoft (R) Windows Debugger Version 6.3.9600.16384 X86
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\YUSRA\Downloads\denzels-SF-dm-logs\010315-5865-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    ************* Symbol Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02e14000 PsLoadedModuleList = 0xfffff800`03057890
    Debug session time: Sat Jan  3 17:17:39.951 2015 (UTC + 6:00)
    System Uptime: 0 days 2:47:07.122
    Loading Kernel Symbols
    .
    
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    
    ..............................................................
    ................................................................
    ....................
    Loading User Symbols
    Loading unloaded module list
    ....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 1ee408, 0, 1ee488}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt
    Arg2: 00000000001ee408, page frame number
    Arg3: 0000000000000000, current page state
    Arg4: 00000000001ee488, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  chrome.exe
    
    CURRENT_IRQL:  2
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) x86fre
    
    LAST_CONTROL_TRANSFER:  from fffff80002f18a4c to fffff80002e89bc0
    
    STACK_TEXT:  
    fffff880`0aa9ae18 fffff800`02f18a4c : 00000000`0000004e 00000000`00000099 00000000`001ee408 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0aa9ae20 fffff800`02e35ed2 : 00000000`00000000 fffff680`00043890 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
    fffff880`0aa9ae60 fffff800`02e597c3 : fffffa80`0f15ab30 fffff700`00007a1b 0000007f`fffffff8 fffff8a0`02c76b08 : nt! ?? ::FNODOBFM::`string'+0x3242a
    fffff880`0aa9aef0 fffff800`02e5a892 : fffffa80`0f15ab30 fffffa80`00000000 fffff880`00005b40 fffff800`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
    fffff880`0aa9b7a0 fffff800`0315f05a : fffff8a0`0e473060 fffff880`0aa9bae0 00000000`00000000 fffffa80`106917f0 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`0aa9b7f0 fffff800`03143b7d : 00000000`c0000005 fffff880`0aa9ba01 00000000`fff98000 fffffa80`0a31c060 : nt!PspExitThread+0x56a
    fffff880`0aa9b8f0 fffff800`02e7c6fa : 00000000`00000001 fffff880`0aa9ba68 00000000`057ce770 fffff880`0aa9baa0 : nt!PsExitSpecialApc+0x1d
    fffff880`0aa9b920 fffff800`02e7ca40 : 00000000`07e6f74c fffff880`0aa9b9a0 fffff800`03143af0 00000000`00000001 : nt!KiDeliverApc+0x2ca
    fffff880`0aa9b9a0 fffff800`02e88ef7 : fffffa80`106917f0 00000000`fff98000 00000000`000000c0 00000000`00000c01 : nt!KiInitiateUserApc+0x70
    fffff880`0aa9bae0 00000000`77732bba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`057ce748 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77732bba
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`02f18a4c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb
    
    IMAGE_VERSION:  6.1.7601.18409
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x4e_99_nt!mibadsharecount+4c
    
    FAILURE_ID_HASH:  {4c83cdad-f603-74ff-b7e1-9eb7f3029c2a}
    
    Followup: MachineOwner
    ---------
    Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

    The goal is to test all the RAM sticks and all the motherboard slots.

    Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

    If you get errors, stop the test and continue with the next step.

    1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
    *Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
    If this stick passes the test then go to step #3.

    2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
    *If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
    *If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
    3. Test the next stick of RAM (stick #2) in the next motherboard slot.
    *If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
    *If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
    4. If you find a stick that passes the test, test it in all the other motherboard slots.

    If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

    In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.
       Information
    Errors are sometimes found after 8 passes.

       Tip
    Memtest should be done overnight.
      My Computer


  3. Posts : 3
    W7 64bit Home
    Thread Starter
       #3

    Thanks I'll remove chrome and hope that stops the BSOD.
    I see you say to run memtest, If I can get at the PC long enough and above doesnt cure it, then will follow that up.
    Thanks for your reply! Fingers crossed...
      My Computer


  4. Posts : 3
    W7 64bit Home
    Thread Starter
       #4

    ok, checked memory all ok.
    removed gfx and drivers, same bsods occurring.
    chrome is nothing to do with it, as various crashes resulted from various software running.
    so now driver verifier is on with a single stick of known good ram..
      My Computer


 

  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:27.
Find Us