Many of the same BSOD. :(

The__Malteser · 22 Dec 2011 at 17:25

Been getting this BSOD:

NO idea what it is. Comes at random intervals.

- First it came when I exited GTA:SA online. Then I right-click to close teamspeak, and i got it.

- Second time was like 3 days after (2 days ago) when i put on Atom Zombie Smasher. (when the pic was taken)

- Third time was when I was trying to burn a disk (today)

- Fourth time was exactly after I put on PC, after the third time. Got it after 5 mins max.

Admittedly, i did install a lot of new programs, but i ran AVG and Spybot and got nothing unusual. i know BSOD are mainly hardware, but I didn't play with any hardware. Didn't open the case at all. My GPU and CPU are OCed. i put down my GPU OC by 5MHz after the first time but it didn't help. Doubt a CPU OC will cause that type of BSOD.
Any help?

The__Malteser · 22 Dec 2011 at 17:44

Interesting. it seems like this BSOD was a one off, and the other 3 were the same.

I downloaded this BSOD reader, and this is what it shows

http://vvcap.net/db/pXHRTY9cJY_md5lgnED-.htp

(latest on the top)

Now, I would zip the minidumps file and upload it, but it seems like I don't have permissions even though I'm an admin O.o

James J · 22 Dec 2011 at 17:45

Its your graphics card doing it by the looks of that crash dump. Possibly overheating?

The__Malteser · 22 Dec 2011 at 17:46

James J said:
Its your graphics card doing it by the looks of that crash dump. Possibly overheating?

Never hits over 60. And is around 30 idle.

EDIT: + had resisted 2 hours FURMARK O.o

James J · 22 Dec 2011 at 18:07

Which drivers are you using? Have you tried different sets? If you have and still have the same problem, try drivercleaner just so you know theres no old files left on your computer.

TNGL · 22 Dec 2011 at 18:10

Most likely some dodgy drivers.

Threepwood · 22 Dec 2011 at 18:18

03B?

Isn't that usually VCORE related?

Up your vcore or drop your cpu clock even further.

Worth running the cpu at stock speeds and seeing if you see the same bsod too.

The__Malteser · 22 Dec 2011 at 18:32

I normally upgrade drivers through STEAM. Never had any problems. Although I got an alert to update CCC a few days ago, directly from CCC, so I doubt it was a wrong one.

shadesofgrey said:
03B?

Isn't that usually VCORE related?

Up your vcore or drop your cpu clock even further.

Worth running the cpu at stock speeds and seeing if you see the same bsod too.

Never touched the VCore! Will put CPU back to stock speeds if people tell me its CPU related.

Deception · 22 Dec 2011 at 18:55

The BSOD code mentions an ATI file, yet the 0x3B means Vcore on a few BSOD code lists. Try putting GPU back to stock now, see if you get any and if you do, try altering CPU speed.

When did these start happening, was it random or recently after a driver update etc.

The__Malteser · 22 Dec 2011 at 19:04

Deception said:
The BSOD code mentions an ATI file, yet the 0x3B means Vcore on a few BSOD code lists. Try putting GPU back to stock now, see if you get any and if you do, try altering CPU speed.

When did these start happening, was it random or recently after a driver update etc.

CPU has been OCed since summer.

GPU has been OCed since CPU, so summer. I remember doing a CCC update a few days ago, so might be it. And I MAY have done GPU drivers via STEAM.

wildman · 22 Dec 2011 at 19:10

The__Malteser said:
CPU has been OCed since summer.

GPU has been OCed since CPU, so summer. I remember doing a CCC update a few days ago, so might be it. And I MAY have done GPU drivers via STEAM.

I am confused, if your CPU is OCed how did you do this without touching vcore ? If you OC and don't have enough vcore to keep it stable you get BSODs. HOwever you say it has been ok since summer ?

If you are running an ATi card check drivers. I know when I first built my new rig I used the OTB drivers with my 6870 and it BSODed when running the windows experience tester thing

The__Malteser · 22 Dec 2011 at 19:14

wildman said:
I am confused, if your CPU is OCed how did you do this without touching vcore ? If you OC and don't have enough vcore to keep it stable you get BSODs. HOwever you say it has been ok since summer ?

If you are running an ATi card check drivers. I know when I first built my new rig I used the OTB drivers with my 6870 and it BSODed when running the windows experience tester thing

I did a small 500 MHz OC, nothing major, without touching the VCore. My mobo is a bad overclocker (I was told) so wasn't worth changing the VCore. I get, at times, BIOS errors telling me that my PC can't load at 2.9 GHz (after a month of it being stable in Prime 95 for 6 hours :O), so I put it down to 2.89 and it has worked amazing since.

Where can i download this driver checker please?

Thanks

Also, bye bye amazing OC

Used to give me 1123MHz instead of 993

wildman · 22 Dec 2011 at 19:18

The__Malteser said:
I did a small 500 MHz OC, nothing major, without touching the VCore. My mobo is a bad overclocker (I was told) so wasn't worth changing the VCore. I get, at times, BIOS errors telling me that my PC can't load at 2.9 GHz (after a month of it being stable in Prime 95 for 6 hours :O), so I put it down to 2.89 and it has worked amazing since.

Where can i download this driver checker please? Thanks

Also, bye bye amazing OC Used to give me 1123MHz instead of 993

I think you might need to crank up vcore a bit to see if that helps stabilise. If you are using an ATi card, got to the ATi website and pull the latest drivers, I beleive there is a link in the Graphics Card subforums here. ALso makre sure you use drivesweeper or similar to clear the old one out first, don't just install the new ones over the top.

The__Malteser · 22 Dec 2011 at 19:29

wildman said:
I think you might need to crank up vcore a bit to see if that helps stabilise. If you are using an ATi card, got to the ATi website and pull the latest drivers, I beleive there is a link in the Graphics Card subforums here. ALso makre sure you use drivesweeper or similar to clear the old one out first, don't just install the new ones over the top.

Will remove the OC for good until I get rid of these BSODs.

Will get latest drivers.

Also

Attention - Guru3D Driver Sweeper has been discontinued as such you will not find any download links here any longer.

EDIT: Found somewhere else.

The__Malteser · 22 Dec 2011 at 22:00

- Removed GPU OC

- Removed old GPU drivers (and my screen went to 800x600)

- Removed CPU OC

- Installed new GPU drivers (it failed first time around,b ut I didn't bother deleting -> installing again, so I just installed again and it worked. Its the same thing over the same thing, now sure if it will cause damage. Screen went back to 1024x768)

I'll wait, see if I get any BSODs now. Lets give it a week. If so, I'll try OC GPU (to se if ti was the drivers)

Threepwood · 23 Dec 2011 at 03:35

Imho, if everything works at stock speeds this will be a simple case of upping the vcore.

CPUs can degrade over time one year it wont bsod on a certain voltage but the next year it will and either needs more volts or less clock to run stable, just life.

Justintime · 23 Dec 2011 at 04:31

wildman said:
I am confused, if your CPU is OCed how did you do this without touching vcore ?

Many (heck, virtually all Core and ix era) will overclock somewhat on stock vcore, examples: most Q6600 will do 3Ghz at stock, most 920 will do 3.6Ghz and most 2600k will do 4.2Ghz etc.. of course theres the odd few that won't but the majority will.
I really doubt its the cpu, likely the gpu or motherboard going flaky somewhere along the line, whether driver related or hardware, 500Mhz from a Wolfdale 2.5 chip is nothing, all my E5200 did about 3.5Ghz on stock volts lol.

Seeing as the card was overclocked, and the BSOD obviously points to an ATI file, i'd say it was the possible driver/CCC update you did.

I've seen that x3b and mostly always pointed to an Nvidia or Ati file, i.e GPU.

danmck · 23 Dec 2011 at 08:55

i had same isses with BSOD

was bad ram , worth running memtest. i know your BSOD points to ati drivers but so did mine. It would only happen on gaming , i could sit on desktop for hours but would crash out in 20 mins gaming.

James J · 23 Dec 2011 at 09:08

danmck said:
i had same isses with BSOD

was bad ram , worth running memtest. i know your BSOD points to ati drivers but so did mine. It would only happen on gaming , i could sit on desktop for hours but would crash out in 20 mins gaming.

You probably got a different error code, if one at all though. This is definitely GPU related.

The__Malteser · 23 Dec 2011 at 10:56

I played a bit today/yesterday, and all seems well

Thanks for the help