TechSpot

Different kinds of BSoD's in the last 2 days - memory problem?

By cura
May 1, 2010
  1. Greetings,

    The last 2 days my computer (Windows 7 64bit) crashes often (when surfing, playing music, chatting, whatever) with a blue screen, always a different message:
    BAD_POOL_HEADER
    MEMORY_MANAGEMENT
    NTFS.SYS PAGE FAULT IN NON PAGED AREA
    DRIVER IRQL NOT LESS OR EQUAL
    KMODE_EXCEPTION_NOT_HANDLED

    Based on those messages I figured it would be something with memory, so last night I ran memtest86 the whole night. 9 hours and 17 passes later: 0 errors.

    I decided to put my memory in a different socket anyway, you never know. So then everything ran smoothly for a whole day, even with some very memory intensive programs, until suddenly I got another blue screen while watching a low resolution movie.

    These are some fragments from the dump files:

    Code:
    BAD_POOL_HEADER (19)
    The pool is already corrupt at the time of the current request.
    This may or may not be due to the caller.
    The internal pool links must be walked to figure out a possible cause of
    the problem, and then special pool applied to the suspect tags or the driver
    verifier to a suspect driver.
    Arguments:
    Arg1: 0000000000000022, 
    Arg2: 0000000000000000
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x19_22
    
    POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc10e0
     0000000000000000 
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  WerFault.exe
    
    CURRENT_IRQL:  2
    
    LAST_CONTROL_TRANSFER:  from fffff80002ae2330 to fffff80002a8af00
    
    STACK_TEXT:  
    fffff880`07e223e8 fffff800`02ae2330 : 00000000`00000019 00000000`00000022 <cut out to get to 20000 chars>
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    fileinfo!FIPfFileOpenRemove+a7
    fffff880`010b18f7 4d8bc5          mov     r8,r13
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  fileinfo!FIPfFileOpenRemove+a7
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: fileinfo
    
    IMAGE_NAME:  fileinfo.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc481
    
    FAILURE_BUCKET_ID:  X64_0x19_22_fileinfo!FIPfFileOpenRemove+a7
    
    BUCKET_ID:  X64_0x19_22_fileinfo!FIPfFileOpenRemove+a7
    
    Code:
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff28005e17eb0, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff88004f82ff0, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000007, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d020e0
     fffff28005e17eb0 
    
    FAULTING_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
    fffff880`04f82ff0 488908          mov     qword ptr [rax],rcx
    
    MM_INTERNAL_CODE:  7
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff8800449a740 -- (.trap 0xfffff8800449a740)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff28005e17eb0 rbx=0000000000000000 rcx=fffffa8005dd76f0
    rdx=fffff8a003853980 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004f82ff0 rsp=fffff8800449a8d0 rbp=0000000000000000
     r8=fffffa8005b7b980  r9=fffff8800449a901 r10=0000000000000000
    r11=fffffa8004cc4010 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa0:
    fffff880`04f82ff0 488908          mov     qword ptr [rax],rcx ds:0002:fffff280`05e17eb0=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002b49b19 to fffff80002acbf00
    
    STACK_TEXT:  
    fffff880`0449a5d8 fffff800`02b49b19 : 00000000`00000050 fffff280`05e17eb0 00000000`00000001 fffff880`0449a740 : nt!KeBugCheckEx
    fffff880`0449a5e0 fffff800`02ac9fee : 00000000`00000001 fffff8a0`068fdb20 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40edb
    fffff880`0449a740 fffff880`04f82ff0 : fffff8a0`06c6c4a0 fffff880`04f82d4b 00000000`00000287 00000000`00000000 : nt!KiPageFault+0x16e
    fffff880`0449a8d0 fffff880`04f808af : 00000000`00000000 fffffa80`05e08020 00000000`00000021 fffffa80`05dfe068 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xa0
    fffff880`0449a910 fffff880`04f9a65d : 00000000`00000000 fffff8a0`03849550 fffffa80`00000000 fffffa80`05743430 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
    fffff880`0449aae0 fffff880`04f9a398 : fffff880`009eaf40 fffff880`04f99d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
    fffff880`0449acd0 fffff880`04f99e96 : 00000000`00000000 fffffa80`05614d50 00000000`00000080 fffffa80`04cc4010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
    fffff880`0449ad00 fffff800`02d6f166 : 00000000`02de27ad fffffa80`05507b60 fffffa80`039739e0 fffffa80`05507b60 : dxgmms1!VidSchiWorkerThread+0xd6
    fffff880`0449ad40 fffff800`02aaa486 : fffff880`009e6180 fffffa80`05507b60 fffff880`009f0fc0 fffff880`0122e534 : nt!PspSystemThreadStartup+0x5a
    fffff880`0449ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
    fffff880`04f82ff0 488908          mov     qword ptr [rax],rcx
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
    
    FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
    
    BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+a0
    
    Code:
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: fffff98003c64001
    Arg3: 0000000000002300
    Arg4: fffff780c0000000
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x1a_41284
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  MsMpEng.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002ac8a63 to fffff80002a71f00
    
    STACK_TEXT:  
    fffff880`07d62198 fffff800`02ac8a63 : 00000000`0000001a 00000000`00041284 fffff980`03c64001 00000000`00002300 : nt!KeBugCheckEx
    fffff880`07d621a0 fffff800`02a14137 : 00000000`00002300 fffff880`07d62390 fffffa80`02146e00 fffff880`07d62380 : nt! ?? ::FNODOBFM::`string'+0x4ac3
    fffff880`07d621e0 fffff800`02d85e35 : fffff980`03c64000 fffff8a0`0008a730 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2bf08
    fffff880`07d624c0 fffff800`02a8ad47 : 00000000`00800000 fffffa80`03a4f260 00000000`00000000 00000000`00900000 : nt!CcUnmapVacb+0x5d
    fffff880`07d62500 fffff800`02a90add : fffffa80`00000001 00000000`00800000 fffffa80`04951c40 00000000`00000001 : nt!CcUnmapVacbArray+0x1b7
    fffff880`07d62590 fffff800`02d755b2 : 00000000`00800000 00000000`00900000 fffff880`07d626e8 fffff880`07d626e0 : nt!CcGetVirtualAddress+0x21d
    fffff880`07d62620 fffff880`012cb522 : 00000000`00000000 fffffa80`03fd6300 00000000`00000000 fffff880`0000000e : nt!CcMapData+0xd2
    fffff880`07d626e0 fffff880`012c14dc : fffffa80`03e41580 fffffa80`04b17180 fffff8a0`099ab898 00000000`00000801 : Ntfs!NtfsReadMftRecord+0xb2
    fffff880`07d62790 fffff880`012904aa : fffffa80`04b18858 fffff8a0`099ab800 fffffa80`03fd6010 00000000`00000000 : Ntfs!NtfsLookupInFileRecord+0x6c
    fffff880`07d62820 fffff880`01292df2 : fffffa80`03e41580 fffff8a0`099ab894 fffffa80`03e41580 fffff8a0`099ab890 : Ntfs!NtfsUpdateFcbInfoFromDisk+0xaa
    fffff880`07d62970 fffff880`012b6b04 : fffff880`07ba8490 fffffa80`03fd6010 fffffa80`03e41580 00000000`00000000 : Ntfs!NtfsOpenFile+0x2c6
    fffff880`07d62b50 fffff880`0121fc0d : fffffa80`03e41580 fffffa80`03fd6010 fffff880`07ba8490 fffffa80`06333800 : Ntfs!NtfsCommonCreate+0xc54
    fffff880`07d62d30 fffff800`02a69d87 : fffff880`07ba8400 00000000`00000000 00000000`00000000 00000000`00000000 : Ntfs!NtfsCommonCreateCallout+0x1d
    fffff880`07d62d60 fffff800`02a69d41 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KySwitchKernelStackCallout+0x27
    fffff880`07ba82d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSwitchKernelStackContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt! ?? ::FNODOBFM::`string'+4ac3
    fffff800`02ac8a63 cc              int     3
    
    SYMBOL_STACK_INDEX:  1
    
    SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+4ac3
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    FAILURE_BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
    
    BUCKET_ID:  X64_0x1a_41284_nt!_??_::FNODOBFM::_string_+4ac3
    
    Code:
    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: fffff2800523fcc3, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff80002a7b01a, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS:  fffff2800523fcc3 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeSetEvent+18a
    fffff800`02a7b01a 0fb6422b        movzx   eax,byte ptr [rdx+2Bh]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  csrss.exe
    
    TRAP_FRAME:  fffff8800818bd20 -- (.trap 0xfffff8800818bd20)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa8003a459b8 rbx=0000000000000000 rcx=fffffa8003a459b8
    rdx=fffff2800523fc98 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002a7b01a rsp=fffff8800818beb0 rbp=0000000000000000
     r8=fffffa800523fc68  r9=fffffa8003a459b0 r10=fffffa8003d08010
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po cy
    nt!KeSetEvent+0x18a:
    fffff800`02a7b01a 0fb6422b        movzx   eax,byte ptr [rdx+2Bh] ds:5410:fffff280`0523fcc3=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002a76469 to fffff80002a76f00
    
    STACK_TEXT:  
    fffff880`0818bbd8 fffff800`02a76469 : 00000000`0000000a fffff280`0523fcc3 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0818bbe0 fffff800`02a750e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0818bd20 fffff800`02a7b01a : fffffa80`03a45978 00000000`00000000 00000000`00000000 fffff880`02fd5180 : nt!KiPageFault+0x260
    fffff880`0818beb0 fffff880`04f979a0 : fffffa80`00000000 fffffa80`00000000 fffffa80`052fb500 fffff280`0523fc98 : nt!KeSetEvent+0x18a
    fffff880`0818bf20 fffff880`04f9a6fd : 00000000`00000001 fffffa80`03d081f8 fffff880`0818c180 00000000`00000000 : dxgmms1!VidSchiSubmitCommandPacketToQueue+0x1d8
    fffff880`0818bf90 fffff880`04ed92e4 : 00000000`00000000 00000000`00000200 fffff880`0818c7f0 00000000`00000000 : dxgmms1!VidSchSubmitCommand+0x3ad
    fffff880`0818bff0 fffff880`04eafe9e : fffff8a0`00000001 fffff8a0`000004e0 fffff880`0818c638 fffff880`00000003 : dxgkrnl!DXGCONTEXT::Render+0xadc
    fffff880`0818c600 fffff960`0072b264 : 00000000`00000000 00000000`00000000 fffff900`c012f020 ffffffff`fffe7960 : dxgkrnl!DxgkCddGdiCommand+0x1ea
    fffff880`0818c690 fffff960`007295d5 : fffffa80`03cd5510 fffffa80`03cd5510 00000000`00000000 fffff900`c012f020 : cdd!CHwCommandBuffer::FlushGdiCommands+0xb4
    fffff880`0818c980 fffff960`00725c6e : ffffffff`fffd74f6 00000000`00000010 00000000`00000001 fffffa80`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81
    fffff880`0818c9b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : cdd!PresentWorkerThread+0x902
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    fffff880`04f979a0 4c8d5c2440      lea     r11,[rsp+40h]
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: dxgmms1
    
    IMAGE_NAME:  dxgmms1.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578
    
    FAILURE_BUCKET_ID:  X64_0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    
    BUCKET_ID:  X64_0xA_dxgmms1!VidSchiSubmitCommandPacketToQueue+1d8
    
    Code:
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff80002aeb774, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    nt!MiUpdateWsleHash+144
    fffff800`02aeb774 448937          mov     dword ptr [rdi],r14d
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  ffffffffffffffff
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d080e0
     ffffffffffffffff 
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    BUGCHECK_STR:  0x1E_c0000005
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    PROCESS_NAME:  dwm.exe
    
    CURRENT_IRQL:  0
    
    LAST_CONTROL_TRANSFER:  from fffff80002b11a17 to fffff80002ad1f00
    
    STACK_TEXT:  
    fffff880`08d91da8 fffff800`02b11a17 : 00000000`0000001e ffffffff`c0000005 <cut out to get to 20000 chars>
    fffff880`08d929b0 fffff800`02aebf23 : ffffffff`ffffff00 00000000`0047b236 00000000`2d050827 00000000`00000000 : nt!MiDispatchFault+0x1de
    fffff880`08d92ac0 fffff800`02acffee : 00000000`00000000 00000000`00000000 fffff880`08d92a01 fffffa80`00000001 : nt!MmAccessFault+0x343
    fffff880`08d92c20 000007fe`fd3c10da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
    00000000`028df8f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fd3c10da
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nt!MiUpdateWsleHash+144
    fffff800`02aeb774 448937          mov     dword ptr [rdi],r14d
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nt!MiUpdateWsleHash+144
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc600
    
    IMAGE_NAME:  memory_corruption
    
    FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiUpdateWsleHash+144
    
    BUCKET_ID:  X64_0x1E_c0000005_nt!MiUpdateWsleHash+144
    
    Code:
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: fffff28005b1f710, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff8800177c82c, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cf90e0
     fffff28005b1f710 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    NETIO!IndexListClassify+50
    fffff880`0177c82c 488b1f          mov     rbx,qword ptr [rdi]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800892b820 -- (.trap 0xfffff8800892b820)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    <cut out to get to 20000 chars>
    iopl=0         nv up ei ng nz na po cy
    NETIO!IndexListClassify+0x50:
    fffff880`0177c82c 488b1f          mov     rbx,qword ptr [rdi] ds:b9b8:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ac2469 to fffff80002ac2f00
    
    STACK_TEXT:  
    fffff880`0892b6d8 fffff800`02ac2469 : 00000000`0000000a fffff280`05b1f710 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0892b6e0 fffff800`02ac10e0 : 00000000`00000000 fffff280`05b1f710 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
    fffff880`0892b820 fffff880`0177c82c : fffff880`0892bbe8 fffff280`05b1f710 00000000`00000000 fffffa80`048ec830 : nt!KiPageFault+0x260
    fffff880`0892b9b0 fffff880`0177dccb : 00000000`00000000 00000000`00000010 fffffa80`048ec830 fffff880`0892bb70 : NETIO!IndexListClassify+0x50
    fffff880`0892ba30 fffff880`018404d0 : fffffa80`048ec830 fffff880`0892be10 00000000`00000000 fffffa80`04fca180 : NETIO!KfdClassify+0xa4e
    fffff880`0892bda0 fffff880`0184339d : fffffa80`048ec830 fffffa80`04a60510 fffff880`0892c958 fffffa80`0650f8d0 : tcpip!WfpAleClassify+0x50
    fffff880`0892bde0 fffff880`018436c5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000002 : tcpip!WfpAlepReauthorizeInboundConnection+0x60d
    fffff880`0892c0e0 fffff880`0186fe71 : fffff880`0892c5a0 00000000`00000000 00000000`00000002 fffffa80`0650f8d0 : tcpip!WfpAleReauthorizeInboundConnection+0x1f5
    fffff880`0892c240 fffff880`0185feef : 00000000`0000006f 00000000`00000001 fffffa80`05148670 fffffa80`0650f8d0 : tcpip!WfpAleReauthorizeConnection+0x321
    fffff880`0892c4d0 fffff880`0183f42a : fffffa80`04a60510 fffffa80`048e0002 00000000`00000000 00000000`00000100 : tcpip!TlShimOptionalReauthorizeConnection+0x2cf
    fffff880`0892c610 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!ProcessALEForTransportPacket+0x3ea
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    NETIO!IndexListClassify+50
    fffff880`0177c82c 488b1f          mov     rbx,qword ptr [rdi]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  NETIO!IndexListClassify+50
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: NETIO
    
    IMAGE_NAME:  NETIO.SYS
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a
    
    FAILURE_BUCKET_ID:  X64_0xD1_NETIO!IndexListClassify+50
    
    BUCKET_ID:  X64_0xD1_NETIO!IndexListClassify+50
    
    
    Based on that I'd think memory corruption, but why doesn't memtest detect anything after 9 hours if this is the case? Are there any better tools out there with which I can pinpoint the problem with 100% certainty? Or does anybody see another reason in the fragments I posted?

    Thanks in advance.
     
  2. Route44

    Route44 TechSpot Ambassador Posts: 11,966   +70

    Hmmm, I can definitely see why you would suspect corrupted memory with the myriad of differing error codes. That would certainly have been my first suspicion.

    Check the memory voltage setting in your BIOS and see how it compares to your RAM manufacture's specs. Is there a noted difference?

    The next to last file this is found there: IMAGE_NAME: memory_corruption
     
  3. cura

    cura TS Rookie Topic Starter

    Hi, thanks for the response. I've checked the voltage in BIOS and it's all as it should be. What part of the dumps are most important for troubleshooting? The image_name, module_name, process_name? I'm kind of new to troubleshooting crash dumps. :)

    Someone mentioned there's alot of mention of video extentions in the crash dumps, I'm gonna remove and reinstall some codecs on his advise and post the results here for future reference.
     
  4. gbhall

    gbhall TechSpot Chancellor Posts: 2,425   +77

    Maybe it is trying to tell you the fault is in the video area - either the video memory or an improper driver; even an incorrectly installed video driver. Some more info about your PC would be useful. In the meantime, check for a video driver update.
     
Topic Status:
Not open for further replies.

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...