I have been getting the blue screen several times a day since installing windows 7. This is what the error report is saying. Problem signature: Problem Event Name: BlueScreen OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional information about the problem: BCCode: 4e BCP1: 00000007 BCP2: 00076373 BCP3: 00000001 BCP4: 00000000 OS Version: 6_1_7600 Service Pack: 0_0 Product: 256_1 Files that help describe the problem: C:\Windows\Minidump\032910-69857-01.dmp C:\Users\Comp\AppData\Local\Temp\WER-2338844-0.sysdata.xml Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt What should I do?

This little checklist that I've composed might be a good start, http://www.theexperienceblog.com/2009/11/16/how-to-solve-blue-screens-of-death-problems-with-windows-7/ together with the fact to analyze the cause of the blue screens of deaths, i.e. either by posting links to the DMP files here or by following the guide last in that guide.Blogging about Windows for IT pros at www.theexperienceblog.com

A simple way to find out what is causing the BSODs is BlueScreenView . BlueScreenView scans all your minidump files created during 'blue screen of death' crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version). For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash. MowGreen Update Services - Consumer Security

Since Windows system uses separated user mode and kernel mode memory space, stop errors are usually caused by kernel portion components, such as a hardware device, third-party drivers, backup software or anti-virus services (buggy services). Please refer to the following steps to troubleshoot the issue. 1. Boot the computer in Clean Boot for a test. 2. Temporarily disable all unnecessary hardware devices in Device Manager, such as Modem, sound card or external device. For detail steps, we can refer to the link below: Device Clean Boot 3. Run antivirus program and perform a full scanning. If the issue persists, please upload the minidump file (%systemroot%\minidump) to SkyDrive ( www.skydrive.live.com ), then share the link to me. I will be glad to assist you to analysis the data. Thanks, Novak