kiaora, it seems you have been having a problem for quite some time. I haven't looked at all the dump files as you have 33 dating back to February of this year. Do you recall what new program you installed then? It may help diagnose what the problem is. I did check the last 5 dump files and each one was exactly the same.
Norton was referenced first in each one
Code:
lmvm SYMNETS
start end module name
fffff880`06abf000 fffff880`06b55000 SYMNETS T (no symbols)
Loaded symbol image file: SYMNETS.SYS
Image path: \SystemRoot\System32\Drivers\NISx64\1505000.013\SYMNETS.SYS
Image name: SYMNETS.SYS
Timestamp: Thu [COLOR=red]Feb 13 05:25:14 2014[/COLOR] (52FCAB9A)
CheckSum: 00098278
ImageSize: 00096000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
You may note the date of the driver. It is Symantec/ Norton NIS/ N360 driver
The other one noted was a Windows driver
Code:
lmvm NETIO
start end module name
fffff880`01765000 fffff880`017c5000 NETIO (pdb symbols) c:\symcache\netio.pdb\1A3624EA66AA400882BAF5885EE923E52\netio.pdb
Loaded symbol image file: NETIO.SYS
Mapped memory image file: c:\symcache\NETIO.SYS\5294760D60000\NETIO.SYS
Image path: \SystemRoot\system32\drivers\NETIO.SYS
Image name: NETIO.SYS
Timestamp: Tue Nov 26 04:21:01 2013 (5294760D)
CheckSum: 0006433E
ImageSize: 00060000
File version: 6.1.7601.18327
Product version: 6.1.7601.18327
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: netio.sys
OriginalFilename: netio.sys
ProductVersion: 6.1.7601.18327
FileVersion: 6.1.7601.18327 (win7sp1_gdr.131125-2337)
FileDescription: Network I/O Subsystem
LegalCopyright: © Microsoft Corporation. All rights reserved.
This is the Network I/O subsystem
Norton is a well know cause of BSODs, so I would like you to uninstall it using the Norton Removal tool (
https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us )
and replace it with Microsoft Security Essentials (
Microsoft Security Essentials - Microsoft Windows ) That may help, at least until we see if that is in fact the cause.
I also noticed quite a few errors blamed on Cyberlink. It has a process that continually scans your media files and has been known to use considerable resources. Some have reported 100% CPU usage. You will have to decide how important that is to you. But if it is using that much resources, it needs to be dealt with.
Once you have done that, please open a elevated command prompt ( click start, type
cmd in the search box,
right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste
sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.
Please run chkdsk. This will tell you how
http://www.sevenforums.com/tutorials/433-disk-check.html
I would also recommend you to download your hard drive manufacturers diagnostic tool and run the long and short tests. It is always better to run the test for DOS. If you will let me know the manufacturer, maybe I could find a link for you. Once you have done these things, please let us know how it goes with you. If you have any more BSODs, please upload the files again.
