Need some advice please

[SlowBurn]

Let me take you through my day...

Today I received my new Abit-KD7 MB and the Chaintech Geforce 4Ti4600. Was very excited for a few reasons...

I haven't had new equipment in awhile
I heard the Chaintech is a VERY good OCer
I have been waiting for these pieces so I could finally take my Kingwin case out of the box and run it
I can install my new AX-7 heatsink with the Tornado on top

Anyway, I took the KD7 out the box, and installed it in the new Case. Took the old CPU (1700 XP) from my old motherboard (KR7A-RAID) mounted the, the heatsink, all the cards, HDD, etc. Plugged everything in, and started it up. After some bonehead mistakes it finally posted.

Now being the agressive person I am I tried to OC my 1700 at 166 FSB, changed the ratio to 5:2:1, raised my vcore to 2.35, and my DDR to 2.75. Saved settings and waited... and waited... ok no post. So I tinkered around with it and finally got it stable at 155 FSB, with a 4:2:1 ratio, with the same vcore and DDR as stated above. Booted into windows fine, and was about to run 3DMark2001. I clicked on the shortcut and it said "Could not create Direct3D device". I think maybe it got corrupted somehow so I try to reinstall it... same message. I look on Madonion's website, and they suggest I reinstall DirectX 8.1 and uninstall my drivers. Did that, and nothing worked.

Everything is running fine in windows, so I'm not sure what is going on. So I think maybe if I go back into the Bios, put everything at default and try that. Now when I log into Windows it reboots the computer. So I'm thinking to myself.. "Let me get this straight... I have to OC my chip for it to be stable??" I gave up after a few hours, because for one my wife was home by then, my son was crying because he wanted to play the "car game", and I was getting tired of seeing it reboot.

Tomorrow when I get home (at work atm) I'm going to try my old Geforce 3 Ti200 and see if I have the same problem. If it does, I will actually be happy, because that means that it's not the Geforce 4. If it doesn't... I might have to reinstall windows, maybe something got corrupted somewhere.

Does anyone have any advice, or has anyone gone through anything like this before.? Any help will be greatly appreciated.

Sorry this was so long, but I wanted to get out as much info as I could.

[badvector]

Hey Slow,

I haven't seen you before so let me do my initial...........

WELCOME TO THESE HERE FORUMS

I had a similiar issue while playing with my GF3TI200. I searched the web/newsgroups and finally came up with something similiar to my problem and this solution worked.

Run the Dxdiagnostics program.(dxdiag.exe) Go to the display tab. Even though the line that reads "Direct3D Accelleration" says:"Enabled", go ahead and click on the "Disable" button. You may or may not get a message that says "Direct 3D enabled". If you do get the message, you can close out the program and t should work. If not, close out the program and re-boot. (I re-boot for shear cleanliness wether it's required or not is debatable). Run dxdiag.exe again and see if "Direct3D Accelleration" says:"Disabled", if so, go ahead and click on the "Enable" button.

Our problems weren't exactly the same, but this did work for me. I honestly couldn't tell you why it worked, it just did. If this doesn't work, you may want to search Google Groups (http://groups.google.com/groups?q=DirectX+8+no+3D&hl=en&lr=&ie=UTF-8&sa=N&tab=wg) for another answer.

Hope this helps.

[toastedzergling]

2.35 Vcore??!!! are you sure?

[SlowBurn]

Orginally posted by badvector
Hey Slow,

I haven't seen you before so let me do my initial...........

WELCOME TO THESE HERE FORUMS

I had a similiar issue while playing with my GF3TI200. I searched the web/newsgroups and finally came up with something similiar to my problem and this solution worked.

Run the Dxdiagnostics program.(dxdiag.exe) Go to the display tab. Even though the line that reads "Direct3D Accelleration" says:"Enabled", go ahead and click on the "Disable" button. You may or may not get a message that says "Direct 3D enabled". If you do get the message, you can close out the program and t should work. If not, close out the program and re-boot. (I re-boot for shear cleanliness wether it's required or not is debatable). Run dxdiag.exe again and see if "Direct3D Accelleration" says:"Disabled", if so, go ahead and click on the "Enable" button.

Our problems weren't exactly the same, but this did work for me. I honestly couldn't tell you why it worked, it just did. If this doesn't work, you may want to search Google Groups for another answer.

Hope this helps.


Thanks for welcome. It's funny cause as you can see by my sign up date, I did it last November, but I completely forgot about it :) Anyway, I will try the dxdiag. I tried it last night, and it gave me an error, but I never did reboot. I'm wondering if I hurt something running the chip at 2.35, since apparently I should have seen smoke at that voltage, and I never did. Maybe I should read up some more before I start running everything at it's highest voltage. I used to OC older systems way back when, but this is a WHOLE different animal.

Originally posted by toastedzergling
2.35 Vcore??!!! are you sure?

Wow I must have gotten lucky that I didn't fry my MB, but yeah that's what someone told me I should OC my vcore to. I actually had it running for the good portion of about 2 hours too. I kind of got leary when I saw my CPU temp continually climb. Once it reached 50C, I said ... ok time to put the vcore down.