Problems after new build - BSOD / Display drivers have stopped responding

Associate
Joined
13 Nov 2012
Posts
6
Hey guys,

Having a few problems after a new build.

I keep getting the error within windows ""Display driver stopped responding and has recovered"

As well as BSOD with error:

BCCode: a0000001
BCP1: 0000000000000005
BCP2: 0000000000000000
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1

----

From What I've read into it, I could be related to display drivers, or perhaps my PSU, but I just can't seem to fix it.

Things I've tried:
-Flashing BIOS to most recent version
-Reinstalling ATI drivers
-Installing older ATI drivers
-Changing from Windows 8 to Windows 7
-Reseating GPU and RAM, and removing PCI wireless card.
-Using the overdrive option from within ATI Catalyst to increase power intake by 20%

My spec is the following:

Gigabyte 990FXA-UD3 mobo
AMD Piledriver 6300+
8GB Corsair RAM
Radeon VTX3D 7850

and lastly a Hiper 730W M PSU - Wondering if this might be causing the problem as its about 5 years old, and the one thing I didn't upgrade?

However, it seemed sufficient enough?

Any help would be greatly appreciated!
 
Soldato
Joined
22 May 2010
Posts
11,802
Location
Minibotpc
PSU.. try a decent make psu and see if that sorts it. If it still crashes you can always return the psu via DSR or ocuk's 14 day satisfaction thingy.
 
Associate
OP
Joined
13 Nov 2012
Posts
6
So I've upgraded the PSU and unfortunately I'm still getting the error.
"Display driver stopped responding and has recovered"
What would be the most logical thing to try next?

Thanks for the help guys.
 
Associate
OP
Joined
13 Nov 2012
Posts
6
Thanks snips86x,

Just an update on this.

Turns out it was the VTX3D graphics card. Dumped my old 8800 GTS in and the problems stopped. So I'm in the process of sending the card back.

Last time I buy a budget brand card! ;)
 
Associate
Joined
4 Dec 2012
Posts
39
Location
Bristol
Arg, I spoke to soon. Display driver failed to respond and yet more BSOD's.

Could it be the RAM that can cause this error?

Just to add my Ten pence; I had this error recurring on my old custom pc. I switched the RAM into another slot and that fixed the issue. Might not be your issue, but its worth a shot?
 
Back
Top Bottom