Blue Screen - Continues after system restore RRS feed

  • Question

  • I have an HP MediaSmart EX495 Windows Home Server (v1).  For a long time I've been putting up with random system crashes and finally decided it was time to reinstall the OS.  I reinstalled everything which went fine and got the system fully patched.  Much to my chagrin it continues to crash periodically (on average it's about once a day).  The report I get back indicates it's caused by the ever helpful unknown device driver but the only hardware in the system that isn't factory installed by HP is a couple of Samsung drives that have been fully chkdisked.  I don't have any other software installed at this point so I can't imagine what could be causing this other than a bad CPU, memory, or system disk.

    I've tried analyzing the memory.dmp file but don't know where to go with it.  It doesn't point at a specific driver as far as I can tell and I'm not sure how to use a kernel debugger to get a stack trace as it suggests (let alone what to do with that stack trace).  Any thoughts?

    Bugcheck Analysis below:


    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *

    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.
    Arg1: 00000007, A driver has unlocked a page more times than it locked it
    Arg2: 0002987e, page frame number
    Arg3: 00028291, current share count
    Arg4: 00000000, 0

    Debugging Details:

    BUGCHECK_STR:  0x4E_7


    PROCESS_NAME:  System


    LAST_CONTROL_TRANSFER:  from 80865a7e to 80827ce9

    f78ca5a4 80865a7e 0000004e 00000007 0002987e nt!KeBugCheckEx+0x1b
    f78ca5d0 80836661 8851b0e8 89d953c8 8851b0e8 nt!MiDecrementReferenceCount+0x42
    f78ca6d8 80837903 e2244318 e22443a8 8851b0e8 nt!MiFlushSectionInternal+0x84d
    f78ca71c 8080f795 8851b0b0 f78ca800 00012000 nt!MmFlushSection+0x23f
    f78ca7a4 ba76fdb7 884141dc f78ca850 00012000 nt!CcFlushCache+0x1ed
    f78ca874 ba7abd93 e209d320 f93ceadd 00000013 Ntfs!LfsFlushLfcb+0x229
    f78ca8c8 ba7bc2b5 0109d320 f93ceadd 00000013 Ntfs!LfsFlushToLsnPriv+0x199
    f78ca928 ba7abea2 e209d320 000000e0 00000001 Ntfs!LfsWriteLfsRestart+0x171
    f78ca974 ba7ab92a e1364008 00000068 f78ca9cc Ntfs!LfsWriteRestartArea+0x149
    f78cabf4 ba7aab2d f78cac28 8841d7f8 00000000 Ntfs!NtfsCheckpointVolume+0x129e
    f78cad80 80880543 00000000 00000000 89d953c8 Ntfs!NtfsCheckpointAllVolumes+0xd2
    f78cadac 80949c7e 00000000 00000000 00000000 nt!ExpWorkerThread+0xeb
    f78caddc 8088e192 80880458 00000000 00000000 nt!PspSystemThreadStartup+0x2e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


    80836661 eba0            jmp     nt!MiFlushSectionInternal+0x7ef (80836603)


    SYMBOL_NAME:  nt!MiFlushSectionInternal+84d

    FOLLOWUP_NAME:  MachineOwner



    IMAGE_NAME:  memory_corruption

    FAILURE_BUCKET_ID:  0x4E_7_nt!MiFlushSectionInternal+84d

    BUCKET_ID:  0x4E_7_nt!MiFlushSectionInternal+84d

    Followup: MachineOwner

    Friday, May 3, 2013 2:34 AM

All replies

  • A STOP 0x0000004E is likely to be a problem with the memory installed in the server.

    I'm not on the WHS team, I just post a lot. :)

    Friday, May 3, 2013 10:42 AM
  • Try running Memtest86+

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Friday, May 3, 2013 12:30 PM
  • Hey guys, sorry for the delayed response--just got sidetracked.

    Not exactly sure how to run Memtest86+ on a system that has no video card.  DDR2 is pretty pricey these days so I hate to go out and buy some in the hopes that it will solve my problem.

    Friday, June 14, 2013 5:16 PM