BSOD PFN_LIST_CORRUPT and ntoskrnl.exe - Charlie415

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by Charlie415, Jan 1, 2011.

  1. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    Happy New Year and I want to say thanks in advance to everybody for running these forums.

    I have been getting a consistent but fairly intermittent BSOD. It usually happens no more than once a week sometimes only once a month or less. The bug check string is always PFN_LIST_CORRUPT and the bug check code is always 0x0000004e and it always complains (according to bluescreenview) about ntoskrnl.exe. Any information I have been able to find about this through Google seems to point to a rather generic memory issue - either a bad memory module, a driver issue or possibly a hard disk issue. The crash usually happens when I am playing Bad Company 2 but it has happened while just leaving the computer sitting idle and doing nothing a few times as well.

    I have run memtest86+ with each individual stick of ram as well as with all of the ram (4 sticks of 2gb memory) installed overnight with no errors.

    I have run a full virus scan with MS Security Essentials and it came back with no errors.

    I ran sfc /scannow and it did not come back with any errors.

    I ran Driver Verifier with all drivers selected and I did not get it to crash. However the network adapter would not operate correctly I'm not sure if that is indicative of anything. I also ran 3dmark without it crashing as well. I have to admit I'm not entirely sure I was using verifier correctly as I have never used it before.

    I updated my BIOS, did a clean install of my video driver and updated as many other drivers as I could although according to the driver list that is output from the SF Diagnostic Tool it does look like I have some older drivers on my system but I am unsure how to find and update these specific drivers.

    Here are the specs from my machine:

    Custom home built machine - I know, that's probably the issue right there!! LOL =)
    I am not overclocking
    Windows 7 64 bit
    Antec 300 case
    Mushkin 650 watt PSU
    Gigabyte GA-P55-UD3L (Revision 1.0 with the P55 Chipset)
    Core i5 750
    8GB Patriot PC1333Mhz Dual Channel Ram (PSD34G1333k)
    Linksys WMP54G wireless G PCI network adapter
    ASUS DRW-24B1ST Optical Drive
    Western Digital Blue Caviar 500GB Drive
    EVGA GTX 460

    Screenshots from CPU-Z are posted below and a zip file with the contents of the output from the SF Diagnostic Tool are attached.

    Thanks in advance for any help that anyone has to offer.

    CPUZ_Mem.

    CPUZ_SPD.
     

    Attached Files:

  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    I'm not really one of our more talented BSOD Analysts, but until Cybercore or Captain Jack or one of the several others come along I will say that your dumps seem to indicate a driver issue resulting in memory corruption. As a result I would suggest starting first by either updating or removing/renaming the following two;
    speedfan.sys 9/24/2006 (Speedfan.sys is the system service for Speedfan.exe)
    wacommousefilter.sys 2/16/2007 (Wacom Mouse Filter Driver Wacom Technology Wacom Mouse Filter Driver)
    both are way too old.
    Memory setting look fine.
    The other guys who are really good at this will probably be along with additional recommendations, just thought that I might get you started.
    Kind regards and
    Welcome to the Forums
    Randy
     
  3. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    Thanks Randy I will update both of these and I plan on running memtest some more as well just to try and rule out a possible hardware memory problem.
     
  4. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    Good thinking, someone would have probably suggested that anyway sooner or later. You may want to additionally check the hard disk as most of the things that I see regarding your specific error seem to indicated either poorly seated memory, bad memory or potentially an issue with the swap file area of the hard disk drive, although with 8 gigs of ram and the system idle, I really don't think you'd be doing much paging.
    So when you have the time you might give it a whirl anyway
    chkdsk c: /r
    reboot
    let it run all five stages and see if it finds anything.
     
  5. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    I uninstalled speedfan completely only to find that it left Speedfan.sys behind so I renamed it to Speedfan.OLD. This was just a hardware monitoring program that showed the speed of all of my system/cpu/gpu etc fans.

    wacommousefilter.sys is used for my Wacom Tablet (graphics tablet used for Photoshop, Zbrush etc). I uninstalled the drivers for this and it did remove wacommousefilter.sys but when I reinstalled the latest drivers (released on 11/25/2010) for the tablet it re-installed wacommousefilter.sys with the same date as before (2/16/2007). I'm not sure what to do about this as I really need to use the tablet and I don't think any alternative drivers are available. I guess I could remove this for the time being if you really think it could be the culprit... ?

    I am going to run chkdsk c: /r and memtest tonight to double check the hardrive and memory.

    Thanks again,
    Charlie
     
  6. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Nothing to add at all, Randy is spot on. Update (or rename to .old) the wacom 2007 device. The memory settings look right.

    Also check for an update for jraid:

    jraid.sys Fri Jul 17 11:31:50 2009
    JMicron JMB36X RAID Driver

    ~~~~~~~~~~

    0x0000004E: PFN_LIST_CORRUPT each time with a different page frame number (Arg. 2)
    Probably caused by : memory_corruption

    Which indicates that the memory management Page File Number list is corrupted.
    Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

    Other possible causes:

    - an issue with RAM or motherboard
    - PSU not putting out enough power


    Run memtest 10 passes overnight Memtest86+ - Advanced Memory Diagnostic Tool. Sometimes it takes to test per each stick of RAM. Sometimes the sticks pass the memtest but are from a mismatching pair and don't work well alongside. Sometimes a memory slot can be the issue.



    ~~~~~~~~





    Crash Dumps:

    Code:
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\010111-16114-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03259000 PsLoadedModuleList = 0xfffff800`03496e50
    Debug session time: Sat Jan  1 20:16:50.884 2011 (UTC - 5:00)
    System Uptime: 0 days 2:03:00.351
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 995e1, 0, 169461}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    3: 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: 00000000000995e1, page frame number
    Arg3: 0000000000000000, current page state
    Arg4: 0000000000169461, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  MsMpEng.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000335938c to fffff800032c9740
    
    STACK_TEXT:  
    fffff880`08871f98 fffff800`0335938c : 00000000`0000004e 00000000`00000099 00000000`000995e1 00000000`00000000 : nt!KeBugCheckEx
    fffff880`08871fa0 fffff800`0333b9ee : 00000000`00000000 fffff680`00088388 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
    fffff880`08871fe0 fffff800`0329dc23 : fffffa80`08085730 fffff700`0000da88 0000007f`fffffff8 fffff8a0`00a2ad80 : nt! ?? ::FNODOBFM::`string'+0x32235
    fffff880`08872070 fffff800`0329c68a : fffffa80`08085730 fffffa80`00000001 fffff8a0`0000c08b fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
    fffff880`08872920 fffff800`035aedcf : fffff8a0`00f61060 fffff880`08872c20 00000000`00000000 fffffa80`07c0ca10 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`08872970 fffff800`03587635 : 00000000`000000ff fffff8a0`02c85701 000007ff`fff7c000 fffffa80`08075b60 : nt!PspExitThread+0x92f
    fffff880`08872a30 fffff800`032a61db : 00000000`00000000 fffffa80`0808e8c0 00000000`0393f920 fffff880`08872be0 : nt!PsExitSpecialApc+0x1d
    fffff880`08872a60 fffff800`032a6620 : 00000000`771b4298 fffff880`08872ae0 fffff800`0358774c 00000000`00000001 : nt!KiDeliverApc+0x2eb
    fffff880`08872ae0 fffff800`032c8a37 : fffffa80`07c0ca10 00000000`771b4270 00000000`000000c0 fffffa80`06dce060 : nt!KiInitiateUserApc+0x70
    fffff880`08872c20 00000000`7710165a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`0393f738 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7710165a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`0335938c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\122110-16286-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`03250000 PsLoadedModuleList = 0xfffff800`0348de50
    Debug session time: Tue Dec 21 18:30:47.683 2010 (UTC - 5:00)
    System Uptime: 0 days 7:05:54.150
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ........................
    Loading User Symbols
    Loading unloaded module list
    ...........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 1c42b4, 3, 1d44de}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    2: 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: 00000000001c42b4, page frame number
    Arg3: 0000000000000003, current page state
    Arg4: 00000000001d44de, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  svchost.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff8000335038c to fffff800032c0740
    
    STACK_TEXT:  
    fffff880`099eaf98 fffff800`0335038c : 00000000`0000004e 00000000`00000099 00000000`001c42b4 00000000`00000003 : nt!KeBugCheckEx
    fffff880`099eafa0 fffff800`033329f7 : 00000000`00000000 fffff680`000296b0 00000000`00000002 00000000`00000001 : nt!MiBadShareCount+0x4c
    fffff880`099eafe0 fffff800`03294c23 : fffffa80`08ef2b30 fffff700`0000aa0c 0000007f`fffffff8 fffff8a0`045003f0 : nt! ?? ::FNODOBFM::`string'+0x3223e
    fffff880`099eb070 fffff800`0329368a : fffffa80`08ef2b30 fffffa80`000003c7 fffff8a0`00009a2c fffff880`00000000 : nt!MiDeleteAddressesInWorkingSet+0x307
    fffff880`099eb920 fffff800`035a5dcf : fffff8a0`00fe2730 fffff880`099ebc20 00000000`00000000 fffffa80`06ebd060 : nt!MmCleanProcessAddressSpace+0x96
    fffff880`099eb970 fffff800`0357e635 : 00000000`000000ff fffff800`032ab401 000007ff`fffa8000 fffffa80`0981f060 : nt!PspExitThread+0x92f
    fffff880`099eba30 fffff800`0329d1db : 00000000`00000000 fffffa80`08f21350 00000000`028cfcf0 fffff880`099ebbe0 : nt!PsExitSpecialApc+0x1d
    fffff880`099eba60 fffff800`0329d620 : 00000000`77bb4298 fffff880`099ebae0 fffff800`0357e74c 00000000`00000001 : nt!KiDeliverApc+0x2eb
    fffff880`099ebae0 fffff800`032bfa37 : fffffa80`06ebd060 00000000`77bb4270 fffff880`000000c0 fffffa80`091409d0 : nt!KiInitiateUserApc+0x70
    fffff880`099ebc20 00000000`77b017ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
    00000000`028cfb08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77b017ba
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`0335038c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\122010-13728-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0324d000 PsLoadedModuleList = 0xfffff800`0348ae50
    Debug session time: Tue Dec 21 00:09:53.205 2010 (UTC - 5:00)
    System Uptime: 0 days 2:04:10.282
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {2, 1436ac, 21ffff, 49}
    
    Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229 )
    
    Followup: MachineOwner
    ---------
    
    3: 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: 0000000000000002, A list entry was corrupt
    Arg2: 00000000001436ac, entry in list being removed
    Arg3: 000000000021ffff, highest physical page number
    Arg4: 0000000000000049, reference count of entry being removed
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_2
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  BFBC2Game.exe
    
    CURRENT_IRQL:  2
    
    TRAP_FRAME:  fffff88006d0c2c0 -- (.trap 0xfffff88006d0c2c0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000880 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800032dd690 rsp=fffff88006d0c450 rbp=fffffa8008d0cc60
     r8=fffffa800a450068  r9=0000000052c27000 r10=0000000000000880
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!MmProbeAndLockPages+0x130:
    fffff800`032dd690 410fb601        movzx   eax,byte ptr [r9] ds:a100:00000000`52c27000=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032de6be to fffff800032bd740
    
    STACK_TEXT:  
    fffff880`06d0c450 fffff880`02c33a25 : fffffa80`0a44d000 00000000`00000000 fffffa80`00000002 00000000`52620000 : nt!MmProbeAndLockPages+0x130
    fffff880`06d0c560 fffff880`02c2e026 : fffffa80`08d0a180 fffff8a0`0b6853e0 fffff880`00000148 00000000`00880000 : dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+0x229
    fffff880`06d0c5f0 fffff880`02c2ff65 : fffffa80`08d0a180 fffff8a0`0b6853e0 00000000`00000000 00000000`00880000 : dxgmms1!VIDMM_APERTURE_SEGMENT::LockAllocationRange+0x23e
    fffff880`06d0c6a0 fffff880`02c21904 : fffffa80`08d0b680 fffff8a0`0b6853e0 00000000`3e170001 00000000`0d73ea00 : dxgmms1!VIDMM_MEMORY_SEGMENT::EvictResource+0x7a5
    fffff880`06d0c810 fffff880`02c217e3 : fffffa80`08d0c000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::EvictAllAllocationInList+0x40
    fffff880`06d0c850 fffff880`02c241dd : fffff8a0`124d2c70 fffff8a0`124d2c70 00000000`00000000 fffff880`00000003 : dxgmms1!VIDMM_GLOBAL::EvictAllReclaimedAllocation+0x43
    fffff880`06d0c8a0 fffff880`02c1fa8f : fffff8a0`124d2c70 fffff8a0`124d2c70 fffffa80`08d0c000 fffffa80`072bf170 : dxgmms1!VIDMM_GLOBAL::AllocateResourceForPinnedAllocation+0x18d
    fffff880`06d0c920 fffff880`02c1f38f : fffff880`06d0cc78 00080000`00000000 fffff880`06d0cbf0 fffff880`06d0cc88 : dxgmms1!VIDMM_GLOBAL::ProcessDeferredCommand+0x19f
    fffff880`06d0ca40 fffff880`02c39231 : 00000000`00000001 fffff880`02c0b0d4 fffffa80`08cdd240 fffffa80`08cdd240 : dxgmms1!VidMmiProcessSystemCommand+0x23
    fffff880`06d0ca70 fffff880`02c383bc : fffff880`06d0cbd0 00000000`00000000 fffffa80`08d2bec0 00000000`00000001 : dxgmms1!VidSchiSubmitSystemCommand+0x39
    fffff880`06d0caa0 fffff880`02c0a77a : 00000000`00000000 fffffa80`08cdd240 fffffa80`08d2bec0 fffffa80`08d2bec0 : dxgmms1!VidSchiSubmitQueueCommand+0x74
    fffff880`06d0cad0 fffff880`02c3a927 : fffffa80`08cf3af0 fffffa80`08cf6000 fffffa80`08d2bec0 fffffa80`6d4d6956 : dxgmms1!VidSchiSubmitQueueCommandDirect+0x1e6
    fffff880`06d0cb60 fffff880`02c1f4b9 : fffffa80`00000001 fffffa80`08ce7140 fffffa80`08d0c000 fffff880`06d0cc78 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x15f
    fffff880`06d0cbd0 fffff880`02c1f8dc : fffff880`06d0cd30 fffff8a0`124d2c70 fffff880`06d0cd30 fffff8a0`124d2c70 : dxgmms1!VIDMM_GLOBAL::QueueSystemCommandAndWait+0xf9
    fffff880`06d0cc40 fffff880`02c1afaa : 00000000`00000000 00000000`00000000 fffffa80`08d0c000 fffff8a0`00a524e0 : dxgmms1!VIDMM_GLOBAL::QueueDeferredCommandAndWait+0x4c
    fffff880`06d0ccb0 fffff880`02c01aa7 : fffff8a0`09649f90 fffff8a0`09c93740 fffff880`06d0ce20 00000000`00000020 : dxgmms1!VIDMM_GLOBAL::OpenOneAllocation+0x2da
    fffff880`06d0cd90 fffff880`03b4d3a1 : fffff8a0`220275e0 fffff880`06d0d260 00000000`00000000 00000000`00000000 : dxgmms1!VidMmOpenAllocation+0xeb
    fffff880`06d0cde0 fffff880`03b46554 : fffff880`06d0d048 fffff8a0`0b09ac10 fffff880`06d0d220 fffff880`06d0d220 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations<_DXGK_ALLOCATIONINFO>+0x28d
    fffff880`06d0ce70 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::CreateAllocation+0xca8
    
    
    STACK_COMMAND:  .trap 0xfffff88006d0c2c0 ; kb
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229
    fffff880`02c33a25 4c8b1d8cd6fdff  mov     r11,qword ptr [dxgmms1!_imp_g_loggerInfo (fffff880`02c110b8)]
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
    
    FAILURE_BUCKET_ID:  X64_0x4E_2_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229
    
    BUCKET_ID:  X64_0x4E_2_dxgmms1!VIDMM_SEGMENT::SafeProbeAndLockPages+229
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [F:\a\Minidump\D M P\DMP\122810-14383-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
    Machine Name:
    Kernel base = 0xfffff800`0321b000 PsLoadedModuleList = 0xfffff800`03458e50
    Debug session time: Tue Dec 28 17:17:17.197 2010 (UTC - 5:00)
    System Uptime: 0 days 1:52:36.664
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 4E, {99, 21ec02, 6, b7}
    
    Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
    
    Followup: MachineOwner
    ---------
    
    2: 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: 000000000021ec02, page frame number
    Arg3: 0000000000000006, current page state
    Arg4: 00000000000000b7, 0
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x4E_99
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff8000331b38c to fffff8000328b740
    
    STACK_TEXT:  
    fffff880`0a454968 fffff800`0331b38c : 00000000`0000004e 00000000`00000099 00000000`0021ec02 00000000`00000006 : nt!KeBugCheckEx
    fffff880`0a454970 fffff800`033bd9e8 : 00000000`00000000 fffffa80`06604180 00000000`00000000 00000000`00000001 : nt!MiBadShareCount+0x4c
    fffff880`0a4549b0 fffff800`033c087c : fffffa80`07a02000 00000000`00000000 fffff6fb`7ea001e8 00000000`00000001 : nt!MiFreePoolPages+0xaa8
    fffff880`0a454ac0 fffff800`036dc6ae : 00000000`00000000 fffffa80`07a22000 fffffa80`63416d4d fffffa80`00000000 : nt!ExFreePoolWithTag+0x7cc
    fffff880`0a454b70 fffff800`036fdcd0 : fffffa80`09a8f401 00000000`00000080 fffffa80`06705040 fffff800`03419568 : nt!PfpFlushBuffers+0x23e
    fffff880`0a454c10 fffff800`0352fc06 : ffffffff`ff676980 fffffa80`09a8f410 fffff880`0a454db0 fffffa80`09a8f410 : nt!PfTLoggingWorker+0xe0
    fffff880`0a454d40 fffff800`03269c26 : fffff800`03405e80 fffffa80`09a8f410 fffff800`03413c40 fffff880`01239a90 : nt!PspSystemThreadStartup+0x5a
    fffff880`0a454d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiBadShareCount+4c
    fffff800`0331b38c cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt!MiBadShareCount+4c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    BUCKET_ID:  X64_0x4E_99_nt!MiBadShareCount+4c
    
    Followup: MachineOwner
    ---------
    
    
    
    
    
    
    
    
    



    Drivers:

    Code:
    start             end                 module name
    fffff880`00d47000 fffff880`00d9e000   ACPI     ACPI.sys     Mon Jul 13 19:19:34 2009 (4A5BC106)
    fffff880`02c90000 fffff880`02d1a000   afd      afd.sys      Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`041ae000 fffff880`041c4000   AgileVpn AgileVpn.sys Mon Jul 13 20:10:24 2009 (4A5BCCF0)
    fffff880`010b3000 fffff880`010be000   amdxata  amdxata.sys  Tue May 19 13:56:59 2009 (4A12F2EB)
    fffff880`077a0000 fffff880`077ab000   asyncmac asyncmac.sys Mon Jul 13 20:10:13 2009 (4A5BCCE5)
    fffff880`00c2a000 fffff880`00c33000   atapi    atapi.sys    Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00c33000 fffff880`00c5d000   ataport  ataport.SYS  Mon Jul 13 19:19:52 2009 (4A5BC118)
    fffff960`00840000 fffff960`008a1000   ATMFD    ATMFD.DLL    Tue Oct 19 23:05:45 2010 (4CBE5C89)
    fffff880`01860000 fffff880`01867000   Beep     Beep.SYS     Mon Jul 13 20:00:13 2009 (4A5BCA8D)
    fffff880`02c77000 fffff880`02c88000   blbdrive blbdrive.sys Mon Jul 13 19:35:59 2009 (4A5BC4DF)
    fffff880`06b08000 fffff880`06b26000   bowser   bowser.sys   Mon Jul 13 19:23:50 2009 (4A5BC206)
    fffff960`00670000 fffff960`00697000   cdd      cdd.dll      unavailable (00000000)
    fffff880`01800000 fffff880`0182a000   cdrom    cdrom.sys    Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`00e3d000 fffff880`00efd000   CI       CI.dll       Mon Jul 13 21:32:13 2009 (4A5BE01D)
    fffff880`0198c000 fffff880`019bc000   CLASSPNP CLASSPNP.SYS Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00ce9000 fffff880`00d47000   CLFS     CLFS.SYS     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`0117c000 fffff880`011ef000   cng      cng.sys      Mon Jul 13 19:49:40 2009 (4A5BC814)
    fffff880`04179000 fffff880`04189000   CompositeBus CompositeBus.sys Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`06bdc000 fffff880`06be5000   cpuz134_x64 cpuz134_x64.sys Fri Jul 09 07:16:58 2010 (4C37052A)
    fffff880`06094000 fffff880`060a2000   crashdmp crashdmp.sys Mon Jul 13 20:01:01 2009 (4A5BCABD)
    fffff880`0120a000 fffff880`01228000   dfsc     dfsc.sys     Mon Jul 13 19:23:44 2009 (4A5BC200)
    fffff880`02c68000 fffff880`02c77000   discache discache.sys Mon Jul 13 19:37:18 2009 (4A5BC52E)
    fffff880`01976000 fffff880`0198c000   disk     disk.sys     Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`04353000 fffff880`04375000   drmk     drmk.sys     Mon Jul 13 21:01:25 2009 (4A5BD8E5)
    fffff880`060ae000 fffff880`060b7000   dump_atapi dump_atapi.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`060a2000 fffff880`060ae000   dump_dumpata dump_dumpata.sys Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`060b7000 fffff880`060ca000   dump_dumpfve dump_dumpfve.sys Mon Jul 13 19:21:51 2009 (4A5BC18F)
    fffff880`06088000 fffff880`06094000   Dxapi    Dxapi.sys    Mon Jul 13 19:38:28 2009 (4A5BC574)
    fffff880`03e9c000 fffff880`03f90000   dxgkrnl  dxgkrnl.sys  Thu Oct 01 21:00:14 2009 (4AC5509E)
    fffff880`03f90000 fffff880`03fd6000   dxgmms1  dxgmms1.sys  Mon Jul 13 19:38:32 2009 (4A5BC578)
    fffff880`0110a000 fffff880`0111e000   fileinfo fileinfo.sys Mon Jul 13 19:34:25 2009 (4A5BC481)
    fffff880`010be000 fffff880`0110a000   fltmgr   fltmgr.sys   Mon Jul 13 19:19:59 2009 (4A5BC11F)
    fffff880`01200000 fffff880`0120a000   Fs_Rec   Fs_Rec.sys   Mon Jul 13 19:19:45 2009 (4A5BC111)
    fffff880`0193c000 fffff880`01976000   fvevol   fvevol.sys   Fri Sep 25 22:34:26 2009 (4ABD7DB2)
    fffff880`0142b000 fffff880`01475000   fwpkclnt fwpkclnt.sys Mon Jul 13 19:21:08 2009 (4A5BC164)
    fffff800`03210000 fffff800`03259000   hal      hal.dll      Mon Jul 13 21:27:36 2009 (4A5BDF08)
    fffff880`03fd6000 fffff880`03ffa000   HDAudBus HDAudBus.sys Mon Jul 13 20:06:13 2009 (4A5BCBF5)
    fffff880`0418c000 fffff880`041a5000   HIDCLASS HIDCLASS.SYS Mon Jul 13 20:06:21 2009 (4A5BCBFD)
    fffff880`041a5000 fffff880`041ad080   HIDPARSE HIDPARSE.SYS Mon Jul 13 20:06:17 2009 (4A5BCBF9)
    fffff880`060ca000 fffff880`060d8000   hidusb   hidusb.sys   Mon Jul 13 20:06:22 2009 (4A5BCBFE)
    fffff880`06a40000 fffff880`06b08000   HTTP     HTTP.sys     Mon Jul 13 19:22:16 2009 (4A5BC1A8)
    fffff880`01933000 fffff880`0193c000   hwpolicy hwpolicy.sys Mon Jul 13 19:19:22 2009 (4A5BC0FA)
    fffff880`00c7b000 fffff880`00c91000   intelppm intelppm.sys Mon Jul 13 19:19:25 2009 (4A5BC0FD)
    fffff880`00c5d000 fffff880`00c7b000   jraid    jraid.sys    Fri Jul 17 11:31:50 2009 (4A609966)
    fffff880`04085000 fffff880`04094000   kbdclass kbdclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`06100000 fffff880`0610e000   kbdhid   kbdhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff800`00b9b000 fffff800`00ba5000   kdcom    kdcom.dll    Mon Jul 13 21:31:07 2009 (4A5BDFDB)
    fffff880`04214000 fffff880`04257000   ks       ks.sys       Wed Mar 03 23:32:25 2010 (4B8F37D9)
    fffff880`013d5000 fffff880`013ef000   ksecdd   ksecdd.sys   Mon Jul 13 19:20:54 2009 (4A5BC156)
    fffff880`01400000 fffff880`0142b000   ksecpkg  ksecpkg.sys  Fri Dec 11 01:03:32 2009 (4B21E0B4)
    fffff880`04375000 fffff880`0437a200   ksthunk  ksthunk.sys  Mon Jul 13 20:00:19 2009 (4A5BCA93)
    fffff880`06160000 fffff880`06175000   lltdio   lltdio.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`0611c000 fffff880`0613f000   luafv    luafv.sys    Mon Jul 13 19:26:13 2009 (4A5BC295)
    fffff880`00c91000 fffff880`00cd5000   mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Mon Jul 13 21:29:10 2009 (4A5BDF66)
    fffff880`0610e000 fffff880`0611c000   monitor  monitor.sys  Mon Jul 13 19:38:52 2009 (4A5BC58C)
    fffff880`04094000 fffff880`040a3000   mouclass mouclass.sys Mon Jul 13 19:19:50 2009 (4A5BC116)
    fffff880`042c3000 fffff880`042d0000   mouhid   mouhid.sys   Mon Jul 13 20:00:20 2009 (4A5BCA94)
    fffff880`00c10000 fffff880`00c2a000   mountmgr mountmgr.sys Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`0182a000 fffff880`01857000   MpFilter MpFilter.sys Sat Mar 20 01:58:08 2010 (4BA463F0)
    fffff880`077ab000 fffff880`077bb000   MpNWMon  MpNWMon.sys  Sat Mar 20 01:58:00 2010 (4BA463E8)
    fffff880`06b26000 fffff880`06b3e000   mpsdrv   mpsdrv.sys   Mon Jul 13 20:08:25 2009 (4A5BCC79)
    fffff880`06b3e000 fffff880`06b6b000   mrxsmb   mrxsmb.sys   Sat Feb 27 02:52:19 2010 (4B88CF33)
    fffff880`06b6b000 fffff880`06bb9000   mrxsmb10 mrxsmb10.sys Sat Feb 27 02:52:28 2010 (4B88CF3C)
    fffff880`06bb9000 fffff880`06bdc000   mrxsmb20 mrxsmb20.sys Sat Feb 27 02:52:26 2010 (4B88CF3A)
    fffff880`018c5000 fffff880`018d0000   Msfs     Msfs.SYS     Mon Jul 13 19:19:47 2009 (4A5BC113)
    fffff880`00fb9000 fffff880`00fc3000   msisadrv msisadrv.sys Mon Jul 13 19:19:26 2009 (4A5BC0FE)
    fffff880`0111e000 fffff880`0117c000   msrpc    msrpc.sys    Mon Jul 13 19:21:32 2009 (4A5BC17C)
    fffff880`02c5d000 fffff880`02c68000   mssmbios mssmbios.sys Mon Jul 13 19:31:10 2009 (4A5BC3BE)
    fffff880`01921000 fffff880`01933000   mup      mup.sys      Mon Jul 13 19:23:45 2009 (4A5BC201)
    fffff880`0148b000 fffff880`0157d000   ndis     ndis.sys     Mon Jul 13 19:21:40 2009 (4A5BC184)
    fffff880`041e8000 fffff880`041f4000   ndistapi ndistapi.sys Mon Jul 13 20:10:00 2009 (4A5BCCD8)
    fffff880`061c8000 fffff880`061db000   ndisuio  ndisuio.sys  Mon Jul 13 20:09:25 2009 (4A5BCCB5)
    fffff880`04000000 fffff880`0402f000   ndiswan  ndiswan.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`042d8000 fffff880`042ed000   NDProxy  NDProxy.SYS  Mon Jul 13 20:10:05 2009 (4A5BCCDD)
    fffff880`02da4000 fffff880`02db3000   netbios  netbios.sys  Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff880`02d1a000 fffff880`02d5f000   netbt    netbt.sys    Mon Jul 13 19:21:28 2009 (4A5BC178)
    fffff880`0157d000 fffff880`015dd000   NETIO    NETIO.SYS    Mon Jul 13 19:21:46 2009 (4A5BC18A)
    fffff880`018d0000 fffff880`018e1000   Npfs     Npfs.SYS     Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`02c51000 fffff880`02c5d000   nsiproxy nsiproxy.sys Mon Jul 13 19:21:02 2009 (4A5BC15E)
    fffff800`03259000 fffff800`03835000   nt       ntkrnlmp.exe Sat Jun 19 00:16:41 2010 (4C1C44A9)
    fffff880`01232000 fffff880`013d5000   Ntfs     Ntfs.sys     Mon Jul 13 19:20:47 2009 (4A5BC14F)
    fffff880`01857000 fffff880`01860000   Null     Null.SYS     Mon Jul 13 19:19:37 2009 (4A5BC109)
    fffff880`053ec000 fffff880`053ed180   nvBridge nvBridge.kmd Sat Oct 16 13:06:16 2010 (4CB9DB88)
    fffff880`042ed000 fffff880`04316000   nvhda64v nvhda64v.sys Tue Sep 07 16:08:40 2010 (4C869BC8)
    fffff880`04812000 fffff880`053eba80   nvlddmkm nvlddmkm.sys Sat Oct 16 13:12:46 2010 (4CB9DD0E)
    fffff880`06175000 fffff880`061c8000   nwifi    nwifi.sys    Mon Jul 13 20:07:23 2009 (4A5BCC3B)
    fffff880`02d68000 fffff880`02d8e000   pacer    pacer.sys    Mon Jul 13 20:09:41 2009 (4A5BCCC5)
    fffff880`0415c000 fffff880`04179000   parport  parport.sys  Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`00e0d000 fffff880`00e22000   partmgr  partmgr.sys  Mon Jul 13 19:19:58 2009 (4A5BC11E)
    fffff880`00fc3000 fffff880`00ff6000   pci      pci.sys      Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`00ff6000 fffff880`00ffd000   pciide   pciide.sys   Mon Jul 13 19:19:49 2009 (4A5BC115)
    fffff880`00c00000 fffff880`00c10000   PCIIDEX  PCIIDEX.SYS  Mon Jul 13 19:19:48 2009 (4A5BC114)
    fffff880`013ef000 fffff880`01400000   pcw      pcw.sys      Mon Jul 13 19:19:27 2009 (4A5BC0FF)
    fffff880`0707d000 fffff880`07123000   peauth   peauth.sys   Mon Jul 13 21:01:19 2009 (4A5BD8DF)
    fffff880`04316000 fffff880`04353000   portcls  portcls.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00cd5000 fffff880`00ce9000   PSHED    PSHED.dll    Mon Jul 13 21:32:23 2009 (4A5BE027)
    fffff880`041c4000 fffff880`041e8000   rasl2tp  rasl2tp.sys  Mon Jul 13 20:10:11 2009 (4A5BCCE3)
    fffff880`0402f000 fffff880`0404a000   raspppoe raspppoe.sys Mon Jul 13 20:10:17 2009 (4A5BCCE9)
    fffff880`0404a000 fffff880`0406b000   raspptp  raspptp.sys  Mon Jul 13 20:10:18 2009 (4A5BCCEA)
    fffff880`0406b000 fffff880`04085000   rassstp  rassstp.sys  Mon Jul 13 20:10:25 2009 (4A5BCCF1)
    fffff880`02c00000 fffff880`02c51000   rdbss    rdbss.sys    Mon Jul 13 19:24:09 2009 (4A5BC219)
    fffff880`018aa000 fffff880`018b3000   RDPCDD   RDPCDD.sys   Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`018b3000 fffff880`018bc000   rdpencdd rdpencdd.sys Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`018bc000 fffff880`018c5000   rdprefmp rdprefmp.sys Mon Jul 13 20:16:35 2009 (4A5BCE63)
    fffff880`018e7000 fffff880`01921000   rdyboost rdyboost.sys Mon Jul 13 19:34:34 2009 (4A5BC48A)
    fffff880`061db000 fffff880`061f3000   rspndr   rspndr.sys   Mon Jul 13 20:08:50 2009 (4A5BCC92)
    fffff880`05e2c000 fffff880`06087d80   RTKVHD64 RTKVHD64.sys Fri Sep 03 04:02:27 2010 (4C80AB93)
    fffff880`01084000 fffff880`010b3000   SCSIPORT SCSIPORT.SYS Mon Jul 13 20:01:04 2009 (4A5BCAC0)
    fffff880`07123000 fffff880`0712e000   secdrv   secdrv.SYS   Wed Sep 13 09:18:38 2006 (4508052E)
    fffff880`04150000 fffff880`0415c000   serenum  serenum.sys  Mon Jul 13 20:00:33 2009 (4A5BCAA1)
    fffff880`02db3000 fffff880`02dd0000   serial   serial.sys   Mon Jul 13 20:00:40 2009 (4A5BCAA8)
    fffff880`0147d000 fffff880`01484000   speedfan speedfan.sys Sun Sep 24 09:26:48 2006 (45168798)
    fffff880`01475000 fffff880`0147d000   spldr    spldr.sys    Mon May 11 12:56:27 2009 (4A0858BB)
    fffff880`07682000 fffff880`07718000   srv      srv.sys      Thu Aug 26 23:38:00 2010 (4C773318)
    fffff880`0716d000 fffff880`071d4000   srv2     srv2.sys     Thu Aug 26 23:37:46 2010 (4C77330A)
    fffff880`0712e000 fffff880`0715b000   srvnet   srvnet.sys   Thu Aug 26 23:37:24 2010 (4C7732F4)
    fffff880`040a3000 fffff880`040a4480   swenum   swenum.sys   Mon Jul 13 20:00:18 2009 (4A5BCA92)
    fffff880`01600000 fffff880`017fd000   tcpip    tcpip.sys    Sun Jun 13 23:39:04 2010 (4C15A458)
    fffff880`0715b000 fffff880`0716d000   tcpipreg tcpipreg.sys Mon Jul 13 20:09:49 2009 (4A5BCCCD)
    fffff880`019f2000 fffff880`019ff000   TDI      TDI.SYS      Mon Jul 13 19:21:18 2009 (4A5BC16E)
    fffff880`015dd000 fffff880`015fb000   tdx      tdx.sys      Mon Jul 13 19:21:15 2009 (4A5BC16B)
    fffff880`02deb000 fffff880`02dff000   termdd   termdd.sys   Mon Jul 13 20:16:36 2009 (4A5BCE64)
    fffff960`00580000 fffff960`0058a000   TSDDD    TSDDD.dll    Mon Jul 13 20:16:34 2009 (4A5BCE62)
    fffff880`0104c000 fffff880`01072000   tunnel   tunnel.sys   Mon Jul 13 20:09:37 2009 (4A5BCCC1)
    fffff880`04257000 fffff880`04269000   umbus    umbus.sys    Mon Jul 13 20:06:56 2009 (4A5BCC20)
    fffff880`060e3000 fffff880`06100000   usbccgp  usbccgp.sys  Mon Jul 13 20:06:45 2009 (4A5BCC15)
    fffff880`060d8000 fffff880`060d9f00   USBD     USBD.SYS     Mon Jul 13 20:06:23 2009 (4A5BCBFF)
    fffff880`03e63000 fffff880`03e74000   usbehci  usbehci.sys  Mon Jul 13 20:06:30 2009 (4A5BCC06)
    fffff880`04269000 fffff880`042c3000   usbhub   usbhub.sys   Mon Jul 13 20:07:09 2009 (4A5BCC2D)
    fffff880`03e0d000 fffff880`03e63000   USBPORT  USBPORT.SYS  Mon Jul 13 20:06:31 2009 (4A5BCC07)
    fffff880`03e00000 fffff880`03e0d000   usbuhci  usbuhci.sys  Mon Jul 13 20:06:27 2009 (4A5BCC03)
    fffff880`00e00000 fffff880`00e0d000   vdrvroot vdrvroot.sys Mon Jul 13 20:01:31 2009 (4A5BCADB)
    fffff880`01867000 fffff880`01875000   vga      vga.sys      Mon Jul 13 19:38:47 2009 (4A5BC587)
    fffff880`01875000 fffff880`0189a000   VIDEOPRT VIDEOPRT.SYS Mon Jul 13 19:38:51 2009 (4A5BC58B)
    fffff880`00e22000 fffff880`00e37000   volmgr   volmgr.sys   Mon Jul 13 19:19:57 2009 (4A5BC11D)
    fffff880`00d9e000 fffff880`00dfa000   volmgrx  volmgrx.sys  Mon Jul 13 19:20:33 2009 (4A5BC141)
    fffff880`01000000 fffff880`0104c000   volsnap  volsnap.sys  Mon Jul 13 19:20:08 2009 (4A5BC128)
    fffff880`04143000 fffff880`04150000   vwifibus vwifibus.sys Mon Jul 13 20:07:21 2009 (4A5BCC39)
    fffff880`02d8e000 fffff880`02da4000   vwififlt vwififlt.sys Mon Jul 13 20:07:22 2009 (4A5BCC3A)
    fffff880`060da000 fffff880`060e3000   wacmoumonitor wacmoumonitor.sys Tue Sep 07 18:38:45 2010 (4C86BEF5)
    fffff880`042d0000 fffff880`042d8000   wacommousefilter wacommousefilter.sys Fri Feb 16 13:12:17 2007 (45D5F401)
    fffff880`04189000 fffff880`0418ba00   wacomvhid wacomvhid.sys Mon Sep 21 19:29:14 2009 (4AB80C4A)
    fffff880`02dd0000 fffff880`02deb000   wanarp   wanarp.sys   Mon Jul 13 20:10:21 2009 (4A5BCCED)
    fffff880`0189a000 fffff880`018aa000   watchdog watchdog.sys Mon Jul 13 19:37:35 2009 (4A5BC53F)
    fffff880`00efd000 fffff880`00fa1000   Wdf01000 Wdf01000.sys Mon Jul 13 19:22:07 2009 (4A5BC19F)
    fffff880`00fa1000 fffff880`00fb0000   WDFLDR   WDFLDR.SYS   Mon Jul 13 19:19:54 2009 (4A5BC11A)
    fffff880`02d5f000 fffff880`02d68000   wfplwf   wfplwf.sys   Mon Jul 13 20:09:26 2009 (4A5BCCB6)
    fffff960`00090000 fffff960`003a0000   win32k   win32k.sys   Tue Oct 19 23:08:46 2010 (4CBE5D3E)
    fffff880`00fb0000 fffff880`00fb9000   WMILIB   WMILIB.SYS   Mon Jul 13 19:19:51 2009 (4A5BC117)
    fffff880`040d0000 fffff880`04143000   WMP54Gv41x64 WMP54Gv41x64.sys Wed Apr 07 08:07:21 2010 (4BBC7579)
    fffff880`07724000 fffff880`0772f000   WSDPrint WSDPrint.sys Mon Jul 13 20:39:20 2009 (4A5BD3B8)
    fffff880`07718000 fffff880`07724000   WSDScan  WSDScan.sys  Mon Jul 13 20:35:37 2009 (4A5BD2D9)
    fffff880`0613f000 fffff880`06160000   WudfPf   WudfPf.sys   Mon Jul 13 20:05:37 2009 (4A5BCBD1)
    
    Unloaded modules:
    fffff880`0772f000 fffff880`077a0000   spsys.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00071000
    fffff880`019bc000 fffff880`019ca000   crashdmp.sys
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000E000
    fffff880`019ca000 fffff880`019d6000   dump_ataport
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  0000C000
    fffff880`019d6000 fffff880`019df000   dump_atapi.s
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00009000
    fffff880`019df000 fffff880`019f2000   dump_dumpfve
        Timestamp: unavailable (00000000)
        Checksum:  00000000
        ImageSize:  00013000
    
    
     
  7. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    Thanks for your reply.

    I ran chkdsk /r and no errors returned.

    I ran memtest last night for five passes (this was before I was able to read your post) with no errors. I will run it for ten next time and post the results.

    I will disable the wacom driver - I will just have to get by without the drawing tablet for a while and see if it crashes with it disabled.

    Looks like there may be an update for the RAID driver I will download and update this.

    A few questions:

    Is there any way I can test my PSU? It is 650 watts I am pretty sure that should be plenty for my system but is there any way to test it just in case?

    Is there any way to test for issues with the motherboard?

    How often does an issue like this end up being with the RAM even though it passes through memtest just fine?

    Also, I am wondering how do you know the ram timings are correct? Everything is set to auto in the bios but I was not able to find the specific timings for my ram anywhere on the internet. I've never dealt with ram timings before so I am just curious.

    Thanks again.
     
    #7 Charlie415, Jan 2, 2011
    Last edited: Jan 2, 2011
  8. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    After you update the RAID driver, run HDD SMART report:

    HDDScan

    Watch for yellow/red warnings. Red would mean a problem. Too many yellow ones - a problem as well.
    HDD Scan is a light test. To test it more thoroughly see this HD Diagnostic.
     
  9. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    I haven't had a blue screen since I updated the RAID driver. This problem has been intermittent though so I'll just have to wait and see what happens.

    Thanks for all the advice guys I really appreciate it.

    Charlie
     
  10. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    You are welcome Charlie, enjoy Christmas now. : )

    Should crashes reoccur, hope not, attach the newest .dmp (-s).



    [​IMG]
     
  11. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    Well it looks like I spoke too soon.

    I got another BSOD while playing Bad Company 2.

    So after doing some more research I found a lot of cases where people were having random BSOD issues due to non QVL ram (which is what I have) despite the fact that their system would pass memtest with flying colors over and over again. In retrospect it was stupid of me to get non QVL ram but I've replaced/added ram many times in the past and never had any issues like this apparently the new ddr3 ram can be very picky with what motherboard they will work inside of.

    Anyway I have replaced my ram with something that is on the QVL list for my motherboard and I am going to see if this fixes the issue.

    I'll keep this thread updated just in case anyone else has a similar issue to mine.
     
  12. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Yes, RAM is an often causer, whether qualifying or not. At the same time it's not easy to have memtest show errors.
    Let us know how it goes even if you get no more bsods.
     
  13. Charlie415

    Charlie415 New Member

    Joined:
    Jan 1, 2011
    Messages:
    14
    Likes Received:
    0
    Well I haven't had any BSOD's since I installed the new (QVL) ram so it looks like that was the culprit.

    I'll post here if the problem does come back but so far it looks like the problem is fixed.

    Thanks again.
     
  14. cybercore

    cybercore New Member

    Joined:
    Jul 7, 2009
    Messages:
    15,823
    Likes Received:
    321
    Thanks for updating. : )
     

Share This Page

Loading...