New
#1
Where do I start? So many errors..
Hi folks.. I wondered if you could help me.
I've got what used to be a pretty solid system, ran stable for 10 months. It's now 13 months old. Mobo, ram, cpu+heatsink are all from ocuk in a guaranteed oc'd bundle.
A few weeks ago I started getting intermittent BSODs. I'm not sure if this is a coincidence but shortly before it started happening, my better half accidentally spilt liquid (beer) over her desk, and some fell onto the top of my case onto a fan grille. Some (very little) liquid did get inside, but not much. I did power down immediately, nothing blew up, no sparks or smoke etc.
I've done a fresh install of windows since then, and can generally play 30-60 minutes before a BSOD. When idle it doesn't seem to crash at all.
I'm hoping that I can find out if any components are damaged, or if it's a software issue, by posting all the logs up here and consulting your brains. So far the logs suggest software issues but I've yet to find the cause. I guess I am realllly hoping it's software but even if it's hardware it'd be nice to know what I need to replace. So far these random errors aren't telling me anything.
There's also a rather large dump in C:\Windows, can't attach it here but got a bit of info from "WhoCrashed":
On Thu 12/05/2011 21:17:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: intelppm.sys (intelppm+0x39C2)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\intelppm.sys
product: Microsoftฎ Windowsฎ Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.
Note that this overwrote a prior dump of an atisys driver error.
Things I've tried:
New C: drive
Format, reinstall win 7 (home full retail 64 bit)
Disable onboard sound
Disable HDMI soundoutput on gfx card
Turn off overclocking
What I haven't done in is update BIOS as it'd invalidate my overclock warranty. And I haven't tried swapping graphics cards yet. Anyways, it's a shot in the dark but maybe someone will spot something I haven't in the dumps.