Welcome
Please uninstall AVG while we troubleshoot problems with your computer.
Code:
Start Menu\Programs\AVG Public:Start Menu\Programs\AVG Public
PROCESS_NAME: avgnsa.exe
Also uninstall Spybot - Search & Destroy.
Code:
Start Menu\Programs\Spybot - Search & Destroy Public:Start Menu\Programs\Spybot - Search & Destroy Public
Download and install MSE. It is known to be the most compatible with Windows 7 + its free!
Microsoft Security Essentials - Free Antivirus for Windows
A replacement for Spybot - Search & Destroy would be Malwarebytes (free).
Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
Run a full scan with both to make sure you are free of nasty worms! :)
You may keep these as long as we are troubleshooting your computer to find out the reasons of its crashes.
If you have an on board video/gpu slot, stay connected to that one see if you crash there.
If you are overclocking any hardware, please stop.
With the different numbers of bug checks I'd suggest you the follows
To make sure that hard drive is good run disk check following the tutorials below:
- Disk Check
- Hard drive scan usings SeaTools SeaTools | Seagate both long and short tests.
After this, run the system file checker to repair any corrupted files within windows
SFC /SCANNOW Command - System File Checker
You should run memtest86+ on each stick for 8 passes preferably overnight.
BSOD Analysis:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1A, {403, fffff680000117c0, c140000206a2f867, fffff68000022f80}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3267c )
Followup: MachineOwner
---------
MEMORY_MANAGEMENT (1a) BSOD Index
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {4f444678, 2, 0, fffff88002d15aa2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hidusb.sys ( hidusb!HumReadReport+13f )
Followup: MachineOwner
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) BSOD Index
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 24, {1904fb, fffff88007f571e8, fffff88007f56a40, fffff8800122bde5}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Ntfs.sys ( Ntfs!NtfsFreeAttributeEntry+79 )
Followup: MachineOwner
---------
NTFS_FILE_SYSTEM (24) BSOD Index
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {80050, 2, 1, fffff8800151c1dd}
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : NETIO.SYS ( NETIO!NetioInitializeNetBufferListContext+4d )
Followup: MachineOwner
---------
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 18, {0, fffffa8003c251b0, 2, ffffffffffffffff}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+49331 )
Followup: MachineOwner
---------
REFERENCE_BY_POINTER (18) BSOD Index
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff80002fbf062, fffff88008ad8090, 0}
Probably caused by : ntkrnlmp.exe ( nt!NtWaitForSingleObject+b2 )
Followup: MachineOwner
---------
SYSTEM_SERVICE_EXCEPTION (3b) BSOD Index
Take your time and do the suggestions above and keep us posted.