Tech Support Forum banner
Status
Not open for further replies.
1 - 7 of 7 Posts

·
Registered
Joined
·
5 Posts
Discussion Starter · #1 ·
1. OS - Windows 7 ?
2. x64
3. see number 1
4. I've installed it myself.
· Graphic aobut 2 years, same Power Supply, rest is about 1 week old.
· I've tried reintalling OS
· CPU AMD Phenom II x4 955 - (it's not overheating)
· Palit GTX260 sp216
· ASUS M4A79XTD EVO
· Modecom 500W (the better one)

Ok, here's the deal, i've tried reinstalling os, i had bad sectors on HDD, soo i bought a new one. Graphic and Power supply worked well on old pc. I'm getting bsods 124 after like 30minutes of playing. It doesn't matter if I play Dead Space 2 or Minecraft. Sometimes there is no BSOD, pc just frezzes, and i need to wait about 5 minutes before i can reset it.

I'm not getting bsods during tests like Orthos, Prime or memtest.
I thought it was because of Deamon Tools, soo I removed it - not worked.
I thought it was beacuse of Kaspersky - same.
I thought it was because of Power Supply, soo i borrowed 600w corsair from a friend -same.

Please help me.

ps. I'm running driver verifier right now, no bsod during "not-playing".
ps2. I think that my graphic card may be overheating, but how is this possible playing Minecraft? (i know that fans are working quite good)
 

Attachments

·
Registered
Joined
·
5 Posts
Discussion Starter · #2 ·
Re: BSOD 124 while gaming

update: been running FurMark xtremeburning mode for about 10minutes, gpu went up to the 89 celcius. No more, no bsod. I'm thinking about motherboard nwo, maybe it's defective.
 

·
Registered
Joined
·
5 Posts
Discussion Starter · #3 ·
Re: BSOD 124 while gaming

after removing one of my 2gb rams, i was able to play Dead Space 2 for about 20 minutes, then pc shuted down, and i had to wait like 5minutes to start it, otherwise power button just din't work.
 

·
Administrator, Manager, Microsoft Support, MVP
Joined
·
34,403 Posts
Re: BSOD 124 while gaming

Bugcheck on both dumps = 0x124 = WHEA = Machine Check Exception

Probable cause listed as "hardware"

The WHEA error record detail -

Code:
[font=lucida console]

1: kd> !errrec fffffa8004c71748
===============================================================================
Common Platform Error Record @ fffffa8004c71748
-------------------------------------------------------------------------------
Record Id     : 01cbe5a2e43154e3
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 3/18/2011 19:30:14
Flags         : 0x00000002 PreviousError

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004c717c8
Section       @ fffffa8004c718a0
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : BUS error
Operation     : Generic
Flags         : 0x00
Level         : 3
CPU Version   : 0x0000000000100f43
Processor ID  : 0x0000000000000000

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004c71810
Section       @ fffffa8004c71960
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000000
CPU Id        : 43 0f 10 00 00 08 04 00 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa8004c71960

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa8004c71858
Section       @ fffffa8004c719e0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 4)
  Status      : 0xfa00000000070f0f
[/font]

I'm moving thread to Hardware Support Forum.

Regards. . .

jcgriff2


.

BSOD BUGCHECK SUMMARY
Code:
[font=lucida console]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Fri Mar 18 15:30:14.396 2011 (GMT-4)
System Uptime: 0 days 0:00:07.567
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04c71748 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Thu Mar 17 17:24:19.256 2011 (GMT-4)
System Uptime: 0 days 0:00:06.801
Probably caused by : hardware
BUGCHECK_STR:  0x124_AuthenticAMD
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_BUS_PRV
Bugcheck code 00000124
Arguments 00000000`00000000 fffffa80`04cee748 00000000`00000000 00000000`00000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  


  [/font]
 

·
Emeritus
Joined
·
51,675 Posts
First thought has to be the 2 yr. old 500W PSU. I've never heard of that brand and 500W is not sufficient for a GTX 260. You should be at 650Wor above with a good quality PSU.
From MS: 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.
 
1 - 7 of 7 Posts
Status
Not open for further replies.
Top