Getting Random BSOD Errors

Same as before. What were the latest results of sfc /scannow?

Since this is a startup based error: Troubleshoot Application Conflicts by Performing a Clean Startup and see if it resolves the problem.

sfc showed errors but didn't fix any. i included the sfc log in the dump.

Ah, so you did. Given that replacing the files did not fix the problem, I now recommend a Repair Install

Official Windows 7 SP1 ISO from Digital River « My Digital Life may be a useful link if you do not have your installation media.

it found errors but didn't repair anything.

newest dump attached.
Attachment 206135

Code:

Loading Dump File [D:\Kingston\BSODDmpFiles\charmaine\040712-36317-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17713.x86fre.win7sp1_gdr.111025-1505
Machine Name:
Kernel base = 0x83011000 PsLoadedModuleList = 0x8315a4d0
Debug session time: Sat Apr  7 09:34:41.989 2012 (UTC - 6:00)
System Uptime: 0 days 0:00:17.799
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: 00000003, Process
Arg2: 8ab61030, Terminating object
Arg3: 8ab6119c, Process image file name
Arg4: 83229d60, Explanatory message (ascii)

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


PROCESS_OBJECT: 8ab61030

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 00000000 

EXCEPTION_CODE: (Win32) 0xe (14) - Not enough storage is available to complete this operation.

BUGCHECK_STR:  0xF4_E

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
8d932c9c 832ef159 000000f4 00000003 8ab61030 nt!KeBugCheckEx+0x1e
8d932cc0 8326ccdc 83229d60 8ab6119c 8ab610c8 nt!PspCatchCriticalBreak+0x71
8d932cf0 8326cc1f 8ab61030 8891b598 0000000e nt!PspTerminateAllThreads+0x2d
8d932d24 8304f21a 00000000 0000000e 0009f930 nt!NtTerminateProcess+0x1a2
8d932d24 77517094 00000000 0000000e 0009f930 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0009f930 00000000 00000000 00000000 00000000 0x77517094


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0xF4_E_IMAGE_wininit.exe

BUCKET_ID:  0xF4_E_IMAGE_wininit.exe

Followup: MachineOwner
---------

The above crash points to corrupted data, a failing hard disk, or both.

• I still recommend a Repair Install if you have not yet done so.

Also, check your hard disk for errors.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using Check Disk (chkdsk) - Read Event Viewer Log.
  For any drives that do not give the message:
  Windows has checked the file system and found no problems
  run disk check again as above. In other words, if it says:
  Windows has made corrections to the file system
  after running the disk check, run the disk check again.
  
  
• Use the Western Digital Lifeguard Diagnostic to scan your hard disk and determine whether the disk is good.

hard disk is fine. just checked with seagate and western digital software. trying repair install now.

chkdsk is also good.

Alright, glad to see the disk is not the problem. Let us know how things are running after the repair install.

system repair didn't fix anything but the frequency of bsod errors has been minimized and it just shuts down my system and gives no error at all. attached newest sfc log:
Attachment 206710