BSOD every few minutes after installing new SSD

Hello

This is my first post here. I have an HP Envy 14 computer which I bought three years ago. I recently installed a new SSD Hard drive on it since the old one was on the verge of crashing. I did not have a copy of the recovery disk and hence decided to purchase a stand alone copy of Windows 7 Home Premium x64. I found and downloaded all the necessary drivers from the HP Website.

The problem started from the first day after I got the hard drive. My computer crashes, with or without a BSOD, and restarts at random frequent intervals. This is the online Analysis of the .dmp file.

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (OSR)
Online Crash Dump Analysis Service
See OSR Online - The Home Page for Windows Driver Developers for more information
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`02a0b000 PsLoadedModuleList = 0xfffff800`02c4f670
Debug session time: Sun Jan 27 10:55:40.558 2013 (UTC - 5:00)
System Uptime: 0 days 0:34:31.010
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa8004b98060, Terminating object
Arg3: fffffa8004b98340, Process image file name
Arg4: fffff80002d89460, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2

PROCESS_OBJECT: fffffa8004b98060

IMAGE_NAME: csrss.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: csrss

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: csrss.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

BUGCHECK_STR: 0xF4_fffff800c0000005

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`077dc0e8 fffff800`02e11822 : 00000000`000000f4 00000000`00000003 fffffa80`04b98060 fffffa80`04b98340 : nt!KeBugCheckEx
fffff880`077dc0f0 fffff800`02dbde0b : ffffffff`ffffffff fffffa80`05c0cb50 fffffa80`04b98060 fffffa80`04b98060 : nt!PspCatchCriticalBreak+0x92
fffff880`077dc130 fffff800`02d3cf04 : ffffffff`ffffffff 00000000`00000001 fffffa80`04b98060 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176e6
fffff880`077dc180 fffff800`02a89253 : fffffa80`04b98060 fffff800`c0000005 fffffa80`05c0cb50 00000000`02330940 : nt!NtTerminateProcess+0xf4
fffff880`077dc200 fffff800`02a85810 : fffff800`02ad4b7f fffff880`077dcb78 fffff880`077dc8d0 fffff880`077dcc20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`077dc398 fffff800`02ad4b7f : fffff880`077dcb78 fffff880`077dc8d0 fffff880`077dcc20 00000000`02332180 : nt!KiServiceLinkage
fffff880`077dc3a0 fffff800`02a89642 : fffff880`077dcb78 00000000`000135e8 fffff880`077dcc20 00000000`02331c58 : nt! ?? ::FNODOBFM::`string'+0x488a4
fffff880`077dca40 fffff800`02a881ba : 00000000`00000001 00000000`02330ef8 00000000`0233cf01 00000000`000135e8 : nt!KiExceptionDispatch+0xc2
fffff880`077dcc20 00000000`775c8e3d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`02330f00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775c8e3d


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_fffff800c0000005_IMAGE_csrss.exe

BUCKET_ID: X64_0xF4_fffff800c0000005_IMAGE_csrss.exe

Followup: MachineOwner

Any help would be gladly appreciated. Thank you

Hello apravink. Search for any available firmware update for the SSD.

No code has to be inserted here.

Intel® SATA Solid-State Drive Firmware Update Tool
Intel® Solid-State Drive Toolbox

Free up the startup.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept the restart.

Also there is some problems with the AVG antivirus's watchdog service. Better you uninstall AVG using AVG Remover. 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.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.