Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VS2012 Unstable
Message
De
26/11/2012 14:40:47
 
 
Information générale
Forum:
ASP.NET
Catégorie:
Visual Studio
Titre:
Divers
Thread ID:
01557954
Message ID:
01558108
Vues:
49
>In my case the BSOD, I think, is caused by memory but not necessarily faulty memory chip (I used the utility you recommended and it found no fault). What I see before the BSOD "fires" is my screens go haywire; they start jumping around, size changes, go On and Off. This goes on for about 5-15 seconds and then very quiet :).

A video problem like that could have several causes:

1. Bad cable connections if you're using more than 1 monitor. Try to avoid "converters" in cables e.g. DVI to VGA. Try to use digital over analog connections e.g. HDMI better than DVI better than VGA

2. Bad video driver. Try using the latest from Windows Update or your computer manufacturer (Dell, HP etc.) or chipset maker (nVidia, AMD)

3. Bad video adapter hardware. All adapters have a controller; if you have a so-called "discrete" adapter it will also have its own video RAM rather than using some of the main system RAM. Either a controller or video RAM failure can cause symptoms like you're seeing.

4. There is a small chance a secondary monitor (if you're using more than 1) could cause problems like this. If you can try a different secondary monitor, do so. If not, try running with just 1 monitor for a while - longer than it would normally take to generate a BSOD - to see if that makes a difference. If the BSODs go away, it could be the secondary monitor, or software/drivers that support multi-monitor operation.
Regards. Al

"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov

Neither a despot, nor a doormat, be

Every app wants to be a database app when it grows up
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform