No signal msg on monitor and PC gets restart

Welcome

Your BSoD is caused by Avast Internet Security.
Please uninstall it. Download and install MSE.
Run a full scan after updated.
Microsoft Security Essentials - Free Antivirus for Windows

Driver Reference Table
STOP 0x0000000A: IRQL_NOT_LESS_OR_EQUAL BSOD Index

Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Yusra\Downloads\SF_20-09-2012\SF_20-09-2012\091912-16879-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c13000 PsLoadedModuleList = 0x82d5b810
Debug session time: Wed Sep 19 09:05:08.986 2012 (UTC + 6:00)
System Uptime: 0 days 0:00:09.718
Loading Kernel Symbols
...............................................................
.............................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {92098fa8, 2, 0, 82d27606}

Unable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
Probably caused by : aswSnx.SYS ( aswSnx+2d56 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 92098fa8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
	bit 0 : value 0 = read operation, 1 = write operation
	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 82d27606, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82d7b718
Unable to read MiSystemVaType memory at 82d5b160
 92098fa8 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!ExpCheckForWorker+66
82d27606 8b00            mov     eax,dword ptr [eax]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0xA

PROCESS_NAME:  autochk.exe

TRAP_FRAME:  8e26d69c -- (.trap 0xffffffff8e26d69c)
ErrCode = 00000000
eax=92098fa8 ebx=91967000 ecx=82d4d590 edx=00000000 esi=82d4d580 edi=00000000
eip=82d27606 esp=8e26d710 ebp=8e26d724 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!ExpCheckForWorker+0x66:
82d27606 8b00            mov     eax,dword ptr [eax]  ds:0023:92098fa8=82d4d590
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82d27606 to 82c597eb

STACK_TEXT:  
8e26d69c 82d27606 badb0d00 00000000 82f60a00 nt!KiTrap0E+0x2cf
8e26d724 82d3209b 91966fd8 8e26d894 91966fd8 nt!ExpCheckForWorker+0x66
8e26d788 82f43f90 91966fd8 00000000 8d354df8 nt!ExFreePoolWithTag+0x96
8e26d79c 82f43f52 91966fd8 00000000 8e26d7b8 nt!VerifierExFreePoolWithTag+0x30
8e26d7ac 850c6e8c 91966fd8 8e26d7d4 850eb33f nt!VerifierExFreePool+0x1f
8e26d7b8 850eb33f 8d334f80 91966fd8 91968fa8 fltmgr!ExFreeToNPagedLookasideList+0x1e
8e26d7d4 850ec038 8d354df8 91968fa8 00000000 fltmgr!FltpvUnlinkResourceFromFilter+0x115
8e26d7ec 8577ed56 91968fa8 8577ed3c 0b5a454e fltmgr!FltvReleaseContext+0x16
WARNING: Stack unwind information not available. Following frames may be wrong.
8e26d850 850eda9d 00000084 00000005 00000008 aswSnx+0x2d56
8e26d878 850debf5 8e26d894 00000005 00000008 fltmgr!FltvInstanceSetup+0x37
8e26d8ac 850df417 91960de8 00000005 0b2b8059 fltmgr!FltpDoInstanceSetupNotification+0x69
8e26d8f8 850df7d1 8d354df8 8d3f4ae0 00000005 fltmgr!FltpInitInstance+0x25d
8e26d968 850df8d7 8d354df8 8d3f4ae0 00000005 fltmgr!FltpCreateInstanceFromName+0x285
8e26d9d4 850e8cde 8d354df8 8d3f4ae0 00000005 fltmgr!FltpEnumerateRegistryInstances+0xf9
8e26da24 850dd7f4 8d3f4ae0 8c9185d0 8c96bd20 fltmgr!FltpDoFilterNotificationForNewVolume+0xe0
8e26da68 82f426c3 8c9185d0 8d3f4ae0 8c94fbe0 fltmgr!FltpCreate+0x206
8e26da8c 82c4f473 00000000 8c94fc3c 8c9185d0 nt!IovCallDriver+0x258
8e26daa0 82e5362d a671e309 8e26dc48 00000000 nt!IofCallDriver+0x1b
8e26db78 82e341d7 8b0a4200 85985618 8c8dc580 nt!IopParseDevice+0xed7
8e26dbf4 82e5a24d 00000000 8e26dc48 00000040 nt!ObpLookupObjectName+0x4fa
8e26dc50 82e525ab 0014fc6c 85985618 8e26dd01 nt!ObOpenObjectByName+0x159
8e26dccc 82e8d5ee 0014fcac 00100080 0014fc6c nt!IopCreateFile+0x673
8e26dd14 82c5642a 0014fcac 00100080 0014fc6c nt!NtOpenFile+0x2a
8e26dd14 777d64f4 0014fcac 00100080 0014fc6c nt!KiFastCallEntry+0x12a
0014fdc4 00000000 00000000 00000000 00000000 0x777d64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSnx+2d56
8577ed56 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  aswSnx+2d56

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME:  aswSnx.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4d652035

FAILURE_BUCKET_ID:  0xA_VRF_aswSnx+2d56

BUCKET_ID:  0xA_VRF_aswSnx+2d56

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

Also look for an update for your BIOS version and get all latest updates including SP1 from windows update.

Let us know if the problem persists.

kumscp,
In addition to the excellent advice you have received from KoolKat, I recommend you increase the memory.

2 GB is sufficient and I have an netbook with only 2 GB, but Win 7 is happier with at least 4 GB.

Also, need you to help us to help you by fully and completely filling in your system specs:

Update your SevenForums System Specs
User CP (located on the top menu bar) |
Your Profile | Edit System Spec (left-hand column)

To gather info, use Speccy (my favorite) or SIW or System Info

In the System Manufacturer Block, enter:
Ø Manufacturer and Model OR Custom build.
Ø ADD the word laptop, desktop, netbook or tablet.
For example:
Toshiba Satellite L305D notebook.

Provide full windows version info, for example:
MS Windows 7 Ultimate SP1 64-bit

Use the “Other Info” block for Optical Reader,
Mouse, touchpad, wifi adapter, speakers, monitor, etc

Scroll down and click on SAVE CHANGES.

With Speccy, you can select with your mouse/touchpad info from the display
and paste that info into your specs.

SIW is a marvelous program, but the free version does not offer
this capability.