Blue Screen

Could you please follow these directions?

https://www.sevenforums.com/crashes-d...tructions.html

I would suggest removing Avast, and replacing it with MSE.

Avast removal tool: http://files.avast.com/files/eng/aswclear5.exe

MSE: http://www.microsoft.com/security_essentials

Update your Intel storage drivers, on the computer manufacturer's site.

I'll take a look at the new report you upload, and then give you more instructions.

...Summary of the Dumps:

Code:

Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Debug session time: Tue Aug 17 08:51:56.595 2010 (UTC - 4:00)
System Uptime: 0 days 0:02:25.345
BUGCHECK_STR:  0x1a_5003
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

The dmp(s) point to ntkrpamp.exe or ntoskrnl.exe as the probable cause. We know this is not the case, as these are core OS files, and will definitely not cause a BSOD. They are just the default files the debuggers blame when they can't see a better cause.

Enable driver verifier, following these directions..

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8f8140, 2, 8, 8f8140}

Probably caused by : ntkrpamp.exe ( nt!KiTrap0E+2cf )

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

These drivers are out of date and need to be updated ...

Code:

91de6000 91df0e80   HECI     HECI.sys     Tue Mar 13 16:05:28 2007 (45F70408) ... Intel(R) Management Engine Interface ... http://downloadcenter.intel.com/Defa...ads/&cl=us,en/
980f0000 980f8700   LVUSBSta LVUSBSta.sys Sat Feb 03 12:46:13 2007 (45C4CA65) ... Logitech Camera driver ... http://www.logitech.com/index.cfm/su...oads/&cl=us,en
981ec000 981fb000   RTSTOR   RTSTOR.SYS   Fri May 11 08:09:48 2007 (46445D0C) ... Realtek Card reader ... http://www.realtek.com.tw/downloads/...&GetDown=false
980fb000 98156000   stwrt    stwrt.sys    Wed Jan 02 17:13:25 2008 (477C0C85) ... SigmaTel Audio Driver  ... http://www.freescale.com/webapp/sear...sset=Downloads

Well no new dumps were generated, but looking through your event viewer I see Avast caused one. Avast has been known to cause BSODs before, so that's what I suspect the issue is.

Remove Avast with this tool: http://files.avast.com/files/eng/aswclear5.exe

Install MSE instead. It is also free. http://www.microsoft.com/security_essentialsIf the crashes persist, enable driver verifier: Driver Verifier - Enable and Disable

Be sure to follow our BSOD Posting Instructions sticky again, and run as Administrator.

Thanks for the report.

When running in dual-channel mode, the motherboard needs matching sticks in corresponding slots.

Glad you got it figured out.