getting to the bottom of my BSODs

Discussion in 'Software' started by gfool, Sep 17, 2011.

  1. gfool

    gfool Private E-2

    Hello.

    My particular motherboard and RAM combo came with some unexpected issues that I had to deal with when I first got the machine. Over time I was able to stabilize my system and it ran fine for quite some time. I recently reformated my HDD's and loaded a 32-bit OS since I only have 4gigs of RAM anyways.

    Since then my machine has been giving me random BSOD's. I followed a guide in here to be able to read the minidumps which I will now post here:

    *Note the Process_Name indicated in each report*

    1st...
    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: 6913ec70, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 82eedbd1, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f87848
    Unable to read MiSystemVaType memory at 82f66e40
    6913ec70

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!MiRemoveLowestPriorityStandbyPage+163
    82eedbd1 834c0804ff or dword ptr [eax+ecx+4],0FFFFFFFFh

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: explorer.exe

    TRAP_FRAME: 8f8bb824 -- (.trap 0xffffffff8f8bb824)
    ErrCode = 00000002
    eax=e533ec6c ebx=83235b48 ecx=83e00000 edx=82f8837a esi=85421b50 edi=82f88368
    eip=82eedbd1 esp=8f8bb898 ebp=8f8bb8c8 iopl=0 nv up ei ng nz ac pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296
    nt!MiRemoveLowestPriorityStandbyPage+0x163:
    82eedbd1 834c0804ff or dword ptr [eax+ecx+4],0FFFFFFFFh ds:0023:6913ec70=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 82eedbd1 to 82e5f5db

    STACK_TEXT:
    8f8bb824 82eedbd1 badb0d00 82f8837a 850e2734 nt!KiTrap0E+0x2cf
    8f8bb8c8 82ebc0c1 a72476a8 89dbdeb8 00001000 nt!MiRemoveLowestPriorityStandbyPage+0x163
    8f8bb8e8 82e7b7b0 00000037 00000000 a408ae84 nt!MiGetPage+0x2a0
    8f8bb9a4 82ecb2b0 abe15000 03f85020 00000000 nt!MmCopyToCachedPage+0x56a
    8f8bba38 82ecb0b2 89692a90 03f85020 8f8bba88 nt!CcMapAndCopyInToCache+0x1f0
    8f8bba94 8bd1abd0 85857f80 8f8bbb9c 00010000 nt!CcCopyWrite+0x1d9
    8f8bbbc0 8bc41fec 85857f80 8f8bbac0 00010000 Ntfs!NtfsCopyWriteA+0x248
    8f8bbbf4 8bc421bb 00000004 00000000 86d045dc fltmgr!FltpPerformFastIoCall+0x22e
    8f8bbc20 8bc54dcf 008bbc44 85857f80 8bc54c6c fltmgr!FltpPassThroughFastIo+0x7d
    8f8bbc64 8308e316 85857f80 8f8bbcac 00010000 fltmgr!FltpFastIoWrite+0x163
    8f8bbd08 82e5c1fa 86463210 0000076c 00000000 nt!NtWriteFile+0x342
    8f8bbd08 773c70b4 86463210 0000076c 00000000 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0547dab8 00000000 00000000 00000000 00000000 0x773c70b4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiRemoveLowestPriorityStandbyPage+163
    82eedbd1 834c0804ff or dword ptr [eax+ecx+4],0FFFFFFFFh

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MiRemoveLowestPriorityStandbyPage+163

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiRemoveLowestPriorityStandbyPage+163

    BUCKET_ID: 0xA_nt!MiRemoveLowestPriorityStandbyPage+163

    Followup: MachineOwner

    2nd

    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: 80786568, memory referenced
    Arg2: 00000000, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 80786568, address which referenced memory

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from 831b8848
    Unable to read MiSystemVaType memory at 83197e40
    80786568

    CURRENT_IRQL: 0

    FAULTING_IP:
    +610f2faf03c5d7ac
    80786568 0000 add byte ptr [eax],al

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: 807866c4 -- (.trap 0xffffffff807866c4)
    ErrCode = 00000002
    eax=00000040 ebx=00003048 ecx=00000002 edx=00000000 esi=91262000 edi=00000001
    eip=830ea7d0 esp=80786738 ebp=80786780 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
    nt!ExpAllocateBigPool+0x242:
    830ea7d0 895c1efc mov dword ptr [esi+ebx-4],ebx ds:0023:91265044=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 80786568 to 830905db

    FAILED_INSTRUCTION_ADDRESS:
    +610f2faf03c5d7ac
    80786568 0000 add byte ptr [eax],al

    STACK_TEXT:
    807864ac 80786568 badb0d00 00000005 8654e000 nt!KiTrap0E+0x2cf
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8078654c 830ed5b8 c0489328 851e386c 00000000 0x80786568
    807865a0 830e0db0 00000001 91265044 00000111 nt!MiResolveDemandZeroFault+0x4eb
    80786620 830de84e 91265044 00000000 831b9240 nt!MiDispatchFault+0x659
    807866ac 830903e8 00000001 91265044 00000000 nt!MmAccessFault+0x157c
    807866ac 830ea7d0 00000001 91265044 00000000 nt!KiTrap0E+0xdc
    80786780 8316f132 00000048 00000001 00003048 nt!ExpAllocateBigPool+0x242
    807867e4 8cd805d1 00000001 00003040 70707746 nt!ExAllocatePoolWithTag+0x12d
    807867fc 8cd9365e 00003040 00000001 70707746 fwpkclnt!WfpPoolAllocQualified+0x17
    80786830 8cd936ff 00000182 00000000 00000000 fwpkclnt!FwppCalloutReserve+0xff
    80786844 8cd93a30 807868ac 80786870 00000000 fwpkclnt!FwppCalloutAlloc+0x3a
    80786864 8cd93c6a 8791d028 00000000 00000000 fwpkclnt!FwppCalloutRegister+0x4b
    80786888 91a27e68 8791d028 807868ac 91a860a8 fwpkclnt!FwpsCalloutRegister0+0x69
    807868d0 91a2e5c8 00000001 00000000 00100180 vsdatant+0x5e68
    807868f4 91a2e67d 91a896d0 00000000 872f1dc0 vsdatant+0xc5c8
    80786908 91a40ece 91a896d0 00000000 87285000 vsdatant+0xc67d
    807869b8 832122ee 872f1dc0 87285000 8d8f2848 vsdatant+0x1eece
    80786b9c 8340053d 00000001 00000000 80786bd4 nt!IopLoadDriver+0x7ed
    80786be8 834001e0 8080fbc8 8080a7d0 00000000 nt!IopInitializeSystemDrivers+0x163
    80786c6c 834041de 0080a7d0 85ac5808 85ac5498 nt!IoInitSystem+0x6de
    80786d48 831db448 80786d90 83257fda 8080a7d0 nt!Phase1InitializationDiscard+0xced
    80786d50 83257fda 8080a7d0 add6142a 00000000 nt!Phase1Initialization+0xd
    80786d90 831001d9 831db43b 8080a7d0 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    fwpkclnt!WfpPoolAllocQualified+17
    8cd805d1 8b4d14 mov ecx,dword ptr [ebp+14h]

    SYMBOL_STACK_INDEX: 8

    SYMBOL_NAME: fwpkclnt!WfpPoolAllocQualified+17

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: fwpkclnt

    IMAGE_NAME: fwpkclnt.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7892c

    FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_fwpkclnt!WfpPoolAllocQualified+17

    BUCKET_ID: 0xD1_CODE_AV_BAD_IP_fwpkclnt!WfpPoolAllocQualified+17

    Followup: MachineOwner


    3rd

    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: 8067e2c1, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 82e968dc, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

    Debugging Details:
    ------------------


    READ_ADDRESS: GetPointerFromAddress: unable to read from 82f71848
    Unable to read MiSystemVaType memory at 82f50e40
    8067e2c1

    FAULTING_IP:
    nt!MmAccessFault+606
    82e968dc 8b3491 mov esi,dword ptr [ecx+edx*4]

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: csrss.exe

    CURRENT_IRQL: 0

    TRAP_FRAME: 8d143bb1 -- (.trap 0xffffffff8d143bb1)
    ErrCode = 00000011
    eax=89cd8a18 ebx=00000000 ecx=8647cd80 edx=8d143720 esi=89bb6000 edi=00000000
    eip=8d1433e0 esp=8d143c25 ebp=8d1433d4 iopl=0 nv up ei ng nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
    8d1433e0 ?? ???
    Resetting default scope

    UNALIGNED_STACK_POINTER: 8d143c25

    LAST_CONTROL_TRANSFER: from 82e493e8 to 82e963db

    STACK_TEXT:
    8d143aa4 82e493e8 00000000 8067e2c1 00000000 nt!MmAccessFault+0x106
    8d143aa4 82e968dc 00000000 8067e2c1 00000000 nt!KiTrap0E+0xdc
    8d143b99 82e493e8 00000008 8d1433e0 00000000 nt!MmAccessFault+0x606
    8d143b99 8d1433e0 00000008 8d1433e0 00000000 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    8d143c21 a889cd8a 348d143c 008d143c d8020100 0x8d1433e0
    8d143c25 348d143c 008d143c d8020100 d8871b4a 0xa889cd8a
    8d143c29 008d143c d8020100 d8871b4a 18871b4a 0x348d143c
    8d143c2d d8020100 d8871b4a 18871b4a d089cd8a 0x8d143c
    8d143c31 d8871b4a 18871b4a d089cd8a 4c871b4a 0xd8020100
    8d143c35 18871b4a d089cd8a 4c871b4a 018d143c 0xd8871b4a
    8d143c39 d089cd8a 4c871b4a 018d143c 38030100 0x18871b4a
    8d143c3d 4c871b4a 018d143c 38030100 38871b77 0xd089cd8a
    8d143c41 018d143c 38030100 38871b77 18871b77 0x4c871b4a
    8d143c45 38030100 38871b77 18871b77 3089cd8a 0x18d143c
    8d143c49 38871b77 18871b77 3089cd8a 64871b77 0x38030100
    8d143c4d 18871b77 3089cd8a 64871b77 028d143c 0x38871b77
    8d143c51 3089cd8a 64871b77 028d143c 28020100 0x18871b77
    8d143c55 64871b77 028d143c 28020100 28864e29 0x3089cd8a
    8d143c59 028d143c 28020100 28864e29 18864e29 0x64871b77
    8d143c5d 28020100 28864e29 18864e29 2089cd8a 0x28d143c
    8d143c61 28864e29 18864e29 2089cd8a 1c864e29 0x28020100
    8d143c65 18864e29 2089cd8a 1c864e29 038d143c 0x28864e29
    8d143c69 2089cd8a 1c864e29 038d143c 00020100 0x18864e29
    8d143c6d 1c864e29 038d143c 00020100 61000000 0x2089cd8a
    8d143c71 038d143c 00020100 61000000 00000261 0x1c864e29
    8d143c75 00020100 61000000 00000261 4e000010 0x38d143c
    8d143c79 61000000 00000261 4e000010 01000cfe 0x20100
    8d143c7d 00000000 4e000010 01000cfe af000000 0x61000000


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+dc
    82e493e8 85c0 test eax,eax

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiTrap0E+dc

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389

    FAILURE_BUCKET_ID: 0x50_nt!KiTrap0E+dc

    BUCKET_ID: 0x50_nt!KiTrap0E+dc

    Followup: MachineOwner


    4th

    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: c2e4bdf8, memory referenced.
    Arg2: 00000008, value 0 = read operation, 1 = write operation.
    Arg3: c2e4bdf8, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000002, (reserved)

    Debugging Details:
    ------------------


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f73848
    Unable to read MiSystemVaType memory at 82f52e40
    c2e4bdf8

    FAULTING_IP:
    +610f2faf03aedbf4
    c2e4bdf8 ?? ???

    MM_INTERNAL_CODE: 2

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0x50

    PROCESS_NAME: StarCraft_2_NA

    CURRENT_IRQL: 0

    TRAP_FRAME: a3e1fb90 -- (.trap 0xffffffffa3e1fb90)
    ErrCode = 00000010
    eax=00000148 ebx=85e508e0 ecx=85e41640 edx=86272980 esi=00000001 edi=85e41640
    eip=c2e4bdf8 esp=a3e1fc04 ebp=a3e1fc20 iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    c2e4bdf8 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 82e4b3e8 to 82e983db

    STACK_TEXT:
    a3e1fb78 82e4b3e8 00000008 c2e4bdf8 00000000 nt!MmAccessFault+0x106
    a3e1fb78 c2e4bdf8 00000008 c2e4bdf8 00000000 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a3e1fc00 8bc4f7e5 8563cf80 a3e1fcac 00000000 0xc2e4bdf8
    a3e1fc20 8bc65b5a 864612d8 00000002 00000000 fltmgr!FltpAllocateIrpCtrl+0xa9
    a3e1fc74 8306d00c 8563cf80 a3e1fcb4 00004000 fltmgr!FltpFastIoRead+0x86
    a3e1fd08 82e481fa 864612d8 00000000 00000000 nt!NtReadFile+0x2d5
    a3e1fd08 77c870b4 864612d8 00000000 00000000 nt!KiFastCallEntry+0x12a
    04b3f5c0 00000000 00000000 00000000 00000000 0x77c870b4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!KiTrap0E+dc
    82e4b3e8 85c0 test eax,eax

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!KiTrap0E+dc

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389

    FAILURE_BUCKET_ID: 0x50_nt!KiTrap0E+dc

    BUCKET_ID: 0x50_nt!KiTrap0E+dc

    Followup: MachineOwner


    5th

    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: dcddb9c8, memory referenced
    Arg2: 00000000, IRQL
    Arg3: 00000001, 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: 82e71410, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82f75848
    Unable to read MiSystemVaType memory at 82f54e40
    dcddb9c8

    CURRENT_IRQL: 0

    FAULTING_IP:
    nt!MiReplaceWsleHash+71
    82e71410 890c98 mov dword ptr [eax+ebx*4],ecx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: firefox.exe

    TRAP_FRAME: 9eb63a4c -- (.trap 0xffffffff9eb63a4c)
    ErrCode = 00000002
    eax=dcc01000 ebx=00076a72 ecx=00002d77 edx=00000000 esi=c0802d08 edi=89e71b50
    eip=82e71410 esp=9eb63ac0 ebp=9eb63ac4 iopl=0 nv up ei pl nz na pe cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010207
    nt!MiReplaceWsleHash+0x71:
    82e71410 890c98 mov dword ptr [eax+ebx*4],ecx ds:0023:dcddb9c8=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 82e71410 to 82e4d5db

    STACK_TEXT:
    9eb63a4c 82e71410 badb0d00 00000000 82ec31f9 nt!KiTrap0E+0x2cf
    9eb63ac4 82e73c6c 76a72c05 00002d77 0000053a nt!MiReplaceWsleHash+0x71
    9eb63ae8 82e73dcc 76a72c05 0000053a 75ed8001 nt!MiExchangeWsle+0x7c
    9eb63b14 82e7154f 0000053a 00002d77 89e71b50 nt!MiSwapWslEntries+0x14c
    9eb63b40 82e706cc 00002d77 75ed8000 89e71b50 nt!MiUpdateWsle+0x12d
    9eb63b74 82ea01ac c03af6c0 840fa0e8 00000000 nt!MiAllocateWsle+0x15f
    9eb63bc4 82ea6fe2 00000000 89e71b50 75ed8d0d nt!MiCompleteProtoPteFault+0x34f
    9eb63c08 82e9dd2d 00000000 75ed8d0d c03af6c0 nt!MiResolveProtoPteFault+0x1e1
    9eb63c90 82e9c8ad 75ed8d0d 00000000 89e71b50 nt!MiDispatchFault+0x5d6
    9eb63d1c 82e4d3e8 00000008 75ed8d0d 00000001 nt!MmAccessFault+0x25cc
    9eb63d1c 75ed8d0d 00000008 75ed8d0d 00000001 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    002def64 00000000 00000000 00000000 00000000 0x75ed8d0d


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt!MiReplaceWsleHash+71
    82e71410 890c98 mov dword ptr [eax+ebx*4],ecx

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MiReplaceWsleHash+71

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4e02a389

    IMAGE_NAME: memory_corruption

    FAILURE_BUCKET_ID: 0xA_nt!MiReplaceWsleHash+71

    BUCKET_ID: 0xA_nt!MiReplaceWsleHash+71

    Followup: MachineOwner


    6th


    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: 00f83a60, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, 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: 82ed1702, address which referenced memory

    Debugging Details:
    ------------------


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82fbf848
    Unable to read MiSystemVaType memory at 82f9ee40
    00f83a60

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt!KiInsertTimerTable+1e2
    82ed1702 895804 mov dword ptr [eax+4],ebx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xA

    PROCESS_NAME: explorer.exe

    TRAP_FRAME: 9ee17aec -- (.trap 0xffffffff9ee17aec)
    ErrCode = 00000002
    eax=00f83a5c ebx=87433800 ecx=256f94d1 edx=874337e8 esi=82f82680 edi=82fbdb78
    eip=82ed1702 esp=9ee17b60 ebp=9ee17ba8 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nt!KiInsertTimerTable+0x1e2:
    82ed1702 895804 mov dword ptr [eax+4],ebx ds:0023:00f83a60=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 82ed1702 to 82e975db

    STACK_TEXT:
    9ee17aec 82ed1702 badb0d00 874337e8 00000000 nt!KiTrap0E+0x2cf
    9ee17ba8 82ed347f 874337e8 000000d1 87433818 nt!KiInsertTimerTable+0x1e2
    9ee17bd8 82ecd0cf 87433758 87433818 000000d1 nt!KiCommitThreadWait+0x1a7
    9ee17c54 82e8baee 872b84d0 0000001b 00000000 nt!KeWaitForSingleObject+0x393
    9ee17cac 82ed7686 872b84d0 00000003 87433758 nt!ExpWaitForResource+0x16f
    9ee17cfc 82edacbe 871cb358 00000001 0264f808 nt!ExAcquireResourceExclusiveLite+0x1cf
    9ee17d10 98bd1709 871cb358 98be2a56 00000003 nt!ExEnterPriorityRegionAndAcquireResourceExclusive+0x24
    9ee17d18 98be2a56 00000003 0264f808 9ee17d34 win32k!EnterCrit+0xc
    9ee17d28 82e941fa 00000003 0264f840 778570b4 win32k!NtUserCallNoParam+0xc
    9ee17d28 778570b4 00000003 0264f840 778570b4 nt!KiFastCallEntry+0x12a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    0264f840 00000000 00000000 00000000 00000000 0x778570b4


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!EnterCrit+c
    98bd1709 a3580bd398 mov dword ptr [win32k!gptiCurrent (98d30b58)],eax

    SYMBOL_STACK_INDEX: 7

    SYMBOL_NAME: win32k!EnterCrit+c

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 4df2d2ee

    FAILURE_BUCKET_ID: 0xA_win32k!EnterCrit+c

    BUCKET_ID: 0xA_win32k!EnterCrit+c

    Followup: MachineOwner

    END

    Almost every minidump indicated a different process so i'm thinking the cause of my BSoDs could be from my initial issue between my mobo and RAM.

    Is this a reasonable conclusion? I posted the entire report in case anyone where could pick out something else that could be the issue.

    Thanks.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds