Skip to main content
J
jprossbach
Participant
October 30, 2008
Question

CF admin crashes

  • October 30, 2008
  • 3 replies
  • 809 views
I think I have some corrupt site info or something that causes the CF admin to lock, even after a complete re-install.

Background:
I am taking a class and was setting up a site in FlexBuilder using supplied files.
In setting up the site, I inadvertently overlapped sites or environments or whatever.
FlexBuilder started recursively copying files into the site directory until it crashed with a BSOD.
Ever since then, the CF admin crashes with the exact same error. PAGE_FAULT_IN_NONPAGED_AREA.

I've uninstalled and re-installed ColdFusion, FlexBuilder, Java etc. and tossed every other file and directory left behind. The ColdFusion server (developer edition) runs just fine, until I go to the admin.

I keep thinking there has to be something left behind from that recursive site that is crashing the admin,
but I'm out of ideas on where to look.

Any help would be appreciated!
John
    This topic has been closed for replies.

    3 replies

    M
    MickDundee
    Participant
    November 15, 2008
    I would be checking out the memory on the computer as I have found lately that problems like this one have been caused when a chip on a memory module has gone bad. There are a number of memory checking programs around, but the one that I have found to be the easiest to you and without the OS running is to use a Ubuntu install disk and run the memory testing from it.
    Charlie Arehart
    Community Expert
    Charlie ArehartCommunity Expert
    Community Expert
    November 4, 2008
    When you do the uninstall/reinstall, do you delete the coldfusion8 directory between steps? If not, I wonder if there may be something that gets left during the uninstall that is still a remnant of the bad initial install.

    I'll say that this is not something I've ever heard of, so I'm grasping at straws. For it to get a BSOD, given your mention of it recursively creating directories, I'd wonder if perhaps some deep directory structure has been created that somehow CF is trying to read/load/process and that's when the problem happens. Or that could be red herring, but some other remnant of the previous attempt remains.
    /Charlie (troubleshooter, carehart. org)
    J
    jprossbachAuthor
    Participant
    November 6, 2008
    quote:
    Originally posted by: carehart
    When you do the uninstall/reinstall, do you delete the coldfusion8 directory between steps? If not, I wonder if there may be something that gets left during the uninstall that is still a remnant of the bad initial install.

    I'll say that this is not something I've ever heard of, so I'm grasping at straws. For it to get a BSOD, given your mention of it recursively creating directories, I'd wonder if perhaps some deep directory structure has been created that somehow CF is trying to read/load/process and that's when the problem happens. Or that could be red herring, but some other remnant of the previous attempt remains.


    I did delete the CF8 directory and was also starting to wonder if something is stored in the registry.
    I restored the registry from before the BSOD started, but no change.

    I think I'll try swapping some memory next, but that seems unlikely too, since the bsod only happens with the CF8 admin.

    Thanks for your help!
    A
    Anonymous
    November 4, 2008
    Sure your hardware is okay?
    J
    jprossbachAuthor
    Participant
    November 4, 2008
    quote:
    Originally posted by: ke4pym
    Sure your hardware is okay?


    It seems unlikely that it's a HW issue, but how can you ever be sure?
    I'd never had this issue before, and it only happens with the CF admin.
    I run plenty of other memory-intensive apps, and have never seen it before.
    It just seems too coincidental after a botched site setup.

    Maybe I can find another laptop and switch memory or something.

    Thanks for you suggestion!

    A
    Anonymous
    November 5, 2008
    quote:
    Originally posted by: jprossbach

    It seems unlikely that it's a HW issue, but how can you ever be sure?


    With a BSOD PAGE_FAULT_IN_NONPAGED_AREA, you can usually be sure its either hardware (usually system memory, then maybe video memory or a hard drive) or a broken driver or a antivirus solution going wonky. If you can catch the stop identifier that can be useful in Google searches.

    Here's a Microsoft article on it...
    http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/w2000Msgs/6093.mspx?mfr=true

    It relates to XP, Vista, 2003, etc as well.
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices