locked
Windows 7 pro x64 BSOD RRS feed

  • Question

  • I'm getting BSODs lately, anyways: error:

    Problem signature:
      Problem Event Name:    BlueScreen
      OS Version:    6.1.7600.2.0.0.256.48
      Locale ID:    4105

    Additional information about the problem:
      BCCode:    50
      BCP1:    FFFFF8A01772D5E0
      BCP2:    0000000000000000
      BCP3:    FFFFF88004176475
      BCP4:    0000000000000002
      OS Version:    6_1_7600
      Service Pack:    0_0
      Product:    256_1

     

     

    Saturday, December 25, 2010 7:19 PM

Answers

  • MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000061940, A PDE has been unexpectedly invalidated.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'+0x1fd23
    nt!MiUpdateWsle+0xd2
    nt!MiDispatchFault+0x6cf
    nt!MmAccessFault +0x343
    nt!KiPageFault+0x16e
    nt!NtLockVirtualMemory +0x2fc
    nt!KiSystemServiceCopyEnd+0x13
    0x77520bba

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8005e53060, Terminating object
    Arg3: fffffa8005e53340, Process image file name
    Arg4: fffff800031cc5d0, Explanatory message (ascii)


    PROCESS_NAME:  csrss.exe

    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 :

    //
    // MessageId: STATUS_STACK_BUFFER_OVERRUN
    //
    // MessageText:
    //
    // The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    //
    #define STATUS_STACK_BUFFER_OVERRUN      ((NTSTATUS)0xC0000409 L)    // winnt

    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!MiBadShareCount+0x4c
    nt! ?? ::FNODOBFM::`string'+0x3223e
    nt!MiDeleteAddressesInWorkingSet+0x307
    nt!MmCleanProcessAddressSpace+0x96

    IMAGE_NAME:  memory_corruption

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'+0x40ec0
    nt!KiPageFault+0x16e
    dxgmms1!VIDMM_PROCESS_HEAP::Free +0x65
    dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
    dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
    dxgmms1!VidMmCloseAllocation+0x44

    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM.

    Also update your BIOS:

    BiosVersion = 080015
    BiosReleaseDate = 11/05/2008
    SystemManufacturer = BIOSTAR Group
    SystemProductName = P43-A7


    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Tuesday, December 28, 2010 5:07 AM
    Saturday, December 25, 2010 9:47 PM

All replies

  • Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

    This indicates that invalid system memory has been referenced.

    http://msdn.microsoft.com/en-us/library/ff559023%28VS.85%29.aspx

    To see the cause I have to take a look at the dumps with the Debugging Tools for Windows.

    Please start the Windows Explorer and go to the folder C:\Windows\Minidump. Next, copy the dmp files to your desktop, zip all dmp into 1 zip file and upload the zip file to your public Skydrive [1] folder and post a link here.

    André

    [1] http://social.technet.microsoft.com/Forums/en-US/w7itproui/thread/4fc10639-02db-4665-993a-08d865088d65


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Saturday, December 25, 2010 7:45 PM
  • Saturday, December 25, 2010 8:12 PM
  • MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000061940, A PDE has been unexpectedly invalidated.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'+0x1fd23
    nt!MiUpdateWsle+0xd2
    nt!MiDispatchFault+0x6cf
    nt!MmAccessFault +0x343
    nt!KiPageFault+0x16e
    nt!NtLockVirtualMemory +0x2fc
    nt!KiSystemServiceCopyEnd+0x13
    0x77520bba

    CRITICAL_OBJECT_TERMINATION (f4)
    A process or thread crucial to system operation has unexpectedly exited or been
    terminated.
    Several processes and threads are necessary for the operation of the
    system; when they are terminated (for any reason), the system can no
    longer function.
    Arguments:
    Arg1: 0000000000000003, Process
    Arg2: fffffa8005e53060, Terminating object
    Arg3: fffffa8005e53340, Process image file name
    Arg4: fffff800031cc5d0, Explanatory message (ascii)


    PROCESS_NAME:  csrss.exe

    EXCEPTION_CODE: (NTSTATUS) 0xc0000409 :

    //
    // MessageId: STATUS_STACK_BUFFER_OVERRUN
    //
    // MessageText:
    //
    // The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
    //
    #define STATUS_STACK_BUFFER_OVERRUN      ((NTSTATUS)0xC0000409 L)    // winnt

    PFN_LIST_CORRUPT (4e)
    Typically caused by drivers passing bad memory descriptor lists (ie: calling
    MmUnlockPages twice with the same list, etc).  If a kernel debugger is
    available get the stack trace.
    Arguments:
    Arg1: 0000000000000099, A PTE or PFN is corrupt

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt!MiBadShareCount+0x4c
    nt! ?? ::FNODOBFM::`string'+0x3223e
    nt!MiDeleteAddressesInWorkingSet+0x307
    nt!MmCleanProcessAddressSpace+0x96

    IMAGE_NAME:  memory_corruption

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.

    STACK_TEXT: 
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'+0x40ec0
    nt!KiPageFault+0x16e
    dxgmms1!VIDMM_PROCESS_HEAP::Free +0x65
    dxgmms1!VIDMM_GLOBAL::CloseLocalAllocation+0x112
    dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x19b
    dxgmms1!VidMmCloseAllocation+0x44

    So it looks like your RAM is damaged. Please download memtest86+ [1], burn a new bootable CD (use a CD-RW if possible) from the ISO (download and use ImgBurn [2] to do this or make double click on the ISO in Windows 7), reboot your PC and scan your RAM 4-5hours for errors. If it detects errors, replace the faulty RAM.

    Also update your BIOS:

    BiosVersion = 080015
    BiosReleaseDate = 11/05/2008
    SystemManufacturer = BIOSTAR Group
    SystemProductName = P43-A7


    André

    [1] http://www.memtest.org/download/4.10/memtest86+-4.10.iso.zip
    [2] http://www.imgburn.com/index.php?act=download


    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    • Marked as answer by Cloud_TS Tuesday, December 28, 2010 5:07 AM
    Saturday, December 25, 2010 9:47 PM