Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BSOD and Stop Codes...


  • Please log in to reply

#1
CFERG

CFERG

    New Member

  • Member
  • Pip
  • 3 posts
I have had the BSOD a few time lately. Originally I used your incredible website to figure out that there was a problem with norton. I uninstalled norton and reinstalled it and everything was good for a few days. Then I got the BSOD again, it would shut down at random, no specific program was running. No new hardware or software changes as of late. When I run whocrashed this is what I am getting now...

On Fri 12/25/2009 2:49:58 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF8022C0, 0xB26E6AB4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini122509-01.dmp
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.


I did have an error recently with the video driver nvidia and I had to uninstall it and reinstall. I have checked in the device manager and nothing currently shows any errors.

Its a gateway computer running windows XP and SP2. I can't recall all of the individual components at the moment as I had to do quite a bit of work to the unit last spring and replaced the mother board and other various items. I can get details if you need.

ANY help or guidance on this issue is greatly appreciated....




Craig
  • 0

Advertisements


#2
jcgriff2

jcgriff2

    Member

  • Expert
  • 90 posts
  • MVP
The bugcheck 0x8e (0xc0000005,,,) = kernel mode app threw an exception; the exception is the 0xc...5 = memory access violation

Did you use the Norton Removal Tool ? --> http://www.symantec....ted_nav=partner

Regards. . .

jcgriff2
  • 0

#3
CFERG

CFERG

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
" Did you use the Norton Removal Tool ? "


Yes, I used the norton removal tool. The only other problem I have noticed both before the norton removal and after the reinstall is that when I try to run norton disc doctor I get this error...

Error on Hard Disk 2 -Master Partition Table is unreadable.
The master Partition Table is physicaly damaged. Norton Disk Doctor is unable to continure with repairs.
Correct this situation if you are unable to access partitions on hard disk 2.

Any realtion? I don't know what its talking about and I don't know what a partition is in relation to my computer. I am assuming it's reffereing to my back up hard drive. It's an external drive, onetouch4 by Maxtor.

Edited by CFERG, 27 December 2009 - 02:08 PM.

  • 0

#4
CFERG

CFERG

    New Member

  • Topic Starter
  • Member
  • Pip
  • 3 posts
In retrospect I thought it would be prudent to give you my entire crash dump to make it a little easier to diagnose and see the history of my issues....

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Fri 12/25/2009 2:49:58 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF8022C0, 0xB26E6AB4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini122509-01.dmp
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.



On Tue 12/22/2009 11:42:36 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE7DB4000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini122209-01.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Mon 12/21/2009 12:03:06 AM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE75E1000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini122009-01.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Thu 12/17/2009 5:10:19 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE75FA000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121709-05.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Thu 12/17/2009 4:59:07 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE7558000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121709-04.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Thu 12/17/2009 4:33:43 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE76D6000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121709-03.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Thu 12/17/2009 1:16:11 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE7B92000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121709-02.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Thu 12/17/2009 1:06:00 PM your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x50 (0xF000EF5D, 0x1, 0xBF80173D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121709-01.dmp
file path: C:\WINDOWS\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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.



On Tue 12/15/2009 6:53:05 AM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE79BE000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121509-02.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Tue 12/15/2009 6:37:57 AM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xF000EF5D, 0x1, 0xBF80173D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121509-01.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Tue 12/15/2009 5:26:38 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xC2 (0x7, 0xCD4, 0x0, 0xE1EE5D78)
Error: BAD_POOL_CALLER
Dump file: C:\WINDOWS\Minidump\Mini121409-02.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.



On Tue 12/15/2009 4:56:48 AM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x50 (0xE8ACE000, 0x1, 0xB9ED7225, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini121409-01.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Tue 12/8/2009 6:59:51 PM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xB20E34C0, 0xB20E31BC, 0xBA633ED4)
Error: NTFS_FILE_SYSTEM
Dump file: C:\WINDOWS\Minidump\Mini120809-01.dmp
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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.



On Fri 11/13/2009 4:25:35 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0x9DDC600C, 0x2, 0x0, 0x8050EF1C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini111309-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.



On Fri 11/6/2009 2:04:37 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xBACDFAB8, 0xBACDF7B4, 0xBA6197D7)
Error: NTFS_FILE_SYSTEM
Dump file: C:\WINDOWS\Minidump\Mini110509-02.dmp
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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.



On Fri 11/6/2009 1:16:09 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xBACDFAE4, 0xBACDF7E0, 0xBA649413)
Error: NTFS_FILE_SYSTEM
Dump file: C:\WINDOWS\Minidump\Mini110509-01.dmp
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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.



On Thu 10/29/2009 9:06:56 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x19 (0x20, 0xE49D2260, 0xE49D2278, 0xC030401)
Error: BAD_POOL_HEADER
Dump file: C:\WINDOWS\Minidump\Mini102909-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.



On Wed 10/28/2009 2:30:10 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x50 (0xFFFFFFFC, 0x0, 0x8054B51A, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
Dump file: C:\WINDOWS\Minidump\Mini102809-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.



On Tue 10/20/2009 6:03:27 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xB9DC600C, 0x2, 0x0, 0x8050EF1C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini102009-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.



On Wed 10/14/2009 12:40:58 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x8054BFD2, 0xB62816E0, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini101409-01.dmp
file path: SYMEFA.SYS
This file could not be located on your computer, we suggest that you search on its name with Google.
Click here to do a Google search on symefa.sys





On Tue 9/29/2009 11:53:43 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xC7DC600C, 0x2, 0x0, 0x8050EF1C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini092909-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.



On Fri 9/4/2009 12:13:32 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0x8A3B, 0x2, 0x1, 0x806E6A16)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini090309-02.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.



On Thu 9/3/2009 7:00:08 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x1A (0x41284, 0x3FD3001, 0x0, 0xC0883000)
Error: MEMORY_MANAGEMENT
Dump file: C:\WINDOWS\Minidump\Mini090309-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.



On Wed 8/5/2009 7:47:01 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xAB846008, 0x2, 0x1, 0x805161FC)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini080509-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.



On Sat 8/1/2009 11:45:39 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xBE (0xBF8082B7, 0x1402A021, 0xB5135C30, 0xC)
Error: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Dump file: C:\WINDOWS\Minidump\Mini080109-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.



On Wed 6/17/2009 1:50:51 AM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0xA (0xAB84600C, 0x2, 0x0, 0x8050EF1C)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\WINDOWS\Minidump\Mini061609-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.



On Sat 5/3/2008 11:04:20 PM your computer crashed
This was likely caused by the following module: ntkrnlpa.exe
Bugcheck code: 0x24 (0x1902FE, 0xF69F8408, 0xF69F8104, 0x80573C63)
Error: NTFS_FILE_SYSTEM
Dump file: C:\WINDOWS\Minidump\Mini050308-04.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.



On Sat 5/3/2008 6:35:52 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x861447DA, 0xF6DABC40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini050308-03.dmp
file path: C:\WINDOWS\system32\ntoskrnl.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.



On Sat 5/3/2008 6:28:43 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x1, 0xF6BD3C40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini050308-02.dmp
file path: C:\WINDOWS\system32\ntoskrnl.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.



On Sat 5/3/2008 6:16:02 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x1, 0xF7118C40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
Dump file: C:\WINDOWS\Minidump\Mini050308-01.dmp
file path: C:\WINDOWS\system32\ntoskrnl.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.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

30 crash dumps have been found and analyzed. Note that it's not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
  • 0

#5
123Runner

123Runner

    Member 4k

  • Member
  • PipPipPipPipPipPipPip
  • 4,308 posts
I did some research on the Symantec site and found some interesting things.

Symantecs Forum
1. The consensus in the beginning from Symantec is that NIS2009 is not the problem. They have since changed their minds.
2. Everyone having trouble has either disabled idle time scan, or uninstalled the product.
3. Symantec states it should probably be fixed in version 16.5
4. Users are uninstalling, using the cleaning tool and then re-installing and still having issues.
5. Users are going back to NIS2008 are are running fine.

123runner
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP