Unfortunately, no. I got tied up with other projects and have requested an MS
support tech to work with me during normal business hours but haven't heard a
word back from them. Server has been humming along since last Wednesday but it
looks like it BSOD sometime during the night last night. If I ever get a
resolution I'll definitely post it up.
-- Original message --
From: David Lum [EMAIL PROTECTED]
Any update on this? Just kind of curious as to the outcome
.
Dave Lum - Systems Engineer
[EMAIL PROTECTED] - (971)-222-1025
..remember that, in the past, those who foolishly sought power by riding the
back of the tiger ended up inside - JFK
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2008 8:36 AM
To: NT System Admin Issues
Subject: RE: Trend 8.0 server hang - revisiting
No, it's been in the same spot for several years.
Poked and prodded, disconnected reconnected and flushed with air. We'll see.
Thank you .
Steve
-- Original message --
From: Miller Bonnie L. [EMAIL PROTECTED]
Any chance it was physically moved around the same time? I remember thats
when our old one started acting up, although no amount of reseating things ever
fixed it. Might help in your system thoughits probably worth a try if you
havent opened it up yet.
-Bonnie
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, June 09, 2008 8:09 AM
To: NT System Admin Issues
Subject: RE: Trend 8.0 server hang - revisiting
Ken and Michael: Pagefile is on the C drive, plenty of space on drive and
pagefile is bigger that physical RAM.
Ran hardware diagnostics last Friday and again today and after I removed the
memory on Bank 2 it all comes back good.
Came in this morning to a KERNEL_STACK_INPAGE_ERROR BSOD.
Server went out of warranty on 03/30/08. The easiest thing to do would be to
buy another server but then I won't know why or how this is happening. It bugs
the heck out of me that this thing ran for three years without a hiccup and the
moment I put Trend on it it starts coughing up hairballs. I'm going to take it
apart and re secure all connectors etc.
Thanks to all who have responded.
Steve
-- Original message --
From: Miller Bonnie L. [EMAIL PROTECTED]
SteveHave you seen this? http://support.microsoft.com/kb/228753
It defines your bugcode as 0xC185, or STATUS_IO_DEVICE_ERROR: improper
termination or defective cabling of SCSI-based devices, or two devices
attempting to use the same IRQ.
I thought this one looked familiar, and I dug back in my notes going WY
back. Found this is the code I was having back in 2001 on a Dell PE 2400
(running W2k at the time) that had a failing backplane. Everything (drives)
would just disappear and the server would dump, with no dmp file (no access to
the drives to create one, as Ken mentioned).
-Bonnie
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Saturday, 7 June 2008 3:46 AM
To: NT System Admin Issues
Subject: RE: Trend 8.0 server hang - revisiting
Thanks for the excellent input Ken and Bonnie.
I've been researching bugcheck codes and running diagnostics. Found some power
supply errors which I corrected and also had a ECC error on Bank 2 Dimm A,
first documented on 08/2006. Switched dimms around and immediately produced
multiple errors on the same bank. Removed that bank of dimms and had high hopes
that would correct the issue. BSOD 20 minutes later.Down loadingg Open Mange
now so I can attempt to clear errors and look deeper. Still no dmp files.
Plenty of room on the pagefile drive.
Not running the /3GB switch in the boot.ini.
Haven't heard a word from Trend or MS although I have open cases with them.
May try the reg hack Bonnie suggested. I have nothing to lose.
Example of screenscrees listed below. 0XF4 and 0X21A are the most common.
STOP: c21a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status
of 0X0080 (0X 0X).
The system has been shut down.
A process or thread crucial to system operation has unexpectedly exited or been
terminated. Technical Information: *** STOP: 0X00F4, (0X0003,
0X89BFD7B0, 0X89BFD914 0X8094B734)
Saw the following ONCE:
KERNEL_STACK_INPAGE_ERROR
***STOP: 0X0077 (0XC185, 0XC185, 0X, 0X008C3000)
Thanks
Steve
From:
Ken Schaefer [EMAIL PROTECTED]
If dump files are not being generated then:
a) You have an issue with mass storage controller drivers or similar
Windows could be losing access to the underlying storage. Check the Bug Check
code *on the screen*
b) You do not have sufficient page file space on your boot drive (the one
that holds your pagefile). Dump information (except minidumps) are written to
pagefile.sys. When the machine next starts up, savedump.exe copies content out
of the pagefile.sys file and into memory.dmp
Cheers
Ken
--
