Installed Norton, Then Computer seemed to slow down. Ran Who Crashed


  1. Posts : 4
    64 bit OS windows 7
       #1

    Installed Norton, Then Computer seemed to slow down. Ran Who Crashed


    I have just put together a ZIP file from the SF Diagnostic program that I was asked to do. I am looking forward to the help you freely provide in this Forum. I am grateful for anything you can assist me with. Thank you!!!

    Can anyone help me. I am so sorry for P.S.ing a bunch of added thoughts. But I think after reading a bunch of other threads about problems with programs that cause issues, I may want to add that I am an avid video editor and I need my computer to be up to speed and not bogged down with unneeded programs. Please advice me for or against Norton. Thank you!

    I bought a brand new Sony Vaio with Windows 7 and here are the details.

    Processor Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz 7.4 5.9
    Determined by lowest subscore

    Memory (RAM) 8.00 GB 7.6
    Graphics AMD Radeon HD 7650M 6.7
    Gaming graphics 5873 MB Total available graphics memory 6.7
    Primary hard disk 260GB Free (683GB Total) 5.9


    (sorry for the details, I want to include as much as possible to help with the solution)

    When I started it all up and installed Pinnacle Studio 15 it ran super fast and everything moved smoothly. Then after a short while I had to install an Anti Virus program so I installed Norton. I believe that is when the problems started. It would crash unexpectedly and have to do a system restore or a system fix. The problem wouldn't always get fixed and eventually the computer seemed to move slower and slower. Recently I read some threads and downloaded WHOCRASHED and here is the report. I think it would be good for me to add that I also know that once I Installed Microsoft Office 2010, some issues came up that never did before. Are there any valid reasons for that outcome.

    Code:
    System Information (local) 
    
    
    computer name: DANIELANDKIM
    windows version: Windows 7 Service Pack 1, 6.1, build: 7601
    windows dir: C:\Windows
    CPU: GenuineIntel Intel(R) Core(TM) i7-3612QM CPU @ 2.10GHz Intel586, level: 6
    8 logical processors, active mask: 255
    RAM: 8558854144 total
    VM: 2147352576, free: 1932914688
    
    
    
    
    Crash Dump Analysis 
    
    
    Crash dump directory: C:\Windows\Minidump
    
    Crash dumps are enabled on your computer.
    
    On Tue 1/29/2013 12:05:36 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\012813-37097-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA800CBBFB30, 0xFFFFFA800CBBFE10, 0xFFFFF80003382460)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Tue 1/29/2013 12:05:36 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA800CBBFB30, 0xFFFFFA800CBBFE10, 0xFFFFF80003382460)
    Error: CRITICAL_OBJECT_TERMINATION
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Wed 1/16/2013 6:55:06 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\011613-20779-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800030E8F74)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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. 
    
    
    
    On Mon 1/7/2013 1:08:30 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\010613-25053-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA800C825B30, 0xFFFFFA800C825E10, 0xFFFFF80003385460)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Tue 12/4/2012 10:06:08 PM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120412-28610-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA800F7C4B30, 0xFFFFFA800F7C4E10, 0xFFFFF8000338C460)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Sun 12/2/2012 12:22:22 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\120112-25896-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0xF4 (0x3, 0xFFFFFA800CDCBB30, 0xFFFFFA800CDCBE10, 0xFFFFF800033D9460)
    Error: CRITICAL_OBJECT_TERMINATION
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue. 
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. 
    
    
    
    On Sat 12/1/2012 6:28:41 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\113012-29250-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
    Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80003096F74)
    Error: IRQL_NOT_LESS_OR_EQUAL
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
    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. 
    
    
    
    
    Conclusion 
    
    
    7 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.
    
    
    Read the topic general suggestions for troubleshooting system crashes for more information. 
    
    Note that it's not always possible to state with certainty whether a reported driver is actually 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.
    Can anyone tell me what might be my problem and how to remedy it from the report above? Also if there is another program that can run to help weed out the problem? Could there be some super virus that Norton can't find? Or maybe a program that I might have downloaded and installed that is not meshing well with my system and making it act up?

    Please help me. I have a 3 out of 10 skill in deep computer technology. So can you please do your best to make the answer in simple terms. Thank you.

    Last edited by Kalixadam77; 28 Jan 2013 at 17:18.
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2
      My Computer


  3. Posts : 4
    64 bit OS windows 7
    Thread Starter
       #3

    All set sir/madam. I have posted my ZIP file with all the reports in it. Thanks so much for your help, ahead of time!!
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    Sir/madam? Good! Dont take a chance to guess

    Sorry to say, but it is Norton. See some examples.

    Norton Internet Security
    Code:
    fffff880`079f43b8  fffff880`016a69f0Unable to load image \??\C:\Windows\system32\Drivers\SYMEVENT64x86.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
     SYMEVENT64x86+0x269f0
    Description here: Driver Reference Table - SYMEVENT64x86.SYS

    Symantec Heuristics Driver
    Code:
    fffff880`079f4358  fffff880`0479f2e0Unable to load image \??\C:\ProgramData\Norton\{0C55C096-0F1D-4F28-AAA2-85EF591126E7}\N360_20.2.0.19\Definitions\BASHDefs\20130107.001\BHDrvx64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BHDrvx64.sys
    *** ERROR: Module load completed but symbols could not be loaded for BHDrvx64.sys
     BHDrvx64+0x1372e0
    Description here: Driver Reference Table - BHDrvx64.sys

    Symantec /Norton
    Code:
    fffff880`079f4028  fffff880`03323ab8Unable to load image \??\C:\Program Files (x86)\Common Files\Symantec Shared\EENGINE\EraserUtilRebootDrv.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for EraserUtilRebootDrv.sys
    *** ERROR: Module load completed but symbols could not be loaded for EraserUtilRebootDrv.sys
     EraserUtilRebootDrv+0x2ab8
    Description here: Driver Reference Table - EraserUtilRebootDrv.sys

    Moreover, the last crash you got is a stop 0xF4. It is generally a HDD error, a HDD is making windows fail to initiate. Let us see what happened exactly before that particular fail occurred.
    Code:
    Event[34314]:
      Log Name: System
      Source: Microsoft-Windows-FilterManager
      Date: 2012-12-01T16:27:36.108
      Event ID: 6
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: DanielandKim
      Description: 
    File System Filter 'SymEFA' (6.0, ?2012?-?10?-?03T11:00:06.000000000Z) has successfully loaded and registered with Filter Manager.
    =========================================================================================
    Event[34315]:
      Log Name: System
      Source: Wd
      Date: 2012-12-01T16:27:36.124
      Event ID: 1
      Task: N/A
      Level: Information
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DanielandKim
      Description: 
    The system watchdog timer was triggered.
    =========================================================================================
    Event[34316]:
      Log Name: System
      Source: Microsoft-Windows-WER-SystemErrorReporting
      Date: 2012-12-01T16:28:02.000
      Event ID: 1001
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DanielandKim
      Description: 
    The computer has rebooted from a bugcheck.  The bugcheck was: 0x000000f4 (0x0000000000000003, 0xfffffa800cdcbb30, 0xfffffa800cdcbe10, 0xfffff800033d9460). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 120112-25896-01.
    Symentec filter manager loads, it triggers the system watchdog, and BSOD

    Clear now, what the problem is? Uninstall Norton and all Symentec products using Norton Removal tool. Use Microsoft Security Essentials as your antivirus with windows inbuilt firewall, and free MBAM as the on demand scanner.
    Download, install and update those, and then run full system scans with both of them, one by one.

    Let us know the results.
      My Computer


  5. Posts : 4
    64 bit OS windows 7
    Thread Starter
       #5

    Full of Thankfulness because.....


    Great thanks for your help my friend!:) That "medicine" was just what the "doctor ordered" It worked so well on my Video editing computer, that I brought all 9 of my other computers in my home into my office and am giving the same "medicine" to each one of them. Fantastic healing balm I must say!!!

    May I add as well that this experience has opened a completely new frontier to me. I would be more than happy to share more in detail ONLY if you are interested to hear it.:)

    I would like to invite you to hear two things today.

    [removed by admin (rule8) ]

    Again your expertise and direction have opened a door of extreme thankfulness for all the computer bugs and BSOD that lead me to this forum.

    Once again great thanks to the work and help you are providing, free of charge by the way, it will be given back to you, without a doubt.

    My sincere apologies if I have violated the Forum rules by pointing you to an outside video. I could not pass up the opportunity to share my greatfullness and appreciation for all that you have helped me with, which then led to me sharing the Youtube link.


    Kalix(Daniel)

    P.S. The computer that made the video you may watch is the computer that is in top shape and running great now. I made the video with the computer all messed up. What a miracle it was too!
    Last edited by z3r010; 31 Jan 2013 at 02:53. Reason: rule 8 violation
      My Computer


  6. Posts : 4
    64 bit OS windows 7
    Thread Starter
       #6

    BSOD locked on at bootup


    I can not seem to get any further than this screen. I tried to start up my old Toshiba and this is the screen that keeps coming up. Can anyone help me with this issue. Thank you ahead of time in faith:)
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    Kalixadam77 said:
    I brought all 9 of my other computers in my home into my office and am giving the same "medicine" to each one of them. Fantastic healing balm I must say!!!

    Hello Kalixadam77. Usually a particular fix that worked for one computer must not be essentially equally applicable to another one. But if you have followed it, you will not be at any loss that I can assure.

    If there are any further issue, let us know.
      My Computer


  8. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #8

    According to Carrona.org, STOP 0xC0000218: STATUS_CANNOT_LOAD_REGISTRY_FILE
    Usual causes:
    File corrupt/missing, Device driver corrupting memory, Memory failure

    The screen says it is a registry failure. Run SFC /SCANNOW Command - System File Checker

    If it fails, or you cannot boot into your desktop, try SFC /SCANNOW : Run in Command Prompt at Boot

    Scan the system for possible virus infection.


    Let us know the results.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 07:51.
Find Us