GPU BSOD can anyone help

[Apocalipse]

Hey guys, recently i have been having a problem i think with my GPU.

After some gaming it just BSOD's, i have overlcocked but even they the GPU should not BSOD?

It should just crash the driver? In any case i wanted to upload my dump files to the thread, but it seams,

i am not permitted to do so?

Any help is appreciated. 

[Xaring]

you need to keep the overclock in safe zones, my 970 can overclock a whooping 250MHz in benchmarks but at those speed it will crash in demanding games, so i have it at 180-190MHz boost as it's a safe zone, it wont crash me that way. When you overclock, make sure to test the shit out of the GPU, not just use benchmarks, make sure you play some uer games (Im testing mine with dying light right now).

 

So yes, its probably your overclock what is causing the BSODs.

[Apocalipse]

you need to keep the overclock in safe zones, my 970 can overclock a whooping 250MHz in benchmarks but at those speed it will crash in demanding games, so i have it at 180-190MHz boost as it's a safe zone, it wont crash me that way. When you overclock, make sure to test the shit out of the GPU, not just use benchmarks, make sure you play some uer games (Im testing mine with dying light right now).

 

So yes, its probably your overclock what is causing the BSODs.

Yea but the thing is i always thought that GPU's don't BSOD, and the thing is when i bench in heaven i get the lowest clock, and when i do in 3DMARK nothing happens,

i can find a consistent way to test. My oc is +131on the gpu and +400 on the vram

[Xaring]

If the GPU drivers can't reboot after an OC fail, it will cause a BSOD. first overclock the core and game a bit in a demanding title, after you have checked its stable, overclock the vram, not both at the same time... Its trial and error.

 

What is  your GPU?

[Apocalipse]

If the GPU drivers can't reboot after an OC fail, it will cause a BSOD. first overclock the core and game a bit in a demanding title, after you have checked its stable, overclock the vram, not both at the same time... Its trial and error.

 

What is  your GPU?

The gpu is a asus gtx 660 ti and i did overclock the gpu first and then the vram. And im testing in bf3 in 2560x1440 so i think that a reasonably demanding setting 

[Godlygamer23]

I've never encountered a BSOD from a GPU overclock stability issue. I've overclocked 560 Ti's, 660 Ti's, and now a GTX 970. What is your overclock set to? Post a screenshot with your settings and actual in game clocks.

[Apocalipse]

I've never encountered a BSOD from a GPU overclock stability issue. I've overclocked 560 Ti's, 660 Ti's, and now a GTX 970. What is your overclock set to? Post a screenshot with your settings and actual in game clocks.

Yea, thats why i wanted to upload the file dump, but the service wont let me.

Here is the screenshot of the clocks

[Godlygamer23]

Yea, thats why i wanted to upload the file dump, but the service wont let me.

Here is the screenshot of the clocks

What stop code do you get when the system crashes?

[Apocalipse]

What stop code do you get when the system crashes?

Not quite sure how i can check that?

Wait for another BSOD or?

[Apocalipse]

It crashed again and i think the code is 0x00000101

 

What stop code do you get when the system crashes?

[Godlygamer23]

It crashed again and i think the code is 0x00000101

Try this. Retest with your GPU clocks reset back to stock. While I am convinced the BSOD is not caused by an unstable GPU overclock, it doesn't hurt to try and may even teach both of us something if it doesn't BSOD again.

[CoolaxGaming]

It crashed again and i think the code is 0x00000101

All creadit goes to radnus @ techsupportforum

 

STOP ERROR: 0X00000101 has been the cause of many peoples bad dreams as it appears to be a hardware malfunction or even a CPU failure. Because it lists a secondary processor as not able to calculate a portion of data under clock cycle and then the crash occurs. Many have said it is because you have a DUAL CORE CPU and are miss-led because of the error message including the secondary processor. The actual secondary processor that is missing the Time Clock is in fact the GPU or graphics processor on your video card.

The reason it is missing it is because you have a set of over clocked or possibly BETA drivers installed. Typically the most common card to fail from this STOP: 0X00000101 error message is theNvidia 8800 series cards. The reason it fails a Clock Cycle on the GPU is because the cards support DirectX 10 on Shader model 4.0 and right now AoC only runs DX9.0c and Shader model 3.0. The cards are being forced to run in degraded mode so they fail not because they cannot run AoC but because AoC is asking them to run below their actually capability's.

THE EASY FIX... Go into Video settings in AoC and turn Shader model 3.0 <OFF> No off option exists so set it to 2.0

The better fix is to remove all Nvidia Drivers and then manually go to HKEY_CURRENT USER and HKEY_LOCAL_MACHINE then delete any folders under SOFTWARE that have an Invidia FOLDER. you can EXPORT and back up the registry to you're Documents folder first to have a copy just in case you need to roll it back. I make one called REG_BAK in a folder I make in Documents called Registry_History for example.

This STOP: 0X00000101 Error is not a CPU failure it is not an overheat issue with a DUAL Core OR Quad core CPU. I took mine out I have an AMD dual core 6400+ Black Box Edition and an ASUS/Nvidia High performance Heat Tube Fan/fin Cooler that costs as much as the CPU almost did. 

I removed all the Thermal Paste on this custom build machine by me 4 months ago and cleaned all the Heat paste and applied a new coat to both processors and heat sink and locked the cooler back onto the processor. System starts fine boot back into AoC ran 4 hours on Shader Model 2.0

I set the card to Shader Model 3.0 and locked up 20 seconds later then to a BSOD blue screen error message of 0X00000101. 

So the root cause failure this one was easy! I removed the BETA drivers I had installed version 177.79_geforce_winvista_32bit_english_beta and installed the WHQL version of 175.19_geforce_winvista_32bit_english_whql

I then played for another 3 hours (IN SHADER 3.0) with no issues and even teamed up with a Clan mate for three quests in the Aztel Mountains with all that casting and swordsmanship going on and no video hang not even a graphics pause. Now different areas of the game will cause the error some times anyways just reboot the game <simple> Computers are not a chrome bumber on a 1959 Desoto they fail all the time and wont push over a fire hydrant without a dent!

If you have a DUAL CORE CPU from AMD you can as many have said already install the DUAL CORE OPTIMIZER from the AMD website takes all of 5 seconds to install it and it will balance the workload over both CORES so the game runs a little smoother.. 

There is no doubt in my mind that the 8800 Series cards from Nvidia suffer terrible being run in Windows XP forced to eat DX9.0c when they were designed to run on DX10 in a Vista 32 bit or 64 bit OS and Shader model 4.0 that all my other games run perfectly on. For WoW fans remember Vista is an old technology called OPENGL that was improved and brought back for Vista. WoW is a Direct3D application and will never achive perfect functionality under Vista or the new Windows7 on the horizon.

Vista IS NOT an upgrade to Windows XP like Windows XP was to Windows 98. Vista is a brand new stand alone software program. Before everyone screams about Vista the new power edge server applications are also suffering from graphics crashes on STOP: 0X00000101 for other reasons and so is XP.

Keep in mind DirectX is an Engineering program <Software> that enables Hardware to talk to other hardware through Software. If the DX level fails it makes all you're hardware CPU video cardsHardware Memory all look bad. 

Ok back to the reason we are here;

Most players will say they can run all their other games just fine until they run AoC and then they crash. yes because they are using Shader model 3.0 in the game and All Reflections under the advanced video options. The Villas will drop a players machine to 9 fps from 50 fps because they are stumbling over the Shader model 3.0 

If you are not effected by fps issues and are not crashing to blue screens on 0X00000101 even for you players turn Shader model down to 2.0 in the Villas and you will see a very marked performance increase in you're computer.

All those with Dual or Quad core Processors DO NOT remove you're heat sink and use more arctic silver this will not resolve the STOP: 0X00000101 Blue Screen Error message, the second clock failure is the Graphics card but its a software Driver problem.

If you have any other Graphics card and have the above STOP: 0X00000101 Blue Screen crash the best way to resolve the issue is to completely remove all the graphics drivers you have in the computer.

You can Check ATi for their removal tools. Nvidia is easy Driver install they will stack and re-stack without even uninstalling if you are not that great at installing software. (USE THE DRIVERS CD THAT CAME WITH YOU'RE COMPUTER) reinstall the drivers from that.

Alienware computers have a default video card drivers CD. You can get the most recent or original Video drivers for you're DELL computer from Welcome to Dell Technical Support and if you are a custom Build your graphics Card came with it's own Drivers/resource CD's use them as a baseline the STOP: 0x00000101 Blue Screen will go away. 

It will not matter with AOC running in DX9.0c mode right now if you have the latest drivers on any PCIe ver 2.0 graphics card because they would be geared for DX10 and are causing the BSOD crash.

So in short:

CPU failure (NO)

Video sub system failure (NO)

Power supply failure (NO)

Thermal Paste failure (NO)

Loose wires or gremlins (NO) not if other games play correctly.

Video drivers DX10 version for newer PCIe Ver 2.0 Graphics cards Failure (YES)

SOLUTION: Use the default drivers that came on your CD with the computer or graphics card. If for any reason you still crash to a blue screen STOP: 0X00000101 just set you're Shader model back to 2.0 from 3.0 and wait until AoC writes a few lines of code to fix this and installs with next weeks update.

FYI I heard a rumor that DX10 will be available some time this month after some Computer games convention in Germany some place I saw written on an AoC website. I cannot find the link I think it was on the pre release beta home page for AoC.

If you still get the error don't despair have a friend help you to completely remove the current and past graphics drivers completely then install the base drivers again. It should resolve the issue for you.

[Godlygamer23]

SOLUTION: Use the default drivers that came on your CD with the computer or graphics card. If for any reason you still crash to a blue screen STOP: 0X00000101 just set you're Shader model back to 2.0 from 3.0 and wait until AoC writes a few lines of code to fix this and installs with next weeks update.

 

Using the default drivers is an awful idea.

 

Edit: Forum messed up the quote.

@CoolaxGaming

 

Double edit: That looks like an old post you borrowed.

Edited January 31, 2015 by Godlygamer23

[CoolaxGaming]

Using the default drivers is an awful idea.

 

Edit: Forum messed up the quote.

@CoolaxGaming

 

Double edit: That looks like an old post you borrowed.

Yup, but sometimes it actually works, Omega didnt work for me but the old drivers did

[Godlygamer23]

Yup, but sometimes it actually works, Omega didnt work for me but the old drivers did

It's not a huge deal if the drivers are pretty recent, but if you're talking about drivers that are years old...BAD idea.

[asim1999]

you need to keep the overclock in safe zones, my 970 can overclock a whooping 250MHz in benchmarks but at those speed it will crash in demanding games, so i have it at 180-190MHz boost as it's a safe zone, it wont crash me that way. When you overclock, make sure to test the shit out of the GPU, not just use benchmarks, make sure you play some uer games (Im testing mine with dying light right now).

 

So yes, its probably your overclock what is causing the BSODs.

Same here: 240mhz in benchmarks with max power limit, but only 225mhz with 110% power in games.

It is normal, lower overclock

[asim1999]

Yea, thats why i wanted to upload the file dump, but the service wont let me.

Here is the screenshot of the clocks

Lower temp target

[Apocalipse]

Using the default drivers is an awful idea.

 

Edit: Forum messed up the quote.

@CoolaxGaming

 

Double edit: That looks like an old post you borrowed.

Will try with the basic clocks. And i appropriate the automatic defaulting to the drivers but the drivers are up to date and the bios is up to date,

This is not something i just said, i have deliberately checked both of them, although i always update both of the drivers regardless of an issue.

 

Yup, but sometimes it actually works, Omega didnt work for me but the old drivers did

[Apocalipse]

It's not a huge deal if the drivers are pretty recent, but if you're talking about drivers that are years old...BAD idea.

And going to the older drivers i have to say might be a better idea, i cant say for sure, but i know that i had a higher clock some time back,

which also crashed in heaven, but did not crash in BF3. And if it did crash it always crashed the driver, and not a BSOD.