BSOD on Beef

thewombleofdeath · Post by **thewombleofdeath** » July 21st, 2007, 9:25

in that case is it likely that mine is overheating or just some err0rz somewhere?

Post by **FatherJack** » July 21st, 2007, 21:26

thewombleofdeath wrote:in that case is it likely that mine is overheating or just some err0rz somewhere?

I wouldn't say 73°C is overheating for a GPU, although it's pretty hot for a CPU. For GPU that's normal operating temperature, and refitting the cooler isn't going to change that.

Post by **Dr. kitteny berk** » July 21st, 2007, 21:27

FatherJack wrote: I wouldn't say 73°C is overheating for a GPU, although it's pretty hot for a CPU. For GPU that's normal operating temperature, and refitting the cooler isn't going to change that.

Hard.

Also refitting coolers will often kill warranties on gpus.

thewombleofdeath · Post by **thewombleofdeath** » July 22nd, 2007, 22:08

right. so its obviously not overheating. must be the drivers or something then.

tits.

Post by **Dr. kitteny berk** » July 22nd, 2007, 23:41

next time you get a bsod, copy down the info before you reboot (or use a camera)

post it here

Post by **deject** » July 23rd, 2007, 5:56

if the BSOD goes too fast to see, open up the System Properties and click on the Advanced tab. in the Startup and Recovery box (the bottom one) click the Settings button. In the new dialog box, uncheck "Automatically restart."

thewombleofdeath · Post by **thewombleofdeath** » July 23rd, 2007, 9:24

the BSOD tends to just stay on the screen with the sound of a game jamming in the background. all i have to do is just press the power button and it generally turns off and restarts so it going too fast shouldnt be a problem.

all it says i think is something like x0000000000e whatever and then nv4.dll or something like that but i'll take a photo or something next time it happens and put it on here.

Post by **Dr. kitteny berk** » July 23rd, 2007, 9:31

Well, that's a start (but obviously, the actual string would help narrow it down a lot)

It's the nvidia graphics driver crapping up, but it's hard to tell why without moar info.

mrbobbins · Post by **mrbobbins** » July 23rd, 2007, 9:34

I think you should seriously look at your memory as the cause, this is exactly the problem I had until I lowered my memory timings.

Post by **Dr. kitteny berk** » July 23rd, 2007, 9:36

mrbobbins wrote:I think you should seriously look at your memory as the cause, this is exactly the problem I had until I lowered my memory timings.

I'm not sure if we've done that in this thread yet.

Womble, can you tell us everything you've done/tried so far?

thewombleofdeath · Post by **thewombleofdeath** » July 23rd, 2007, 9:56

ok ill try.....right.....

1. bought card (8600gt overclocked)
2. installed driver from disk
3. seemed to work fine for a while
4. started getting BSODs
5. RAGE
6. removed drivers using the cleaner berk suggested on the other page
7. installed newest version of Nvidia drivers which seemed to fix the BSODs but started getting jams (ie. beef and other games freezing or going black (or in beefs case - YELLOW!?!?)
8. used driver cleaner thing again
9. reverted back to disc driver
10. BSODs again
11. MOAR RAGE

i think thats it

oh...and at somepoint, i cant remember whether it was before or after i got the card (before i think), i wiped the hard drive and re-installed windows

buzzmong · Post by **buzzmong** » July 23rd, 2007, 9:59

Have you tried the not so latest driver, but not one as old as the disk?

Post by **Dr. kitteny berk** » July 23rd, 2007, 10:01

okay, first thing to try is memtest It's quite unlikely (the yellow in beef usually indicates a graphics problem) but it's worth a shot.

Then i'd do drivercleaner etc and install the latest drivers again.

Check heat again under the new drivers.

If nothing works, I'd try to get an RMA.

thewombleofdeath · Post by **thewombleofdeath** » July 23rd, 2007, 10:02

no not yet.....i was going to the other day but forgot so i might try that.

any particular one that you would recommend as being alright?

thewombleofdeath · Post by **thewombleofdeath** » July 23rd, 2007, 10:04

Dr. kitteny berk wrote:If nothing works, I'd try to get an RMA.

ok....whats an RMA and how do i do it

Post by **Dr. kitteny berk** » July 23rd, 2007, 10:07

thewombleofdeath wrote:ok....whats an RMA and how do i do it

RMA = Return Merchandise Authorization = I can send it back now please?

Depends where you bought it, but their website should have the info.

thewombleofdeath · Post by **thewombleofdeath** » July 23rd, 2007, 10:14

ah

well ill try some other drivers because that seemed to fix the BSODs but create other problems and as Bobbins said earlier, he had the same problems and had to lower memory timings, so that might be a possibility.

if none of this works then i may just send it back to ECS.

eion · Post by **eion** » July 23rd, 2007, 10:20

It seems to me that the most likely cause of your (BSOD

) problems is a fucked graphics card. I'd therefore recommend doing as Berk suggests and RMAing it.

mrbobbins · Post by **mrbobbins** » July 23rd, 2007, 10:22

thewombleofdeath wrote:ah

well ill try some other drivers because that seemed to fix the BSODs but create other problems and as Bobbins said earlier, he had the same problems and had to lower memory timings, so that might be a possibility.

if none of this works then i may just send it back to ECS.

Try one stick of memory at stock timings etc. if it crashes, try the other at stock, if it still crashes try one with lowered (Well, increase the latency numbers) repeat until insane etc.

Post by **Dr. kitteny berk** » July 23rd, 2007, 10:34

Other thing to try is downloading ATITool and using it to underclock your graphics card (both GPU and graphics memory) by ~10%

If it's a card issue, that'll usually stop the errors (or make them take longer to appear) If it does, your card is ill.