help windows xp
Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: help windows xp

  1. #1
    AO's MMA Fanatic! Computernerd22's Avatar
    Join Date
    Mar 2003
    Miami, FL

    help windows xp

    hello fellow members of AO. Been a while since I last posted. Anyways, I have a customers computer which is a Dell OPTIPLEX GX520 series. Running Windows xp with SP2. System has 512mb of ram. Hard drive space has over 75% free space. However, when I load into windows normally it takes me to the desktop, then within 5 seonds it brings up the B.S.O.D (Blue screen of death) then this message is displayed Page (Fault_in_nonpaged Area) (oooooA37) & (0X00000050), then it says check to see if you have the adequate disk space. From safe mode is the only option I'm able to use to log into the desktop. I have tried safe mode with networking but am not able to durf the net (I was earler though in safe mode) anyways, what has caused this issue? Also, how can I resolve the customers issue?

    Things I tried, made sure OS was up-to-date. Ran full anti virus scan using AVG in safe mode. Ran Hijack this, and got rid of all nasty things. I have pictures, music and videos that the customers can not loose but wants me to delete everything else. The only way I can get this computer to work is in safe mode, which is unacceptable for the customer. All help is greatly appreciated.

    PS also my jump drive is not being detected by the dell while in safe mode. need help asap?

  2. #2
    AOs Resident Troll
    Join Date
    Nov 2003
    Bad driver loading....

    Up to date XP = SP3 + + not SP2

    USB does not load in safemode

    Remove all drivers and make sure you have the latest versions from Dell

    How people treat you is their karma- how you react is yours-Wayne Dyer

  3. #3
    Join Date
    Aug 2004
    Few thing's you can try :

    Re-scan with some other AV. I don't trust AVG a lot. I think you can download trial of symantec or some other av and it's update files too

    Run chkdsk /r

    Try using Fixmbr comman in recovery console
    Parth Maniar,

    *Thank you GOD*

    Greater the Difficulty, SWEETER the Victory.

    Believe in yourself.

  4. #4
    Senior Member t34b4g5's Avatar
    Join Date
    Sep 2003

    Maybe hook the drive up to another PC as a "Slave" and transfer the important stuff over. then try doing a Repair Install.

    Here is a very easy walk through on how to do it.

  5. #5
    Some Assembly Required ShagDevil's Avatar
    Join Date
    Nov 2002
    New Jersey
    Sometimes it helps to get down & dirty with these Optiplex machines. I have a GX620 that's BSOD'ing once a week. The best tools I've used are the Windows Debugging Tools.
    (You'll probably have to download the Symbols package and configure the debugger to look wherever it is you downloaded the symbols to). If you don't ,your output will be all fudged up.

    This debugger will tell you what's most likely causing the BSOD. Basically, install this program. Install the symbols. Grab your minidumps from (c:\Windows\Minidump) and look for
    Probably caused by :
    towards the bottom of your output.

    Then pray it doesn't point to ntoskrnl.exe. Like mine does. That's a more general error and requires further investigating.
    The object of war is not to die for your country but to make the other bastard die for his - George Patton

  6. #6
    Senior Member
    Join Date
    Dec 2006
    Myrtle Beach, SC
    Well now, service pack 2 seems to do the job just fine. Why fix something thats not broke? However, I do agree that it is probably a driver conflict. Has the customer installed any new hardware lately?

    I do agree with mr teab4g there, as that is a very foolproof course of action to take. Usually, that is a last resort because you never really get around to figure out what caused the problem. Although it seems that what you are asking for is a quick fix, so I'd go with the latter.

  7. #7
    AO übergeek phishphreek's Avatar
    Join Date
    Jan 2002
    Did you try to start in diagnostic startup? Start --> Run --> msconfig. Choose diagnostic startup and see if you can boot the computer. If so, the problem may be with third party software and not device drivers.

    If the problem just started, check out system restore and see what's been installed lately. A new device of some sort? Otherwise, download the latest drivers for the components from dell and other manufacturers. Burn them to a CD if you can't use your flash drive. Then start updating the drivers. I prefer to uninstall the device/driver and install rather than just update the driver. Don't forget the update the BIOS if needed.

    @ShagDevil: A repair install or sfc didn't fix that problem?
    Quitmzilla is a firefox extension that gives you stats on how long you have quit smoking, how much money you\'ve saved, how much you haven\'t smoked and recent milestones. Very helpful for people who quit smoking and used to smoke at their computers... Helps out with the urges.

  8. #8
    Senior Member nihil's Avatar
    Join Date
    Jul 2003
    United Kingdom: Bridlington
    Hi there CN22, long time no see.............hope you are keeping well

    Apart from the advice given above, there is one thing I would like you to try:

    Swap out the RAM for a known good stick or at least run either the Microsoft Memory Test or MemTest86.

    0x00000A37 is a very unusual stop error code in my experience, so I think that it might be a fundamental problem that you have. 512Mb is not a lot of RAM, and you can be sure that XP in normal mode will be using pretty much all of it within a few seconds of loading. That could be when it hits the bad areas and crashes.

    The only other thing I think might vaguely be responsible is a corrupt user profile. I have known those produce some very strange error messages

    Try creating a new one and see if that produces the same errors.


  9. #9
    Some Assembly Required ShagDevil's Avatar
    Join Date
    Nov 2002
    New Jersey
    A repair install or sfc didn't fix that problem?
    Unfortunately, No. In fact, I think this computer might be a lemon. We have another GX620 that's performing fine with the exact same setup. Initially, BSOD's were being caused by a video card. Installed a new video card and started getting BSOD's with new error codes.

    This current BSOD is being caused by a INVALID_WORK_QUEUE_ITEM related to ntoskrnl.exe. I've ran SFC, Dell Crash Analysis Tool, Dell Driver Reset Tool, Updated all the drivers from Dell, MemTest86 to name a few.

    I've opened up the box, cleaned out everything, made sure all the cards were seated correctly, blah blah blah. I still think it may be video driver related but, I've uninstalled and re-installed the video drivers more than once.
    The object of war is not to die for your country but to make the other bastard die for his - George Patton

  10. #10
    Senior Member
    Join Date
    Oct 2004
    Quote Originally Posted by nihil View Post
    ... 512Mb is not a lot of RAM, and you can be sure that XP in normal mode will be using pretty much all of it within a few seconds of loading.
    Sorry to jump in - I have an old laptop, designed for Windows 98, which has 128MB RAM and it's running XP Pro SP3 quite happily! Granted, it's only in a test domain that I've set up at home. I'm amazed just how well (and quickly) it runs.

Similar Threads

  1. Windows and lack of Email and Media clients
    By gore in forum Operating Systems
    Replies: 13
    Last Post: May 29th, 2009, 05:11 PM
  2. May 06 security patches
    By mohaughn in forum Microsoft Security Discussions
    Replies: 9
    Last Post: May 13th, 2006, 10:17 PM
  3. Replies: 6
    Last Post: October 5th, 2004, 08:26 AM
  4. Windows 2003 Server Vulnerability
    By warl0ck7 in forum Microsoft Security Discussions
    Replies: 7
    Last Post: August 14th, 2003, 12:23 PM
  5. OS History and other info.
    By Remote_Access_ in forum Security Archives
    Replies: 9
    Last Post: January 12th, 2002, 02:02 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts