Solved Frequent BSODs after changing Graphics Card

[Here is Johnny]

I just got it back and they've exchanged RAM. It's working just fine now and I hope it'll be so in the future, but there is a question: why RAM failed when I plugged new video card in? And how am I supposed to upgrade the card without such issues?

EDIT: The new card (Radeon 6770) is still at repairs.

 

[writhziden]

It is likely the RAM was bad before the video card was plugged in, but due to the video RAM increase or video RAM speed increase, there was more data being swapped through your RAM and the previously unknown faults caused crashes.

 

[Here is Johnny]

Well, I'd like to say that everything's fine and working properly, but I can't. BSODs are still there. Latest minidumps attatched.

I think maybe there's something wrong with the slots, not the RAM itself.

EDIT: What about the PSU? Is it possible that 420W Tracer works better than 500W Chieftec?

 

[writhziden]

Unless you have a faulty motherboard, I would not suspect the RAM slots. Was this latest crash without the new graphics card in?

The latest crash indicates memory_corruption. Since the RAM has been replaced, I suspect a driver issue. I do see your Atheros LAN driver is out of date. Please update it from MSI Global ? Mainboard - 760GM-P33


I also still see nVidia software installed. Is this intentional? Are you now running with your old nVidia card again?

 

[Here is Johnny]

Yep, this nVidia software is installed on purpose. I'm using my old card, cause the new one is still being checked by Sapphire.

Driver for Atheros LAN updated.

New minidumps attatched.

 

[writhziden]

Check your drivers:

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do the following:
  
  a. Backup your system and user files
  b. Create a system restore point
  c. If you do not have a Windows 7 DVD, Create a system repair disc
  d. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    View attachment 212761
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using http://www.sevenforums.com/tutorials/700-system-restore.html OPTION TWO.
  
  Thanks to zigzag3143 for contributing to the Verifier steps.
  If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.​
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.
  
  When you are ready to disable Verifier: Start Menu -> All Programs -> Accessories -> Right click Command Prompt -> Run as administrator -> Type the following command and then Enter:
  verifier /reset​
  -> Restart your computer.

 

[Here is Johnny]

OK, I think that will be enough. Verifier is reseted.

Minidumps attatched.

 

[writhziden]

Looking more and more like hardware... Let's check if the RAM is compatible with your motherboard and processor:

Download and install CPU-Z and Upload screenshots of the CPU, Mainboard, Memory, and SPD tabs. In the SPD tab, upload an image of each slot.

 

[Here is Johnny]

OK, here are requsted screenshots.

View attachment 213187
View attachment 213188
View attachment 213189
View attachment 213190
View attachment 213191

 

[writhziden]

AMD processors' memory controllers have a hard time handling 800 MHz RAM without BIOS setting changes. It appears your RAM is overclocked, anyway, so please clock it down to 666 MHz. The first four timings should still be 9-9-9-24. See if that provides more stability.

 

[Here is Johnny]

I'm not sure how to do this. I haven't overclocked it, so I don't know how to clock it down. Could you give me some hints?

 

[writhziden]

First, try going into your BIOS and go to the Exit screen. Load setup defaults or fail safe defaults depending on what options you have. Check your memory tab in CPU-Z to see if it still shows 800 MHz.

 

[Here is Johnny]

Loaded fail-safe defaults and it's still 800 MHz.

 

[writhziden]

That doesn't seem right. Please fill in your system specs so I do not have to read through your thread to determine your motherboard and find the motherboard manual to determine how to guide you in manually changing the frequency.

http://www.sevenforums.com/tutorials/180324-system-info-see-your-system-specs.html

Fill the system specs in on your profile, not in a post in this thread.

 

[Here is Johnny]

Done.

 

[writhziden]

Any difference in the frequency if you load optimized defaults?

If it still give 800 for optimized, try setting the first four timings to 7-7-7-20

Cas Latency (CL) - TRCD - TRP - TRAS = 7 - 7 - 7 - 20

Also, change the Memory Timing to 2T.

 

[Here is Johnny]

I switched to optimized and it's still 800 MHz. I also changed Memory Timing to 2T, but I can't change anything with the four timings as all these options are greyed out.

BTW, the new card is back from Sapphire. I'm picking it up from the shop next week.

 

[writhziden]

You need to set the DRAM timings to manual in order to change them. Advance DRAM Configuration -> DRAM Timing Mode -> Manual

 

[Here is Johnny]

I've set CL, TRCD and TRP to 7, as you said, but the only option for TRAS was Auto, so I left it that way. Unfortunately, it didn't worked and I changed it back to Fail-Safe defaults.

 

[writhziden]

See if the system is more stable with fail safe defaults. If not, try optimized defaults and see if the system is any more stable.