We're back to nVidia and Memory Corruption.

Have you tried running in Safe Mode?

Try booting into Safe Mode options:

After the power-on and BIOS POST or your Logo screen repeatedly tap the F8 key or hold the Ctrl key before Windows starts.

This will not load your graphics drivers so may be a test in that area. If you crash in Safe Mode we can discount many driver issues and start to blame hardware.

I know you asked about a new Graphics Card. I use ATI cards in general. The specific card depends on what you do with the computer. The high end cards are for Gamers or Video editors.

http://www.ati.com/

Originally Posted by jephree

BugCheck 1000008E, {c0000005, 804e7001, b82f20ab, 0}

Probably caused by : avg7rsxp.sys ( avg7rsxp+181b )

I suppose a good thing is that all theses dumps are so similar as to suggest one definite problem.

AVG appears to be the current trigger.

Hi Jephree
At 10:15 PM as I was finishing posting to you again did get the dump.
Send to MS and their response was
Hardware failure: replace failed component

Thank you for submitting an error report.

Problem description

The error was caused by an unrecoverable hardware error which forced the operating system to stop functioning.

Although we know the problem is caused by a hardware component, unfortunately the error report does not contain enough information to tell us the specific component. More than likely the problem is being caused by problems with one or more of the following computer components:

Random Access Memory (RAM)
System board
Central Processing Unit (CPU)
Power supply
Recommendations

If you have received this error more than once, it could indicate a serious problem with your computer. We recommend that you do the following:

I am attaching both dumps again this time big dump is only 108 meg.
Thanks Walter

I would suggest running in Safe Mode just to see if it still crashes.

Perhaps switch to your other stick of RAM.

You can get a PSU tester such as:

http://www.google.com/search?sourcei...n&q=psu+tester

Just additional thoughts:

Power Supply failures can often display strange behaviors.

A motherboard or CPU or even RAM failure often result in no start up at all.

With RAM the most problems would be mis-matched modules but again the result would be in no start.

Your Graphics Card is also a source of RAM (as it has it's own). Therefore Memory Corruption could be found there as well.

Originally Posted by jephree

Just additional thoughts:

Power Supply failures can often display strange behaviors.

A motherboard or CPU or even RAM failure often result in no start up at all.

With RAM the most problems would be mis-matched modules but again the result would be in no start.

Your Graphics Card is also a source of RAM (as it has it's own). Therefore Memory Corruption could be found there as well.

Hi Jephree
I am using again single memory stick(original that came with the system)
Going to get tester. Had 3 BSD yesterday. created 4 dumps. posting 3 of them . number 4 to big to generate was 167 meg. All 3 times it was in normal mode(NOT IN SAVE).
Thanks Walter

Walter,

At this point I would be almost certain that this is a hardware problem.

All similarities point to your RAM. Here is a quote from another board addressing dumps very similar to yours:

This is hardware problem. IP_Misaligned (Instruction Misaligned) is usually caused by faulty memory.

Suggestion:

1. Check the temperature of the CPU and make sure that it is not overheat (ie temperature < 60C)
2. Reseat the memory stick to another memory slot
3. Downclock the ram
4. Clean the dust inside the computer case
5. Make sure that the ram is compatible to the motherboard

If it still crashes, diagnostic which memory stick is faulty:

1. Take out one memory stick. If windows does not crash, the removed memory stick is faulty.
2. If you have only one memory stick, replace the ram

It is also very possible that MemTest could have missed this issue. It might be worth it to try the other stick and try both slots. Also cleaning the slots with alcohol might help.

You can download the old (free) version of Everest Home here: http://www.oldversion.com/ (under utilities).

In Everest click on Computer then Sensor. This should give you your CPU temperature.


Is this your motherboard?

http://h10025.www1.hp.com/ewfrf/wc/d...name=c00006476

If so I would go to the on-board VGA with your monitor and remove the Graphics Card. Make sure that the on-board VGA is enabled in the BIOS first.

This can test your graphics card in the equation.

If it still crashes I'd keep experimenting with the RAM and check your CPU temperature.

Originally Posted by jephree

Walter,

At this point I would be almost certain that this is a hardware problem.

All similarities point to your RAM. Here is a quote from another board addressing dumps very similar to yours:



It is also very possible that MemTest could have missed this issue. It might be worth it to try the other stick and try both slots. Also cleaning the slots with alcohol might help.

You can download the old (free) version of Everest Home here: http://www.oldversion.com/ (under utilities).

In Everest click on Computer then Sensor. This should give you your CPU temperature.


Is this your motherboard?

http://h10025.www1.hp.com/ewfrf/wc/d...name=c00006476

If so I would go to the on-board VGA with your monitor and remove the Graphics Card. Make sure that the on-board VGA is enabled in the BIOS first.

This can test your graphics card in the equation.

If it still crashes I'd keep experimenting with the RAM and check your CPU temperature.

Hi Jephree
Sorry about not responding for a week. took a little vacation. Came back yeasterday. took care of all emails on the system. Had Everest that only shows sensor for HD at 42C. While back loaded Evido spyware. Trail period expired so did uninstall and restarted the pc. Came back with BSD. tried again . proceeded at that point to try all options. Normal start, last known configuration, safe safe with networking and save with command prompt. All ended with BSD. copied info after Save with prompt. last line was AGP440.sys(video). right after that BSD message was STop 0X00000024(0x00190203, 0x86137f848, 0xc0000102, 0x00000000)
System is setup that I can boot to normal windows or recovery console. Booted to recovery console. Ran chkdsk on all 3 drives. clean. Did switch to all drives and did DIR to check if I can see them. All ok. Loaded floppy with memtest ran that. came out clean(2 passes). At that point it was 11 PM. started HP's PCDoctor tests Those took 4 hours. Only 2 flaggs were on 2 SCSI drives that it failed SMART test(which is correct since 336950n drives are not smart). Atempted to boot to recovery console again to run some other tests. BSD at that point stop with 0x00000024(0x001901ff, 0x866f1ab0, 0xc0000102, 0x00000000). did go into bios at that point hardware monitoring is showing that CPU temp is in 61-63C or 142-143F.
Thanks Walter

61°-63°C at a BIOS level is quite hot. I would expect to see CPU temps in the 60's only under a heavy load: (greater than 70% CPU usage).

Whereas not critical (70°C's would be) I would think it worth cleaning and changing the thermal compound between the heat sink and CPU. Also clean and oil the fan.

In this link look at Arctic Silver as well as ArctiClean (just for example):

http://www.arcticsilver.com/instructions.htm

Originally Posted by jephree

61°-63°C at a BIOS level is quite hot. I would expect to see CPU temps in the 60's only under a heavy load: (greater than 70% CPU usage).

Whereas not critical (70°C's would be) I would think it worth cleaning and changing the thermal compound between the heat sink and CPU. Also clean and oil the fan.

In this link look at Arctic Silver as well as ArctiClean (just for example):

http://www.arcticsilver.com/instructions.htm

Hi Japhree
thanks for answer. will get arcticsilver tomorrow.
as for BSD how do I force system to get to due anything since going into save mode, normal windows, last good restart or recovery console give me same blue screen with 0x00000024.
using hp's pc doctor it inflates to virtual drive and will perform all tests shows correct drives memory and so on.
using hitatchi/ibm utility it scans and tests all 3 drives. bios is showing 3 drives.
do i go and reload from scratch using hp's save restore from day 1 and apply all ms fixes and load all programs? This is going on asumption that there is no big hardware issue. This would be last resort since I do not want to lose all the data on system.
Thanks Walter

Stop 0x00000024 or NTFS_FILE_SYSTEM
The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Possible Resolutions:

Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System log or Autochk in the Application log.
Verify that the tools you use to continually monitor your system, such as virus scanners, backup programs, or disk defragmenters are compatible with Windows XP. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests.
To test hard disk or volume integrity

Method 1:

In the Run dialog box, in the Open box type:
cmd

Start the Chkdsk tool, which detects and attempts to resolve file system structural corruption. At the command prompt type:
chkdsk drive: /f

Method 2:

Double-click My Computer, and then select the hard disk you want to check.
On the File menu, click Properties.
Click the Tools tab.
In the Error-checking box, click Check Now.
In Check disk options, select the Scan for and attempt recovery of bad sectors check box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk error checking until the next time you restart your computer. After you restart, disk error checking runs and the volume chosen is not available to run other tasks during this process. If you cannot restart the computer due to the error, use safe mode or Recovery Console.

If you are not using the NTFS file system, and the system partition is formatted with the file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be lost if hard disk tools are started from an MS-DOS command prompt. A command prompt appears when using a startup floppy disk or when using the command prompt startup option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft® Windows® 95 OEM Service Release 2 (OSR2), Microsoft® Windows® 98, or Microsoft® Windows® Millennium Edition (Me) installed. Do not use tools meant for other operating systems on Windows XP partitions!

Nonpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.
Microsoft KB articles:

Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
http://support.microsoft.com/default...;en-us;Q228888
STOP 0x23 (or STOP 0x24) When restarting PC after installing PC-Magic Encrypted Magic Folders
http://support.microsoft.com/default...;en-us;Q312582

http://www.updatexp.com/stop-messages.html


That being said: from the recovery console try FIXBOOT