Server BSOD's

I am having fits with a Server 2003 machine that has been rebooting for over a week now. I have taken the server clear down to bare bones and reinstalled server and it's updates and still have the same problem. I would appreciate any help with this issue. Here is the dump file analysis:



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


Loading Dump File [C:\Documents and Settings\scott.williams\Desktop\New Folder\Mini041206-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: LanManNt, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_sp1_rtm.050324-1447
Kernel base = 0x80800000 PsLoadedModuleList = 0x808af988
Debug session time: Wed Apr 12 09:40:15.672 2006 (GMT-5)
System Uptime: 0 days 15:49:52.906
Loading Kernel Symbols
.............................................................................................................
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 808281c0, f78deca0, f78de99c}

Probably caused by : ntkrnlmp.exe ( nt!CmpDelayCloseWorker+d2 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 808281c0, The address that the exception occurred at
Arg3: f78deca0, Exception Record Address
Arg4: f78de99c, Context Record Address

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!CmpDelayCloseWorker+d2
808281c0 8b5808 mov ebx,[eax+0x8]

EXCEPTION_RECORD: f78deca0 -- (.exr fffffffff78deca0)
ExceptionAddress: 808281c0 (nt!CmpDelayCloseWorker+0x000000d2)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 3b8255bd
Attempt to read from address 3b8255bd

CONTEXT: f78de99c -- (.cxr fffffffff78de99c)
eax=3b8255b5 ebx=00000193 ecx=808ad280 edx=00000001 esi=8979b8d0 edi=808ad280
eip=808281c0 esp=f78ded68 ebp=f78ded80 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
nt!CmpDelayCloseWorker+0xd2:
808281c0 8b5808 mov ebx,[eax+0x8] ds:0023:3b8255bd=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx ". The memory could not be "%s ".

READ_ADDRESS: 3b8255bd

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 8083f72e to 808281c0

STACK_TEXT:
f78ded80 8083f72e 00000000 00000000 8979b8d0 nt!CmpDelayCloseWorker+0xd2
f78dedac 8092ccff 00000000 00000000 00000000 nt!ExpWorkerThread+0xeb
f78deddc 80841a96 8083f671 00000001 00000000 nt!PspSystemThreadStartup+0x2e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!CmpDelayCloseWorker+d2
808281c0 8b5808 mov ebx,[eax+0x8]

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!CmpDelayCloseWorker+d2

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42435e60

FAILURE_BUCKET_ID: 0x7E_nt!CmpDelayCloseWorker+d2

BUCKET_ID: 0x7E_nt!CmpDelayCloseWorker+d2

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

 

This looks like a hardware / memory error.

Suggestion
1. chkdsk /r
2. Re-allocate paging space
3. Reseat RAM
4. Check overheat
5. Check the PSU has adequate power supply to drive all devices including USB device.

CPC2004 any advice on this one. You are deffinately the expert on this, not me....

 

Maybe hardware problem

Hi,

The debug log is incomplete. No module list is attached. One minidump is insufficient to determine the hardware problem. As hardware problem occurs randomly, the debug reports have different symptoms and they are the signs of hardware error. Software problem always have consistent symptoms.

 

Debug Log is Incomplete

This thing is really driving me insane. Do you need me to post more of the dumps?

 

Hi,

More debug logs are definitely useful to diagnostic blue screen problem. Would you provide the output of lmnt (ie the load module list) as well.

 

lmnt

How do i do that?

I REALLY appreciate your help on this!

 

Hi,

kd command

.logopen c:\debuglog.txt
.sympath srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
.reload;!analyze -v;r;kv;lmnt;.logclose;q

 

Same problem, tried EVERYTHING

We have the same problem, with similar - or none at all - dumps.
Server just BSOD's every hour or so.
Have tried EVERYTHING I know, in the meantime back to w2k server (show MUST go on, we are on a 24/7 shop).
We got the 2003 enterprize fresh with an HP 4 CPU server, tried calling them, had 2 tech's come over and REALLY test ALL hardware, changed 3 types of memory, had MS admins come over and try, but NOTHING happened.
The **** thing just keeps rebooting after a week or so, but operates perfectly until it starts happening. I even suggested we give it Seltzer through the CD slot ( fig, level of DESPERATION ).
Please, you or ANYONE, help, since HP says, and I actually beleive when they say that harware is NOT the problem. MS should change name to BS 'cause they keep promising but don't put out, that they are "working on a solution" (inbetween frags in UT2007, I think) and we HAVE to keep our bussines running.

Thanks in advance.

Newmark

 

Hi,

The following software also causes bugcheck code 7E.

Netlimiter
Visual Insight
klif.sys (Kaspery AntiVirus)
pci.sys (compact flash)

 

Hi
thx for a swift reply

none of the above is present and/or installed on server
...

 

Attach the debug log

Hi,

Usually bugcheck code 7E is caused by software problem. Maybe it is caused by registry corruption. Do you find system event 1517? If you attach the debug log here, it will take a look to it.