locked
BSOD memory management RRS feed

  • Question

  • Hello,

    For a while now i have been experiencing BSOD's when using programs or websites that contain graphics. This only happens when on graphics websites like youtube, facebook etc.. when word processing it is fine. I have uploaded 10 of the latest windows dump files here:

    http://cid-ad9b621ef8223829.office.live.com/browse.aspx/Dump%20Files

    I always thought it was a RAM problem or a graphics problem but i have removed the graphics card now and am using the on-board graphics and i have also removed two lots of RAM sticks which i thought may be causing the issue but it still persists.

    Note: This computer ran fine with these type of things in the past it has only just started to happen in the last few months.

    Any input would be much appreciated.

    Kind Regards,
    Steven

    Monday, April 25, 2011 12:39 PM

Answers

  • I have purchased a new motherboard and have installed it. Everything is working a lot better now there are no more crashes at all. 

     

    Thank you everyone for your help. 

     

    Kind Regards,

    Steven

    • Marked as answer by Leo Huang Thursday, May 5, 2011 7:20 AM
    Monday, May 2, 2011 2:47 PM

All replies

  • Hello,

    please set the folder for public access because I am unable to access it.

    If you want to read dump files without my help, use Windbg and refer to this Microsoft article:

    http://support.microsoft.com/kb/315263

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Monday, April 25, 2011 12:49 PM
  • The skydrive folder has already been marked for public access upon creation of the directory.

    Skydrive Settings:

    Shared with:
    Everyone (public)

     

    Again the link is: http://cid-ad9b621ef8223829.office.live.com/self.aspx/Dump%20Files

     

    Alternativly i have uploaded the zip file to my ISP webspace here:

    http://users.tpg.com.au/98214791/dump.zip

    Tuesday, April 26, 2011 1:02 AM
  • Bump :)
    Tuesday, April 26, 2011 10:54 PM
  • Hi,

     

    The dump file analyze:

     

    Executable search path is:

    Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7600.16695.x86fre.win7_gdr.101026-1503

    Machine Name:

    Kernel base = 0x82e11000 PsLoadedModuleList = 0x82f59810

    Debug session time: Sun Apr 24 08:46:04.312 2011 (UTC + 8:00)

    System Uptime: 0 days 0:39:00.107

    Loading Kernel Symbols

    ...............................................................

    ................................................................

    ...................................

    Loading User Symbols

    Loading unloaded module list

    ......

    *******************************************************************************

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    Use !analyze -v to get detailed debugging information.

     

    BugCheck 1000008E, {c0000005, 2874ead, 8b867c20, 0}

     

    Probably caused by : win32k.sys ( win32k!UserGetRedirectedWindowOrigin+36 )

     

    Followup: MachineOwner

     

     

    About error 1000008E, please refer http://msdn.microsoft.com/en-us/library/ff557203(v=VS.85).aspx

     

     

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, April 27, 2011 5:34 AM
  • *******************************************************************************

     

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

    *******************************************************************************

     

    MEMORY_MANAGEMENT (1a)

        # Any other values for parameter 1 must be individually examined.

    Arguments:

    Arg1: 00041287, The subtype of the bugcheck.

    Arg2: 02eb0870

    Arg3: 00000000

    Arg4: 00000000


    Debugging Details:

    ------------------



    BUGCHECK_STR:  0x1a_41287


    CUSTOMER_CRASH_COUNT:  1


    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


    PROCESS_NAME:  java.exe


    CURRENT_IRQL:  0


    TRAP_FRAME:  9ab93c1c -- (.trap 0xffffffff9ab93c1c)

    ErrCode = 00000010

    eax=86686270 ebx=9ab93ce0 ecx=00005a0b edx=00000000 esi=c002d058 edi=05a0b000

    eip=02eb0870 esp=9ab93c90 ebp=9ab93ca0 iopl=0         nv up ei ng nz ac pe cy

    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010297

    02eb0870 ??              ???

    Resetting default scope


    LAST_CONTROL_TRANSFER:  from 82e4f628 to 82e8e9eb


    STACK_TEXT:  

    9ab93c04 82e4f628 00000008 02eb0870 00000000 nt!MmAccessFault+0x106

    9ab93c04 02eb0870 00000008 02eb0870 00000000 nt!KiTrap0E+0xdc

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    9ab93c8c 84f9bd48 c002d058 00000000 00000000 0x2eb0870

    9ab93ca0 82e906e4 9ab93ce0 9ab93cd8 05a0b000 0x84f9bd48

    9ab93d1c 82e4f628 00000001 05a0b000 00000001 nt!MmAccessFault+0x1dfd

    9ab93d1c 7054ab62 00000001 05a0b000 00000001 nt!KiTrap0E+0xdc

    06f4fed4 00000000 00000000 00000000 00000000 0x7054ab62



    STACK_COMMAND:  kb


    FOLLOWUP_IP: 

    nt!KiTrap0E+dc

    82e4f628 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:  4cc78ed4


    FAILURE_BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc


    BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc


    Followup: MachineOwner

    ---------

     

    ______________________________________________________________________

    Bug Check Code 0x1A: http://msdn.microsoft.com/fr-be/library/ff557391(v=VS.85).aspx

    0x41287

    Internal memory management structures are corrupted. To further investigate the cause, a kernel memory dump file is needed.

    Start by running memtest86+ to check that all is okay with your RAM and upload the kernel dumps (Please configure your Windows to generate a full dump, zip it and upload it).

    I see that the dump files (I analyzed) are for the same error so do what I said.

    For the BSOD analyzed by leo, I don't know which one it is (Could you tell which one it is, leo?) but it is possible that win32k is corrupted and in this case I recommand the re-install of Windows.

     

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Wednesday, April 27, 2011 6:31 AM
  • I analyzed the dump file from http://users.tpg.com.au/98214791/dump.zip, the latest dump file created 042511-24382-01.dmp.

     

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, April 27, 2011 6:40 AM
  • Hello leo,

    thanks for the reply.

    I think you mean the 042411-39374-01.dmp or another dump that dates the 24/04/2011.

    The output on my debugger is the following:

     

    *******************************************************************************

    *                                                                             *

    *                        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: 8304899d, The address that the exception occurred at

    Arg3: 84cefc60, Trap Frame

    Arg4: 00000000

     

    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!NtWaitForSingleObject+7e

    8304899d 8b4010          mov     eax,dword ptr [eax+10h]

     

    TRAP_FRAME:  84cefc60 -- (.trap 0xffffffff84cefc60)

    ErrCode = 00000000

    eax=00000000 ebx=00000000 ecx=97d5f8c8 edx=00000001 esi=8304d4b7 edi=00000000

    eip=8304899d esp=84cefcd4 ebp=84cefd20 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!NtWaitForSingleObject+0x7e:

    8304899d 8b4010          mov     eax,dword ptr [eax+10h] ds:0023:00000010=????????

    Resetting default scope

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0x8E

     

    PROCESS_NAME:  Tibia.exe

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from 82e5a43a to 8304899d

     

    STACK_TEXT:  

    84cefd20 82e5a43a 000001fc 00000000 00000000 nt!NtWaitForSingleObject+0x7e

    84cefd20 777a6344 000001fc 00000000 00000000 nt!KiFastCallEntry+0x12a

    WARNING: Frame IP not in any known module. Following frames may be wrong.

    05e5ff38 00000000 00000000 00000000 00000000 0x777a6344

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_IP: 

    nt!NtWaitForSingleObject+7e

    8304899d 8b4010          mov     eax,dword ptr [eax+10h]

     

    SYMBOL_STACK_INDEX:  0

     

    SYMBOL_NAME:  nt!NtWaitForSingleObject+7e

     

    FOLLOWUP_NAME:  MachineOwner

     

    MODULE_NAME: nt

     

    IMAGE_NAME:  ntkrpamp.exe

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4

     

    FAILURE_BUCKET_ID:  0x8E_nt!NtWaitForSingleObject+7e

     

    BUCKET_ID:  0x8E_nt!NtWaitForSingleObject+7e

    ___________________________________________________________
    For me it does not show win32k.sys driver but like mentioned in the link you provided and like I said previously, a kernel dump is needed for more information.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Wednesday, April 27, 2011 6:59 AM
  • Hi Mr X,

     

    I analyzed the dump 042511-24382-01.dmp which dated on 2011/4/25 10:07PM , not 042411-39374-01.dmp.

     

    And for dump 042411-39374-01.dmp, I analyzed it get the same result of yours.

     

     

     

    Regards,

    Leo   Huang

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, April 27, 2011 7:15 AM
  • Debug session time: Sun Apr 24 08:46:04.312 2011 (UTC + 8:00)

    Hello again leo, I said that the dump you analyzed dates of 24/04/2011 because it is mentioned that the Debug Session time is Sun Apr 24 08:46:04.312 2011.

    In all cases, a kernel dump should be provided like mentioned in the Microsoft article you provided.

    Regards.

    Wednesday, April 27, 2011 7:57 AM
  • Hello,

     

    I have run the Memory test as suggested. However the computer switches off when about 60% through. This happens for both windows memory diagnostic tool and Memtest. I'll assume this indicates a hardware problem - but i am skeptical that it is the RAM sticks i would lean towards the motherboard being faulty.. is there anyway to determine this?

    Also i would be providing a kernel dump but i see no reference to it in the Microsoft article.

    Kind Regards,

    Steve

     

    Thursday, April 28, 2011 3:15 AM
  • To generate a kernel/full dump, refer to this Microsoft article: http://support.microsoft.com/kb/972110

    You have to wait to the next crash so that it will be generated.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Thursday, April 28, 2011 6:40 AM
  • Hi, Here is the new dump file: http://users.tpg.com.au/98214791/042811-20077-01.dmp After doing this the computer would not boot back into windows with have a blue screen. It kept went to the windows loading screen then crashed. Something about IRQL and a stop code. Also weirdly enough this was also happening in SAFE mode... I have had to remove a RAM stick for the computer to not BSOD upon startup.
    Thursday, April 28, 2011 1:48 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    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: 8131faa4, memory referenced.
    Arg2: 00000000, value 0 = read operation, 1 = write operation.
    Arg3: 8d7cb623, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)
    Debugging Details:
    ------------------
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Could not read faulting driver name
    READ_ADDRESS: GetPointerFromAddress: unable to read from 82fb3718
    Unable to read MiSystemVaType memory at 82f93160
     8131faa4 
    FAULTING_IP: 
    nvlddmkm+1a1623
    8d7cb623 8b45f4          mov     eax,dword ptr [ebp-0Ch]
    MM_INTERNAL_CODE:  0
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0x50
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    TRAP_FRAME:  8931fa24 -- (.trap 0xffffffff8931fa24)
    ErrCode = 00000000
    eax=00000000 ebx=00009400 ecx=00000006 edx=00000001 esi=857b5cc0 edi=84573180
    eip=8d7cb623 esp=8931fa98 ebp=8131fab0 iopl=0         nv up ei pl zr na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
    nvlddmkm+0x1a1623:
    8d7cb623 8b45f4          mov     eax,dword ptr [ebp-0Ch] ss:0010:8131faa4=????????
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 82e91628 to 82ed09eb
    STACK_TEXT:  
    8931fa0c 82e91628 00000000 8131faa4 00000000 nt!MmAccessFault+0x106
    8931fa0c 8d7cb623 00000000 8131faa4 00000000 nt!KiTrap0E+0xdc
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8931fa94 84573180 85d33400 858e0290 00000000 nvlddmkm+0x1a1623
    8931fa98 85d33400 858e0290 00000000 00000000 0x84573180
    8931fa9c 858e0290 00000000 00000000 00000000 0x85d33400
    8931faa0 00000000 00000000 00000000 8931fac4 0x858e0290
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nvlddmkm+1a1623
    8d7cb623 8b45f4          mov     eax,dword ptr [ebp-0Ch]
    SYMBOL_STACK_INDEX:  2
    SYMBOL_NAME:  nvlddmkm+1a1623
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4cb9dbec
    FAILURE_BUCKET_ID:  0x50_nvlddmkm+1a1623
    BUCKET_ID:  0x50_nvlddmkm+1a1623
    Followup: MachineOwner
    ---------
    0: kd> lmvm nvlddmkm
    start    end        module name
    8d62a000 8dfc65a0   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sat Oct 16 19:07:56 2010 (4CB9DBEC)
        CheckSum:         009A1A8C
        ImageSize:        0099C5A0
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    ___________________________
    The BSOD was caused by a your NVIDIA Graphic Card driver.
    Please update it.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Thursday, April 28, 2011 1:56 PM
  • I have updated my Nvidia driver to the latist one. However it did still BSOD a short time after.

     

    The new dumps files are here: http://users.tpg.com.au/98214791/new_dump.zip

    Again the only way i was able to get back into windows was by change the RAM to a different slot.

     

    The computer would BSOD on safe mode (all choices) and on windows startup repair.

    Friday, April 29, 2011 1:03 AM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 00041287, The subtype of the bugcheck.
    Arg2: 02ea8870
    Arg3: 00000000
    Arg4: 00000000
    Debugging Details:
    ------------------
    BUGCHECK_STR:  0x1a_41287
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    PROCESS_NAME:  Tibia.exe
    CURRENT_IRQL:  0
    TRAP_FRAME:  90c0bc1c -- (.trap 0xffffffff90c0bc1c)
    ErrCode = 00000011
    eax=9cb0a368 ebx=90c0bce0 ecx=00006630 edx=00000000 esi=c0033180 edi=06630000
    eip=02ea8870 esp=90c0bc90 ebp=90c0bca0 iopl=0         nv up ei ng nz ac po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010293
    02ea8870 0000            add     byte ptr [eax],al          ds:0023:9cb0a368=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from 82e47628 to 82e869eb
    STACK_TEXT:  
    90c0bc04 82e47628 00000008 02ea8870 00000000 nt!MmAccessFault+0x106
    90c0bc04 02ea8870 00000008 02ea8870 00000000 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    90c0bca0 82e886e4 90c0bce0 90c0bcd8 06630000 0x2ea8870
    90c0bd1c 82e47628 00000001 06630000 00000001 nt!MmAccessFault+0x1dfd
    90c0bd1c 6dfc0ea9 00000001 06630000 00000001 nt!KiTrap0E+0xdc
    065efed4 00000000 00000000 00000000 00000000 0x6dfc0ea9
    STACK_COMMAND:  kb
    FOLLOWUP_IP: 
    nt!KiTrap0E+dc
    82e47628 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:  4cc78ed4
    FAILURE_BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc
    BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc
    Followup: MachineOwner
    _______________________________________________________

    0x41287

    Internal memory management structures are corrupted. To further investigate the cause, a kernel memory dump file is needed.

    You should configure your Windows to generate a kernel dump or contact CSS to solve your problem.

    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Friday, April 29, 2011 6:49 AM
  • Kernal dump uploaded here: http://cid-ad9b621ef8223829.office.live.com/self.aspx/Dump%20Files/Kernel%20Dump

     

    it is split into two different files you will need 7zip to un-compress

     

    Friday, April 29, 2011 4:03 PM
  • *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

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

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


    READ_ADDRESS:  80f53824

    FAULTING_IP:
    nt!RtlInterlockedSetClearRun+17
    82e98f91 037204          add     esi,dword ptr [edx+4]

    MM_INTERNAL_CODE:  2

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    PROCESS_NAME:  taskhost.exe

    CURRENT_IRQL:  0

    TRAP_FRAME:  89377b78 -- (.trap 0xffffffff89377b78)
    ErrCode = 00000000
    eax=000137be ebx=00000001 ecx=00000001 edx=80f53820 esi=000026f7 edi=000137be
    eip=82e98f91 esp=89377bec ebp=89377bfc iopl=0         nv up ei pl nz ac po cy
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010213
    nt!RtlInterlockedSetClearRun+0x17:
    82e98f91 037204          add     esi,dword ptr [edx+4] ds:0023:80f53824=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from 82e53628 to 82e929eb

    STACK_TEXT: 
    89377b60 82e53628 00000000 80f53824 00000000 nt!MmAccessFault+0x106
    89377b60 82e98f91 00000000 80f53824 00000000 nt!KiTrap0E+0xdc
    89377bfc 82ea098a 82f53820 000137be 00000001 nt!RtlInterlockedSetClearRun+0x17
    89377c2c 82ebfd1e 82f53820 00000001 00000000 nt!MiReservePtes+0x8c
    89377c50 82e9ba14 8460a030 c0001560 00000000 nt!MiZeroPhysicalPage+0x2f
    89377c90 82e946a8 00000001 002ac000 89377d34 nt!MiResolveDemandZeroFault+0x158
    89377d1c 82e53628 00000001 002ac000 00000001 nt!MmAccessFault+0x1dc1
    89377d1c 77a24605 00000001 002ac000 00000001 nt!KiTrap0E+0xdc
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    020cf848 00000000 00000000 00000000 00000000 0x77a24605


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt!RtlInterlockedSetClearRun+17
    82e98f91 037204          add     esi,dword ptr [edx+4]

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  nt!RtlInterlockedSetClearRun+17

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  4cc78ed4

    FAILURE_BUCKET_ID:  0x50_nt!RtlInterlockedSetClearRun+17

    BUCKET_ID:  0x50_nt!RtlInterlockedSetClearRun+17

    ------------------------------------------------------------------------------------

    Hello, this is not the same bug. The Bug Check Code here is 0x50: http://msdn.microsoft.com/en-us/library/ff559023(VS.85).aspx

    I suspect that there is something wrong with your RAM. A read operation in the memory was performed and the crash occured.

    I think it will be better to contact CSS or your manufacturer Technical Support.

    If you run memtest86+, is there any error that is displayed? If yes, you have to replace the faulty RAM.


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration

    Friday, April 29, 2011 6:13 PM
  • Question do you have SAS hard drives or the new SSD drives in your system?

    If not did you allow these following updates on your system KB2492386 and KB982018, If they are on your system and you don't own the above mentioned hard drives try uninstalling these 2 patches and see if it helps.


    • Edited by DirtyOleBeggar Saturday, April 30, 2011 12:53 PM changed PATA to SAS
    Friday, April 29, 2011 6:24 PM
  • Hello, I have run the memory test but there is no error displayed because the computer just switches off while running the test. However im thinking it is more a mother board issue since i have three different RAM sticks 1GB each and i have put the 3 different sticks in at different times and still the same thing. i would think it is unlikely three RAM sticks all failed at the same time.
    Saturday, April 30, 2011 12:33 AM
  • Hello, I have run the memory test but there is no error displayed because the computer just switches off while running the test. However im thinking it is more a mother board issue since i have three different RAM sticks 1GB each and i have put the 3 different sticks in at different times and still the same thing. i would think it is unlikely three RAM sticks all failed at the same time.
    I would tend to agree with the memory stick assessment.

    Also try updating your motherboards BIOS and any other motherboard related software updates the manufacturer offers
    • Edited by DirtyOleBeggar Saturday, April 30, 2011 1:55 AM added a line of txt
    Saturday, April 30, 2011 1:48 AM
  • I have purchased a new motherboard and have installed it. Everything is working a lot better now there are no more crashes at all. 

     

    Thank you everyone for your help. 

     

    Kind Regards,

    Steven

    • Marked as answer by Leo Huang Thursday, May 5, 2011 7:20 AM
    Monday, May 2, 2011 2:47 PM
  • I have purchased a new motherboard and have installed it. Everything is working a lot better now there are no more crashes at all. 

     

    Thank you everyone for your help. 

     

    Kind Regards,

    Steven

    Well that is definitely one way to get around the problem. :)

    Take care and enjoy!

    Monday, May 2, 2011 3:27 PM