Need Help Identifying problem Bluescreen Error Messages

I've had my new computer since end of October and bar two days have experienced the 'Bluescreen' error messages at least once a day after a computer crash and re-start. I have made no hardware changes since it was built and tested by Shuttle and the OS was installed by the dealer.
I'm running Windows 7 64-bit and have added very little software since it arrived. A summary of my computers hardware is below with the detailed system information in the file 'SystemInformation.zip' if that helps. I also attach a copy of my Minidump folder in the file 'Minidump.zip'.

Can anyone help ??

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ALAN-PC
System Manufacturer Shuttle Inc.
System Model SX58
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz, 3068 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 080016, 21/05/2009
SMBIOS Version 2.5
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7600.16385"
User Name Alan-PC\Alan
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 6.00 GB
Total Physical Memory 5.99 GB
Available Physical Memory 4.47 GB
Total Virtual Memory 12.0 GB
Available Virtual Memory 10.2 GB
Page File Space 5.99 GB
Page File C:\pagefile.sys

PopeyeMills said:

I've had my new computer since end of October and bar two days have experienced the 'Bluescreen' error messages at least once a day after a computer crash and re-start. I have made no hardware changes since it was built and tested by Shuttle and the OS was installed by the dealer.
I'm running Windows 7 64-bit and have added very little software since it arrived. A summary of my computers hardware is below with the detailed system information in the file 'SystemInformation.zip' if that helps. I also attach a copy of my Minidump folder in the file 'Minidump.zip'.

Can anyone help ??

OS Name Microsoft Windows 7 Ultimate
Version 6.1.7600 Build 7600
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ALAN-PC
System Manufacturer Shuttle Inc.
System Model SX58
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz, 3068 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 080016, 21/05/2009
SMBIOS Version 2.5
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7600.16385"
User Name Alan-PC\Alan
Time Zone GMT Standard Time
Installed Physical Memory (RAM) 6.00 GB
Total Physical Memory 5.99 GB
Available Physical Memory 4.47 GB
Total Virtual Memory 12.0 GB
Available Virtual Memory 10.2 GB
Page File Space 5.99 GB
Page File C:\pagefile.sys

I took a quick look at 2 of your dumps both were identical. The dugcheck 124, the hal.dll file, and the memory corruption is indicative of a hardware problem.

I would first download and run memtestx86 overnight.
Run a system file check by typing cmd in search>right click and run as admin>then type SFC /scannow

let us know the results

I would also
If overclocking stop
if you are running a raid upgrade the driver.
Upgrade bios, and video.

There are several drivers that are from 2006-2008


Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\110909-16255-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`0303ee50
Debug session time: Mon Nov 9 13:19:17.485 2009 (GMT-5)
System Uptime: 0 days 0:25:33.485
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {4, fffffa80062a88d8, 0, 0}

Probably caused by : hardware

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

6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: fffffa80062a88d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x124_4

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 6

STACK_TEXT:
fffff880`0313da78 fffff800`033f0903 : 00000000`00000124 00000000`00000004 fffffa80`062a88d8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0313da80 fffff800`02f87513 : 00000000`00000001 fffffa80`054c20c0 00000000`00000000 fffffa80`054c1b70 : hal!HalBugCheckSystem+0x1e3
fffff880`0313dac0 fffff880`00f5daff : fffffa80`00000750 fffffa80`054c20c0 00000000`00000000 fffffa80`062a8010 : nt!WheaReportHwError+0x263
fffff880`0313db20 fffff880`00f5d526 : 00000000`00000000 fffff880`0313dc70 fffffa80`06338d80 fffff880`0313dbf0 : pci!ExpressRootPortAerInterruptRoutine+0x27f
fffff880`0313db80 fffff800`02e6ecfc : fffff880`03115180 fffff880`0313dc70 fffffa80`06338d80 00000000`00000001 : pci!ExpressRootPortInterruptRoutine+0x36
fffff880`0313dbf0 fffff800`02e7b6d2 : fffff880`03115180 fffff880`00000001 00000000`00000001 fffff800`00000000 : nt!KiInterruptDispatch+0x16c
fffff880`0313dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x32


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_4_PCIEXPRESS

BUCKET_ID: X64_0x124_4_PCIEXPRESS

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

OK Thanks. Will run Memtest86 overnight as you suggest. Although it already passed the Windows 7 memory test.

1. Result of SFC scan - Windows Resource Protection found no integrity violations.
2. Checked all the device drivers in Device Manager and they all seem to be up to date.
3. Not running in RAID configuration - just 2 identical Seagate 500 Gb's.
4. Not overclocking anything to my knowledge. Certainly haven't changed anything since built by ICubes.
5. Computer bought in October - BIOS last updated by Shuttle in May 2009. But I will check it.
6. Video is up to date.

Thank you for your thoughts, will update tomorrow after the Memtest.

Don't know what a dugcheck 124 is, or the importance of the hal.dll file which seems to be from Microsoft. Is this significant?

PopeyeMills said:

OK Thanks. Will run Memtest86 overnight as you suggest. Although it already passed the Windows 7 memory test.

PopeyeMills,

from my experience I can tell that your memory may pass the win 7 memory test even if it is faulty. when I tested my defective 2 GB DIMM together with another 2GB DIMM that works fine, even MemTest86 ran for over 12 hours without a single error. so if I may give you an advice, I would suggest to test your RAM modules one at a time - that way you will get the most reliable results.

check out this thread for the full chronology of my odyssey.

good luck,
~sahib

Thanks to zigzag3143, wallyincc and sahib for their suggestions.
The situation at present is that neither Windows 7 memory test or an overnight run of Memtest86 revealed any errors (despite 9 passes).
The motherboard BIOS is the most current available.
The video driver is the up to date although its a Microsoft approved one. Will check ATI's site for something more recent.

Haven't had a crash since yesterday, which is a relief, and from the forums it would seem I am not alone in the world, although that's hardly comforting.

Will try Wallyincc's suggestion first as that is probably the easiest to try.
I have read elsewhere on this site that there is some Memtest can find errors on memory chips when they are tested one at a time, so will try sahib's suggestion if re-seating the graphics card doesn't bring any improvement.

Thanks again.

No sooner had I posted a reply on a day without a Bluescreen crash, and guess what. 5 minutes later and I'm struck again, just as I was downloading what seems to be a more recent graphic driver from Sapphire.

If anyone would care to look I have attached the MiniDump file.
No error message on re-start, just the message 'Windows has recovered from an unexpected shutdown'. And that has been on the screen for the last 10 minutes.

The minidump file.......

Reboot into safe mode + networking.

Download the latest driver for the card from ATI's site. Extract it to C:\ATI. Close installer after it extracts.

In device manager, right click on the card. Update driver software. Browse my computer. Let me pick. Have disk. Browse. Double click on the first .inf when viewed in alphabetical order, somewhere inside C:\ATI

Hit ok, maybe next after...let it install. When done, reboot to Windows normal mode and hopefully enjoy the new driver.

Latest Update.
Windows 7 crashed again. This time did not restart and didn't get an error message after switch off and on.
MiniDump file attached if anyone can help.

I have tried reseating the graphics card.
I have installed the latest graphic driver from ATI under safe mode with networking.
I have tested the memory chips seperately, using Memtest, over the course of a day without error.

Nothing tried seems to help. I have noted that alot (but not all) of the crashes seem to occur about 10 mins after startup. What that could mean I don't know.

Anybody??