Blue Screen

[Pieter Pretorius]

Hi,
I am new to this newsgroup.

I have a problem in that my computer from time to time freezes and gives
that dreaded blue screen. I thought it was my memory and changed that but it
still happens and I can't discern any pattern to the problem.

I wrote this mornings stop message down:
Stop: 0X0000008E (0XC0000005, 0XF41F12DB, 0XF7C7E078, 0X00000000)
Symevent.sys Address F41F12DB base at F41E7000
Datestamp 3f31ac37

Can somebody please help??

Regards,

 

[Will Denny]

Hi

Try the following link to MVP Jim Eshelman's web page:

"0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED"
http://aumha.org/win5/kbestop.php#0x8e

 

[Johnny_1]

The clue is there. Symevent.sys is a Symantec driver for
the Symantec Event Manager. Try their knowledge base:
http://www.symantec.com/techsupp/consumer.html?
asa=controldoa_WindowsXP
(watch the wrap)
The 8E shutdown usually refers to a bad driver:
http://aumha.org/win5/a/shtdwnxp.htm
Hope this helps,
John

[Symantec is a virus]

 

[Pieter Pretorius]

Hi,
Could this just be a memory problem? I now remember that I only replaced one
of the memories but left a 512 Mb in place. This is the first time that I
saw the Symevent message.

Pieter.

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)

The clue is there. Symevent.sys is a Symantec driver for
the Symantec Event Manager. Try their knowledge base:
http://www.symantec.com/techsupp/consumer.html?
asa=controldoa_WindowsXP
(watch the wrap)
The 8E shutdown usually refers to a bad driver:
http://aumha.org/win5/a/shtdwnxp.htm
Hope this helps,
John

[Symantec is a virus]

-----Original Message-----
Hi,
I am new to this newsgroup.

I have a problem in that my computer from time to time freezes and gives
that dreaded blue screen. I thought it was my memory and changed that but it
still happens and I can't discern any pattern to the problem.

I wrote this mornings stop message down:
Stop: 0X0000008E (0XC0000005, 0XF41F12DB, 0XF7C7E078, 0X00000000)
Symevent.sys Address F41F12DB base at F41E7000
Datestamp 3f31ac37

Can somebody please help??

Regards,

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)


.

 

[Johnny_1]

Pieter,
Read through this article:
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/ddtools/hh/ddtools/bccodes_59k7.asp
(watch the wrap)
Is the error KERNEL_MODE_EXCEPTION_NOT_HANDLED (should be
at the top of the bsod) as Will Denny suggested?
Could be memory, could be several things. Read the article
and look at each possible cause. If you added the RAM and
started to get these shortly after, try removing the new
module and see if this clears up. Just because Ram is new
does't mean it's good. Also be sure it is the correct
module for your moboard. Make sure you are grounded when
removing/installing RAM, electrostatic discharge can kill
it.
John

-----Original Message-----
Hi,
Could this just be a memory problem? I now remember that I only replaced one
of the memories but left a 512 Mb in place. This is the first time that I
saw the Symevent message.

Pieter.

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)

The clue is there. Symevent.sys is a Symantec driver for
the Symantec Event Manager. Try their knowledge base:
http://www.symantec.com/techsupp/consumer.html?
asa=controldoa_WindowsXP
(watch the wrap)
The 8E shutdown usually refers to a bad driver:
http://aumha.org/win5/a/shtdwnxp.htm
Hope this helps,
John

[Symantec is a virus]

-----Original Message-----
Hi,
I am new to this newsgroup.

I have a problem in that my computer from time to time freezes and gives
that dreaded blue screen. I thought it was my memory

and
changed that but it

still happens and I can't discern any pattern to the problem.

I wrote this mornings stop message down:
Stop: 0X0000008E (0XC0000005, 0XF41F12DB, 0XF7C7E078, 0X00000000)
Symevent.sys Address F41F12DB base at F41E7000
Datestamp 3f31ac37

Can somebody please help??

Regards,

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)


.

.

 

[Johnny_1]

Reading that article myself your exception code does point
to memory access violation:

0xC0000005: STATUS_ACCESS_VIOLATION
A memory access violation occurred.

Hope this solves it,
John

-----Original Message-----
Hi,
Could this just be a memory problem? I now remember that I only replaced one
of the memories but left a 512 Mb in place. This is the first time that I
saw the Symevent message.

Pieter.

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)

The clue is there. Symevent.sys is a Symantec driver for
the Symantec Event Manager. Try their knowledge base:
http://www.symantec.com/techsupp/consumer.html?
asa=controldoa_WindowsXP
(watch the wrap)
The 8E shutdown usually refers to a bad driver:
http://aumha.org/win5/a/shtdwnxp.htm
Hope this helps,
John

[Symantec is a virus]

-----Original Message-----
Hi,
I am new to this newsgroup.

I have a problem in that my computer from time to time freezes and gives
that dreaded blue screen. I thought it was my memory

and
changed that but it

still happens and I can't discern any pattern to the problem.

I wrote this mornings stop message down:
Stop: 0X0000008E (0XC0000005, 0XF41F12DB, 0XF7C7E078, 0X00000000)
Symevent.sys Address F41F12DB base at F41E7000
Datestamp 3f31ac37

Can somebody please help??

Regards,

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)


.

.

 

[Bruce Chambers]

Greetings --

The problem file identified, Symevent.sys, is part of a Symantec
product, most likely the Anti-virus. You might try removing and
reinstalling it, or consulting Symantec's knowledge base.

Bruce Chambers

--
Help us help you:




You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

 

[Bruce Chambers]

Greetings --

It could possibly be a memory problem, but. if it were, it
wouldn't be the same file each time you get the error.

Bruce Chambers

--
Help us help you:




You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH

Hi,
Could this just be a memory problem? I now remember that I only
replaced one
of the memories but left a 512 Mb in place. This is the first time
that I
saw the Symevent message.

Pieter.

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)

The clue is there. Symevent.sys is a Symantec driver for
the Symantec Event Manager. Try their knowledge base:
http://www.symantec.com/techsupp/consumer.html?
asa=controldoa_WindowsXP
(watch the wrap)
The 8E shutdown usually refers to a bad driver:
http://aumha.org/win5/a/shtdwnxp.htm
Hope this helps,
John

[Symantec is a virus]

-----Original Message-----
Hi,
I am new to this newsgroup.

I have a problem in that my computer from time to time freezes and gives
that dreaded blue screen. I thought it was my memory and changed that but it
still happens and I can't discern any pattern to the problem.

I wrote this mornings stop message down:
Stop: 0X0000008E (0XC0000005, 0XF41F12DB, 0XF7C7E078, 0X00000000)
Symevent.sys Address F41F12DB base at F41E7000
Datestamp 3f31ac37

Can somebody please help??

Regards,

--
Pieter Pretorius
(e-mail address removed)
(e-mail address removed)


.