BSOD Hell

[lewie49]

I had a major PC crash several weeks ago and MPC, the PC's manufacturer replaced the Intel 875P MB, the RAM (DDR SDRAM 512x2) and the CPU (P4\3.2) and the power supply. Everything seemed to be OK but, I think due to a problem with my USB HP scanner, the PC crashed again and would not boot up Tech support had me pull one of the 512 modules out and the PC did fire up and run chkdsk, with a number of repairs. Another RAM module was sent and Ramtest shows both chips to be good. My hard drives are Seagate SATA 160MB Raid 0'ed to a 320MB drive. The disks appear to be OK and I've cleaned out my swap file and let XP create a new one. The PC boots up and XP loads and seems to run normally. Here is the problem. On almost every shutdown (command or power button), as the screen shows "Windows is shutting down" I get a BSOD with a Stop 050 error. I'm not sure what the cause is, although, disabling my resident virus scanner may help (can't swear to it). I've disabled the Windows Exit sound as well. Everytime that I think I have it licked, bam, the next shutdown the same thing happens. All of my minidunp files read the same so I'm hoping that someone can give me a lead on this. One odd thing is that with the DVI port connected, the BSOD screen shows as a two sided page with small, almost illegible text. With the analogue port connected, the screen is normal. I've considered everything from uninstalling my Nvida video drivers and/or my Creative audigy drivers to pulling the video card and slipping an older PCI Nvidia card in to (gulp) reloading Xp from scratch (my licensed copy was SP1 in 2004 and I manually updgraded to SP2 long ago, so I may not be able to try a Windows Repair). Before I consider a complete reload, I want to try to be sure that I don't have either a driver issue or hardware issue that can be resolved. The video card is an AGP Nvidia GeForce 5950 Ultra. Sorry to be so long winded. Here is the minidump. Any help would be greatly appreciated.


Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini102306-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\program files\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Sun Oct 22 23:00:34.093 2006 (GMT-7)
System Uptime: 0 days 0:32:02.793
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10000050, {e559f000, 1, 805d711a, 1}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpCopyCell+72 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: e559f000, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 805d711a, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000001, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: e559f000

FAULTING_IP:
nt!CmpCopyCell+72
805d711a f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

MM_INTERNAL_CODE: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: winlogon.exe

LAST_CONTROL_TRANSFER: from 805d71f3 to 805d711a

STACK_TEXT:
baa39b78 805d71f3 00561020 00000004 e52db378 nt!CmpCopyCell+0x72
baa39bac 805d7c60 019d2008 00403080 0055ffe0 nt!CmpCopyValue+0xc0
baa39bf4 805d7d0b e29d2008 00403020 00560020 nt!CmpCopyKeyPartial+0x16f
baa39c34 805d77ed e1063000 00000400 00000007 nt!CmpCopySyncTree2+0x25a
baa39c64 8065b1d5 e29d2008 00000020 e52db378 nt!CmpCopySyncTree+0x4f
baa39c98 8065315f 00000020 000006c4 00000003 nt!CmSaveKey+0xde
baa39cbc 804dd99f e29ac3c8 000006c4 baa39d54 nt!NtSaveKey+0x78
baa39cbc 804e42bf e29ac3c8 000006c4 baa39d54 nt!KiFastCallEntry+0xfc
baa39d3c 8065312c 00000094 000006c4 806530e7 nt!ZwSaveKey+0x11
baa39d54 804dd99f 00000094 000006c4 0006f8b8 nt!NtSaveKey+0x45
baa39d54 7c90eb94 00000094 000006c4 0006f8b8 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0006f8b8 00000000 00000000 00000000 00000000 0x7c90eb94


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!CmpCopyCell+72
805d711a f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250f77

SYMBOL_NAME: nt!CmpCopyCell+72

FAILURE_BUCKET_ID: 0x50_W_nt!CmpCopyCell+72

BUCKET_ID: 0x50_W_nt!CmpCopyCell+72

Followup: MachineOwner
---------

 

[lewie49]

Quick update. I tried running the PC with only one 512MB memory module at a time with no change. The RAM appears to be good. I also pulled and reseated all of my cards, including the Nvidia AGP video card, updated the Nvidia drivers and uninstalled my antivirus program. Unfortunately, the same BSOD occurs on shutdown but it is now happening while XP is on "saving your settings". I'm getting a sinking feeling that I'm going to have to do a complete system recovery but, again, any thoughts on the debug report would be helpful.