Solved BSOD randomly (mostly) when idle dxgkrnl.sys

[writhziden]

VTT should be bumped to 1.168 V and the system tested by doing your normal routine in Windows for twice as long as it normally takes for a crash. See if the system runs stable.

 

[ckonze]

Sounds good. I will implement that immediately.

Just out of curiosity though, if changing these values were in fact the fix, theoretically wouldn't running through Memtest86 again result in no errors? If so, wouldn't that be a quicker stability test? Don't misunderstand though. I'm not challenging your instructions. I'm really just genuinely curious. As much as this BSOD sucks, I am actually learning quite a bit through these various troubleshooting attempts.

 

[writhziden]

Running Memtest86+ is another option if you have time to do so. Often, Windows is a better test of the RAM settings than Memtest86+ because it stresses the RAM in more ways than Memtest86+ does. Also, testing the RAM through Windows allows you to do your normal routine rather than being kept from using the system during a memory diagnostic.

If you have the time and patience to run Memtest86+, it would be a good idea to do so to see if the errors still occur.

 

[ckonze]

Alright. I'll do that as an initial stress test. I most definitely have the time. My present computer needs are being met with an old iMac I have lying around. It's only my gaming that is suffering in the meantime

I'll relay the Memtest86 report once it's had several passes. If it comes up error free, than I will convert my daily computer usage back to the PC and stand by for a potential BSOD. Thanks.

 

[writhziden]

You're welcome. Let us know how things go as you progress.

 

[ckonze]

Wow! So, there have been 5 passes so far and no errors yet. The last time I ran Memtest86, the errors were early and often. Now, none. I'm not going to get too excited yet as it still has to go through a Windows stress test for a good month before it's wise to call it good. Nevertheless, it's a promising development.

Educate me. What does the VTT voltage do and how would increasing its value potentially be the fix for the problems I was experiencing? From what little research I managed to do, it has something to do with the CPU. Right?

 

[writhziden]

The VTT voltage increase provides more support for the CPU's memory controller. The default VTT in many motherboard BIOS settings is designed for up to 4 GB of RAM. Usually 8 GB will run fine on these settings, as well. Anything over 8 GB in my experience will need a voltage bump for some systems. I'm hesitant to say your problem is solved, as well. Errors in Memtest86+ leave a bad feeling, but hopefully now that you are not getting errors, Windows will run stable and you can come back in a month or however long you need to feel comfortable.

I'll remain subscribed to the thread, so whenever you are ready, just post back, and I'll get a notification in my e-mail.

 

[ckonze]

I really appreciate it. I cannot thank you enough for your patience and your continued support.

 

[writhziden]

No problem. Best of luck!

 

[ckonze]

...and again. This is frustrating.

 

[writhziden]

Your graphics card driver caused another TDR Failure: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

It appears your graphics card driver is corrupted. Re-install or install the latest drivers for your display card. Use the following method to re-install the drivers.

1. Download the drivers you want for your display card(s)
2. Click Start Menu
3. Click Control Panel
4. Click Uninstall a program
5. For AMD:
   • Uninstall AMD Catalyst Install Manager if it is listed (this should remove all AMD graphics software and drivers)
   • If AMD Catalyst Install Manager is not listed, use the following method to uninstall the graphics drivers:
     1. Click Start Menu
     2. Right Click My Computer/Computer
     3. Click Manage
     4. Click Device Manager from the list on the left
     5. Expand Display adapters
     6. Do the following for each adapter (in case you have multiple display cards)
        • Right click the adapter
        • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
        • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
        
        Alternatively:
        1. Login as an adminstrative user
        2. Click Start Menu
        3. Click Control Panel
        4. Click Hardware and Sound
        5. Click Device Manager (the last link under Devices and Printers)
        6. Expand Display adapters
        7. Do the following for each adapter (in case you have multiple display cards)
           • Right click the adapter
           • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
           • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
   • Restart your computer after uninstalling drivers for all display cards
   • Install the driver you selected for the display cards once Windows starts

 

[ckonze]

Believe me. It's no exaggeration to say that I have done that exact thing 20+ times. The last time I did it was at the same time that we last talked when you had me change the VTT value on my computer. I have the Radeon HD 7950.
AMD Radeon

So, when I get a driver, I go here:
Global Provider of Innovative Graphics, Processors and Media Solutions | AMD

I then go to the "Find a Driver" drop down in the upper right hand corner. From there I can have it auto detect the best driver for me or I can manually input what kind of GPU I have. I have done both methods about equally. When I'm manually inputting the kind of GPU I have, I put in "Desktop Graphics" for "Component Category." I put in "Radeon HD Series" for "Product Line." I put in "Radeon HD 7xxx Series PCIe" for "Product Model." Lastly, I put in "Windows 7 - 64 Bit" for "Operating System." I click "View Results." From there, I download the "Catalyst Software Suite" that they provide given the identification selections I made previously.

I detailed above everything that I do when I download new drivers because, at this point, I'm beginning to question my competency at being able to install display drivers.

Not only have I applied the driver removal method you detail here, but I have also completely reinstalled Windows as a method to remove them. I have applied the latter method far more often than the former.

This leaves me with so many questions. Are AMD's officially provided driver's corrupt? Is there anything other than a corrupt driver that could be causing this?

Can I do this yet again? Yes. But I promise you, I will be here another week or two down the line replying to this thread, reporting yet another BSOD. And I wouldn't doubt if it once again reported a corrupt driver. I'm sorry if my words come across with a bit of a bite to them. I'm just so frustrated. Before seeking help here, I sought help elsewhere for months and have been told there was a problem with my display driver so many times it makes my head spin.

 

[ckonze]

I've done all of the steps you outlined above and removed/updated graphics drivers. I guess we'll wait and see what happens next. If it stays true to form, I'll be posting again in about 2 weeks. Thanks for all of your advice.

 

[writhziden]

What about the advice in the link I gave to the 0x116 information? As you said, you have done the driver steps before. If the problem occurs anyway, there are only a few possible causes:

1. You have a software or driver conflict that is being missed
   
   
2. Your solid state drive is accumulating errors or data corruption on a fairly frequent basis. This is actually common with SSDs if there is an incompatibility with the system or if the system firmware/drivers are not up to date. Make sure the following are up to date:
   • SSD firmware
   • BIOS version
   • Chipset drivers
   • Hard disk controller drivers
   All should be post 2011 and would be best if they were late 2011 or early 2012. If all are up to date, it may be time to switch out your SSD for an HDD and see if the problems still occur.
   
   
3. A hardware issue with your graphics/display card that can be found using the steps in the link I gave for the 0x116 TDR Failure: http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[ckonze]

I'm currently running FurMark and so far (after 10 minutes) I have no issues.

I know the SSD firmware is update to date, I will figure out how to check on the others.

As far as a software/driver conflict, any recommendations on how to hunt this down? I know when this first started (back in Feb) my husband ran some sort of 8+ hour test that came recommended from a friend, no it yielded no errors.

 

[writhziden]

There are steps through Windows for stressing drivers and determining if any are causing conflicts. It appears you did them earlier in this thread when enabling Verifier. Here are the steps I provide for Verifier if/when you want to check for driver issues:

• 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 210539
  • 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.

 

[ckonze]

All firmware appears to be up to date, except I have not been able to check the Bios firmware. I have started the verifer using above instructions and restarted my computer (no issues yet).

edit: I have confirmed that the Bios firmware is up to date as well.

 

[ckonze]

New BSOD as of today. Last night my husband set everything up to run from the HDD and not the SSD. I never would have thought buying a computer would lead to months of frustration! I could had gotten a comfy new living room set instead!

 

[writhziden]

What steps were used to replace the SSD with an HDD?

You are getting hard disk errors. This could mean your memory is still having problems. Try bumping the DRAM voltage to 1.65 Volts; keep VTT at 1.168 Volts. Also, run a http://www.sevenforums.com/tutorials/433-disk-check.html with Automatically fix file system errors checked.

 

[ckonze]

To replace the SSD with the HDD, I simply installed Windows 7 on the HDD rather than the SDD. When the part came up where you can choose the drive to install to, I first chose to "delete" everything that was already on both drives and then I chose the HDD to install to and went through the rest of the process. I left the SSD unformated.

I went ahead and changed the DRAM to 1.650 Volts and I just finished running through the Disk Check on the HDD.