UNHANDLED ACCESS VIOLATION c0000005
sarge
items>restart the computer
also check out windowsupdate.microsoft.com and make sure you got all the
latest.... scandisk and defrag help too, alas, you can always reinstall
windows just be sure to reinstall directx 7.0a if you do
"Anthony Cooke" <anthon...@voyager.net> wrote in message
news:39810e13$0$48163$2c3e...@news.voyager.net...
> @!Q%$!!, Ack!
> Ok people... here we go. 50% rant, 50% troubleshooting.
> Are we on our own here? WTF...
> Diablo 2 Server Error
> "Unhandled Eception, Access Violation c000005"
> What does that EVEN MEAN! Ack!
> Yes Blizzard, I have done as your web site says.
> ***********************
> Sys configuration is as follows:
> AMD K6 2 450Mhz (yeah, it aint a Vette, but she runs hard)
> 160MB RAM
> 350MB flat swap file
> FIC PA - 2013 (tried to update my BIOS, killed it, had to swap out BIOS
> chips)
> V770 (that's a TNT2, 32 MB) Running Beta Detonator 5.32 (crashed with Beta
> 5.30, and currently released Detonators)
> SoundBlaster Live! (Tried it with new Liveware and 3.0 Reference drivers.
> Maxtor 15GB, 7200RPM, 2MB buffer
> 48x Creative CDROM
> Patch 1.2 from our *homies* at Blizzard
> ***********************
> I've:
> Reinstalled
> Uninstalled/defrag/reinstall/patch
> Updated video/sound
> Set Swap file, defragged again.
> Yelled at my system (yeah, that hurts)
> Emailed Bliz., laughed.
> Done all above again.
> Uninstalled sound car/moved to a different slot/reinstalled sound.
> Pulled some hair out.
> Thought "wow, I bet this is a cool game"
> Read these here news groups.
> Quit
> ************************
>
> So, you know, I seen a lot of people havin problems with nVidia stuff, and
> SB sometimes too.
> Whats up people... any worth while fixes? 'Cause I am getting REAL sick of
> reinstalling.
> Only reply if you HAVE HAD THIS EXACT problem (the error above).
> Even if you haven't fixed it, but have the error, POST IT LIKE 3M!
>
> -Tony
>
>
Anthony Cooke
Tim Morrow
news:39810e13$0$48163$2c3e...@news.voyager.net...
I had the same problem - exactly the same access violation spit out from the
diablo II server. When playing the game I also got system hangs (it
automatically rebooted on me) or blue screens (unhandled exceptions). However
my hardware is different than yours so what follows may not apply to you.
I have a PII 450, NVidia RIVA TNT, 128 Mb ram + other stuff. I'm running Win
98.
As per Blizzards documentation I installed the latest Detonator video drivers
so I could enjoy the 3D accelerated features offered by Diablo II. What I got
what a world of access violation pain...
I mistakenly installed the detonator driver straight over the top of my
existing drivers. As was later pointed out to me, this a classic no-no.
After of week of access violations (around 3 crashes per night) I did the
proper installation of the new detonator drivers by first selecting stock
standard generic VGA drivers and rebooting, then installing the detonator
drivers and rebooting again. My access violation problems went away
immediately.
Sadly in the wonderful world of Windows there are several causes of access
violations so the above may not work for you. Good luck!
Tim
Purple
yours. I find that a shutting down, switch-flip, and then try again
usually works.
--
Purple
http://bounce.to/purple - go there. NOW.
http://www.angelfire.com/md/PurpleDragon2/Guild.htm -- the Politically
Incorrect Diablo guild
/7 Come with me, I'll take you there, to land of make-believe /7
CyberSurfer
Doesn't work.
I've been trying to crack this nut. Tried reinstalling OS, Running without
sound card installed. Installing only Diablo II & Win98. Did all the driver
& OS updates. Reset bios to default and tried all switches. Tried msconfig.
Still getting Unhandled access.
When I figure this out I'll send Blizzard the bill.
"sarge" <eliminatespa...@nwinfo.net.eliminatespam> wrote in message
news:3981e47c$1...@huge.aa.net...
> start button>run>msconfig>un check box next to load startup group
> items>restart the computer
>
> also check out windowsupdate.microsoft.com and make sure you got all the
> latest.... scandisk and defrag help too, alas, you can always reinstall
> windows just be sure to reinstall directx 7.0a if you do
>
sarge
is, or memory has gone BAD which means replace, just have it tested, or your
diablo 2 cd is bad...
"CyberSurfer" <cyber...@attglobal.net> wrote in message
news:39839...@news1.prserv.net...
fuadr...@my-deja.com
--
I too have had this dumb problem. At first I would just restart the
computer and the game would work okay after about three atempts. Now I
can't get past a level in act 1. The error makes reference to a
directory in the c drive. Of course my game is installed in the d
drive. I have tried everything blizzard recomends, but nothing improves
the situation. And by the looks of Blizzard's tech support page, it
doesn't look like they know what the problem is: the ole "make sure you
have the latest drivers, defrag and scandisk, and the most famous
reinstall it." We all know to try this and other ridiculous time
consuming methods, all in hope to have fun???
I have seen a lot of the same problem with AMD and SoundBlaster live
users, but the problem is not isolated there. I guess I wait passivly
for the next version.
I use an
AMD K6-2 400mhz
192MB RAM
Sound Blaster Live value
ATI Rage Fury 32MB AGP
Win 98
FIC VIA 503+ motherboard with an Appolo chipset
Sent via Deja.com http://www.deja.com/
Before you buy.
Donald Hutchings
As a refresher, here is my stuff:
K6-3 450
320MG PC100
Matrox G400 and Voodoo2
SBLive
WinME and Win2K
Dx7.1 and 7a
Latest released drivers for all.
At first I thought that the problem might be limited to Win2K so I installed
it under WinME: no change.
Then, I tried switching from D3D on the G400 to Glide on the Voodoo2. This
changed me from constant errors, to maybe once and hour.
Then, I switched to Dx mode on the G400. This was about the same as the
Voodoo2.
Then, I downloaded and installed the latest beta driver for the G400 as well
as flashing the latest bios. I have not had the error since in Dx, but I
still get it in D3D. Still, I am content with were I am now.
Good Luck
"CyberSurfer" <cyber...@attglobal.net> wrote in message
news:39839...@news1.prserv.net...
> Sorry Sarge tried that one . . .
> Doesn't work.
> I've been trying to crack this nut. Tried reinstalling OS, Running
without
> sound card installed. Installing only Diablo II & Win98. Did all the
driver
> & OS updates. Reset bios to default and tried all switches. Tried
msconfig.
> Still getting Unhandled access.
> When I figure this out I'll send Blizzard the bill.
>
> "sarge" <eliminatespa...@nwinfo.net.eliminatespam> wrote in
message
> news:3981e47c$1...@huge.aa.net...
> > start button>run>msconfig>un check box next to load startup group
> > items>restart the computer
> >
> > also check out windowsupdate.microsoft.com and make sure you got all the
> > latest.... scandisk and defrag help too, alas, you can always reinstall
> > windows just be sure to reinstall directx 7.0a if you do
> >
> > "Anthony Cooke" <anthon...@voyager.net> wrote in message
> > news:39810e13$0$48163$2c3e...@news.voyager.net...
Linepithema humile
clue you. Mine does that when I exit the game. :(
> -Tony
--
"We are closer to the ants than to butterflies. Very few people can
endure much leisure." --Gerald Brenan
--
If you are replying to Ant's news post by e-mail, please kindly remove
ANT in one of the return e-mail address listed below. Note: CaSe!!
----------------------------------------------------------------------
/\___/\ Ant from The Keep.
/ /\ /\ \ E-Mail: phi...@earthlink.netANT, phi...@apu.eduANT,
| |. .| | or harves...@hotmail.comANT
\ _ / The Ant Farm: http://antfarm.home.dhs.org
( ) ICQ UIN: 2223658
Linepithema humile
And no, I don't overclock.
> I had the same problem - exactly the same access violation spit out from the
> diablo II server. When playing the game I also got system hangs (it
> automatically rebooted on me) or blue screens (unhandled exceptions). However
> my hardware is different than yours so what follows may not apply to you.
> I have a PII 450, NVidia RIVA TNT, 128 Mb ram + other stuff. I'm running Win
> 98.
> As per Blizzards documentation I installed the latest Detonator video drivers
> so I could enjoy the 3D accelerated features offered by Diablo II. What I got
> what a world of access violation pain...
> I mistakenly installed the detonator driver straight over the top of my
> existing drivers. As was later pointed out to me, this a classic no-no.
> After of week of access violations (around 3 crashes per night) I did the
> proper installation of the new detonator drivers by first selecting stock
> standard generic VGA drivers and rebooting, then installing the detonator
> drivers and rebooting again. My access violation problems went away
> immediately.
> Sadly in the wonderful world of Windows there are several causes of access
> violations so the above may not work for you. Good luck!
Quartz
check on 1.03 :)
"Linepithema humile" <a...@accuser37.apu.edu> wrote in message
news:elCn5.2075$Nz4....@newsread1.prod.itd.earthlink.net...
> Anthony, did you view the d2* debug logs yet? Maybe they will
> clue you. Mine does that when I exit the game. :(
>
>
> Anthony Cooke <anthon...@voyager.net> wrote:
Linepithema humile
> I get this same error when I try to cheat and the character fails the sanity
> check on 1.03 :)
Hmm, I haven't used any cheats yet. Unless my game got corrupted
during the crashes I had in the past?