Hi Everyone,
I recently built an Abit AV8 based system with an Athlon 64 3400+, 1 gig DDR 400 ram (2X512) anda GeForce FX5700LE.
My problem is this: It randomly generates the BSOD error 0X0000009C (0X00000004, 0X80545FF0, 0XB2000000, 0X00070F0F0).
Although it occurrs randomly, about once an hour, the frequency seems to increase when I have my film scanner up and running. Also, since I have two ram sticks, I started it up with one to check the ram and the BSOD frequency increased dramatically so I figured I had found the problem until I put the other stick in and it did the same thing. Any suggestions what I might check next??

Augie100,
Welcome to the PC Guide Forums!

I would suggest you download and install memtest86 (http://www.memtest86.com/) and test one stick of memory at a time.

You will find reasons for for your error in the following link. I have not zeroed in on a specific link for you as it will be easier for you to that yourself.

http://www.google.com/search?q=0X0000009C&sourceid=opera&num=0&ie=utf-8&oe=utf-8

Thanks for the replies.

I have searched for several hours and found three other instances of the same machine check exception that I encounter on my machine. One of them mentions that this is a rarely encountered code. The only commonality that I can pick up in the hardware is the AMD 64. I have the latest BIOS for this board.

I will run the memory test that PrntRhd suggests and see if that turns anything up.

It appears to be random with the only variable being CPU activity, the more the CPU is working the more liable it is to crash.

Thanks Again,
Augie100

Hello!. Let us know if this is problem with the cpu... TTYL

It can even be caused by bad power to the PC. You do want to use a filter strip between the wall and PC or better yet a Uninterruptable Power Supply.
I suggested a memory test as it is the cheapest place to start looking. The next place would be to make certain the memory specs match the PC and the other memory chip.
:)

Searching for 0X80545FF0 through Google gives a result of the exact error encountered here, above. Though not many solutions offered. Some mention hardware related between CPU and mobo, but my thoughts are insufficient power supply could be at fault also. Here (http://www.google.com/search?hl=en&q=0X80545FF0&btnG=Google+Search) is the Google page.

Thanks again for the replies.

I have been trying to get some film scanning done between crashes but after the last one I figured I should back to trying fix the problem rather then hoping it doesn't occur again. That is what happened in some of the cases that I was able to follow but unfortunately just about the time I am breathing easier bam the BSOD!

As far as the power supply goes, it is a generic 425 watt from Tiger Direct that was advertized as AMD approved. Immediately after a crash, I rebooted into the Abit Guru menu and checked all the voltages and temps and they are well within tolerances. Is instability a possibilty??

Augie100

What are the current (amperage) specs on the CPU for
12 volt?
3.3 volt?
5 volt?
Look on the label of the supply.

Bargain PSU's from Tiger Direct? :o Ooiy!!! It is a possibility that the voltage is right but the current is lacking even though it is stated as 425 watts, it may be a peak power rating.

Check that memory too! That was my main problem on a recent new build.

Hi All,
I ran several passes of the memory test as suggested by PrntRhd and others and the memory is OK. Fuss Tray Ted,here are the amp ratings from the ps and OBTW it is a Just PC brand if that means anything,+12v 12A, +5v 40A, and +3.3 20A. Since it is Valentines Day and my wife is waiting by the fire in the fireplace, I have to go join here :-).
Augie 100

Anyone Interested,
The ram is Corsair Value select and has a mfg. spec of 2.5 cas latency. I slowed it down to 3 clock cycles and that seems to have cured the problem with the BSOD. I waited for four days to make sure it was gone.
Augie100

Augie a question if you have time>> Did you slow the ram down in the setup menu??
Thank you

ATC,
Yes, I changed the ram screen from auto-detect to manual and then changed the cas latency setting.
Augie100