BSOD while playing Borderlands x64 (not a known issue)

[player66]

Attached are my logs of this issue. It happens when I'm in-game anywhere from 5-30 minutes. This is a brand new machine with a clean install of Win 7 64 bit. Please help.

System Manufacturer/Model Number
N/A (self-built)
OS
Windows 7 64-bit
CPU
AMD Athlon II X4 620 Propus 2.6GHz
Motherboard
MSI NF750-G55 AM3 NVIDIA nForce 750a SLI
Memory
4GB DDR3 1600MHz A-DATA
Graphics Card(s)
[BFG Tech] Nvidia GeForce GTS 250
Sound Card
On-board sound via n-force chipset.

 

[sup3rsprt]

your dumps point to a hardware issue.

What power supply do you have? Are you doing any overclocking? Have you set the proper memory voltage and timings?

You could try doing a hardware stress test and/or a memory test overnight.

 

[zigzag3143]

Attached are my logs of this issue. It happens when I'm in-game anywhere from 5-30 minutes. This is a brand new machine with a clean install of Win 7 64 bit. Please help.

System Manufacturer/Model Number
N/A (self-built)
OS
Windows 7 64-bit
CPU
AMD Athlon II X4 620 Propus 2.6GHz
Motherboard
MSI NF750-G55 AM3 NVIDIA nForce 750a SLI
Memory
4GB DDR3 1600MHz A-DATA
Graphics Card(s)
[BFG Tech] Nvidia GeForce GTS 250
Sound Card
On-board sound via n-force chipset.

Player

I took a quick look at the first 3 dumps. they were exactly the same. all probably caused by hardware. either an old driver or a deivce that isnt completely compatible.

suggest
If overclocking STOP
download a memory stress test like memtestx86
run a system file check by typing cmd into search>right click and run as admin>
SFC /scannow


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


Loading Dump File [C:\Users\K\Desktop\102909-19046-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 (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a00000 PsLoadedModuleList = 0xfffff800`02c3de50
Debug session time: Thu Oct 29 20:17:15.953 2009 (GMT-4)
System Uptime: 0 days 0:00:16.453
Loading Kernel Symbols
................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa80057e78f8, 0, 0}

Probably caused by : hardware

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

2: 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: fffffa80057e78f8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`02faf6f0 fffff800`02cbaa89 : fffffa80`057e78d0 fffffa80`039f9680 00000000`0000000b 00000000`00000001 : nt!WheapCreateLiveTriageDump+0x6c
fffff880`02fafc10 fffff800`02b9c547 : fffffa80`057e78d0 fffff800`02c155f8 fffffa80`039f9680 00000002`00000005 : nt!WheapCreateTriageDumpFromPreviousSession+0x49
fffff880`02fafc40 fffff800`02b04b95 : fffff800`02c77360 fffffa80`04553828 fffffa80`04553820 fffffa80`039f9680 : nt!WheapProcessWorkQueueItem+0x57
fffff880`02fafc80 fffff800`02a7f161 : fffff880`010c6e00 fffff800`02b04b70 fffffa80`039f9680 00000000`00000000 : nt!WheapWorkQueueWorkerRoutine+0x25
fffff880`02fafcb0 fffff800`02d15166 : 00000000`00000000 fffffa80`039f9680 00000000`00000080 fffffa80`0396c9e0 : nt!ExpWorkerThread+0x111
fffff880`02fafd40 fffff800`02a50486 : fffff880`02d63180 fffffa80`039f9680 fffff880`02d6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02fafd80 00000000`00000000 : fffff880`02fb0000 fffff880`02faa000 fffff880`035ba540 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

FAILURE_BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

BUCKET_ID: X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV

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

 

[player66]

Thanks for your suggestions. I'll run the tests tonight.

On the power supply, I have a 450w (Rhino SP-450Y) supply. I'll try a larger, possibly more reliable one.

 

[player66]

I just found the Corsair 750w is on sale at Fry's. Hopefully that will be a good replacement. If the other issues are the cause, at least I'll have a better supply.

 

[player66]

The "sfc /scannow" memory scan didn't find any "integrity violations". That's one down.

 

[player66]

Have you set the proper memory voltage and timings?

You could try doing a hardware stress test and/or a memory test overnight.

I haven't done any OC'ing. Would the default memory settings work without requiring any special configuration?

What should I use for a hardware stress test? I ran "sfc /scannow" for a memory test and it came up without issue.

 

[player66]

Okay, I'm officially frustrated. The new 750w power supply didn't fix the crash. I'm running out of ideas. Can someone suggest further tests? I don't have a different GPU to swap out for a quick check to see if it's the BFG Tech GeForce GTS 250.

 

[usasma]

Try the Windows 7 Upgrade advisor (free here: Download details: Windows 7 Upgrade Advisor )

Double check all of your connections on the inside of the system (I had a STOP 0x124 on a Vista machine at work yesterday due to an improperly inserted video card).

Research all of your drivers and install the most up to date Windows 7 drivers that you can find. If Win7 drivers aren't available, install Windows Vista drivers in compatibility mode for ALL USERS to both Run as Windows Vista and to Run as adminsitrator.
Disconnect anything that you absolutely do not need on the system (to rule those devices out).

STOP 0x124 errors are hardware problems that are reported to Windows by your hardware - as such they're not that easy to decipher. But, they are primarily hardware errors - and normally point to either a hardware failure or to a compatibility problem..

 

[Machone]

I have the same thing happing to me now. The only differece is XFX 5770. I tired alot of ideas already. I dont know what to do after I dumped all this money!