lto:[EMAIL PROTECTED] On Behalf Of John DeCarlo
Sent: Saturday, June 23, 2007 3:00 PM
To: COMPUTERGUYS-L@LISTSERV.AOL.COM
Subject: Re: [CGUYS] blue screen
On 6/23/07, Tony B <[EMAIL PROTECTED]> wrote:
>
> This has not been my experience since migrating to the NT kernel. I
> can&
Well, that qualifies.
If you haven't blue screened yet today, assuming you are using it at your
usual workload and running the same apps, then the tech probably cleared up
the problem during troubleshooting. It would be unusual for a BSOD to
"cure" itself with no other intervention.
> -Origi
it happened 6-8 times in 2 days (most in 1 day) with same stop code.
today is still clean!!! :()
Jeff Wright wrote:
Many BSODs are one-time events. I wouldn't worry about it unless it happens
frequently and with the same STOP code.
-Original Message-
very very weird.
has stopped!!!
Many BSODs are one-time events. I wouldn't worry about it unless it happens
frequently and with the same STOP code.
> -Original Message-
> very very weird.
> has stopped!!!
>
> a computer tech & I spent a time trying to figure out & couldn't.
> today has been clean so far!
M
To: COMPUTERGUYS-L@LISTSERV.AOL.COM
Subject: [CGUYS] blue screen
ok, I've never paid too much attention to this..tell me
what it means!?!!??
* ==> QUICK LIST-COMMAND REFERENCE - Put the follow
r Guys Announcements and Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Judy Cosler
Sent: Saturday, June 23, 2007 8:44 AM
To: COMPUTERGUYS-L@LISTSERV.AOL.COM
Subject: [CGUYS] blue screen
ok, I've never paid too much attentio
e
Purcellville, VA
-Original Message-
From: Computer Guys Announcements and Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Judy Cosler
Sent: Saturday, June 23, 2007 8:44 AM
To: COMPUTERGUYS-L@LISTSERV.AOL.COM
Subject: [CGUYS] blue screen
ok, I've never paid too much at
On 6/23/07, Tony B <[EMAIL PROTECTED]> wrote:
This has not been my experience since migrating to the NT kernel. I
can't recall *ever* seeing an application cause a blue screen in
either WinXP or Win2k.
OTOH, the last time I had BSODs, they were because of a Cisco VPN service
running. An upgr
This has not been my experience since migrating to the NT kernel. I
can't recall *ever* seeing an application cause a blue screen in
either WinXP or Win2k.
Again, from personal experience, I almost always trace Stop errors
back to hardware problems. Bad RAM, motherboard, disk drive, take your
pic
ok, I've never paid too much attention to this..tell me what
it means!?!!??
It means, at least in Windows, that the operating system has
terminated function. That is, the OS has crashed. This can
happen for two reasons, hardware failure (unlikely) or in most
cases, software failu
It usually means some sort of hardware failure. But can also be a
driver failure. Or just about anything.
Try http://aumha.org/a/stop.htm for some help with your specific
error. Good Luck.
On 6/23/07, Judy Cosler <[EMAIL PROTECTED]> wrote:
ok, I've never paid too much attention to this..
ok, I've never paid too much attention to this..tell me what
it means!?!!??
* ==> QUICK LIST-COMMAND REFERENCE - Put the following commands in <==
* ==> the body of an email & send 'em to: [EMAIL PROTECTED] <=
12 matches
Mail list logo
