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.

Ntfs.sys & IRQL BSOD

Discussion in 'Windows XP' started by Golfer, 2006/06/12.

  1. 2006/06/12
    Golfer

    Golfer Inactive Thread Starter

    Joined:
    2006/06/12
    Messages:
    2
    Likes Received:
    0
    Until yesterday my system was running perfectly. All of a sudden I got a BSOD and the computer restarted immediately. When trying to restart the computer, it told me that System32/Drivers/Ntfs.sys is either missing or damaged - "You can attempt to repair this file by starting windows setup using the original setup CD-ROM Select "r" at the first screen to start repair. "

    Upon putting the xp disc in, it boots to the cd, and it looks at my hardware configuration and the Windows Setup blue screen appears to tell me: "File setupdd.sys could not be loaded. The error code is 4. Setup cannot continue. Press any key to exit. "

    Nonetheless the computer worked fine after about half an hour. Until it crashed again with the same error message. After restarting the computer several times, I received the following error message:
    DRIVER_SRQL_NOT_LESS_OR_EQUAL

    Stop: 0x0000000D1 (0x64836C5E, 0x00000002, 0x00000001, OxF9815ACB)

    arp1934.sys - Address F9815ACB base at F9813000, Datestamp 00000000

    My specs are:
    Yakumo N243S1 Laptop Pentium IV 2 GHz
    Windows XP Home SP1

    Thanks for your help.
     
    Last edited: 2006/06/12
  2. 2006/06/12
    PeteC

    PeteC SuperGeek Staff

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

    Stop: 0x0000000D1 errors are caused by ....
    sourced from TROUBLESHOOTING WINDOWS STOP MESSAGES

    The driver which is noted as being the source of the problem arp1934.sys is not found on Google, which is suspicious. Are you sure that the name is correct?

    As a precaution I would check out the memory by running Windows Memory Diagnostic Tool - this runs from a floppy on boot - assuming you have a floppy drive or from a bootable CD. Full instructions on the page.
    See this MS KB article ....

    Windows XP problems with damaged or incompatible hardware from which ....
    I think the bottom line is that you have a hardware problem - which could be hard to track down in a laptop, but a key player is arp1934.sys

    If you can get the beast booted up again search for the file and if found look at it's properties and see if you can determine what it is connected with. Post your findings here.

    As arp1934.sys appears to be unknown at this stage please download HijackThis through Quicklinks in my signature and save it to a folder on your hard drive, say C:\HJT - not to the Desktop or a temporary location. When entries are fixed with HJT a backup is made to the folder from which HJT is run and this must be in a permanent location.

    Boot into Safe Mode and log onto your usual account.
    Open the folder in which you placed HJT and double click on hijackthis.exe and select Scan and save a log file - this will be saved in the fokder from which you ran HJT.

    Reboot into Normal mode and post the log here.

    All the above - if you can, of course :)
     

  3. to hide this advert.

  4. 2006/06/13
    Golfer

    Golfer Inactive Thread Starter

    Joined:
    2006/06/12
    Messages:
    2
    Likes Received:
    0
    Hi Pete,
    thanks for the advise. While at work yesterday, I kept playing around with the laptop, got it started a few times, ran HJT, etc. Got more BSODs, other error messages, pp.

    Suddenly I had the idea to check the system information, and it told me that my laptop all of a sudden only had half the RAM, it is supposed to have. So I unscrewed the bottom, checked the RAM, and realised that one block was about half a milimeter out of the snapper. Snapped it back in, and voilá, everything works now.

    I assume that the RAM was still somewhat accessible, but when it tried to write on or read from it, the half milimeter made the difference and caused the errors.

    The only problem left for my laptop is the fact, that my energy saver button stopped working. I used to almost always run the processor on 1.2 GHz, as I hardly ever needed the full 2 GHz, and it substantially prolonged the battery life. Now it constantly runs on 2 GHz, but at least the machine works again.

    Thanks again for your help.
     
  5. 2006/06/13
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    That's good news :)

    These Stop errors can be a pig to track down - good sleuthing on your part :D - ill-fitting RAM = faulty RAM as per the quote. Glad it was as simple as that.

    Re your processor speed - you may need to reload the control applet for this - take a look at the manufacturer's web site for drivers. I'm basically an AMD person and know little about Intel these days :)
     

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.