Keep getting BSOD!!!

[Saintranger]

Trying to find out what is wrong. I've taken out hard drives, sticks of memory and even changed graphic cards. Still getting when rendering in AE CS5.5 and rendering videos I've edited. Sometimes I am just browsing the net and it crashes. Any help would be appreciated.

Here are my specs:
Model: 3DBOXX Special Edition
Model Specifications:

FBDIMM ECC DDR2-667-800Mhz
. . (4) FBDIMM Slots
(6) Serial ATA ports
. . (RAID 0, 1)
(2) External Serial ATA ports
(1) Parallel ATA IDE interface
. . (2 devices)
(1) Gigabit Ethernet ports
HD Audio
. . Front panel mic + audio out
(2) IEEE1394a Ports:
(1) Front (1) Rear
(8) USB 2.0 Ports:
(2) Front, (6) Rear
1,000 W Power Supply
4U: 7"w x 17"h x 18"d

Expansion options:
(4) 3.5" hard drive bays
(2) 5.25" drive bays
(4) PCI Express x16
(2) PCI

Configuration as Built:

Base Builds

W8454SE-0-AW (ROHS)Operating System

Windows XP Professional Edition with SP2CCPU

WS Intel Dual Quad Core Enhanced Performance (LC)Memory

4GB FBDIMM DDR2 800 REG ECC (4 - 1GB FBDIMMS)Video Cards

NVIDIA Quadro FX 570 PCI-E (R)Hard Drives
250GB 7,200rpm SATA (SUB)
80GB 7,200rpm SATA (SUB)
Floppy, CD, DVD Drives

Dual Layer 20X DVD±RW Writer (SUB)(R)Kybds, Mice, Spkrs
Logitech MX 400 Corded Mouse (R)
USB Logitech Keyboard (R)
Misc. Peripherals
USB External Floppy Drive (R)

 

[JMH]

Stop 0x124 is a hardware error.... if you are overclocking try resetting your processor to standard settings and see if that helps ... if you continue to get BSOD here are some more things you may want to consider ..

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. Otherwise, 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/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[Saintranger]

How do I reset my processor to standard settings? Never messed with the BIOS much. Just to set boot sequence.

 

[JMH]

If you don't know what Overclocking is you have not altered anything.

FYI.
Overclocking - Wikipedia, the free encyclopedia

 

[Saintranger]

I think I screwed up really bad. I know the company that built the computer had overclocked it. But I just set the BIOS to defaults and now it has a blue screen that says MACHINE_CHECK_EXCEPTION. WON'T EVEN BOOT UP

 

[zigzag3143]

I think I screwed up really bad. I know the company that built the computer had overclocked it. But I just set the BIOS to defaults and now it has a blue screen that says MACHINE_CHECK_EXCEPTION. WON'T EVEN BOOT UP

Is it under warranty?

If not you can try a "cmos" battery reset. I am betting you wished you had backed up right about now, but unplug the computer from the wall and hold the power button in for 1 minute.

Plug it back in and test.

If it still isnt working please provide the make and model so we can investigate.

 

[Saintranger]

No not under warranty. Just went out in September. As for as backing up I don't have any files on the hard drive except for software installed. All files are on an external drive. Everything about my CPU is listed above in the thread. I will try the CMOS thing you suggested

 

[Saintranger]

CMOS battery reset did not work. I did install a 1tb hard drive two months ago and installed 7 ultimate. Did have xp pro before.

 

[zigzag3143]

No not under warranty. Just went out in September. As for as backing up I don't have any files on the hard drive except for software installed. All files are on an external drive. Everything about my CPU is listed above in the thread. I will try the CMOS thing you suggested

OK I cant find any information about your system, but most system have a bios reset jumper. When one wants to reset to factory one moves the jumper waits a bit then moves it back

Please see the owners manual on the correct procedure for your system (of better yey contact the mfr)

 

[Saintranger]

Ok. I will have to call Boxx Tech. Or can I just reinstall 7?

 

[Saintranger]

I just know it's an intel something.

 

[zigzag3143]

Ok. I will have to call Boxx Tech. Or can I just reinstall 7?

How can you install win 7 if you cant get it to boot?