New
#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.
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?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.
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.