Graphics drivers crashing homebuild

[EmeraldClaws]

Hey, about 6 months ago I asked about building a computer, everyone here was great and I was really happy with my build. Had a bit of trouble installing windows, but I got it working.

On Sunday it had a few blue screens, and due to to the way I deal with things, it seemed like it'd be easier to just reinstall windows. It was not.

Windows itself installs fine, when I come to install the motherboard drivers, doing all at once results in a restarting a few seconds after the mouse shows up on startup, doing each individually identifies the problem driver as Intel HD graphics 4000. I've tried this from the CD, the internet and from windows update and it's still not working.

When I try to install my dedicated card, the same thing happens, whether I install the graphics before or after putting the card in.

I use both though and have had it working before, so it's not an option to just get the dedicated card to work.

Specs
Intel i5 3570k
GA-Z77-DS3H (Rev 1)
Gigabyte HD 7770 (Rev 2)
XFX ProSeries 550 Watt
16GB DDR3 1600 MHz (2x8GB)

Unfortunately that's as much info on the ram as I can give you, the ebay page I bought it from doesn't exist anymore, so I can't be more specific, though it was only £65, so I'm guessing it's not too great. Any ideas/suggestions are appreciated?

[Domestic_Ginger]

Intel do a self scanning/updater for the onboard. may be worth a shot or just turn it off and use the 7770 (not what you wanted to hear I imagine) and come back to update the drivers when you feel strong.

[EmeraldClaws]

Thanks for your suggestions, i tried the self scanner but it didn't work. I've also tried installing the 7770 and had no luck with that. it crashes with a 0x7E starting up normally, and an 0xf4 in safe mode.

[Zak33]

First... take out the graphic card. Unplug it and put it on your desk. I need to know its OUT.....

Now install the Windows operating system and see if all is well. Fresh install.. it's pretty quick.

Because, you need to remove the potential errors and the graphicd card 7770 is one of them. (it MIGHT be dead,. hence the blue screens... but lets NOT assume yet)

Get Win7 running on the motherboard graphics first. Update the drivers on the whole board inc graphics.

IF... you get that running well (bet you do)... the put the 7770 card BACK IN... plug the monitor into the added 7770 graphics card,, then reboot and see if it boots ok.. if it does, then install AMD's latest Radeon drivers and see if it still boots.

What you 're trying to do is

A) take out ALL potential issues and install Win7 fresh
B) Get Win7 solid
C) Install ONE thing at a time
D) find the issue

[EmeraldClaws]

Ok, the 7770 is out and on the desk.

I start by installing the latest graphics driver first. Restarted then this...

Stop 0x00000050 (0xFFFFFFFFFFFFFF89, 0x0000000000000001, 0xFFFFF960000D953E, 0x0000000000000000)
win32k.sys - Address FFFFF960000D953E base at FFFFF96000070000, Datestamp 4a5bc5e0

I can get into safe mode and uninstall the driver if needs be. I'll wait for you judgement before I do though

Started it up again and got a different error this time, thought I'd post it here incase it gives a clearer understanding of what's going on:
0x0000007E (0xFFFFFFFFC0000005, 0xFFFFF960007EFF3D, 0xFFFFF88002EC5FA8, 0xFFFFF88002EC5800)
cdd.dll address FFFFF960007EFF3D base at FFFFF960007D0000, DateStamp 4a5bde94

0x000000F4 (0x0000000000000003, 0xFFFFFA800EF12350, 0xFFFFFA800EF12630, 0xFFFFF80002B99240)

[ajones]

What BIOS version is the Mobo running?

[EmeraldClaws]

BIOS version is F2

[ajones]

BIOS version is F2

Oh.. bit old that. According to the CPU support chart for this board, your CPU was added in F8 (although to be honest it's a bit misleading since all CPUs, SB or IB were first supported in F8!). There's also a microcode revision in F9, although I've no idea what was fixed in it. There are mixed reports on the F10f beta BIOS, some folks saying it's the wonder BIOS (especially for 16GB systems whereas before it was only reporting 8GB) and others needing to downgrade to F9.

Sounds to me like a BIOS upgrade is needed here.

[EmeraldClaws]

Sounds to me like a BIOS upgrade is needed here.

Hopefully this'll fix it. Just updated to F9, installing windows now.

No luck I'm afraid, exactly the same as before, windows installs fine, then as soon as I install the 4000 driver, it bluescreens on boot

[ajones]

bugger. Still, at least you've a relatively an upto date BIOS now!

I hate MS error codes, always seem to mean many things: http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

Think you are going to have to look at the hardware basics (you can't get past step B from Zaks list above!). One of the problems reported on the F9 BIOS was that the MoBo only recognised 8GB of RAM in a 16GB system. Can you try running up the system only with a stick RAM stick? (checking each stick in different slots in case there's a dodgy slot). Get Win7 up then increase RAM to 16GB later.

Remove everything that is unecessary so that you can try to eliminate hardware problems. There's the old route of adding each subsystem one at a time (cpu > memory etc) and checking the POST reports only the expected error.

There are also some general reports that suggest that there is a problem with the socket on this mobo, leading to poor connections between the CPU and LGA socket. A gentle wriggle of the heatsink seems to be the most common fix to make sure the CPU is seated firmly - may be BS but who doesn't like a quick wriggle?

Other than this, I'd be looking at testing the components on a different system if you can.

[Splash]

0x00000050 is a pagefault in nonpaged area error. Given this, as well as the somewhat random nature of these errors I'm pointing at your RAM - can you run Memtest for a while with just one module installed at a time and see what happens?

[EmeraldClaws]

Memtest-ing now. What's the recommended amount of passes before we can be "pretty sure" that the memory's not broken?

Unfortunately I've been thinking it was the ram for some time. I tried to find out more about it, brand name ect but the guy I bought it off on ebay (Sounds stupid, but his reputation was good and it wasn't listed as second hand) has closed his account, so I only know as much as it says on the stickers, which isn't much.

As for testing components on different systems, the only one I can do is the graphics card. I'll have a go at that now.

EDIT: Nope, no systems. Just opened up the one I was going to test it on, but it's not got a 6-Pin power plug, the card came with a molex + molex to 6 pin, but the one I just opened up only has one molex. I have a molex to molex + molex, is there any point trying that?

[Splash]

I'd probably be looking at a minimum of 8 hours, pref 24 for Memtest for each module.

It could also be a duff RAM slot - so you're probably looking at testing each module in each slot too.

One other thought: are you overclocking at all? If so do you still get the same errors at stock?

[EmeraldClaws]

What I've done so far is done three passes (2 hours) in each slot to check the slots, so far they've all turned up clear. As soon as I've done the fourth slot I'll put it back in slot one and run it for 24 hours.

I'm not, I saw something about upping the voltage from 1.5 to 1.6 or 1.65, tried 1.6, no effect, didn't want to go and further, but it's back at stock now.

[Splash]

If the RAM checks out after 24 hours then I guess your next point of reference is either PSU or hard drive. Hard drive is easier to rule out with a low level format and vendor disk check.

[kalniel]

Well could be a faulty CPU as well - bad PCI-E controller or broken PCI-E lanes for eg.

But I wouldn't entirely rule out software still either. Tried running linux from a USB or something?