• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New 7900...now I get MACHINE_CHECK_EXEMPTION

Entity

Lifer
I just got a 7900GTO in from Newegg and started the installation process. I removed ATI's drivers, booted into safe mode, ran drivercleaner, and then rebooted. When I'm booting into anything other than safe mode (this even includes network-enabled safe mode), I get a BSOD with MACHINE_CHECK_EXEMPTION. My former ATI card was an x800GT. My system setup is as follows:

1x250GB SATA drive; 1x300GB SATA drive (7200rpm)
4gb OCZ memory
520w OCZ PSU
DFI Lanparty UT SLI-DR + AMD 4400+
XP

One other thing I changed was switching from the PCIe4 slot to the PCIe1 slot on the motherboard. Now it seems that when I put either the x800GT or the 7900GTO in, it's destined to BSOD. Any ideas, short of reinstalling Windows and seeing if it works then (yuck)?

Rob
 
The error message pops up right after the Windows XP screen starts loading (gets about 1/2way to boot). I'm running memtest86 right now to check for any potential memory corruption, but it really seems like a strange time for memory to go bad given how everything was running fine until I switched video cards (and now it doesn't seem to matter what video card I try to run).

Rob
 
I'm considering giving booting in the PCIe4 slot a try again, and seeing if that fixes things. Memtest is running fine so far. The problem with running in that slot is that next week I'm getting a 3007WFP, and will need 2x video cards to be operational, and the PCIe1 has priority over the other (runs at x16 and the other runs at x2), which would suck for gaming if my good card gets throttled that much. Ugh.
 
Another update: tried booting with the old card in the old slot, and I get the same error message. Frustrating.
 
I think there is an ATI driver cleaner. I remember reading about it a few years ago.

Try that and try to boot into Windows safe mode.
 
Originally posted by: Entity
MACHINE_CHECK_EXEMPTION

STOP: 0x0000009C (0x0000004, 0x8054D5F0, 0xB2000000, 0x00070F0F)

Well, its too late now as you have reinstalled windows but that error is a fubared nvidia error, either the chipset drivers or video.
 
Just in case the problem persists after the reinstallation, here is what I found for the error

0x0000009C: MACHINE_CHECK_EXCEPTION
(Click to consult the online MSDN article.)
This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

It gives a MS link to

http://support.microsoft.com/?kbid=329284&sd=RMVP
 
If both cards give you the same problem, then it's probably a driver issue or the PCO slot might be busted. Oh, and ATI driver cleaner is crap. Use Driver Cleaner Pro, it cleaned out a lot of extra stuff that got left behind and caused a few errors/crashes. After running it, no crash in about half a year. Only thing that errors is crApobat Reader.

I got that error for months and didn't want to believe something was busted. If you reinstall windows, that will eliminate driver conflict as a source for the nost part. Note: a driver error in Event Viewer should point you in the right direction. My effed SATA controller onboard mobo kept 0x000009c'in and an SATA error kept popping up in the Viewer.
 
Originally posted by: Oyeve
Originally posted by: Entity
MACHINE_CHECK_EXEMPTION

STOP: 0x0000009C (0x0000004, 0x8054D5F0, 0xB2000000, 0x00070F0F)

Well, its too late now as you have reinstalled windows but that error is a fubared nvidia error, either the chipset drivers or video.

Yeah, I tried using DriverCleaner Pro and still had no luck. Eventually just gave up, all is well now.

Rob
 
I get it occasionally again on the new machine when I enable the Marvell Yukon Gold Gigabet Ethernet port on the DFI Lanparty. The computer stalls right now when I try to install the drivers for the port. I'll probably just disable it, but I'd like to figure out a way around it...maybe it's an IRQ conflict or something along those lines?

Rob
 
Back
Top