Suddenly random freezes,restarts and BSODs.

Hi, 4 days now my pc sometimes freezes at startup and it needs restart.Also suddenly it restarts without a message.And today i got 2 BSODs and one of them was at welcome screen.I scanned my pc with malwarebytes and found nothing.

System Specs:
Microsoft Windows 7 Ultimate 32-bit 7601 Multiprocessor Free Service Pack 1
MICRO-STAR INTERNATIONAL CO.,LTD G31M3-L V2(MS-7529)
Intel(R) Core(TM)2 Duo CPU E7500 @2.93 Ghz (2 CPUs)
RAM 4GB
Graphics Card: ATI Radeon HD 4890 2GB


Attatchement:

Code:

Loading Dump File [G:\Kingston\BSODDmpFiles\omonoia91\Windows_NT6_BSOD_jcgriff2\020312-20468-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 = 0x83051000 PsLoadedModuleList = 0x83191230
Debug session time: Fri Feb  3 05:09:17.515 2012 (GMT-7)
System Uptime: 0 days 0:00:31.031
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 96d0897b, 82ab5cb4, 0}

Probably caused by : hardware ( win32k!vSynchronizeDriver+100 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 96d0897b, The address that the exception occurred at
Arg3: 82ab5cb4, Trap Frame
Arg4: 00000000

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


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

FAULTING_IP: 
win32k!vSynchronizeDriver+100
96d0897b 800000          add     byte ptr [eax],0

TRAP_FRAME:  82ab5cb4 -- (.trap 0xffffffff82ab5cb4)
ErrCode = 00000002
eax=00000099 ebx=96d08a35 ecx=877bd758 edx=96d08a35 esi=0015f294 edi=0015f2b0
eip=96d0897b esp=82ab5d28 ebp=82ab5d34 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
win32k!vSynchronizeDriver+0x100:
96d0897b 800000          add     byte ptr [eax],0           ds:0023:00000099=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

CURRENT_IRQL:  0

MISALIGNED_IP: 
win32k!vSynchronizeDriver+100
96d0897b 800000          add     byte ptr [eax],0

LAST_CONTROL_TRANSFER:  from 76f77094 to 96d0897b

STACK_TEXT:  
82ab5d34 76f77094 badb0d00 0015f294 00000000 win32k!vSynchronizeDriver+0x100
WARNING: Frame IP not in any known module. Following frames may be wrong.
82ab5d3c 0015f294 00000000 00000000 00000000 0x76f77094
82ab5d40 00000000 00000000 00000000 00000000 0x15f294


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!vSynchronizeDriver+100
96d0897b 800000          add     byte ptr [eax],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k!vSynchronizeDriver+100

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

Loading Dump File [G:\Kingston\BSODDmpFiles\omonoia91\Windows_NT6_BSOD_jcgriff2\020312-15375-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 = 0x83045000 PsLoadedModuleList = 0x83185230
Debug session time: Fri Feb  3 05:07:46.452 2012 (GMT-7)
System Uptime: 0 days 0:02:31.967
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 00041287, The subtype of the bugcheck.
Arg2: 31e23294
Arg3: 00000000
Arg4: 00000000

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


BUGCHECK_STR:  0x1a_41287

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

CURRENT_IRQL:  0

TRAP_FRAME:  a1c51acc -- (.trap 0xffffffffa1c51acc)
ErrCode = 00000000
eax=00325009 ebx=873c1770 ecx=84400000 edx=ada23280 esi=c0402ff8 edi=c04026a8
eip=830c6152 esp=a1c51b40 ebp=a1c51b4c iopl=0         ov up ei pl nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210a07
nt!MiSwapWslEntries+0x54:
830c6152 f7440a1400000008 test    dword ptr [edx+ecx+14h],8000000h ds:0023:31e23294=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 8307da48 to 830a3d87

STACK_TEXT:  
a1c51ab4 8307da48 00000000 31e23294 00000000 nt!MmAccessFault+0xbf
a1c51ab4 830c6152 00000000 31e23294 00000000 nt!KiTrap0E+0xdc
a1c51b4c 830b0af5 00000254 0000148e 873c1770 nt!MiSwapWslEntries+0x54
a1c51b78 830bb613 0000148e 00c47000 873c1770 nt!MiUpdateWsle+0x12d
a1c51ba8 830e009f c000311c 8533c5b8 00000000 nt!MiAllocateWsle+0x14c
a1c51be8 830b2a2c 00000000 873c1770 00c470fa nt!MiCompleteProtoPteFault+0x29e
a1c51c28 830a707e 00000000 00c470fa c000311c nt!MiResolveProtoPteFault+0x1cd
a1c51ca4 830a5c6e 00c470fa 00000000 00000000 nt!MiDispatchFault+0x511
a1c51d1c 8307da48 00000000 00c470fa 00000001 nt!MmAccessFault+0x1fa3
a1c51d1c 00c470fa 00000000 00c470fa 00000001 nt!KiTrap0E+0xdc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0017d76c 00000000 00000000 00000000 00000000 0xc470fa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KiTrap0E+dc
8307da48 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!KiTrap0E+dc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ea76e9b

FAILURE_BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc

BUCKET_ID:  0x1a_41287_nt!KiTrap0E+dc

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

1. In my experience this is usually driver related, though it could be hardware as it suggests. Other possible causes are Memory problems... Viruses... Corrupted hard disk file system... Corrupted System Files... Lack of Windows updates... Drivers...
   Thanks to JMH for helping with my understanding of this crash.
2. Possible causes are Memory problems... Drivers...

We will start with the common problems first (see bold possible causes). Do the following steps and test after each to see if stability increases (the memory tests you can run concurrently as they will not increase stability unless you are forced to move modules around). Post back your results after each step, and if you get a blue screen crash, upload the files again and await further instructions after we are able to analyze the crash.

• If you are overclocking any hardware, please stop.
  
  
  
• Download and install the appropriate version of HWINFO: HWiNFO32 for 32-bit Windows 7 or HWiNFO64 for 64-bit Windows 7 to check hardware temperatures by running in sensor-only mode.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
  
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  
  
• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. Run Driver Verifier
  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.