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

Stop Error or Blue Screen


  • Please log in to reply

#1
berto85

berto85

    Member

  • Member
  • PipPip
  • 36 posts
I look around and this messages appear, what can I do how can I fix it?


system error, category 102, event ID 1003
error code 1000000a, parameter1 fffec080, parameter2 00000002, parameter3 00000001, parameter4 806ee2dc

system error, category 102, event ID 1003
error code 1000000a, parameter1 fffe4080, parameter2 00000002, parameter3 00000001, parameter4 806ee2dc

system error, category 102, event ID 1003
error code 100000d1, parameter1 00008446, parameter2 00000007, parameter3 00000000, parameter4 f749d1d0

TCP/IP has reached the security limit emposed on the number of concurrent TCP connect attempts
source;tcpip
event id 4226

the attempt to reboot computer failed
  • 0

Advertisements


#2
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
Can you explain where you got the error messages from?
Can you boot into Windows?
Do you get errors in Safe Mode?
What is the error code of the BSODs you see?
  • 0

#3
berto85

berto85

    Member

  • Topic Starter
  • Member
  • PipPip
  • 36 posts
yeah I went to the EVEN VIEWER
on the administrative tools
  • 0

#4
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
How are these errors effecting you? Tell me what is happening because of them, and when they occur.
  • 0

#5
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
Started a new topic and this is what was posted there

this is what i see, this is one of the error messages can someone help me please


  • 0

#6
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
This is not showing anything so let's try a different approach.

Download WhoCrashed from the link in my signature below
This program checks for any drivers which may have been causing your computer to crash....

Click on the file you just downloaded and run it.
Put a tick in Accept then click on Next
Put a tick in the Don't create a start menu folder then click Next
Put a tick in Create a Desktop Icon then click on Install and make sure there is a tick in Launch Whocrashed before clicking Finish
Click Analyze
It will want to download the Debugger and install it Say Yes

WhoCrashed will create report but you have to scroll down to see it
Copy and paste it into your next reply
  • 0

#7
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
Along with the WhoCrashed report...
Go to the directory C:\Windows\Minidump
Make sure that hidden files are visible.
Zip up the files that you find in that directory, and attach the .zip archive to your next post.
  • 0

#8
berto85

berto85

    Member

  • Topic Starter
  • Member
  • PipPip
  • 36 posts
This is what I found or what it show


Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


Too many crashes have been detected. Only the latest 40 crashes will be displayed.

On Mon 6/29/2009 4:33:14 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symefa.sys





On Mon 6/29/2009 4:17:35 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 4:08:33 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symefa.sys





On Mon 6/29/2009 3:55:14 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 3:48:23 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 3:36:02 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/29/2009 3:23:47 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symefa.sys





On Mon 6/29/2009 2:27:10 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symefa.sys





On Mon 6/29/2009 1:00:18 AM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symefa.sys





On Mon 6/29/2009 12:11:52 AM your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xF6068A84, 0xF6068780, 0x8051A4B0)
Error: NTFS_FILE_SYSTEM
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 8:37:14 PM your computer crashed
This was likely caused by the following module: symefa.sys
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on symefa.sys





On Sun 6/28/2009 2:51:15 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 2:40:02 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 2:29:06 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 2:18:12 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 2:08:05 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 1:52:18 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 1:42:13 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 1:30:20 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 1:18:32 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 1:06:36 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 12:54:14 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/28/2009 12:42:18 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sat 6/27/2009 5:47:35 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sat 6/27/2009 5:27:01 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFE4080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sat 6/27/2009 4:15:24 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Sat 6/27/2009 4:04:45 PM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xFFFEC080, 0x2, 0x1, 0x806EE2DC)
Error: Unknown
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. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/15/2009 3:26:50 AM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x8446, 0x7, 0x0, 0xF749D1D0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sun 6/14/2009 11:03:26 PM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x8446, 0x7, 0x0, 0xF749D1D0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 6/13/2009 5:34:06 PM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x8446, 0x7, 0x0, 0xF749D1D0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 6/13/2009 5:48:29 AM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x8446, 0x7, 0x0, 0xF749D1D0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 6/1/2009 4:56:24 AM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x8444, 0x7, 0x0, 0xF749D1D0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Sat 4/11/2009 2:31:44 AM your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x8054B6DA, 0xF68FB8E8, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
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. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/19/2009 6:38:04 AM your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0x100000D1 (0x8441, 0x9, 0x0, 0xF7231BD4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/19/2009 6:32:56 AM your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0x100000D1 (0x8441, 0x9, 0x0, 0xF7231BD4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/19/2009 3:52:57 AM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x8444, 0x7, 0x0, 0xF749D1D0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Thu 3/19/2009 12:56:01 AM your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0x100000D1 (0x8443, 0x9, 0x0, 0xF7231BD4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 3/18/2009 6:44:40 AM your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0x100000D1 (0x8441, 0x9, 0x0, 0xF7231BD4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Wed 3/18/2009 6:43:17 AM your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0x100000D1 (0x8443, 0x9, 0x0, 0xF7231BD4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.



On Mon 3/16/2009 5:19:54 AM your computer crashed
This was likely caused by the following module: usbport.sys
Bugcheck code: 0x100000D1 (0x8444, 0x9, 0x0, 0xF7231BD4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




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

57 crash dumps have been found on your computer. Only 40 have been 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

#9
edge2022

edge2022

    Member 2k

  • Member
  • PipPipPipPipPip
  • 2,117 posts
Check your RAM... click on Memtest Instructions in my sig, and follow the directions. Post the results of the diagnostic.
Also, do you have a Norton or Symantec product installed?

Edited by edge2022, 03 July 2009 - 11:28 PM.

  • 0

#10
berto85

berto85

    Member

  • Topic Starter
  • Member
  • PipPip
  • 36 posts
I want to thank you all for your assistance, you guys are amazing. I just run the WHOCRASHED program again and the analyze and everything dissapear, now it only shows this, Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.


On Mon 7/6/2009 1:52:51 AM your computer crashed
This was likely caused by the following module: ohci1394.sys
Bugcheck code: 0x100000D1 (0x84C4, 0x7, 0x0, 0xF749D2FA)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\ohci1394.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: 1394 OpenHCI Port Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.




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

1 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.


my computer still runs slow, and sometimes it takes forever to restart, like I mean to get turn off, what I can do to make it faster?
  • 0

Advertisements


#11
berto85

berto85

    Member

  • Topic Starter
  • Member
  • PipPip
  • 36 posts

Check your RAM... click on Memtest Instructions in my sig, and follow the directions. Post the results of the diagnostic.
Also, do you have a Norton or Symantec product installed?



I'm trying to do this but my cd burner doesnt work, none of the cd roms work, they dont read cds, or anything at all, what can I do?
  • 0

#12
rshaffer61

rshaffer61

    Moderator

  • Moderator
  • 34,114 posts
It looks like your OS is corrupted. Ntoskrnl and ohci1394.sys are needing to be repaired.
To repair the latter Microsoft has a hotfix for it located HERE
HERE if slowdown on internet

Ntoskrnl would require a repair installation of XP.
symefa.sys is related to Nortons. Is Nortons installed on your system?

Do you have your XP installation disk?
  • 0

#13
berto85

berto85

    Member

  • Topic Starter
  • Member
  • PipPip
  • 36 posts

It looks like your OS is corrupted. Ntoskrnl and ohci1394.sys are needing to be repaired.
To repair the latter Microsoft has a hotfix for it located HERE
HERE if slowdown on internet

Ntoskrnl would require a repair installation of XP.
symefa.sys is related to Nortons. Is Nortons installed on your system?

Do you have your XP installation disk?



I already uninstall Norton from my computer, now I use

Avira
Comodo
AVast


and I dont have the installation disc, but my computer dont read disc anyways cuz the cd rom doesnt read them
  • 0

#14
123Runner

123Runner

    Member 4k

  • Member
  • PipPipPipPipPipPipPip
  • 4,308 posts

Avira
Comodo
AVast

You need to uninstall either avira or avast. Running 2 virus scanners will conflict.

As for Norton, run the norton cleanup tool found under "antivirus cleanup programs".
  • 0

#15
berto85

berto85

    Member

  • Topic Starter
  • Member
  • PipPip
  • 36 posts

Avira
Comodo
AVast

You need to uninstall either avira or avast. Running 2 virus scanners will conflict.

As for Norton, run the norton cleanup tool found under "antivirus cleanup programs".



ok thanks, I also have CCleaner
  • 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