Question about Dell Dimension 4500 PC Desktop

1 Answer

Experiencing Delayed Write Failed (DWF) errors caused by complete loss of nonpaged pool of kernel memory (i.e., the entire 256 MB made available by Windows XP gets allocated, so that none is available). The memory bus has a frequency of 177 MHz (2x 177 = 354 MHz), instead of 133 MHz (2x 133 = 266 MHz). Per the Dell website, the memory bus should be 133 MHz when using a 533 MHz (4x 133 MHz = 533 MHz) front side bus CPU, which I am doing. Even though the memory bus is set to 177 MHz, the memory chip timings are set to 2-2-2-6, which is proper for 133 MHz. Can this be causing the DWF errors (and occasional "blue screen" errors)? No "blue screen" errors since I have been monitoring the nonpaged pool and reboot whenever it is close to maximum allocation of 262,144 KB (256 MB).

Posted by on

1 Answer

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    All-Star:

    An expert that got 10 achievements.

    MVP:

    An expert that got 5 achievements.

    Vice President:

    An expert whose answer got voted for 100 times.

  • Master
  • 558 Answers

Have you tried increasing the swap file on your computer?

Posted on Sep 08, 2009

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

Fix kernel dell xp


There are several different ways that kernel.dll errors can show up on your computer. Here are some of the more common ways that you might see kernel.dll errors:
  • "Kernel.dll Not Found"
  • "This application failed to start because kernel.dll was not found. Re-installing the application may fix this problem."
  • "Cannot find [PATH]\kernel.dll"
  • "The file kernel.dll is missing."
  • "Cannot start [APPLICATION]. A required component is missing: kernel.dll. Please install [APPLICATION] again."
Kernel.dll error messages might appear while using or installing certain programs, when Windows starts or shuts down, or maybe even during a Windows installation.
The context of the kernel.dll error is an important piece of information that will be helpful while solving the problem.

Cause of Kernell.dll Errors
Kernel.dll errors are caused by situations that lead to the removal or corruption of the kernel DLL file.
In some cases, kernel.dll errors could indicate a registry problem, a virus or malware issue or even a hardware failure.

How to Fix Kernel.dll Errors
Important: Do not download kernel.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of kernel.dll, it's best to obtain it from its original, legitimate source.
Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the kernel.dll error.
  1. Restore kernel.dll from the Recycle Bin. The easiest possible cause of a "missing" kernel.dll file is that you've mistakenly deleted it.
    If you suspect that you've accidentally deleted kernel.dll but you've already emptied the Recycle Bin, you may be able to recover kernel.dll with a free file recovery program.
    Important: Recovering a deleted copy of kernel.dll with a file recovery program is a smart idea only if you're confident you've deleted the file yourself and that it was working properly before you did that.
  2. Run a virus/malware scan of your entire system. Some kernel.dll errors could be related to a virus or other malware infection on your computer that has damaged the DLL file. It's even possible that the kernel.dll error you're seeing is related to a hostile program that's masquerading as the file.
  3. Use System Restore to undo recent system changes. If you suspect that the kernel.dll error was caused by a change made to an important file or configuration, a System Restore could solve the problem.
  4. Reinstall the program that uses the kernel.dll file. If the kernel.dll DLL error occurs when you use a particular program, reinstalling the program should replace the file.
    Important: Try your best to complete this step. Reinstalling the program that provides the kernel.dll file, if possible, is a likely solution to this DLL error.
  5. Update the drivers for hardware devices that might be related to kernel.dll. If, for example, you're receiving a "The file kernel.dll is missing" error when you play a 3D video game, try updating the drivers for your video card.
    Note: The kernel.dll file may or may not be related to video cards - this was just an example. The key here is to pay very close attention to the context of the error and troubleshoot accordingly.
  6. Roll back a driver to a previously installed version if kernel.dll errors began after updating a particular hardware device's driver.
  7. Run the sfc /scannow System File Checker command to replace a missing or corrupt copy of the kernel.dll file. If this DLL file is provided my Microsoft, the System File Checker tool should restore it.
  8. Install any available Windows updates. Many service packs and other patches replace or update some of the hundreds of Microsoft distributed DLL files on your computer. The kernel.dll file could be included in one of those updates.
  9. Test your memory and then test your hard drive. I've left the majority of hardware troubleshooting to the last step, but your computer's memory and hard drive are easy to test and are the most likely components that might cause kernel.dll errors as they fail.
    If the hardware fails any of your tests, replace the memory or replace the hard drive as soon as possible.
  10. Repair your installation of Windows. If the individual kernel.dll file troubleshooting advice above is unsuccessful, performing a startup repair or repair installation should restore all Windows DLL files to their working versions.
  11. Use a free registry cleaner to repair kernel.dll related issues in the registry. A free registry cleaner program may be able to help by removing invalid kernel.dll registry entries that might be causing the DLL error.
    Important: I rarely recommend the use of registry cleaners. I've included the option here as a "last resort" attempt before the destructive step coming up next.
  12. Perform a clean installation of Windows. A clean install of Windows will erase everything from the hard drive and install a fresh copy of Windows. If none of the steps above correct the kernel.dll error, this should be your next course of action.
    Important: All the information on your hard drive will be erased during a clean install. Make sure you've made the best attempt possible to fix the kernel.dll error using a troubleshooting step prior to this one.
  13. Troubleshoot for a hardware problem if any kernel.dll errors persist. After a clean install of Windows, your DLL problem can only be hardware related.
Applies To
The kernel.dll error message could apply to any program or system that might utilize the file on any of Microsoft's operating systems including Windows 8, Windows 7, Windows Vista, Windows XP, and Windows 2000.

Sep 12, 2013 | Microsoft Windows XP Professional for PC

Tip

Place Windows Kernel into RAM



It's a given that anything that runs in RAM will be faster than an item that has to access the hard drive and virtual memory. Rather than have the kernel that is the foundation of XP using the slower Paging Executive functions, use this hack to create and set the DisablePagingExecutive DWORD to a value of 1.
Edit the Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ Session Manager\Memory Management\DisablePagingExecutive to 1 to disable paging and have the kernel run in RAM (set the value to 0 to undo this hack). Exit the Registry and reboot. Perform this hack only if the system has 256 MB or more of installed RAM!

on Mar 17, 2008 | HP Pavilion a1410n (ER890AA) PC Desktop

1 Answer

How much memory can I ad to a SR1802HM computer and do I need an external hard drive to handle more memory?


Maximum allowed 4 GB* (4 x 1 GB) requires the replacement of the installed 256 MB DIMMs

*Actual available memory may be less Maximum allowed 4 GB* (4 x 1 GB) requires the replacement of the installed 256 MB DIMMs

*Actual available memory may be lessThere will be 4 slots for the memory, you can use 4 memory cards of 1 GB each meaning thereby u can use 4 GB maximum.

Sep 22, 2010 | Compaq CPQ SR1802HM PRESARIO DESKTOP...

1 Answer

I have a Fujitsu Lifebook E2010 with one 256 MB RAM module. When I try to upgrade to one (or two) 512 MB standard Kingston memory (266MHz Pc2100), the notebook won't boot, I only get 1-3-3-1 beeps which is...


Hi,

Make sure that you got the right memory module with this specs:

Memory
  • DDR266 (266 MHz) so-DIMM 200 pin
  • 2 DIMM slots; upgradable to 1 GB total memory (512 MB x 2)
or better go to this link http://support.fujitsupc.com/CS/Portal/supportsearch.do?srch=GUIDES

there's a step by step troubleshooting for memory modules. Also make sure you purchase memory module from Fujitsu or Authorized Fujitsu Dealers .

You can also find us over the web, visit us at www.fujitsu.com or for Around-the-Clock Expert Technical Support you may contact us at :
Phone Support (Direct to Service Desk)
1-800-8FUJITS (1-800-838-5487)
Available 24 hours, 7 days a week.
Consumer Sales - 1-800-FUJITSU
Corporate Sales - 1-800-831-3183
Tech Support - 1-800-8FUJITS /1-800 8385487 or 1- 888 -3854212
-ERNZ

Feb 03, 2010 | Fujitsu LIFEBOOK E2010 PC Notebook

1 Answer

How do i get rid of the KERNEL_STACK_INPAGE_ERROR on my d600? Occasionally it says UNMOUNTABLE_BOOT_VOLUME instead. Help?


This issue can occur if a requested page of kernel data could not be read from the paging file into memory, or the master boot record is infected with a virus. To further determine the possible cause, you must properly interpret the error message. If both the first and third parameters are zero, then the four parameters are defined as:
  1. 0 (zero)
  2. Page Table Entry (PTE) value at time of error
  3. 0 (zero)
  4. Address of signature on kernel stack
If either the first or the third parameter is not a zero, then the following definitions apply:
  1. Status code
  2. I/O status code
  3. Page file number
  4. Offset into page file
If this is the case, the cause of this issue may be determined from the second parameter (the I/O status code) by using the following information that is listed in a "value of second parameter" followed by "general cause" format:

0xC000000E, or STATUS_NO_SUCH_DEVICE: the drive went unavailable, possibly a bad hard drive, disk array, and/or controller card.

0xC000009A, or STATUS_INSUFFICIENT_RESOURCES: lack of nonpaged pool resources.

0xC000009C, or STATUS_DEVICE_DATA_ERROR: bad blocks on the hard disk.

0xC000009D, or STATUS_DEVICE_NOT_CONNECTED: bad cabling, non-termination, or the controller is not able to obtain access to the hard disk.

0xC000016A, or STATUS_DISK_OPERATION_FAILED: bad blocks on the hard disk.

0xC0000185, or STATUS_IO_DEVICE_ERROR: improper termination or defective cabling of SCSI-based devices, or two devices attempting to use the same IRQ.








To resolve this issue, use the appropriate method:
Boot sector virus loadTOCNode(2, 'resolution'); To determine if you have a boot sector virus, run a current virus-checking program, and if needed, disinfect your computer.
Not a boot sector virus loadTOCNode(2, 'resolution'); View the System Log in Event Viewer for additional error messages that help you determine the device that is causing the error.

Bad block. Stop 0x77 is caused by a bad block in a paging file, or a disk controller error, or in extremely rare cases it is caused when non-paged pool resources are unavailable.

If the first and second parameters are 0, then the stack signature was not found in the kernel stack. The cause of this issue is defective hardware. If the I/O status is C0000185 and the paging file is on a SCSI-based hard disk, you should verify the disk cabling and SCSI termination.

If the I/O status code is 0xC000009C or 0xC000016A, this normally indicates that the data could not be read from the disk due to a bad block.

If you can restart your computer after the error message, Autochk runs automatically and tries to map out the bad sector. If for some reason Autochk does not scan the hard disk for errors, manually start the disk scanner. If your computer is formatted with the NTFS file system, run Chkdsk /f /r on the system partition. You must restart your computer before the disk scan begins. If you cannot start your computer due to this issue, use the Command Console and run Chkdsk /r.

Defective or unreliable random access memory (RAM) is another common cause of this issue.

Verify that all the adapter cards in your computer are properly seated.

Ensure that all adapter card contacts are clean.

Disable system caching in the BIOS to see if this resolves the error.

If this does not resolve the issue, your computer mainboard may be damaged.

Oct 23, 2009 | Dell Inspiron 1150 Latitude D600 14.1 LCD...

1 Answer

Cannot install 6940 driver


this is straight from hp
64 MB RAM for basic software installation (256 MB RAM for full software installation), 200 MB available hard disk space for basic software installation (450 MB for full software installation)
unless you get another 256mb memory it would be best for you to do basic installation.
Mark

Apr 21, 2009 | HP Deskjet 6940 InkJet Printer

1 Answer

I want to install memory on a Compaq SR1503


The following list shows what your basic computer came with and approx what you
can go to. When ordering make sure you specify speed and type

Memory Installed 256 MB (1 x 256) Maximum allowed 4.0 GB* (4 X 1 GB) requires the replacement of the installed 256 MB DIMM

*Actual available memory may be less Speed supported PC2-3200 MB/sec Type 240 pin, DDR2 SDRAM

Oct 02, 2008 | Compaq Computers & Internet

1 Answer

Windows delayed write failed


Some common reasons for a delayed-write failure are:
  • 1. Problems with a device driver, especially a SCSI or RAID device driver. Some RAID device drivers are known to issue spurious "Delayed Write Failed". Most manufacturers have been alerted to this, so check to make sure the disk drivers are up-to-date.
  • 2. Cabling problems. A faulty or broken cable -- especially for an external USB or Firewire enclosure—can generate this error. It can also happen if the cable is too long, or if it is hooked up through a hub that isn't up to spec. Another possible culprit is if you have a UDMA drive that requires an 80-pin cable, and you are using a 40-pin cable.
  • 3. SCSI termination errors. This has become less likely with the advent of self-terminating SCSI hardware, but it shouldn't be counted out.
  • 4. Media errors. This is the worst possible scenario -- essentially, drive failure. If you can garner statistics on the drive via SMART (such as SMART & Simple (http://www.beyondlogic.org/solutions/smart/smart.html), you may be able to determine if there's a mechanical failure in the offing. Gibson Research's SpinRite tool (http://grc.com/) is also useful for assessing media errors, but be warned: It may take a long time to do a thorough test.
  • 5. BIOS settings on the computer are forcing faster UDMA modes than the drive controller can handle. This is unlikely, especially with newer hardware (which can support UDMA far more flexibly), but it can usually be fixed with a BIOS upgrade, or by resetting the BIOS entries for the hard drives to auto-detect settings. Devices set to UDMA Mode 6 that produce this error, for instance, might need to be set to Mode 5.
  • 6. Controller issues. I've observed that USB controllers that contend strongly with other hardware can produce this error. In systems that have both "long" and "short" PCI slots (i.e., 64-bit and 32-bit), try moving the USB controller to the long slot. Older PCI cards will not fit in such a slot.
  • 7. Memory parity issues. If the problem appears after installing new memory, the memory in question may be faulty or not of the correct type for the motherboard in question. (This may go hand-in-hand with other problems such as random lockups, too.)
  • 8. The LargeSystemCache Registry tweak and ATI video adapters. One peculiar set of circumstances that has been observed on multiple machines with ATI video adapters and more than 512MB of memory involves the LargeSystemCache Registry setting, a DWORD entry found in HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management. This setting governs the amount of memory set aside by the system for certain kernel processes. If it's set to 1 (which allegedly improves performance on systems with more than 512MB of memory), it can cause data corruption on some systems, and produce the "Delayed Write Failed" error. Try resetting it to 0 if it's been set.

Jun 27, 2008 | Computers & Internet

1 Answer

Memory card error


try formating.
but u may lose the data
also see that u format through sd utility available on sd.com

if still a issue than get free replacement by kingston as it has 5 yrs warranty

Jun 21, 2008 | Kingston flash memory card - 256 MB -...

1 Answer

AOpen AX3S


It may be possible that the memory that you are trying to use may not be completly compatible with the architecture of the motherboard, if you are using Win XP SP2 you will need a minimum of 512 Mb mem otherwise it will run slowly (especially if running norton AV or Mcafee AV)

It would be a good Idea to buy replacement memory, as the compatibility of the memory you are trying to use is in question.

Kingston memory have a "configurator" which ensures that you get the correct memory for their board, and their memory has a lifetime warranty.

http://www.kingston.com

Nov 06, 2007 | AOpen AX3S (91.87A10.001) Motherboard

Not finding what you are looking for?
Dell Dimension 4500 PC Desktop Logo

177 people viewed this question

Ask a Question

Usually answered in minutes!

Top Dell Computers & Internet Experts

Les Dickinson
Les Dickinson

Level 3 Expert

18391 Answers

Doctor PC
Doctor PC

Level 3 Expert

7733 Answers

mukhtar21 shaikh
mukhtar21 shaikh

Level 3 Expert

2017 Answers

Are you a Dell Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...