Solved BSOD Restart Display Driver (For Hd5850 and HD 6970, no crossfire)

[writhziden]

Problem Devices:

Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_04\4&108ABD8A&0&00E4	The drivers for this device are not installed.
SM Bus Controller	PCI\VEN_8086&DEV_1C22&SUBSYS_844D1043&REV_05\3&11583659&0&FB	The drivers for this device are not installed.
Universal Serial Bus (USB) Controller	PCI\VEN_1033&DEV_0194&SUBSYS_84131043&REV_04\4&DDEC341&0&00E1	The drivers for this device are not installed.
CanoScan	USB\VID_04A9&PID_2224\6&DF2EE03&0&7	The drivers for this device are not installed.
PCI Simple Communications Controller	PCI\VEN_8086&DEV_1C3A&SUBSYS_844D1043&REV_04\3&11583659&0&B0	The drivers for this device are not installed.

In the latest crash, your chipset, Intel Management Engine Interface, and USB drivers were not installed; make sure they are installed now from your motherboard support site. GIGABYTE - Motherboard - Socket 1156 - GA-P55-UD3 (rev. 1.0) -> Drivers -> Windows 7 64bit


Your crashes point to the SSD. Due to the firmware update, you may need to power cycle the SSD:

• The following steps should be carried out and take ~1 hour to complete.
  1. Power off the system.
  2. Remove all power supplies (ac adapter then battery for laptop, ac adapter for desktop)
  3. Hold down the power button for 30 seconds to close the circuit and drain all components of power.
  4. Reconnect all power supplies (battery then ac adapter for laptop, ac adapter for desktop)
  5. Turn on the system and enter the BIOS (see your manual for the steps to enter the BIOS)
  6. Let the computer remain in the BIOS for 20 minutes.
  7. Follow steps 1-3 and physically remove the SSD from the system by disconnecting the cables for a desktop or disconnecting the drive from the junction for a laptop.
  8. Leave the drive disconnected for 30 seconds to let all power drain from it.
  9. Do steps 1-3 and replace the drive connection(s) and then do steps 4-8 again.
  10. Repeat steps 1-4.
  11. Start your computer normally and run Windows.
  
  The above steps were a result of: Why did my SSD "disappear" from my system? - Crucial Community
  
  While that may not be your drive, a power cycle should be the same on all SSD drives. See how the system responds after the SSD power cycle.

 

[ugd]

The dumps given here were from before upgrading the firmware.
Oh and i was after the upgrade having the same problems with the regular hdd. Bsods while installing, and errors and such.
I did a memtest86 just now i got errors in the thousands for both crossairs (done separately)
I suppose that can explain all the errors all over the place. But i was wondering, checking my older ram which didn't get any errors (only a quick run to check). Got their info shown up in memtest86, while the crossairs did not. Could memtest be affected by not knowing what it's dealing with? Or if the memory is running on lower speeds etc?


EDIT: With the old ram i was finally able to upgrade windows, and got to use the reg key.

 

[writhziden]

I am not sure whether Memtest86+ will have problems if it misreads the RAM info. It is fairly uncommon for it to misread it, but it does happen on newer systems. Your troubleshooting step to switch out the RAM and test through Windows was what I would have suggested, so see if the old RAM provides stability where the new RAM did not. Let us know after you have had a chance to test it more whether the system is stable.

Nice work thinking ahead!

 

[ugd]

It seems odd to me that both sticks were getting errors all over the place. From the moment the test started running. These are 1600 MHz sticks, but it was set to 1333 instead. I figured it had to do with the processor "limits". I turned it up to 1600 MHz, since it's supposed to be able to handle that. But i let the bios handle the voltage automatically. (oc'ing set to auto) Could this have damaged it?
I sent the two Corsair (I know i keep writing them wrong...) back today, and seeing as I've had no problem yet, and how frequent the problems were getting and how many bsods i had yesterday i was thinking of waiting to see what the store i bought the corsair from figures out. But I might give it a go later today, or tomorrow with the old ones.

 

[writhziden]

It is unlikely the RAM was damaged by setting them to 1600 MHz. More likely the RAM was faulty when supplied through the kit or became faulty due to ESD damage. Avoid Static Damage to Your PC may be good further reading.

What frequency were you running at when crashes were occurring and when the memtest86+ diagnostics were run? It could also be the memtest86+ is throwing errors due to bad RAM settings.

 

[ugd]

I thought about static. "Frying" one stick is one thing, but two seems a bit odd considering i was "caressing" everything when building the computer, and i can't see any problems with those parts.

It was back to default settings 1333, threw everything back to default when this started. Though i set the sata settings to ide instead of ahci when i was getting the bsod errors during w7 installation. Not that, that should affect the test.

 

[writhziden]

The RAM probably arrived faulty, is incompatible with your system, or the settings are not right. You could contact the RAM manufacturer and find out whether they believe the RAM should work with your motherboard and CPU.

 

[ugd]

It should, it was sold as a package, ram motherboard and cpu together. And seeing the reviews on the package were mostly 5 out of 5, with an occasional 4 out of 5, and others mentioned increasing the speed on their setup from 1333 to 1600, but whether or not they did it manually i don't know. Tells me it works. But yeah if they find no fault with the sticks i only have to pay 30$.
I ran the memtest with the old sticks, but only with 3 passes as i needed the computer again, and I'm not too fond of leaving it on when I'm out. I didn't get any errors.



As for the previous problem, with the older build it seems like the problem was either with the motherboard or cpu. Chances are higher for the mb then cpu.

The new problem seems to be with the memory sticks.
(just in case this has all been a mess, and people look for solutions here..)

 

[writhziden]

Wasn't aware it was sold as a package. Let us know whether or not the RAM manufacturer finds anything.

Thanks for posting back for others, too.

 

[ugd]

Ok, they found the sticks to be defective. I suppose this one can be marked as solved.
Thanks for the help!

 

[writhziden]

You're welcome. Glad it worked out in the end.