BSOD at church

[Abstract Art]

This machine is at my church and has been giving us fits since the first of the year. I've gotten BlueScreenView which has helped but my tech skills are not enough to really understand what is going on. I've done some low tech stuff (Memtest86+ and trying to cool the CPU) but that hasn't worked. So I joined the forum to get expert advice.

Perfmon's report is inside the folder in the zipped file.

System specs:
Windows 7 Home Premium Service Pack 1 (auto updates are turned on)
Processor: Intel (R) Core (TM) i7 CPU 920 @ 2.67 GHz
Installed RAM: 8 GB
System type: 64-bit
Video Card: ATI Raedon HD 4600
This is a Dell XPS desktop 435MT box.

We run the presentation software of MediaShout 4.5.0.211.
Antivirus is ESET NOD32 4.0.474.0

Neither MediaShout nor NOD32 were running when I ran the diagnostic software.

 

[Maguscreed]

This is obviously the work of the devil. I suggest a prayer vigil. (sorry couldn't resist)

Okay seriously.
What you are experiencing here doesn't look good. The MCE (Machine_Check_Exception) error almost always means hardware has been damaged.
This is the error the bugchecks are producing.

There is a very slight possibility that ESET is blocking instruction sets it shouldn't be, and this is leading to the error.
There is no other software possibility I see here that could be causing it though.

There is a small possibility this is caused by incorrect bios settings, though I doubt it.

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

MACHINE_CHECK_EXCEPTION (9c)
A fatal Machine Check Exception has occurred.
KeBugCheckEx parameters;
    x86 Processors
        If the processor has ONLY MCE feature available (For example Intel
        Pentium), the parameters are:
        1 - Low  32 bits of P5_MC_TYPE MSR
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of P5_MC_ADDR MSR
        4 - Low  32 bits of P5_MC_ADDR MSR
        If the processor also has MCA feature available (For example Intel
        Pentium Pro), the parameters are:
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    IA64 Processors
        1 - Bugcheck Type
            1 - MCA_ASSERT
            2 - MCA_GET_STATEINFO
                SAL returned an error for SAL_GET_STATEINFO while processing MCA.
            3 - MCA_CLEAR_STATEINFO
                SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
            4 - MCA_FATAL
                FW reported a fatal MCA.
            5 - MCA_NONFATAL
                SAL reported a recoverable MCA and we don't support currently
                support recovery or SAL generated an MCA and then couldn't
                produce an error record.
            0xB - INIT_ASSERT
            0xC - INIT_GET_STATEINFO
                  SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
            0xD - INIT_CLEAR_STATEINFO
                  SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
            0xE - INIT_FATAL
                  Not used.
        2 - Address of log
        3 - Size of log
        4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
    AMD64 Processors
        1 - Bank number
        2 - Address of MCA_EXCEPTION structure
        3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
        4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
Arguments:
Arg1: 0000000000000000
Arg2: fffff8800311dc70
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x9C_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

LAST_CONTROL_TRANSFER:  from fffff800037fb818 to fffff8000327fd00

STACK_TEXT:  
fffff880`0311dc38 fffff800`037fb818 : 00000000`0000009c 00000000`00000000 fffff880`0311dc70 00000000`00000000 : nt!KeBugCheckEx
fffff880`0311dc40 fffff800`037faf57 : 00000000`00000008 00000000`00000000 00000000`00000008 00000000`00000000 : hal!HalpMcaReportError+0x164
fffff880`0311dd90 fffff800`037eee88 : 00000000`00000001 fffff880`03115180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x9f
fffff880`0311ddc0 fffff800`0327e5ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`0311ddf0 fffff800`0327e453 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`0311df30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!KxMcheckAbort+6c
fffff800`0327e5ec 488d8c2400010000 lea     rcx,[rsp+100h]

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nt!KxMcheckAbort+6c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4d9fdd5b

FAILURE_BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

BUCKET_ID:  X64_0x9C_GenuineIntel_nt!KxMcheckAbort+6c

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

 

[Abstract Art]

This is obviously the work of the devil. I suggest a prayer vigil. (sorry couldn't resist)

Okay seriously.
What you are experiencing here doesn't look good. The MCE (Machine_Check_Exception) error almost always means hardware has been damaged.
This is the error the bugchecks are producing.

"Hardware. Why did it have to be hardware?"

There is a very slight possibility that ESET is blocking instruction sets it shouldn't be, and this is leading to the error.
There is no other software possibility I see here that could be causing it though.

There is a small possibility this is caused by incorrect bios settings, though I doubt it.

On May 1 I have updated the BIOS via Dell from 1.1.1 to 1.1.4.

We'll run for a bit without the ESET NOD Antivirus. If we unplug from the network we should not have any problems.

 

[The Howling Wolves]

How about restoring machine back to when it was working properly...Before the bios update?
Something I would consider IMHO
Say Ten Hail Mary's and sprinkle Holy Water near not on the machine...

 

[Abstract Art]

How about restoring machine back to when it was working properly...Before the bios update?
Something I would consider IMHO

I first started logging stuff on this machine back in January. It failed several times before I updated the BIOS, so I don't think setting it back to what it was will fix anything. No one that works in the tech booth has the knowledge or guts to try to mess with the BIOS, so I'm pretty sure it hasn't been touched since we got this machine.

Say Ten Hail Mary's and sprinkle Holy Water near not on the machine...

This box went BSOD again tonight during a special CD Breakout/Announcement party/concert for the group FourTwelve.

Sorry, but no one here is considering Holy Water. They tend to favor instead the Holy Hand Gernade of Antioch.

 

[The Howling Wolves]

Once last effort...
http://www.sevenforums.com/tutorials/92394-sf-diagnostic-tool-using-troubleshooting.html

Give this a go and see if it pin points your problem. IMHO
I am not a BIOS tech!
THW

 

[Abstract Art]

Once last effort...
http://www.sevenforums.com/tutorials/92394-sf-diagnostic-tool-using-troubleshooting.html

Give this a go and see if it pin points your problem. IMHO
I am not a BIOS tech!
THW

Attached are the dump files and other things. I did not include the log files, they would have been too big.