ATTN: wangcomps

DeviousJ · 12-04-2002, 02:31 PM

Your pm box is full. Here is a link!
http://www.windows-administrator.com/stop_errors.shtml

Check out the list of error codes further down - I think it's referring to the ones in the parentheses. It's looking like a device driver though... I think atapi is for cd drives

StillBecomingApart · 12-04-2002, 02:33 PM

atapi is for cd drivers and cd burners

DeviousJ · 12-04-2002, 02:38 PM

http://negabenji.homestead.com/files/shutup.jpg

wangcomputers · 12-04-2002, 02:39 PM

Quote:

Originally posted by Graveflower

i like to prepare for every circumstance

and thanks lee.
that's pretty helpful.

i'll delete some PMs.
mr pakula, can you extend the limit plz.

wangcomputers · 12-04-2002, 02:40 PM

oh yeah, in case other people are vaguely interested in my comp problems.

http://www.piksandcrap.homestead.com/files/blue.jpg

Affect · 12-04-2002, 02:41 PM

Shit, I haven't seen a blue screen in so damn long.

StillBecomingApart · 12-04-2002, 02:42 PM

http://www.karaokeanonymous.com/nony...usuck01opt.gif

DeviousJ · 12-04-2002, 02:44 PM

I think what it's basically saying, is that the atapi.sys driver tried to reference a bit of memory it isn't allowed to, and that's why the system crashed. The D1 code is apparently usually down to bad drivers - see if you can get a more up-to-date one, or reinstall the one from the XP disk. If you get these screens a lot, with different codes and driver names, write them down and I'll see what I can find out.

(Ignore what I said about parentheses - that's just extra information about the D1 error)

wangcomputers · 12-04-2002, 02:46 PM

thanks man.
i don't think it will boot up at all now, so i guess no more photo taking for me

i'll write 'em down though.

lol @ sean.
stop using my evil powers against me.

lament · 12-04-2002, 02:48 PM

Quote:

Originally posted by DeviousJ
I think what it's basically saying, is that the atapi.sys driver tried to reference a bit of memory it isn't allowed to, and that's why the system crashed. The D1 code is apparently usually down to bad drivers - see if you can get a more up-to-date one, or reinstall the one from the XP disk. If you get these screens a lot, with different codes and driver names, write them down and I'll see what I can find out.

(Ignore what I said about parentheses - that's just extra information about the D1 error)

blue screen in XP. I don't think i've ever gotten one of those. I guess you could try popping in the xp install cd, and repairing the installation.

wangcomputers · 12-04-2002, 02:52 PM

yeah that used to work.
I'd format the hardrive and fresh install.
but then it'd crash again after a couple of days..
i just kind of think that my motherboard or processor may be damaged.

lament · 12-04-2002, 02:56 PM

Quote:

Originally posted by wangcomputers
yeah that used to work.
I'd format the hardrive and fresh install.
but then it'd crash again after a couple of days..
i just kind of think that my motherboard or processor may be damaged.

What mobo chipset are you using? I had an old VIA apollo pro board that was very blue screen prone.

12-04-2002, 02:31 PM	#1
DeviousJ CORNFROST Location: GUREITO DESU YO Posts: 24,891	ATTN: wangcomps Your pm box is full. Here is a link! http://www.windows-administrator.com/stop_errors.shtml Check out the list of error codes further down - I think it's referring to the ones in the parentheses. It's looking like a device driver though... I think atapi is for cd drives

12-04-2002, 02:33 PM	#2
StillBecomingApart I'M FROM ITALY Location: Back the tape up. I need it again! Let it roll! Just as high as the fucker can go! And when it comes to that fantastic note where the rabbit bites its own head off, I want you to THROW THAT FUCKING RADIO INTO THE TUB WITH ME! Posts: 4,355	atapi is for cd drivers and cd burners

12-04-2002, 02:38 PM	#3
DeviousJ CORNFROST Location: GUREITO DESU YO Posts: 24,891	http://negabenji.homestead.com/files/shutup.jpg

12-04-2002, 02:40 PM	#5
wangcomputers Apocalyptic Poster Location: UK Posts: 4,058	oh yeah, in case other people are vaguely interested in my comp problems. http://www.piksandcrap.homestead.com/files/blue.jpg

12-04-2002, 02:41 PM	#6
Affect Fuck Location: xxx Posts: 5,360	Shit, I haven't seen a blue screen in so damn long.

12-04-2002, 02:42 PM	#7
StillBecomingApart I'M FROM ITALY Location: Back the tape up. I need it again! Let it roll! Just as high as the fucker can go! And when it comes to that fantastic note where the rabbit bites its own head off, I want you to THROW THAT FUCKING RADIO INTO THE TUB WITH ME! Posts: 4,355	http://www.karaokeanonymous.com/nony...usuck01opt.gif

12-04-2002, 02:44 PM	#8
DeviousJ CORNFROST Location: GUREITO DESU YO Posts: 24,891	I think what it's basically saying, is that the atapi.sys driver tried to reference a bit of memory it isn't allowed to, and that's why the system crashed. The D1 code is apparently usually down to bad drivers - see if you can get a more up-to-date one, or reinstall the one from the XP disk. If you get these screens a lot, with different codes and driver names, write them down and I'll see what I can find out. (Ignore what I said about parentheses - that's just extra information about the D1 error)

12-04-2002, 02:46 PM	#9
wangcomputers Apocalyptic Poster Location: UK Posts: 4,058	thanks man. i don't think it will boot up at all now, so i guess no more photo taking for me i'll write 'em down though. lol @ sean. stop using my evil powers against me.

12-04-2002, 02:52 PM	#11
wangcomputers Apocalyptic Poster Location: UK Posts: 4,058	yeah that used to work. I'd format the hardrive and fresh install. but then it'd crash again after a couple of days.. i just kind of think that my motherboard or processor may be damaged.