Turns out RAM was bad.  The fix was simple, pull out a DIMM and reboot, press F10 at the Power On Self Test phase, run Memory Check, if problems were found then I shut it down again and replaced the RAM and pulled another stick and repleated.  Eventually the memory test found no problems and the RAM in hand was the bad stick. $39 for new RAM and the CPU is actually upgraded by 1GB. Now it runs as smooth as butter on a bald monkey!
One of our machines has had BSOD's since 9-15.  No known software or hardware additions or updates.  The BIOS seems to be the up-to-date version for Dimension 9200 of 2.5.3  This is one of the errors. Additionally there are repeated errors with these particular elements:           DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT           PROCESS_NAME:  svchost.exe           MODULE_NAME: nt           IMAGE_NAME:  ntfs.sys Also there are a few errors involving IMAGE_NAME: ntkrnlmp.exe.  and also Ntfs.sys.  Any ideas about this issue?         Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Helps\Desktop\Dump Files\100311-35615-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\debug_symbols*[URL] search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506Machine Name:Kernel base = 0xfffff800`02c10000 PsLoadedModuleList = 0xfffff800`02e55670Debug session time: Mon Oct  3 14:04:02.113 2011 (UTC - 5:00)System Uptime: 0 days 0:10:47.110Loading Kernel Symbols.........................................................................................................................................................Loading User SymbolsLoading unloaded module list....********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ******************************************************************************** Use !analyze -v to get detailed debugging information. BugCheck 1E, {ffffffffc0000005, fffff80002f68ac0, 0, ffffffffffffffff} Probably caused by : memory_corruption ( nt!MiPerformFixups+80 ) Followup: MachineOwner--------- 1: kd> !analyze -v********************************************************************************                                                                             **                        Bugcheck Analysis                                    **                                                                             ******************************************************************************** KMODE_EXCEPTION_NOT_HANDLED (1e)This is a very common bugcheck.  Usually the exception address pinpointsthe driver/function that caused the problem.  Always note this addressas well as the link date of the driver/image that contains this address.Arguments:Arg1: ffffffffc0000005, The exception code that was not handledArg2: fffff80002f68ac0, The address that the exception occurred atArg3: 0000000000000000, Parameter 0 of the exceptionArg4: ffffffffffffffff, Parameter 1 of the exception Debugging Details:------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!MiPerformFixups+80fffff800`02f68ac0 410fb603        movzx   eax,byte ptr [r11] EXCEPTION_PARAMETER1:  0000000000000000 EXCEPTION_PARAMETER2:  ffffffffffffffff READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebf100 ffffffffffffffff ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. BUGCHECK_STR:  0x1E_c0000005 CUSTOMER_CRASH_COUNT:  1 DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT PROCESS_NAME:  svchost.exe CURRENT_IRQL:  0 LAST_CONTROL_TRANSFER:  from fffff80002cd8588 to fffff80002c8cc40 STACK_TEXT:  fffff880`07331798 fffff800`02cd8588 : 00000000`0000001e ffffffff`c0000005 fffff800`02f68ac0 00000000`00000000 : nt!KeBugCheckExfffff880`073317a0 fffff800`02c8c2c2 : fffff880`07331f78 fffff880`02ca5000 fffff880`07332020 00000000`01400000 : nt! ?? ::FNODOBFM::`string'+0x4977dfffff880`07331e40 fffff800`02c8abca : 00000000`00000001 fffff880`02ca49f1 fffffa80`05a15000 fffff880`02ca4000 : nt!KiExceptionDispatch+0xc2fffff880`07332020 fffff800`02f68ac0 : fffff6fc`40016058 0000007f`ffffffff fffff6fc`40016528 fffffa80`01281b10 : nt!KiGeneralProtectionFault+0x10afffff880`073321b0 fffff800`02f64c37 : 00000000`00000000 00000000`00000000 00000000`00000e3e fffff8a0`11400000 : nt!MiPerformFixups+0x80fffff880`07332210 fffff800`02c6e7d2 : fffffa80`001ed2c0 00000000`00e3d400 fffffa80`01281b10 fffff8a0`113457c0 : nt!MiRelocateImagePfn+0xf7fffff880`07332270 fffff800`02f68d21 : fffffa80`03fbca60 fffff6fc`40016058 fffff8a0`00000002 00000000`00000000 : nt!MiValidateImagePages+0x362fffff880`07332320 fffff800`02f68e60 : ffffffff`ffffffff 00000000`00000001 fffff8a0`11400000 00000000`00000140 : nt!MiSwitchBaseAddress+0x61fffff880`07332350 fffff800`02f899ff : 00000000`00000004 00000000`00000080 00000000`01000000 00000000`01000000 : nt!MiRelocateImageAgain+0x100fffff880`073323a0 fffff800`02f68596 : fffff880`073325f0 fffff880`07332840 fffff880`07332698 fffff880`073325e8 : nt!MmCreateSection+0x2dffffff880`073325a0 fffff800`030e99c3 : 00000000`00000000 fffff8a0`12e23a10 00000000`00000000 00000000`00000001 : nt!NtCreateSection+0x171fffff880`07332620 fffff800`030e9f51 : 00000000`00000000 fffff8a0`12e23a10 fffffa80`04226b10 fffff880`00000060 : nt!PfpFileBuildReadSupport+0x163fffff880`07332710 fffff800`030f206e : fffff8a0`00000000 fffff8a0`00000007 fffff8a0`00000032 fffff8a0`00000000 : nt!PfpPrefetchFilesTrickle+0x121fffff880`07332810 fffff800`030f2c07 : 00000000`00000000 fffff880`07332ca0 fffff880`07332a08 fffff8a0`104b1060 : nt!PfpPrefetchRequestPerform+0x30efffff880`07332960 fffff800`030ff1de : fffff880`07332a08 00000000`00000001 fffffa80`03042ce0 00000000`00000000 : nt!PfpPrefetchRequest+0x176fffff880`073329d0 fffff800`03103a0a : 00000000`00000000 00000000`0000004f 00000000`00000000 fffffa80`0304c701 : nt!PfSetSuperfetchInformation+0x1adfffff880`07332ab0 fffff800`02c8bed3 : fffffa80`05a15060 00000000`00000000 00000000`00000001 00000000`00000001 : nt!NtSetSystemInformation+0xc8dfffff880`07332c20 00000000`77182a0a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x1300000000`00d1fa38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77182a0a STACK_COMMAND:  kb FOLLOWUP_IP: nt!MiPerformFixups+80fffff800`02f68ac0 410fb603        movzx   eax,byte ptr [r11] SYMBOL_STACK_INDEX:  4 SYMBOL_NAME:  nt!MiPerformFixups+80 FOLLOWUP_NAME:  MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP:  4e02aaa3 IMAGE_NAME:  memory_corruption FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!MiPerformFixups+80 BUCKET_ID:  X64_0x1E_c0000005_nt!MiPerformFixups+80 Followup: MachineOwner---------  
BSOD 