Sign in with
Sign up | Sign in
Your question

Driver Failure BSoD trouble :(

Tags:
  • Blue Screen
  • Driver Failure
  • Graphics
Last response: in Graphics & Displays
Share
April 3, 2014 4:29:34 PM

I have the biggest headache. I was encountering crash errors last week after reinstalling my gpu, and I had to reinstall windows because of a registery error. So I reinstalled windows, installed the newest drivers for my card, disabled the old built in gpu through the device manager (uninstalling it just prompts an automatic reinstallation upon boot) and played D3 hastle free. Then, as of yesterday, I started getting blue screened.

The first blue screen started yesterday. I was playing D3 for a couple hours when the screen when black. Everything minimized to the desktop, went full screen black, and then I got the blue screen. I turned my computer off, let it "rest" for a while, and then logged back on. After playing for a couple more hours it happened again!

I did some research on the net to find out what the cause might be, and made sure to run src /scannow (as admin) to find no problems. Then I checked my mouse and keyboard drivers.

Finally (today) I opened up the game, lowered ALL of the graphics settings and switched to windowed mode. After a couple hours of playing it crashed again, but instead of going to the Bluescreen immediately, my system went to the desktop and displayed the message "the driver software has crashed but recovered". It displayed this repeatedly after switching to a black screen and then finally crashed to the BSoD.



I'm at a loss here. I've double checked all of my drivers to make sure they are up to date and triple checked the device manager and various devices. I'm at a loss here!



My system specs are:

GPU: Asus AMD HD 7750

OS: Windows 7 64bit

Processor: AMD Phenom 2 X4 810 Quad Core

Memory: 8GB DDR2



The Blue screen info I tried to grab but closed (including after boot up) before I could read everything but it was a 1033 BCCode: 116.



Also interesting to note (though it may not mean anything), when I ran AMD auto detect and install it said that the card name was "0x1002-0x9619 PCI 0x1002-0x683F PCIE"

More about : driver failure bsod trouble

April 3, 2014 5:04:45 PM

I would monitor the CPU and GPU temperatures while gaming and see if they go to some insane levels. You can use this http://www.cpuid.com/softwares/hwmonitor.html or just google for similar programs that monitor your CPu and GPU temps.
m
0
l
April 3, 2014 5:11:16 PM

I've read about the temps problem before (and thanks for posting a link rather than just saying "check your temps") so I'll run that program. However the comp doesn't feel warm (the psu does but not hot), while nice cold air is running out of the side.
m
0
l
Related resources
April 3, 2014 5:21:53 PM

Okay so it looks like the comp runs at about 38 degress celc at standalone. During D3 the temp jumps to about 48-50 (with a screen full of creatures).

ALSO there is a sound coming from the GPU. Now this may mean absolutely nothing, but its an audible buzzing. Almost like a hiss (but still clearly a buzz if that makes sense) coming from the gpu during gameplay. I was told that this could be the ball bearings attached to the fan. It only makes the sound when playing the game and at no other time.
m
0
l
April 3, 2014 5:24:08 PM

I think this is a driver issue and also might the power supply insufficiency.
m
0
l
April 3, 2014 5:26:40 PM

the power supply is brand new. It's an EvGA 600w Bronze. It meets all of the qualifications for the card and then some.

As for the drivers, that seems like the most likely scenario, however everything is up to date. Running src /scannow got me nothing and I'm at a loss here. Not really sure what else I could be running that would help me out.
m
0
l
April 3, 2014 5:27:04 PM

Well, maybe one of your fans isn't spinning properly, or the heatsink could be blocked with dust etc. which would prevent the given component (CPU, GPU) of getting proper cooling. At first (when you have just turned on your PC) it would work well for a while but in hardware intensive stuff like games the temperatures will slowly raise until they reach a point where the PC either shuts down or hangs or similar. At least that's what happens usually.

I see..

That noise you are hearing is what people refer to as "coil whine". I usualy get coil whine from my PSU when playing some older games and haven't enabled v-sync so my FPS go to like 350-400 FPS. But for you to get that type of blue screens etc. I presume it's more than just coil whine.

Did you manage to see what is the GPU temp in game? You only said about the CPU.
m
0
l
April 3, 2014 5:29:15 PM

I'll look into that now. I cleaned out all of the fans when I installed everything (the psu and gpu), but I wasn't aware of any heatsink and that might be clogged to high heaven.

I'm also unsure as to whether or not that would cause a blue screen driver failure (I'm not TOO literate when it comes to this stuff) or just a power down.
m
0
l
April 3, 2014 5:32:22 PM

It is somewhat a graphics driver conflict. I remember that I had this one when I changed graphics card and ended with corrupt system files. Making me to reformat whole my PC.

You also mention that "src /scannow" it supposed to be "sfc /scannow".
m
0
l
April 3, 2014 9:54:31 PM

So I ran disc check from start up and installed all of the new windows updates. I haven't played the game long enough to notice another blue screen HOWEVER, I did run SRC and found nothing, as well as the system check for corrupt or missing files. I'm going to try cleaning the heat sink next.
m
0
l
April 3, 2014 9:56:55 PM

The only conflict I can find in the device manager btw is between the built in graphics card (AMD 3200) and the current installed one. I can't uninstall the old one because on every start up it automatically reinstalls it into the computer. The only thing I can do with it is disable it.
m
0
l
April 4, 2014 12:14:58 AM

I'm not entirely sure but I think there should be an option for you to disable it from BIOS. It would be better to do it straight from there rather than from Windows Device Manager.
m
0
l
!