Where do I start? So many errors..

silkw7 · 12 May 2011

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.

mgorman87 · 12 May 2011

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 (42476C4C)

A known BSOD maker in Windows 7. The 2005 version of this driver is known to cause BSOD on Windows 7 systems.
Download the ATK0110 utility from here - ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE.
After you install it browse to C:\windows\system32\drivers and check the properties of ASACPI.sys and make sure it now says 2009.

Please disable your overclocking for now and see if the system stabilizes.

Code:

Event[462]:
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2011-05-12T08:35:00.604
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: SilkPC
  Description: 
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Internal Timer Error
Processor ID: 6

The details view of this entry contains further information.

This error happens frequently in your event logs

Please run these tests and report back the results
1. Memtest86 - Run for 7-8 passes - RAM - Test with Memtest86+
2. Prime95 - Run all three tests for 3-4 hours each or until fail - https://www.sevenforums.com/tutorials...t-prime95.html
3. Hard drive scan usings SeaTools - SeaTools for Windows | Seagate - Both long and short tests

BSOD BUGCHECK SUMMARY

Code:


Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Debug session time: Thu May 12 17:17:56.055 2011 (UTC - 4:00)
System Uptime: 0 days 4:24:44.914
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_intelppm+39c2
BiosReleaseDate = 07/15/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 4200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed May 11 18:11:45.006 2011 (UTC - 4:00)
System Uptime: 0 days 0:22:50.865
Probably caused by : hardware ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BiosReleaseDate = 07/15/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 4200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Wed May 11 16:40:12.607 2011 (UTC - 4:00)
System Uptime: 0 days 3:43:34.466
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : atikmdag.sys ( atikmdag+e3035 )
PROCESS_NAME:  System
BUGCHECK_STR:  0xD1
FAILURE_BUCKET_ID:  X64_0xD1_CODE_AV_BAD_IP_atikmdag+e3035
BiosReleaseDate = 07/15/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 4200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Debug session time: Tue May 10 16:44:51.567 2011 (UTC - 4:00)
System Uptime: 0 days 0:10:34.426
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : intelppm.sys ( intelppm+39c2 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_intelppm+39c2
BiosReleaseDate = 07/15/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 4200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat May  7 11:49:26.759 2011 (UTC - 4:00)
System Uptime: 0 days 2:07:56.618
Probably caused by : hardware ( nt! ?? ::FNODOBFM::`string'+40f90 )
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
BiosReleaseDate = 07/15/2009
SystemManufacturer = System manufacturer
SystemProductName = System Product Name
CPUID:        "Intel(R) Core(TM) i7 CPU         930  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 4200
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

silkw7 · 19 May 2011

Thanks mgorman87..

Just an update,

Went through the tests but nothing unusual was revealed.

However I did turn OC off, and games seem to not crash anymore. It's a guaranteed overclock though (which *was* working fine) so I'm chasing this up with the folks I bought it off.