OC wnet wrong

hello,

using sager np8150

I have radeon 6990m.

windows 7 home premium 64 bit.

2nd Generation Intel® Core™ i7-2720QM Processor ( 6MB L3 Cache, 2.20GHz)

2nd Generation Intel© Core™ Chipset HM65

I thought it wouldnt be so stupid to try and overclock by just 10Mhz..I was wrong..

now every time i start my computer i get black screen after windows logo.

I tried to go into safe mode and disabling the adapter, go back to normal mode and remove catalyst ith all the drivers using DriverSweeper and reinstalling everything back.

still no luck.

is there any one who's familiar with this problem and can help me?

 

Uninstall your OC software (reset to default first, also in CCC), reboot to safemode and de-install the video adapter in device manaager with the "delete drivers too" box ticked.

Then boot back into normal mode, run ATIman Uninstaller ( version 7.02), then fresh install the new driver.

If the problem persists, your GPU possibly died...

 

yeah, just un install your overclock program in safe mode, and you're good to go

 

i've tried to remove CCC in safe mode and all the drivers and the adapter and reinstall everything.. still no go.
i cant open CCC to reset the settings caus' it needs a reset after installation...which then the computer doesnt start up

 

Which OC Software are you using? Or did you OC within CCC?
You could try the following:
Go into the folder where you extracted the video driver, /Packages, /Apps, /CCC2, Core-Static-Net4, scroll down and rightclick on ccc-core-static.msi and hit "Repair". After the repair wait 5mins and reboot.
The full path in my case is C:\AMD\Support\13-1_vista_win7_win8_64_dd_ccc_whql\Packages\Apps\CCC2\Core-Static-Net4\core-static-net4.msi

Also try ATIman Uninstaller I mentioned.

 

both didnt work.

i'm starting to get the worst feeling.. how is it even possible that 10Mhz will fry my GPU? i read posts where poeple said that they OC'd to 840Mhz..u just scaled it to 725Mhz,, Thats my luck :/

anyway...thank you very much for your help. I really appreciate that!

does anyone have another suggestion?

I think i'll take it to an engineer...

 

I doubt that 10MHz fried your GPU. There must be a trace of the OC software settings still that caused the problem to begin with. And if you can boot into your OS/into a GUI, that tells me your GPU isn't gone.

Try uninstalling from Device Manager, and check "delete driver software for this device" before proceeding. Then boot into Safe Mode when you reinstall the software.

I came across a thorough guide on removing ATI drivers and affiliated directories + files. I'll see if I can find it again.

 

i think you may be looking for this

how to properly uninstall ATI/AMD Software Drivers for Graphics Cards.

 

thanks for replying.

I used this ATIman thing that sirana suggested which deleted everything related to ATI and then i reinstalled everything..still no go.

For the sake of certainty i'll try the guide kookiesandmilf suggested but i doubt it..

 

This is what I will suggest. Back everything out (if you can) and reformat your whole computer.

As you can see in my rig, I run a 680m. I do enjoy some minor overclocking on my computer. One day, for some unknown reason, I was not able to get Kombuster and Afterburner to run correctly anymore. They will always drive the HD4000 graphic chip, instead of the 680m. However, gaming was still fine. Since I was lazy, I didn't even bother with the issue. Last weekend, I've decided to update my video driver. The moment I uninstalled my stock driver, my computer failed to detect my 680m. No matter what I had done, it just won't detect my 680m. In the end, I decided to reformat as a last resort. Guess what, it worked. Something was goofing up my computer and I just can't seem to be able to pinpoint the cause.


By the way, I did encounter that windows black screen like you did with my previous Alienware M15X. However, that was due to the windows update rather that the overclocking. That was fixed by reformatting and reinstalling Windows.

 

You can do this... but it won't tell you what the problem was, if it does in fact fix it.

I think the guide I saw was on toms hardware, but that will suffice. Thanks!