Share via

symevent.sys Bugcheck code: 0x4E Regular BSOD PFN_LIST_CORRUPT

Anonymous
2010-06-21T16:46:15+00:00

Several times each week my windows 7 fails and restarts.  The problem most often results from:

On Mon 6/21/2010 7:09:19 AM your computer crashed

This was likely caused by the following module: symevent.sys

Bugcheck code: 0x4E (0x99, 0x351B0, 0x3, 0x456D8)

Error: PFN_LIST_CORRUPT

Dump file: C:\Windows\Minidump\062110-34491-01.dmp

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

Periodically, however, there are other causes:

This was likely caused by the following module:symevent.sys

Bugcheck code: 0x1A (0x403, 0xC0049010, 0x2411F867, 0xC001CEB8)

Error: MEMORY_MANAGEMENT

Dump file: C:\Windows\Minidump\061910-33555-01.dmp

file path: C:\Windows\system32\drivers\symevent.sys

product: SYMEVENT

company: Symantec Corporation

description: Symantec Event Library

And sometimes other modules:

On Sat 5/22/2010 8:19:39 AM your computer crashed

This was likely caused by the following module: ntkrnlpa.exe

Bugcheck code: 0x1A (0x41201, 0xC002E050, 0x396D3825, 0xB3098E78)

Error: MEMORY_MANAGEMENT

Dump file: C:\Windows\Minidump\052210-18501-01.dmp

file path: C:\Windows\system32\ntkrnlpa.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit may be another driver on your system which cannot be identified at this time.

Any help will be much appreciated.

Thanks,

Rosscons

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2010-06-21T18:41:51+00:00

    The bugcheck types you are getting suggest you are experiencing memory corruption.  This could be faulty hardware such as RAM, or faulty/incompatible drivers.  The Symantec software may simply be "triggering" the detection of corruption that has already taken place, and may in and of itself be innocent in the crash.

    When did the behavior start? Did you recently add or remove any hardware or software?

    Start here: Can you upload the contents of c:\windows\minidump to**SkyDrive**and provide a link?

    Consider the following general guidance for dealing bluescreens.  

    Consider running chkdsk on all partitions.  Let chkdsk complete on each partition and see if that helps.

    Also consider running SFC /SCANNOW.

    If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?

    Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test.  Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules.

    Other common suggestions include ensuring drivers are up to date, as well as ensuring that you're using the latest BIOS. 

    It can be helpful to use Driver Verifier.  To enable Driver Verifier... start->verifier.exe->OK->Create standard settings->Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog.

    Then, reboot and use the system as you normally would, and wait for a problem.  In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.

    Wait for a bugcheck to occur after enabling verifier as described, and then upload the dump to your SkyDrive, and provide a link.

    0 comments