If You are Getting BSODs

iSkylla

[H]ard|Gawd
Joined
Jul 22, 2005
Messages
1,685
I am starting to see a trend here. While traveling over to the DFI Forums to ask them about my BSOD problem, I came across quite a few people with the same BSOD of 0x0000009C plus more (But that is the more important part). If you have an ATI card, do not install to the Catalyst 6.1 drivers, or the Omega ones that are based off of them. They seem to cause BSODs and a lot of them. So I thought I would post my thoughts on this to help people.

Full System Specs:

Lian Li PC-60B Plus
AMD FX-55 Clawhammer + Zalman 7700Cu
DFI LanParty Ultra-D - 704-2BT BIOS
Antec TruePower II 550W
2GB G.Skill
2x Maxtor 300GB HD 16MB Cache
Pioneer DVD±RW Drive Dual Layer
AOpen CD±RW/DVD-ROM Combo Drive
NEC Black 1.44" Floppy Drive
ATI Radeon X800XL
Creative Sound Blaster Audigy 2 ZS
Hyundai L90D+ 19" LCD
 
I've got the 6.1's installed with narry a problem. If there is a trend, it must be with a card + mobo combo. You should check into that more and update your post.
 
Well see, here is the full error Code

MACHINE_CHECK_EXCEPTION

STOP 0x0000009C (0x00000004, 0x80545FF0, 0xB2000000, 0x00070F0F)
 
Right, but what motherboard are you guys using who are getting this all the time? What card are guys using? Is there a pattern with a certain motherboard and video card combo?

Inquiring minds want to know. :p
 
Of course. I was looking on the DFI Forums. ;)

I am using an X800XL, I am guessing the others were using the X800 or 850 series.
 
Interesting thread. I've noticed minor instability with my DFI nf3 at 290 HHT where I know for a fact that the cpu and ram are 100% stable. Basically, 3D games occasionally crash (usually when navigating in game menus).

I've just rolled back to 5.11 (from 6.1 of course) and I'll report back with my findings.
 
Was 5.11 the last good version? I downloaded 5.5 but not sure if I should install or get 5.11 instead
 
iSkylla said:
Was 5.11 the last good version? I downloaded 5.5 but not sure if I should install or get 5.11 instead
Dunno, just seemed like a reasonable driver to step back to.

Anyway....


Reporting back:

6.1 drivers do not cause any instability for me. I had an issue which I thought was video related and it has turned out to be that I needed to give my cpu a tad more voltage. So yeah, count me as one without a Cat 6.1 issue on a DFI board ;)
 
great, i see this now just after updating two boxes from 5.11's to 6.1's.... oh well i havent had much time to game since classes startrd back up, maybe everything will be ok and fixed when the 6.2's come out
 
I am ok with 6.1's and my X1800XT, DFI Ultra-D and . In fact system is rock stable, only time I crash is my gpu gets to hot which it does and I have to have the fan at 100% GRRRR!!! Stupid room at 85F ambient in the winter!!!
 
I've also experience this same BSOD error. I have never had any BSOD's ever on my system until I recently formated with a clean load. I too, have the latest ATI drivers. If this is truely the culpret... then off these go..

Oh
I'm running an Abit AN8-SLI, X800GTO, 400W Fortron Blue Storm, etc. .etc..
Never any blue screens previously until now..
GPU constantly runs around 39-40C idle
 
It's quite curious that a driver could cause a machine check.
 
A driver can very well cause a machine check, especially ATI drivers. I am always afraid to upgrade because after I upgraded once my machine constantly BSODed, I ended up having to reinstall windows because it would just randomly restart. I am using 5.9 and am completely stable.
 
tack me onto the "not a single BSOD problem" list. BTW im using the Omega Drivers (3.8.205)
 
benamaster said:
A driver can very well cause a machine check,
Can you explain how? I don't understand how it can influence the MCA.
 
benamaster said:
A driver can very well cause a machine check, especially ATI drivers. I am always afraid to upgrade because after I upgraded once my machine constantly BSODed, I ended up having to reinstall windows because it would just randomly restart. I am using 5.9 and am completely stable.

yeah i remember the 4.8's (or 4.9's) gave me a fit with BSOD's saying it was a memory problem... turned out it was their drivers because when the 4.11's came out no more BSOD (nothing else had changed)
 
pstang said:
yeah i remember the 4.8's (or 4.9's) gave me a fit with BSOD's saying it was a memory problem... turned out it was their drivers because when the 4.11's came out no more BSOD (nothing else had changed)

What kind of memory problem did your BSOD say you were having? Remember that a Machine Check Exception is not the same thing as a BSOD, and there are many different causes for BSODs -- only one of which is an MCE. It's pretty easy for a driver to cause a BSOD by referencing invalid or privelege-protected memory.
 
mikeblas said:
What kind of memory problem did your BSOD say you were having? Remember that a Machine Check Exception is not the same thing as a BSOD, and there are many different causes for BSODs -- only one of which is an MCE. It's pretty easy for a driver to cause a BSOD by referencing invalid or privelege-protected memory.

i dont remember exactly it has been a while, but i referenced the numbers on MS's knowledge base and it said that it was a possible memory problem
 
pstang said:
i dont remember exactly, but i referenced the numbers on MS's knowledge base and it said that it was a possible memory problem

Then you might not have had a MCE. What i'm wondering is how a driver can cause an MCE.
 
I'm seeing this with an nVidia GeForce 6600GT...dunno why. I'm going to try updating drivers to beta, then rolling back to earlier drivers. Will let you guys know if it makes a difference.
 
On my new machine nf4 chipset drivers kept causing blue screens and other stability issues.

When I reverted to the dfi nf4 driver cd all of the blue screens stopped and the system is rock stable.

I tried about 4 or 5 newer chipset driver versions including the latest officials, using driver cleaner between. Massive stability issues.

The latest chipset drivers on DFI's Ultra-D page are derived from version 6.66.

I didnt try those dfi 6.66's yet, but I tried nvidia 6.66's without any luck.

http://us.dfi.com.tw/Support/Downlo...D=3471&CATEGORY_TYPE=LP&STATUS_FLAG=A&SITE=NA

It may be a long shot, but I suggest trying chipset drivers from the install cd or dfi.

nForce chipset drivers can be real bitchy at times.

Good luck.

fx55
Ultra-D (704-2BTA big toe bios)
X1900xt cat 6.2
2x1gb ocz
 
I have a DFI RDX200 and X1900's Crossfire setup, and no BSOD's so far.

However, since installing the latest 6.2 CAT's I've noticed a drop in performance compared to the driver for the X1900's that came on the CD. I was between vid cards so never ran cat 6.1.
 
Have been getting this BSOD recently with MCE and in x-64 edition. I thought it was some other issue but this enlightens me. I am running my sig machine and have been quite frustrated by the randomness of teh BSODs. Will definately rollback ATi drivers.

WOOT LIMP GAWD!!
 
Yeah I have read those threads and I was going to post there but I have fubar'd my X1900 pc with too much tweaking...

Somewhere along the lines of registry tweaking, ATI Tool overclocking, AMD X2 bug fixing, 6.2CATs and other stuff, games started to stutter or jump, and performance droppped - NFSMW, FEAR, X3:Reunion, BF2 all suffered. 3DMark5&6 also illustrated the problem. It was while trying to narrow down the issue I had changed too much with little choice but to start from a fresh install - format time.

The fact that I have a multi-core cpu means I shouldn't have had a drop, making me think it was something I did. Once I've cleaned the system up I'll see how it stands and perhaps report in that thread.
 
The only time I got BSOD's in my X1900 XTX was after installing .net 2.0

A simple uninstall of .net 2.0 fixed it. The only version I can run is .net 1.1
 
I've been getting BSOD's a lot lately myself. I just built my system about 3 weeks and all seemed fine until about a week ago. It just started gettings BSOD's mostly when gaming but not always.
 
Back
Top