1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Many BSODs of diff. types

Discussion in 'Windows XP' started by Pentragon, 2008/03/11.

  1. 2008/03/11
    Pentragon

    Pentragon Inactive Thread Starter

    Joined:
    2008/03/11
    Messages:
    3
    Likes Received:
    0
    Hi There!

    I would like to get some help from anyone who knows more than me about these ugly blue screens.
    I was getting these error codes all the time, when playing a game, copying files and also when doing nothing :
    0x7F
    0x8E (many times)
    0x0A (well, this one ocured just after the reboot from an other error so some of them were caused by faulty shutdown (as shown in a dump file))
    0x50
    and some others but these were the most frequent

    After few days of finfing the cause i eventually managed to damage the system somehow. So i made a clean reinstall as it seemed the most helpful at this state.
    But the errors came again when i was copying some data from the old system's disc to the new one's (i installed it to a different _physical_ disc to avoid all the backuping).

    Now the errors are mostly the same as before - i made a memtest of my RAMs with no errors, i cleaned the inside of a case.
    I just dont know what to do since the errors are of many types and they point to many drivers.
    Today i had a bsod with nv4_disp.dll while playing a game (it's the most of the cases with games - its true that if i run only "normal" desktop applications its all ok), here is the minidump file:
    Loading Dump File [C:\WINDOWS\Minidump\Mini031108-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\C:\Program Files\Debugging Tools for Windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Tue Mar 11 16:11:16.671 2008 (GMT+1)
    System Uptime: 0 days 1:55:22.313
    Loading Kernel Symbols
    ..............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for nv4_disp.dll -
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, bfb4462f, ba4b3aa8, 0}



    Probably caused by : nv4_disp.dll ( nv4_disp+16f62f )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: bfb4462f, The address that the exception occurred at
    Arg3: ba4b3aa8, Trap Frame
    Arg4: 00000000

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




    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

    FAULTING_IP:
    nv4_disp+16f62f
    bfb4462f 899690040000 mov dword ptr [esi+490h],edx

    TRAP_FRAME: ba4b3aa8 -- (.trap 0xffffffffba4b3aa8)
    ErrCode = 00000002
    eax=00000000 ebx=e1d07800 ecx=00000000 edx=00000000 esi=e213f580 edi=e213f5b4
    eip=bfb4462f esp=ba4b3b1c ebp=00000000 iopl=0 nv up ei pl zr na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
    nv4_disp+0x16f62f:
    bfb4462f 899690040000 mov dword ptr [esi+490h],edx ds:0023:e213fa10=00000000
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: VietCong.exe

    LAST_CONTROL_TRANSFER: from 00000000 to bfb4462f

    STACK_TEXT:
    00000000 00000000 00000000 00000000 00000000 nv4_disp+0x16f62f


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nv4_disp+16f62f
    bfb4462f 899690040000 mov dword ptr [esi+490h],edx

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nv4_disp+16f62f

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nv4_disp

    IMAGE_NAME: nv4_disp.dll

    DEBUG_FLR_IMAGE_TIMESTAMP: 47567aa4

    FAILURE_BUCKET_ID: 0x8E_nv4_disp+16f62f

    BUCKET_ID: 0x8E_nv4_disp+16f62f

    Followup: MachineOwner
    ---------


    than, when i started to analyze the minidump in Windbg another bsod came out:

    Loading Dump File [C:\WINDOWS\Minidump\Mini031108-02.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\C:\Program Files\Debugging Tools for Windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Tue Mar 11 16:13:17.921 2008 (GMT+1)
    System Uptime: 0 days 0:01:23.546
    Loading Kernel Symbols
    ............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 80566cd1, ba4e968c, 0}

    *** ERROR: Module load completed but symbols could not be loaded for cmdguard.sys
    *** ERROR: Symbol file could not be found. Defaulted to export symbols for eamon.sys -


    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 80566cd1, The address that the exception occurred at
    Arg3: ba4e968c, Trap Frame
    Arg4: 00000000

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




    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

    FAULTING_IP:
    nt!ObpCloseHandle+10
    80566cd1 a124010000 mov eax,dword ptr ds:[00000124h]

    TRAP_FRAME: ba4e968c -- (.trap 0xffffffffba4e968c)
    ErrCode = 00000000
    eax=00000000 ebx=80566d49 ecx=00000000 edx=ba4e97e0 esi=ba4e97e4 edi=ba4e9768
    eip=80566cd1 esp=ba4e9700 ebp=ba4e9748 iopl=0 nv up ei ng nz ac po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010292
    nt!ObpCloseHandle+0x10:
    80566cd1 a124010000 mov eax,dword ptr ds:[00000124h] ds:0023:00000124=????????
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 2

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0x8E

    PROCESS_NAME: windbg.exe

    MISALIGNED_IP:
    nt!ObpCloseHandle+10
    80566cd1 a124010000 mov eax,dword ptr ds:[00000124h]

    LAST_CONTROL_TRANSFER: from 80566d66 to 80566cd1

    STACK_TEXT:
    ba4e9748 80566d66 80000f0c 00000000 00000000 nt!ObpCloseHandle+0x10
    ba4e975c 804de7ec 80000f0c ba4e9814 804dc8c1 nt!NtClose+0x1d
    ba4e975c 804dc8c1 80000f0c ba4e9814 804dc8c1 nt!KiFastCallEntry+0xf8
    ba4e97d8 f849394b 80000f0c 8208f160 0000003d nt!ZwClose+0x11
    ba4e9814 f8493bff 8208f110 ba4e984c f849411c fltMgr!FltpNormalizeNameComponent+0xab
    ba4e9820 f849411c 8208f110 00000000 8208f110 fltMgr!FltpCallNormalizeNameComponentHandler+0x41
    ba4e984c f8494df6 0000003d 00000000 8208f110 fltMgr!FltpExpandShortNames+0x110
    ba4e9868 f8495407 0000f110 00000000 000000fe fltMgr!FltpGetNormalizedFileNameWorker+0x90
    ba4e9880 f8492f3e 8208f110 00000000 8208f110 fltMgr!FltpGetNormalizedFileName+0x19
    ba4e9898 f8493001 80551480 8208f110 ba4e98d4 fltMgr!FltpCreateFileNameInformation+0x84
    ba4e98a8 f8483aac 8208f110 81a5527c 00000000 fltMgr!CreateTemporaryFileNameInformation+0xf
    ba4e98d4 f8484008 8208f110 00000021 819beb90 fltMgr!FltpGetFileNameInformation+0xaa
    ba4e98fc f518ccd8 00a5527c 00000101 ba4e9934 fltMgr!FltGetFileNameInformation+0x114
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ba4e9950 f51804d2 81958ba8 ba4e9980 ba4e99c0 cmdguard+0xccd8
    ba4e9960 f847f888 81a5527c ba4e9980 ba4e99b0 cmdguard+0x4d2
    ba4e99c0 f84812a0 004e9a04 81a55220 8224e1e0 fltMgr!FltpPerformPreCallbacks+0x2d4
    ba4e99d4 f848df17 ba4e9a04 f848c3aa 00000000 fltMgr!FltpPassThroughInternal+0x32
    ba4e99ec f848e436 ba4e9a04 821c1990 00000001 fltMgr!FltpCreateInternal+0x63
    ba4e9a20 804e37f7 81fe3020 8224e008 8224e1e0 fltMgr!FltpCreate+0x258
    ba4e9a30 ba9d7be9 8224e018 8201c7e0 821c1990 nt!IopfCallDriver+0x31
    ba4e9a60 804e37f7 81b15020 8224e008 8224e008 eamon+0x3be9
    ba4e9a70 8056f54a 82369bf0 81a7e6d4 ba4e9c18 nt!IopfCallDriver+0x31
    ba4e9b50 8056336c 82369c08 00000000 81a7e630 nt!IopParseDevice+0xa12
    ba4e9bd8 8056749a 00000000 ba4e9c18 00000040 nt!ObpLookupObjectName+0x56a
    ba4e9c2c 8056fa23 00000000 00000000 1c197001 nt!ObOpenObjectByName+0xeb
    ba4e9ca8 8056faf2 0112a7dc 00100001 0112a780 nt!IopCreateFile+0x407
    ba4e9d04 8056fbba 0112a7dc 00100001 0112a780 nt!IoCreateFile+0x8e
    ba4e9d44 804de7ec 0112a7dc 00100001 0112a780 nt!NtOpenFile+0x27
    ba4e9d44 7c90eb94 0112a7dc 00100001 0112a780 nt!KiFastCallEntry+0xf8
    0112aa4c 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -db !nt
    2 errors : !nt (80566d18-80566d68)
    80566d10 75 0c ff 75 08 50 57 e8 *0c ff ff ff ff 86 d4 00 u..u.PW.........
    ...
    80566d60 08 e8 5b ff ff ff 5d c2 *00 00 90 90 90 90 90 8b ..[...].........

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: STRIDE

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    BUCKET_ID: MEMORY_CORRUPTION_STRIDE

    Followup: memory_corruption
    ---------

    Well i think the last 2 or 3 are just consequences of the first one but i'm not really an expert to read from these files ;)
    I hope i didn't forget about anything important... i would really appreciate any help, thanks in advance ;)
     
    Pentragon,
    #1
  2. 2008/03/11
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Decoded from original post .....

    Continued ....

    followed by this one when i clicked to log in to my user account:

    Loading Dump File [C:\WINDOWS\Minidump\Mini031108-03.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\C:\Program Files\Debugging Tools for Windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Tue Mar 11 16:14:59.562 2008 (GMT+1)
    System Uptime: 0 days 0:00:50.203
    Loading Kernel Symbols
    ..........................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000008E, {c0000005, 0, 82062d34, 0}



    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner
    ---------

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
    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.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 00000000, The address that the exception occurred at
    Arg3: 82062d34, Trap Frame
    Arg4: 00000000

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




    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukce na adrese 0x%08lx odkazovala na adresu pam

    FAULTING_IP:
    +0
    00000000 ?? ???

    TRAP_FRAME: 82062d34 -- (.trap 0xffffffff82062d34)
    ErrCode = 00000000
    eax=81b415a8 ebx=81fc8240 ecx=00000000 edx=00000000 esi=81fc829c edi=821df17c
    eip=00000000 esp=82062da8 ebp=001b0003 iopl=0 nv up ei ng nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
    00000000 ?? ???
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 3

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from 82041758 to 00000000

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    82062da4 82041758 81b53750 82062db0 82062db0 0x0
    82062da8 81b53750 82062db0 82062db0 0dc34000 0x82041758
    82062dac 82062db0 82062db0 0dc34000 0dc35000 0x81b53750
    82062db0 00000000 0dc34000 0dc35000 00000000 0x82062db0


    STACK_COMMAND: .trap 0xffffffff82062d34 ; kb

    SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME: Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    BUCKET_ID: BAD_STACK

    Followup: MachineOwner

    _______________________________________________

    Loading Dump File [C:\WINDOWS\Minidump\Mini031108-04.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\C:\Program Files\Debugging Tools for Windows\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\WINDOWS;C:\WINDOWS\system32
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 2600.xpsp_sp2_gdr.070227-2254
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a620
    Debug session time: Tue Mar 11 16:15:57.968 2008 (GMT+1)
    System Uptime: 0 days 0:00:32.593
    Loading Kernel Symbols
    ...............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {49, 2, 0, bac7ea17}



    Probably caused by : memory_corruption

    Followup: memory_corruption

    --------- than again on win log on this one:

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

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

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




    READ_ADDRESS: 00000049

    CURRENT_IRQL: 2

    FAULTING_IP:
    kmixer!AgeIrps+7
    bac7ea17 8b7508 mov esi,dword ptr [ebp+8]

    CUSTOMER_CRASH_COUNT: 4

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: winlogon.exe

    LAST_CONTROL_TRANSFER: from bac7ec99 to bac7ea17

    STACK_TEXT:
    f8950ec0 bac7ec99 81bafea8 81fcbf2b 81fcbe70 kmixer!AgeIrps+0x7
    f8950ee8 804e3d38 00000000 81fcbe70 02fa9b40 kmixer!MxWriteComplete+0x209
    f8950f18 f73e4bf2 82002d20 81fcbe70 00000000 nt!IopfCompleteRequest+0xa2
    f8950f2c f73de68d 81bad014 81fcbe70 f8950f48 portcls!CPortPinWaveCyclic::TransferKsIrp+0x71
    f8950f40 f73de1ef 81bad014 81fcbe70 82002d20 portcls!KspShellTransferKsIrp+0x19
    f8950f5c f73e0a9f 81fcbe70 81fc4288 000052a0 portcls!CIrpStream::ReleaseUnmappingIrp+0x80
    f8950f7c f73e4a24 82002d20 00001b40 f8950fa8 portcls!CIrpStream::Complete+0xa8
    f8950fb8 f73de497 000037c0 8214c238 ffdff000 portcls!CPortPinWaveCyclic::RequestService+0x3a1
    f8950fd0 804dbbd4 81ba8308 81ba82f8 00000000 portcls!CServiceGroup::ServiceDpc+0x2a
    f8950ff4 804db89e f86a4cd0 00000000 00000000 nt!KiRetireDpcList+0x46
    f8950ff8 f86a4cd0 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    804db89e 00000000 00000009 bb835675 00000128 0xf86a4cd0


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !kmixer
    bac7ecd0 - kmixer!MxWriteComplete+240
    [ cc:c8 ]
    1 error : !kmixer (bac7ecd0)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: ONE_BIT

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

    BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT

    Followup: memory_corruption

    ---------Well i think the last 2 or 3 are just consequences of the first one but i'm not


    ---------
     
    PeteC,
    #2


  3. to hide this advert.

  4. 2008/03/11
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    Pentragon - Welcome to the Board :)

    Please do not enclose dump data in CODE tags - it makes the logs almost impossible to read. I have edited your post and spread the data across 2 posts.

    First a caveat ....
    That said there is reference to memory corruption more than once - that is where you should start.....
    Unfortunately that means very little .....
    The most reliable method of checking RAM is to do it physically - this tests both the memory module and the slot into which it fits. So, if you have a single stick switch it between slots and test in each position by working it hard. If you have two sticks run each stick separately switching between slots. Then if you are using matched pairs (don't get them mixed up if you have 2 pairs) switch them around the pairs of slots. It's a process of elimination, can be tedious, but it's the most reliable method.
     
    PeteC,
    #3
  5. 2008/03/11
    Pentragon

    Pentragon Inactive Thread Starter

    Joined:
    2008/03/11
    Messages:
    3
    Likes Received:
    0
    Oh ok i just wanted to make my post a bit shorter ;)

    I think i already did something like what you said about the testing of rams but yeah i'll try again in a more organized way, thx for now ;)
     
    Pentragon,
    #4
  6. 2008/03/12
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    2 minidumps are crashed due to memory corruption. This culprit is ram. Reseat the memory module to another ram slot may resolve the blue screen.
     
    cpc2004,
    #5
  7. 2008/03/15
    Pentragon

    Pentragon Inactive Thread Starter

    Joined:
    2008/03/11
    Messages:
    3
    Likes Received:
    0
    Ok, so i tested my RAMs some more - i have got 2 memory modules in 2 slots. I tried to use only one module and pluged it in the 1st slot, then in the other slot and the problem did not disappear. Same thing with the other module...

    So i reinstalled the system once more (not a clear reainstall, just an innovation) and i didn't install any windows updates. Everything went ok but only one day ! The day after all the BSODs were back, so i used the System Restore tool to return just after the new reinstall. And again evething went well for one day ! Today i had this one:

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    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: 00000020, a pool block header size is corrupt.
    Arg2: e2f2b7ac, The pool entry we were looking for within the page.
    Arg3: e2f2c1dc, The next pool entry.
    Arg4: 0d46744e, (reserved)

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




    BUGCHECK_STR: 0x19_20

    POOL_ADDRESS: e2f2b7ac

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT

    LAST_CONTROL_TRANSFER: from 8054be41 to 805339ae

    STACK_TEXT:
    b90b6600 8054be41 00000019 00000020 e2f2b7ac nt!KeBugCheckEx+0x1b
    b90b6650 f76eac50 e2f2b7b4 00000000 f76e60cc nt!ExFreePoolWithTag+0x2be
    b90b665c f76e60cc 00015c00 00000000 cd495d30 Ntfs!NtfsCommonCreate+0x1563
    b90b6860 f76e7f64 85fd0320 85ded890 b90b68b8 Ntfs!NtfsCommonCreate+0x14c0
    b90b6940 804e3d77 86760020 85ded890 864ceb30 Ntfs!NtfsFsdCreate+0x1ec
    b90b6950 f776b876 00000000 86755268 865a1270 nt!IopfCallDriver+0x31
    b90b699c 804e3d77 867989d8 00000001 85ded890 sr!SrCreate+0x150
    b90b69ac f777be67 00000000 85ded890 00000000 nt!IopfCallDriver+0x31
    b90b69d0 f7788153 b90b69f0 86043a70 00000000 fltMgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x20b
    b90b6a0c 804e3d77 86043a70 85deda68 00000de4 fltMgr!FltpCreate+0x1e3
    b90b6a1c b9f35be9 85ded8a0 86442030 864ceb30 nt!IopfCallDriver+0x31
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b90b6a4c 804e3d77 864e8380 85ded890 85ded890 eamon+0x3be9
    b90b6a5c 80570f9c 8677dbf0 863b8b6c b90b6c04 nt!IopfCallDriver+0x31
    b90b6b3c 8056386c 8677dc08 00000000 863b8ac8 nt!IopParseDevice+0xa58
    b90b6bc4 80567c63 00000000 b90b6c04 00000040 nt!ObpLookupObjectName+0x56a
    b90b6c18 80571477 00000000 00000000 0fffff01 nt!ObOpenObjectByName+0xeb
    b90b6c94 80571546 0013f67c 80100080 0013f648 nt!IopCreateFile+0x407
    b90b6cf0 8057167c 0013f67c 80100080 0013f648 nt!IoCreateFile+0x8e
    b90b6d30 804df06b 0013f67c 80100080 0013f648 nt!NtCreateFile+0x30
    b90b6d30 7c90eb94 0013f67c 80100080 0013f648 nt!KiFastCallEntry+0xf8
    0013f680 00000000 00000000 00000000 00000000 0x7c90eb94


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    eamon+3be9
    b9f35be9 8bf0 mov esi,eax

    SYMBOL_STACK_INDEX: b

    SYMBOL_NAME: eamon+3be9

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: eamon

    IMAGE_NAME: eamon.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 47bbf93c

    FAILURE_BUCKET_ID: 0x19_20_eamon+3be9

    BUCKET_ID: 0x19_20_eamon+3be9

    Followup: MachineOwner
    ---------
    I just can't imagine what could change during the last night ! I didn't do anything :eek:

    Any ideas what could be this magic ?

    PS: i have an option to INSTALL THE DOWNLOADED UPDATES on my 'Turn Off Computer' button so could these downloaded but not installed updates cause problems ? (since it is the only thing which seems to have changed)
     
    Pentragon,
    #6
  8. 2008/03/17
    cpc2004

    cpc2004 Inactive

    Joined:
    2005/07/08
    Messages:
    366
    Likes Received:
    0
    The latest crash is also related to faulty ram. Try reseating the ram and clean up dust inside the ram slot. If it still crashes, replace the ram.
     
    cpc2004,
    #7

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...