Re: Windows installation problem. Help.

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: David Candy (david_at_mvps.org)
Date: 06/13/04 

Date: Sun, 13 Jun 2004 20:18:15 +1000

Faulty CDs or floppies can certainly crash XP. 

-- 
----------------------------------------------------------
http://www.smh.com.au/yoursay/2004/06/11/index.html
"Kelly" <kelly@mvps.org> wrote in message news:utBXzzSUEHA.1048@tk2msftngp13.phx.gbl...
> Hi David,
> 
> Could be so.....but had two systems in last week and was surprised to find 
> that following the process I recently noted, worked!  :o)
> 
> -- 
> All the Best,
> Kelly
> 
> Microsoft-MVP Windows® XP
> 2004 Windows MVP "Winny" Award
> 
> Troubleshooting Windows XP
> http://www.kellys-korner-xp.com
> 
> Taskbar Repair Tool Plus!
> http://www.kellys-korner-xp.com/taskbarplus!.htm
> 
> 
> "David Candy" <david@mvps.org> wrote in message 
> news:eslhdoSUEHA.1048@tk2msftngp13.phx.gbl...
> Help says it can be caused by Lexar Media USB Universal Reader (type the 
> error in help while online)
> 
> Also generally (Win 2000 Resource Kit Reference) (a fault means in the 
> context below that it needs to read from the page file - it doesn't mean 
> faulty - faults are normal and happen many times a minute - the processor 
> tries to read the memory, can't find it, generates a processor fault, 
> windows memory manager takes over, loads the memory from page file, and 
> everything goes on happily - usually)
> 
> Explanation:
> This Stop message occurs when requested data is not found in memory. The 
> system generates a fault, which normally indicates that the system looks for 
> data in the paging file. In this circumstance, however, the missing data is 
> identified as being located within an area of memory that cannot be paged 
> out to disk. The system faults, but cannot find, the data and is unable to 
> recover. Faulty hardware, a buggy system service, antivirus software, and a 
> corrupted NTFS volume can all generate this type of error.
> 
> User Action:
> This Stop message usually occurs after the installation of faulty hardware 
> or in the event of failure of installed hardware (usually related to 
> defective RAM, either main memory, L2 RAM cache, or video RAM). If hardware 
> has been added to the system recently, remove it to see if the error recurs. 
> If existing hardware has failed, remove or replace the faulty component. Run 
> hardware diagnostics supplied by the system manufacturer. For details on 
> these procedures, see the owner's manual for your computer. Another cause of 
> this Stop message is the installation of a buggy system service. Disable the 
> service and determine if this resolves the error. If so, contact the 
> manufacturer of the system service about a possible update. If the error 
> occurs during system startup, restart your computer, and press F8 at the 
> character-mode menu that displays the operating system choices. At the 
> resulting Windows 2000 Advanced Options menu, choose the Last Known Good 
> Configuration option. This option is most effective when only one driver or 
> service is added at a time. Antivirus software can also trigger this Stop 
> message. Disable the program and determine if this resolves the error. If it 
> does, contact the manufacturer of the program about a possible update. A 
> corrupted NTFS volume can also generate this Stop message. Run Chkdsk /f /r 
> to detect and repair disk errors. Restart the system before the disk scan 
> begins on a system partition. If the hard disk is SCSI, check for problems 
> between the SCSI controller and the disk. Finally, check the System Log in 
> Event Viewer for additional error messages that might help pinpoint the 
> device or driver causing the error. Disabling memory caching of the BIOS 
> might also resolve it. For more troubleshooting information about this Stop 
> message, refer to the Microsoft Knowledge Base at 
> http://support.microsoft.com/support.
> 
> 
> --------------------------------------------------------------------------------
> Send feedback to MSDN.Look here for MSDN Online resources.
> 
> -- 
> ----------------------------------------------------------
> http://www.smh.com.au/yoursay/2004/06/11/index.html
> "Andy Jackson" <djpaxo@hotmail.com> wrote in message 
> news:1be9301c45127$f7c82540$a001280a@phx.gbl...
> > Windows XP Home will crash or freeze when installing
> > devices.
> > If it crashes the following message appears,
> > PAGE_FAULT_IN_NONPAGED_AREA
> >
> > These are the system specs. on which windows is trying to
> > be installed:
> >
> > Asus P4P800-E motherboard
> > P4 3.0GHz Prescott CPU 800MHz FSB
> > 2x 512MB PC3200 RAM
> > Gainward GF FX5700 Ultra/880 256MB
> > Asus x16 DVD rom
> > Asus 52x32x52 CD-RW
> > 80GB Samsung SP0812C Serial ATA  7200rpm hard drive
> > 
> 
>

Relevant Pages

  • Re: Crashes and the Blue Screen of Death!
    ... but the most common cause is hardware failure. ... The most common cause of this is hardware memory corruption. ... are listed on the Windows 2000 Hardware Compatibility List. ... recommended that all users install them as they become available. ...
    (microsoft.public.win2000.general)
  • Re: error restarts intermittently
    ... A problem has been detected and windows has been shut down to prevent ... And text about newly installed hardware or software, ... Device manager is good. ... The system attempted to access pageable memory using a kernel process ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Windows installation problem. Help.
    ... 2004 Windows MVP "Winny" Award ... Faulty CDs or floppies can certainly crash XP. ... > tries to read the memory, can't find it, generates a processor fault, ... > This Stop message usually occurs after the installation of faulty hardware ...
    (microsoft.public.windowsxp.general)
  • Re: Windows installation problem. Help.
    ... 2004 Windows MVP "Winny" Award ... tries to read the memory, can't find it, generates a processor fault, ... This Stop message usually occurs after the installation of faulty hardware ...
    (microsoft.public.windowsxp.general)
  • Re: BAD_POOL_HEADER blue screen of death
    ... The "pool" referred to is a memory pool. ... > Also, I installed no new hardware, except for some more memory. ... >> Here is a MSDN article with regard to this error in Windows 2000. ... >> the error reporting tool will get this for you. ...
    (microsoft.public.windowsxp.perform_maintain)