Access violation

Hi,
I'm having a problem with a particular address location.
I'm using MS SQL Server 2000
I checked the server logs and I see some stack dumps now and then.
I checked the stack dumps and all of them seem to have the same problem.
* BEGIN STACK DUMP:
* 06/14/05 23:18:37 spid 0
*
* Exception Address = 258B6EF6
* Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
* Access Violation occurred reading address 77BEC370
All the stack dumps shows error reading the address 77BEC370
Is this because of a faulty memory?
DanielAccess violations are usually down to one of three things:
1) Faulty hardware
2) Buggy drivers
3) A bug in SQL Server
You would be best advised to call Microsoft Support to discover the
cause, if it's a bug in SQL Server you will get your support call refunded.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Daniel Chen wrote:
> Hi,
> I'm having a problem with a particular address location.
> I'm using MS SQL Server 2000
> I checked the server logs and I see some stack dumps now and then.
> I checked the stack dumps and all of them seem to have the same problem.
> * BEGIN STACK DUMP:
> * 06/14/05 23:18:37 spid 0
> *
> * Exception Address = 258B6EF6
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 77BEC370
> All the stack dumps shows error reading the address 77BEC370
> Is this because of a faulty memory?
> Daniel
>|||so it has nothing to do with buggy programming? As i am using the db with
ASP.
Thanks,
Daniel
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:OrotFVYcFHA.1392@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Access violations are usually down to one of three things:
> 1) Faulty hardware
> 2) Buggy drivers
> 3) A bug in SQL Server
> You would be best advised to call Microsoft Support to discover the cause,
> if it's a bug in SQL Server you will get your support call refunded.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Daniel Chen wrote:|||"Daniel Chen" <lifehalo@.yahoo.com.sg> wrote in message
news:d8orha$tli$1@.nobel.pacific.net.sg...
> so it has nothing to do with buggy programming? As i am using the db with
> ASP.
> Thanks,
> Daniel
Yes ;)
This is internal SQL Server error, the causes Mark Allsion give in previous
post|||*This time* it's not your buggy programming, but could be your buggy
drivers or faulty hardware, or MS's buggy programming. ;-)
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Daniel Chen wrote:
> so it has nothing to do with buggy programming? As i am using the db with
> ASP.
> Thanks,
> Daniel
>|||alright. thanks for your help.
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:ua59M$YcFHA.2840@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> *This time* it's not your buggy programming, but could be your buggy
> drivers or faulty hardware, or MS's buggy programming. ;-)
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Daniel Chen wrote:|||I recently had an issue similiar to this where the developers introduced a
READPAST hint into several code bases. I was getting this access violation
and Support recommended a patch (which I couldn't do because I had 36
clusters and couldn't afford to have something different on a few) or put a
clustered index instead of a non-clustered index on the table where the
READPAST hint was being used. That worked like a charm. Don't know if
that's your issue, but thought I'd mention it.
"Daniel Chen" wrote:

> Hi,
> I'm having a problem with a particular address location.
> I'm using MS SQL Server 2000
> I checked the server logs and I see some stack dumps now and then.
> I checked the stack dumps and all of them seem to have the same problem.
> * BEGIN STACK DUMP:
> * 06/14/05 23:18:37 spid 0
> *
> * Exception Address = 258B6EF6
> * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
> * Access Violation occurred reading address 77BEC370
> All the stack dumps shows error reading the address 77BEC370
> Is this because of a faulty memory?
> Daniel
>
>