Re: Re:Blue Screen

From: Johnny_1 (anonymous_at_discussions.microsoft.com)
Date: 04/26/04


Date: Mon, 26 Apr 2004 04:27:48 -0700

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
>pwo@jantar.co.za
>pwo@mweb.co.za
>"Johnny_1" <anonymous@discussions.microsoft.com> wrote in
message
>news:42e201c42b72$1a7f4130$a301280a@phx.gbl...
>> 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
>> >pwo@jantar.co.za
>> >pwo@mweb.co.za
>> >
>> >
>> >.
>> >
>
>
>.
>



Relevant Pages

  • Re: memory in XP
    ... (watch the wrap...you may have to use copy and paste to get the entire link) ... Bobby ... is not a bad ram. ... > Bios and also I tested the memory. ...
    (microsoft.public.windowsxp.general)
  • Re: C# SUCKS - BIG TIME !!! (Arrrgh !!!)
    ... gave me this first link: ... Which is located at (watch for line wrap): ... You should note that this is syntax in C++ using Managed Extensions ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Scripting DC Replication
    ... 'Replicate Now', hit okay, then do the other three DC's, what a pain! ... Dim $secondary ...
    (microsoft.public.scripting.wsh)
  • Re: plenty of memory. running out anyway.
    ... > Well, it's not wraped when it gets to the nntp servers, and the ... > reply if I don't wrap. ... It's definitely not that photoshop is using 1 Gb of memory. ... using the registry during log off. ...
    (microsoft.public.windowsxp.general)
  • Re: Ongoing HD problem:
    ... read through the second link for SP3 you gave me above. ... it is "Gold" or SP1, use these instructions: ... (watch the wrap, it's a long address) ...
    (microsoft.public.windowsxp.general)