[AccessD] How to troubleshoot a blue screen

That's good news John. 

I tend to prefer hard down equipment to flaky equipment as problems are
easier to resolve. Will the problems cost much to fix and can everything run
in the interim?

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Monday, June 18, 2012 6:53 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] How to troubleshoot a blue screen

Well, I got a blue screen today and when I went downstairs to look at the
server, an SSD had failed. 
  I could not even detect it nor get past the bios where it was trying to
detect SATA ports.  This 
box is stuffed with drives so I started with the SSDs (the most likely
culprit) disconnecting all 4 
(I could now boot) and then one at a time until I found the one drive.

John W. Colby
Colby Consulting

Reality is what refuses to go away
when you do not believe in it


On 6/16/2012 10:53 AM, jwcolby wrote:
> My SQL Server blue screens about once a month or so.  It does not appear
to be heat related, or at
> least CPU heat related as I have top flight HSFs which hold the temps
below 35 C.  The temps in the
> case stay around that temperature or below.  The blue screens appear to be
SQL Server related, as
> they seem to be triggered by my doing something in SSMS.  This last time I
started an update query
> and it immediately blue screened, by which I mean I clicked start (the
query) and the blue screen
> occurred.
>
> This is an AMD dual cpu server, both CPUs populated.  32 gigs ECC RAM on
each side.  Being a server
> there is no overclocking.  There is a lot going on hardware wise however.
I use an Areca 16 port
> RAID controller, RAID 6 arrays built from 1 tb WD black drives.  I am
using SSDs to create a Raid1
> array hosting several of my Read Mostly databases.  The specific update
that caused the blue screen
> was not on SSD however, it was on the Areca rotating media raid 6.
>
> I am at a loss on how to troubleshoot.  It "feels" like it must be a
memory problem, and yet the
> memory is ECC.  Perhaps I have a bad DIMM which just flakes out.
>


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com