Member Avatar for GriffIT34

Anyone have any experience with "machine exception errors, I've googled it and get a few corses of action but i'm looking to narrow it down. I've got a foxconn mobo 6150, aspire x-pac case, 2gb OCZ ram, AMD athlon 1.8ghz cpu.

I can test or replace the ram
replace the power supply with something more powerful

I don't think it has to do with the temp. I have gauges run and both the cpu and hard drives never really get above 32 degrees celcius.

Or is there some random hardware problem, mobo, d-link wireless, seagate hard drives, the OCZ ram, or my amd chip??????or the powersupply can't power the 2 hd, 2 cd drives, floppy, mobo, and wireless card???

Any Idea's Anyone.....Just lookin for suggestions with out buying parts and randomly replacing stuff.

  • 1 Contributor
  • 2 Replies
  • 363 Views
  • 3 Weeks Discussion Span
  • Latest Post Latest Post by GriffIT34

Dani AI

Generated

Short technical summary: the stop code 0x0000009C is the Windows bug check named MACHINE_CHECK_EXCEPTION — a fatal machine-check that the CPU reports when it detects an unrecoverable hardware error. On later Windows versions many of the same conditions surface as 0x124 (WHEA_UNCORRECTABLE_ERROR). Microsoft: Bug Check 0x9C — MACHINE_CHECK_EXCEPTION. (learn.microsoft.com)

Common root causes are hardware-related: CPU/cache errors or throttling, bad or mismatched RAM, power-supply instability, motherboard faults (VRMs or failing capacitors), overheats, failing I/O devices or controllers, and instability from overclocking. The machine-check facility is implemented in Intel/AMD processors so the CPU reports these errors directly to the OS. See vendor/diagnostic guidance on MCE and common hardware causes. (learn.microsoft.com)

Concise, ordered checklist to narrow the fault (start at top and stop when the error stops reproducing):

  • Reset BIOS/UEFI to defaults and disable any overclocking.
  • Boot with minimum hardware (one HDD, one RAM stick, no add-in cards) and try to reproduce.
  • Run a full-memory sweep with a bootable tester such as Memtest86 or Memtest86+ (multiple passes overnight). Memtest86+ / MemTest86.
  • If a crash occurs, capture the minidump and analyze with WinDbg or a crash-analysis tool to read MCA/bank status (that often points to the failing subsystem). WinDbg / Debugging Tools for Windows.
  • If the drive removal changed behavior, try a known-good PSU or measure rail voltages; inspect motherboard caps and try each drive/device individually. (memtest.org)

Thread-specific note: ’s test results (error stopped after unplugging the second SATA drive, then later disappeared after an OS reinstall) are useful clues. Removing the drive points toward a hardware problem (power draw, a failing drive, or controller issue) while an OS reinstall can temporarily hide driver/disk corruption without fixing failing hardware. If the fault returns, follow the checklist above and attach the crash-dump output — decoding the MCA bank/status is the most direct way to identify the faulty component. (learn.microsoft.com)

Member Avatar for GriffIT34

Possible Solution: Too many draws on the power supply, 420W running 2 DVD, a floppy, a wireless card, but most importantly 2 7200rpm SATA drives. I unplugged one and no more error, so I guess the solution is to buy a more powerful Power supply..............

If anyone searches "machine exception error" I hope this helps.

Member Avatar for GriffIT34

good think I didn't go out and buy that powersupply, For sh*&%$ts and gigles I re-installed the OS and haven't seen the problem again.

Funny all my research points toward a hardware issue, so i'm fearful that the issue will reappear.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.