BSOD ntkrnlmp. on start up


  1. Posts : 4
    Win 7 home 64
       #1

    BSOD ntkrnlmp. on start up


    Hi, Im getting a weird BSOD on startup of my computer and I cant figure it out. Now it usually only happens on initial startup. Once I restart I almost never have another problem. Previous BSODs were solved by a reseat of my vid card and memory cards. Its seems to be some kind of power issue but frankly i cant narrow it down to either hardware or software. Anyway heres my info from "Who Crashed". Any help would be appreciated. Rich.

    On Fri 4/25/2014 7:57:26 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800DFFC388, 0xFFFFF8800DFFBBE0, 0xFFFFF8000347EF1D)
    Error: NTFS_FILE_SYSTEM
    Bug check description: This indicates a problem occurred in the NTFS file system.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Oh and one other thing. After the crash all my stored passwords in my forums are wiped out. Thanks.
      My Computer

  2.    #2

    USAF77 said:
    Hi, Im getting a weird BSOD on startup of my computer and I cant figure it out. Now it usually only happens on initial startup. Once I restart I almost never have another problem. Previous BSODs were solved by a reseat of my vid card and memory cards. Its seems to be some kind of power issue but frankly i cant narrow it down to either hardware or software. Anyway heres my info from "Who Crashed". Any help would be appreciated. Rich.

    On Fri 4/25/2014 7:57:26 PM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800DFFC388, 0xFFFFF8800DFFBBE0, 0xFFFFF8000347EF1D)
    Error: NTFS_FILE_SYSTEM
    Bug check description: This indicates a problem occurred in the NTFS file system.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Oh and one other thing. After the crash all my stored passwords in my forums are wiped out. Thanks.
    First of all I noticed that the location of your dump files is C:/Windows/memory.dmp which means you have Kernel Memory Dump selected, this type of dump file is too large and unnecessary for most analysis but sometimes we do need it.

    Please follow these instructions on how to configure dump files.

    Dump Files - Configure Windows to Create on BSOD

    Afterwards when you next get a BSOD please post it by following the Blue Screen of Death (BSOD) Posting Instructions

    Right, without any dump files we will have to go with the more general approach.

    Can you run a disk check by following these instructions.

    Disk Check

    After that please go into the elevated command prompt and type sfc /scannow
    If it finds errors please reboot then scan again, do this 3 times altogether.
    If you are confused just follow these instructions.

    SFC /SCANNOW Command - System File Checker

    Please download and run SeaTools to test if your hard drive is failing.
    Follow these instructions.

    SeaTools for DOS and Windows - How to Use
      My Computer


  3. Posts : 4
    Win 7 home 64
    Thread Starter
       #3

    I had a BSD and downloaded the collector. Attached is the zip.

    Thank you very kindly for the help.
      My Computer

  4.    #4

    Code:
    MEMORY_MANAGEMENT (1a)
        # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041284, A PTE or the working set list is corrupt.
    Arg2: 000000002ea2c001
    Arg3: 0000000000017dc6
    Arg4: fffff70001080000
    Please follow the instructions above, afterwards please run Memtest86 to see if your memory is failing.
    Run it for at least 8 passes.

    RAM - Test with Memtest86+
      My Computer


  5. Posts : 4
    Win 7 home 64
    Thread Starter
       #5

    Well I had 3 bad ones this morning. I did all best as I could understand them. I ran mem test and didnt see any problems. I did a quick disk check and there was no message after so I assumed the disk is OK. The only problem I see in device manager is under network adopters "Teredo Tunneling Pseudo-Interface" has a yellow check near it and Ive been unable to disable and/or install a new driver for it.

    Attached is my two zips. Thank you very much.
      My Computer

  6.    #6

    Can you remove the driver for it as that will be causing some issues.

    Then Windows should re-install it.
      My Computer


  7. Posts : 4
    Win 7 home 64
    Thread Starter
       #7

    I was able to remove the driver by changing a registry value. Now Im unable to reinstall it, whatever it was anyways. All thats left to do is try a repair with my install disk, I already tried a standard repair and it didnt help. If none of that helps I'll have to to a clean re-image. If that doesnt do it then I'll know its hard ware. Three things that have me confused.

    1,st, a reseat of vid card and meory modules seems to correct the problem for up to 3 weeks. usually.

    2, The crash causes all stored passwords to be wiped clean.

    3,rd a re-start right to Windows almost always stays stable and I then have no more issues. One crash, a re-start, and then Im fine. This is a new problem for me in what was a very stable system. I wish I could point to one thing that caused this but i cant which leaves me with a gut feeling its hardware related.

    Anyway could anyone look at those zips I posted and tell me if they mean anything? Thank you very much......................Rich
      My Computer

  8.    #8

    You shouldn't go messing with the registry when you don't know what you're doing, as your case shows it can do a lot of damage if you do the wrong thing.
    You should also create a registry backup in case something like that happens.
    You can run a system restore which should restore the registry.

    You also said that re-seating the GPU fixes the issue temporarily so I recommend stress testing your GPU.


    Stress test your graphics card with Furmark

    I recommend running it for around 30 minutes

       Warning

    Furmark will increase the temperature of your GPU rapidly so keep and eye on your temperatures


    Memtest86 will test your RAM

       Information

    Run Memtest86 for at least 8 passes so we get enough information to confirm that your RAM isn't failing
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:52.
Find Us