Need urgent suggestions

[Reclaimer1991]

Hey guyz...

I have an old pc.From last a week or so, it suddenly started giving hardware related Windows BCCodes(like 116, 124) out of the blue. It started with not detecting the GPU(which i surely know is working fine), then parity circuit error beeps, etc.

But still it worked fine after reinstalling the components.

Last night, it has stopped booting itself.

After I press the power-on button, front panel led lights up, fans start spinning but then after 2-3 seconds everything stops without rebooting(no POST, no BIOS SCREEN, no beep codes).

My best guess is that the motherboard is dead. I don't have alternate motherboard to test.

I don't think my CPU is dead coz I have never OCed my CPU, hence a burnt Intel CPU is highly unlikely.

Can you guys suggest whats going on?

Any help is appreciated.

Thank you.

[Castdeath97]

What is your full specs including your power supply. And please use paragraphs your text is confusing.

[Aytex]

Stop 0x124 - what it means and what to try
Synopsis:

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.


Generic "Stop 0x124" Troubleshooting Strategy:

1) Ensure that none of the hardware components are overclocked. Hardware that is driven beyond its design specifications - by overclocking - can malfunction in unpredictable ways.


2) Ensure that the machine is adequately cooled.
If there is any doubt, open up the side of the PC case (be mindful of any relevant warranty conditions!) and point a mains fan squarely at the motherboard. That will rule out most (lack of) cooling issues.


3) Update all hardware-related drivers: video, sound, RAID (if any), NIC... anything that interacts with a piece of hardware. 
It is good practice to run the latest drivers anyway.


4) Update the motherboard BIOS according to the manufacturer's instructions. 
Their website should provide detailed instructions as to the brand and model-specific procedure.


5) Rarely, bugs in the OS may cause "false positive" 0x124 events where the hardware wasn't complaining but Windows thought otherwise (because of the bug). 
At the time of writing, Windows 7 is not known to suffer from any such defects, but it is nevertheless important to always keep Windows itself updated.

6) Attempt to (stress) test those hardware components which can be put through their paces artificially. 
The most obvious examples are the RAM and HDD(s). 
For the RAM, use the in-built memory diagnostics (run MDSCHED) or the 3rd-party memtest86 utility to run many hours worth of testing.
For hard drives, check whether CHKDSK /R finds any problems on the drive(s), notably "bad sectors". 
Unreliable RAM, in particular, is deadly as far as software is concerned, and anything other than a 100% clear memory test result is cause for concern. Unfortunately, even a 100% clear result from the diagnostics utilities does not guarantee that the RAM is free from defects - only that none were encountered during the test passes.

7) As the last of the non-invasive troubleshooting steps, perform a "vanilla" reinstallation of Windows: just the OS itself without any additional applications, games, utilities, updates, or new drivers - NOTHING AT ALL that is not sourced from the Windows 7 disc.
Should that fail to mitigate the 0x124 problem, jump to the next steps. 
If you run the "vanilla" installation long enough to convince yourself that not a single 0x124 crash has occurred, start installing updates and applications slowly, always pausing between successive additions long enough to get a feel for whether the machine is still free from 0x124 crashes. 
Should the crashing resume, obviously the very last software addition(s) may be somehow linked to the root cause.
If stop 0x124 errors persist despite the steps above, and the harware is under warranty, consider returning it and requesting a replacement which does not suffer periodic MCE events. 
Be aware that attempting the subsequent harware troubleshooting steps may, in some cases, void your warranty:

8) Clean and carefully remove any dust from the inside of the machine. 
Reseat all connectors and memory modules. 
Use a can of compressed air to clean out the RAM DIMM sockets as much as possible.

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. 
Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Should you find yourself in the situation of having performed all of the steps above without a resolution of the symptom, unfortunately the most likely reason is because the error message is literally correct - something is fundamentally wrong with the machine's hardware.

 

http://www.sevenforums.com/bsod-help-support/225425-bccode-116-124-a.html

[Aytex]

I would have to say that is a good possibility.  The Stop 0x116 is usually video related and the stop 0x124 means a hardware error was reported to the processor.

 

I would start trying to remove some of these pieces from the puzzle until it starts working.

[Reclaimer1991]

What is your full specs including your power supply. And please use paragraphs your text is confusing.

Intel Q8400 @2.66 GHz

MSI P7NGM-DIGITAL(GEFORCE 9300 CHIPSET)

2X2GB DDR2 @800 MHz

Seagate 320GB HDD @ 7200 RPM

PSU : VIP GOLD 600W

nothing was ever overclocked.

New to this forum.

[Reclaimer1991]

I would have to say that is a good possibility.  The Stop 0x116 is usually video related and the stop 0x124 means a hardware error was reported to the processor.

 

I would start trying to remove some of these pieces from the puzzle until it starts working.

Its not even giving any beep codes so is mobo dead?

i mean bios gives these codes right? so if the bios itself is done nothing would start?

[Aytex]

Its not even giving any beep codes so is mobo dead?

i mean bios gives these codes right? so if the bios itself is done nothing would start?

prolly your gpu and ur hardware is screwed up

[Reclaimer1991]

prolly your gpu and ur hardware is screwed up

by hw u mean mobo and cpu too?

[Aytex]

by hw u mean mobo and cpu too?

idk dude tbh 

[Reclaimer1991]

Replaced the PSU.

 

But, still while trying to play FHD/60fps videos using CUDA, the display shuts off and PC reboots.

 

After reboot this is the info shown by Windows :

 

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1033

Additional information about the problem:
  BCCode:    124
  BCP1:    0000000000000000
  BCP2:    FFFFFA8004AAB038
  BCP3:    0000000000000000
  BCP4:    0000000000000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

 

I am fed up by this problem.
 

[Reclaimer1991]

What is your full specs including your power supply. And please use paragraphs your text is confusing.

Replaced the PSU.

 

But, still while trying to play FHD/60fps videos using CUDA, the display shuts off and PC reboots.

 

After reboot this is the info shown by Windows :

 

Problem signature:

  Problem Event Name:    BlueScreen

  OS Version:    6.1.7601.2.1.0.256.48

  Locale ID:    1033

Additional information about the problem:

  BCCode:    124

  BCP1:    0000000000000000

  BCP2:    FFFFFA8004AAB038

  BCP3:    0000000000000000

  BCP4:    0000000000000000

  OS Version:    6_1_7601

  Service Pack:    1_0

  Product:    256_1

 

I am fed up by this problem.