W7 New Build Crash...semi NOOB

OK...so I have been building XP boxes for ever and now I just finished my first W7 X64 build. I am getting the BSOD randomly and my gut is thinking it is the video card...don't have a real reason to suspect it...just my gut.

Any hoo here is my system.



MB
GIGABYTE GA-P55A-UD3 LGA 1156 Intel P55 SATA 6Gb/s USB 3.0 ATX Intel Motherboard

CPU
Intel Core i5-750 Lynnfield 2.66GHz LGA 1156 95W Quad-Core Processor BX80605I5750

RAM
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL

VIDEO
MSI N460GTX CYCLONE 1GD5/OC GeForce GTX 460 (Fermi) 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

HD
Western Digital VelociRaptor WD1500HLFS 150GB 10000 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

Optical Drive
ASUS DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner


Power Supply
CORSAIR CMPSU-750TX 750W ATX12V / EPS12V SLI Ready CrossFire Ready

Case
COOLER MASTER HAF 912


I have attached the files as requested in this thread...
https://www.sevenforums.com/crashes-d...tructions.html

I am really at a loss and need this machine sorted so I can use it to finish a big project at work!

Thanks again!

Steve

I would instantly suggest to try this procedure to eliminate already the possibility of a ram related problem.
RAM - Test with Memtest86+

If not done already, I also suggest to update your nvidia drivers to the 260.99.

For more advices, I would wait for more experienced users assistances. Also, make sure all your drivers of all your devices are up to date.

n24re said:

OK...so I have been building XP boxes for ever and now I just finished my first W7 X64 build. I am getting the BSOD randomly and my gut is thinking it is the video card...don't have a real reason to suspect it...just my gut.

Any hoo here is my system.



MB
GIGABYTE GA-P55A-UD3 LGA 1156 Intel P55 SATA 6Gb/s USB 3.0 ATX Intel Motherboard

CPU
Intel Core i5-750 Lynnfield 2.66GHz LGA 1156 95W Quad-Core Processor BX80605I5750

RAM
G.SKILL Ripjaws Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) Desktop Memory Model F3-12800CL9D-4GBRL

VIDEO
MSI N460GTX CYCLONE 1GD5/OC GeForce GTX 460 (Fermi) 1GB 256-bit GDDR5 PCI Express 2.0 x16 HDCP Ready SLI Support Video Card

HD
Western Digital VelociRaptor WD1500HLFS 150GB 10000 RPM SATA 3.0Gb/s 3.5" Internal Hard Drive -Bare Drive

Optical Drive
ASUS DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner


Power Supply
CORSAIR CMPSU-750TX 750W ATX12V / EPS12V SLI Ready CrossFire Ready

Case
COOLER MASTER HAF 912


I have attached the files as requested in this thread...
https://www.sevenforums.com/crashes-d...tructions.html

I am really at a loss and need this machine sorted so I can use it to finish a big project at work!

Thanks again!

Steve

These were caused by hardware. read the whys and what to try here. Your .dmp file shows a stop error of 0x124 which is a general hardware error .. A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint. Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress. You can read more on this error and what to try here... Stop 0x124 - what it means and what to try Stop 0x124 - what it means and what to try

Thanks


Ken

Code:

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


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

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03091e50
Debug session time: Wed Nov 10 19:34:53.413 2010 (GMT-5)
System Uptime: 0 days 0:54:56.234
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80077f0028, f2000000, 20008f}

Probably caused by : hardware

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

1: 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: 0000000000000000, Machine Check Exception
Arg2: fffffa80077f0028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000f2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000020008f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f1a58 fffff800`02e1d903 : 00000000`00000124 00000000`00000000 fffffa80`077f0028 00000000`f2000000 : nt!KeBugCheckEx
fffff880`009f1a60 fffff800`02fda513 : 00000000`00000001 fffffa80`077f1d30 00000000`00000000 fffffa80`077f1d80 : hal!HalBugCheckSystem+0x1e3
fffff880`009f1aa0 fffff800`02e1d5c8 : 00000000`00000728 fffffa80`077f1d30 fffff880`009f1e30 fffff880`009f1e00 : nt!WheaReportHwError+0x263
fffff880`009f1b00 fffff800`02e1cf1a : fffffa80`077f1d30 fffff880`009f1e30 fffffa80`077f1d30 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f1c50 fffff800`02e1cdd5 : 00000000`00000004 00000000`00000001 fffff880`009f1eb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f1c90 fffff800`02e10e88 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f1cc0 fffff800`02ec47ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f1cf0 fffff800`02ec4613 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f1e30 fffff800`02ec4ec0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`01c6eeb8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemCall64


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN

BUCKET_ID:  X64_0x124_GenuineIntel_MEMORY__UNKNOWN

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

Thanks guys!

I will start working my way through the testing and report back!

Steve

OK...so I did some testing and talking to a coworker with way more knowledge than me. Seems the Gigabyte MB comes out of the box with the BIOS setting for overclocking the memory. I have adjusted everything back to normal or fail-safe mode and the machine has been running great.

I also ran SiSoftware Sandra benchmarking...not for the data but for the stress test it gives the box...and so far no BSOD!

I really hope it was just a DIM voltage or frequency issue with the BIOS settings. I will keep this thread up to date as I find out more.

Cheers'

Steve

OK... so I thought I would post this if even only for my records. The system is now running flawlessly as I found the BIOS to be set to extreme overclocking mode. Seems that GIGABYTE ships this mother board ( GIGABYTE GA-P55A ) with the BIOS setting defaulted to the extreme setting.

It is odd to me that they would do this but anyways after setting all the setting to a more conservative setup I have a super running machine. Thank you guys so much for the information!

All the best

Steve