Can someone help me debug this? This machine has been going through BSOD episodes at least once a day and at some points a few times a day. Here's the resulting analysis from one of the Minidumps: 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: ffffffe8, memory referenced. Arg2: 00000001, value 0 = read operation, 1 = write operation. Arg3: 8086c93d, If non-zero, the instruction address which referenced the bad memory address. Arg4: 00000000, (reserved) Debugging Details: ------------------ Could not read faulting driver name WRITE_ADDRESS: ffffffe8 FAULTING_IP: nt!ObfDereferenceObject+23 8086c93d f00fc11e lock xadd dword ptr [esi],ebx MM_INTERNAL_CODE: 0 CUSTOMER_CRASH_COUNT: 2 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP BUGCHECK_STR: 0x50 PROCESS_NAME: Idle CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 80831862 to 80888c52 STACK_TEXT: 8089a4f4 80831862 ffdffa40 ffdff120 00000000 nt!KeAcquireQueuedSpinLockAtDpcLevel+0x22 8089a5a8 808320ab 00000000 00000000 020785ca nt!KiTimerExpiration+0xda 8089a600 8088de4f 00000000 0000000e 00000000 nt!KiRetireDpcList+0x65 8089a604 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x37 STACK_COMMAND: kb FOLLOWUP_IP: nt!KeAcquireQueuedSpinLockAtDpcLevel+22 80888c52 74ee je nt!KeAcquireQueuedSpinLockAtDpcLevel+0x12 (80888c42) SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!KeAcquireQueuedSpinLockAtDpcLevel+22 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 49c21e56 FAILURE_BUCKET_ID: 0x50_nt!KeAcquireQueuedSpinLockAtDpcLevel+22 BUCKET_ID: 0x50_nt!KeAcquireQueuedSpinLockAtDpcLevel+22 I've analyzed a few more and the results are essentially the same. Looking for some ideas on where to start. Thanks!

Also, throughout all the minidumps, ARG1 is always the same address (0xffffffe8). Server has 32GM of memory, so I guess it's probably more plausible that we have a bad memory card somewhere... ugh.

Hi, Thank you for posting here. According to your description, I understand that BSOD 0x50 was encountered on your Windows 2003 SP2 TS Server. If I have misunderstood he problem, please don't hesitate to let me know. I agree with you that we should check memory before we take more actions. Please follow the guide below to download and run Windows Memory Diagnostic. http://oca.microsoft.com/en/windiag.asp If the problem is caused by Memory hardware, please contact the vendor to replace bad memory stick. If its not caused by bad memory stick, lets try to narrow down the cause. 1. When did the issue start to occur? 2. Is there any change made on this server? Or software, hardware installed on this server? 3. If possible, please perform a parallel installation on this server. Also, to narrow down the root cause of the BSOD issue, we need to analyze the crash dump file. As it is not effective for us to debug the crash dump file here in the forum, if you want to know the root cause and the resolution, I would like to suggest that you contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request. To obtain the phone numbers for specific technology request please take a look at the web site listed below: http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607 Hope the issue will be resolved soon. Thanks. This posting is provided "AS IS" with no warranties, and confers no rights.

Unfortunately, WMD only supports up to 4GB and I need to scan 32GB. So, rather than wait around and scan 4GB at a time I'm scanning with Memtest86+. We'll see what it comes back with since it will take about all weekend to run.

Hello, This is a driver relatedissue. Usually terminal servers printer drivers are corrupted and the issue happens and more over its possible please upload the complete dump file and if possible please mention the applications and the system hardware configuration and number of users connecting to the TS.Thankshttp://technetfaqs.wordpress.com

Hi, Thank you for update. Please let us know the scan result for research and if there is anything else we can do for you. Thanks. This posting is provided "AS IS" with no warranties, and confers no rights.

Was this ever resolved? What was the resolution, if it was resolved?I'm experiencing same issue with Windows 2003 SP2 server. Same error and same BSOD message. Thanks,AU