Multiple BSOD's caused by everything from Youtube to BF3

[RedHawke]

Ok so everything seemed to be going fine. The driver did not automatically update again and I had no more issues, until yesterday. Yesterday the pc was just sitting on my desktop with no applications open when it suddenly started getting the error where your driver has stopped responding and has recovered over and over for about 5 minutes followed by a blue screen of death. I have attached the image of the first error and the crash dump. Edit* The driver was not updated, the driver which had this issue was the 306.23 driver.

Generally this is a hardware error. It happens as the GPU is taking more time than permitted to display graphics to your monitor. We tried with different driver versions, got the same results. Now, IMHO, if you try to increase the GPU (Graphics Processing Unit) processing time by adjusting the Timeout Detection and Recovery registry value, It will not be a good attempt, as said here:

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly.

Source: "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista

I would suggest you to not modify the registries if you are not sure yourself what you are doing. Coz those settings will continue in registry even after you change the GPU. So better you replace your GPU.

So are you saying I need to replace my GPU? Also how do I change the the timeout detection and recovery registry value back to normal if I already changed it with the "fix it for me" application on this page you linked to me http://support.microsoft.com/kb/2665946

Edit* Also do you think this "hardware issue" might have anything to do with the 32 inch hdtv I started using as a monitor? - In addition did you check the latest crash dump from the bsod that happened right after the "display driver has stopped responding and has recovered errors?" Is that a separate issue or the same thing.

 

[Arc]

If you have changed the registry values, a system restore to a date earlier than today, or a repair install will get teh right registry values back.

BTW, concentration got troubled for some unwanted situations .... missed the crash dump to check. Yes, that is graphics related, undoubtedly, but indicating to LucidLogix Virtu.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800d66a4e0, fffff88003ff367c, ffffffffc00000b5, a}

Unable to load image \SystemRoot\system32\DRIVERS\[URL="http://www.carrona.org/drivers/driver.php?id=VirtuWDDM.sys"]VirtuWDDM.sys[/URL], Win32 error 0n2
*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=VirtuWDDM.sys"]VirtuWDDM.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=VirtuWDDM.sys"]VirtuWDDM.sys[/URL]
Probably caused by : [URL="http://www.carrona.org/drivers/driver.php?id=VirtuWDDM.sys"]VirtuWDDM.sys[/URL] ( VirtuWDDM+867c )

Followup: MachineOwner
---------

And the program is not the latest version there.

fffff880`03feb000 fffff880`04000000   VirtuWDDM T (no symbols)           
    Loaded symbol image file: VirtuWDDM.sys
    Image path: \SystemRoot\system32\DRIVERS\VirtuWDDM.sys
[COLOR=Red]    Image name: VirtuWDDM.sys
    Timestamp:        Thu Jul 07 18:10:25 2011[/COLOR] (4E15A939)
    CheckSum:         0001FFD7
    ImageSize:        00015000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Earlier I have noticed that stop 0x116 issue got solved by uninstalling Virtu, but you may try to update it as a test before uninstalling it. Get it from lucidlogix with GPU Solution

Saying again, sorry for missing the crash dump. My concentration to the issue got hampered.

The hardware issue should not be connected with the monitor, but might be connected with the virtualization of GPU.

Keep the decision of replacing the GPU pending before the Virtu update/uninstall test completes.

 

[RedHawke]

Ok thanks! I will do that.
Also what is this "LucidLogix Virtu" anyways?

 

[Arc]

Ok thanks! I will do that.
Also what is this "LucidLogix Virtu" anyways?

It is used vor GPU virtualiazation. about lucidlogix
You have it installed

Start Menu\Programs\VIRTU

And it is running.

NAME | DESCRIPTION | FILE | TYPE | STARTED
virtuwddm | VirtuWDDM | c:\windows\system32\drivers\virtuwddm.sys | Kernel Driver | Yes

Uninstall it, and free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

1. Click on the Start button
2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
3. Select the “Startup” tab.
4. Deselect all items other than the antivirus.
5. Apply > OK
6. Accept then restart.

 

[RedHawke]

Alright I removed the lucidlogix virtu completely, but this morning I still had the same issue again.
I got repeated "your display driver has stopped responding and has recovered" for 5 minutes again (though this time it was while streaming on youtube) followed by a BSOD. I have attached an image of the error again and the New Crash Dump.

 

[Arc]

You said that you tried the fixit "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista too?

As a last try, swap with a few other versions of display driver (other than 310.** and 311.**) and if you still have the same result, there is no way but abandon the GPU.

Personally I faced that issue, koolkat77 guided me over all possible fixes and later checking the temperature of my GPU over time, abandoned that one. After the GPU got replaced, never faced that incidence over last 9 months.

 

[RedHawke]

Unfortunate I will have to replace it but ok
Also it is not the temperature. I have been monitoring it.