Results 1 to 5 of 5

  1. #1
    cs7
    Guest

    Default symevent64x86.sys causing crash?

    A Win8 machine my 8 year old son uses exclusively to play Minecraft and poke around on learning Python has been crashing a lot. I updated its BIOS and ran WhoCrashed, which points to the modules in different minidumps - most often ntoskrnl.exe, but also dxgmms1.sys, win32k.sys, tcpip.sys, volmgr.sys. At the end of the report it suggests I see if there is an update for the driver symevent64x86.sys, but I uninstalled Symantec EndPoint protection early on in trying to figure out what was causing the crashes and that file doesn't seem to exist on the computer. Does anyone have a suggestion, please?

    Below are various bug reports. They all boil down to a driver is bad but which one is unknown.


    Bug check description: This indicates that the page frame number (PFN) list is corrupted.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time

    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

    Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

  2. #2
    Senior Member TechnoMage's Avatar
    Join Date
    Mar 2012
    Location
    Central Florida, USA
    Posts
    2,017

    Default Re: symevent64x86.sys causing crash?

    What you don't, or Won't say, speaks volumes.

    What is the Security Software that you're using on your PC?

    TM
    A man with experience is never at the mercy of a man with an argument.
    Backup! Backup! Backup! Ghost rocks!

  3. Windows 8 Forums Ads
    Join Date
    Mar 2012
    Posts
    1,222

  4. #3
    cs7
    Guest

    Default Re: symevent64x86.sys causing crash?

    Windows Defender.

  5. #4
    Senior Member TechnoMage's Avatar
    Join Date
    Mar 2012
    Location
    Central Florida, USA
    Posts
    2,017

    Default Re: symevent64x86.sys causing crash?

    and NOT Norton?
    A man with experience is never at the mercy of a man with an argument.
    Backup! Backup! Backup! Ghost rocks!

  6. #5
    cs7
    Guest

    Default Re: symevent64x86.sys causing crash?

    Correct, Norton is not on the machine.

Thread: symevent64x86.sys causing crash? - Windows 8

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Featured Pages:    Windows 8 | Windows 8 Forum | Windows 8 Install | Windows 8 Error | Windows 8 Download | Windows 8 System Requirements | Windows 8 Themes | Windows 8 Key | Windows 8 Drivers| Windows 8 Security | Windows 8 Hardware | Windows 8 Networking | Windows 8 Performance | Windows 8 Sound | Windows 8 Software | Windows 8 Tutorials | Windows 8 Virtualization Virtual Desktop Windows 8 | Windows 8 Registry | Windows 8 Backup | Windows 8 Recovery | Windows 8 Restore | Windows 8 Firewall | Windows 8 Aero Theme | Windows 8 Blue Screen | Windows 8 Activation| SEO by WebProfits