I sure hope someone more skilled than myself (into computer since 1983, electronics engineer) can give this a read, because it's stumped me for years. Ok a few years ago I bought an ECS micro ATX, AMD X2 64 4000+ BH-G1 Brisbane, and SuperTalent 2x 1GB non-ECC DDR2-800. (Bear with me.) Also 2x SATA 80GB drives in a RAID0, CoolerMaster Real Power Pro 650W PFC supply, and a GeForce 8600GTS. Was on WinXP Pro, now Win7 Pro. Tried both 32 & 64-bits, same deal. Never overclocked any of it, and from the very first day, experienced similar problems. The issue is rather convoluted:
Windows will run 2D graphics without issue. And 3D graphics apps like games or whatnot run fine, as long as they are windowed. However, running *anything* full-screen (requiring a graphics mode change) will start the issue. And that is:
1. Random video "blackouts" - mouse cursor still visible and movable, audio playing, but nothing else seen. Happens maybe once every 6 hours on average but can go days without occurring. Can alt-tab out and back to a blacked-out screen. Sometimes partially-blacked out, and/or "cutting planes" exaggerated, and move with character. Exiting the game usually returns to desktop, upon which time navigating an explorer window (or doing just about anything really) may cause a "video display driver stopped responding" error, which Win7 can often recover from, but not always. Infrequently, "snow" also appears on the desktop, but usually clears itself up. Once any of these things manifest, system stability is significantly compromised, and a BSOD may occur doing almost anything, but never without provocation (User must click on something.)
2. Video "scrambling" and artifacts. More frequently, various parts of the video frame become scrambled, both textures and color. Vertexes may be distorted in 3D. It may do it for a second, clear up, then stop for hours, or stay scrambled for awhile, or do it a few times rapidly then crash. Once it does any of this, the chances for a "video driver stopped responding" or "video driver in infinite loop" BSOD dramatically increase, and may occur at any time, without provocation.
3. Video "stuttering" and much increased time changing video modes. Alt-tabbing from a (working) fullscreen game, or experiencing any of the previous issues, might cause further alt-tabs to take an exorbitant amount of time, up to 30 or 45 seconds or more, to complete. During this time, the display flickers on and off about six times as it struggles to change modes. A BSOD can occur in this process.
Now this all sounds definable as a power issue, old drivers, or RAM... until I talk of what has been replaced in this system. EVERYTHING but the CPU, RAID, and RAM have been replaced with different components, yet exhibit the same results. I've tried WHQL's to Guru3D drivers, and update frequently. Even have a new monitor (only one, nothing fancy there.) Temps are good, voltages are good. Even under-clocked the CPU and RAM to half their rated speeds, toyed with their voltages across the safe range, tried running on each RAM stick separately, and nothing has EVER helped one iota. I don't have any other DDR2 RAM to test with, but ran memory tests for DAYS without a fault. Went through two mainboards, tried both onboard videos and the 8600GTS, all did the same thing.
The 8600GTS recently died, because the old ECS board had bad caps (tried replacing but lead-free solder proved to be a bitch to work with.) New board is a Biostar TA780G mini-ATX with ATI onboard vid... and get this, the ATI video driver crashes in place of the nVidia driver! Baffling.
At this point, I'm thinking of buying 2 Corsair 2GB DDR2-800 sticks, a better CPU (Phenom II x4 920 AM2+), and a GeForce GTS 450. I want to know what the culprit is that has been plaguing me all these years, and squash it like a little bug!
What do you think this problem could be, defective CPU? I can't find any links between these components and the stated video errors. Then again, defining the "error" is hard in itself. But over the years, I've logged many hundreds of BSOD's... sometimes a handful a day. Very annoying. The only reason this has gone on, is because I'm not an avid gamer. When I do play, I like to heal, so imagine how frustrating it is when the party healer goes linkdead multiple times a night... same with tanking.
Thanks for looking, have a great day.
Regards,
Mark
Windows will run 2D graphics without issue. And 3D graphics apps like games or whatnot run fine, as long as they are windowed. However, running *anything* full-screen (requiring a graphics mode change) will start the issue. And that is:
1. Random video "blackouts" - mouse cursor still visible and movable, audio playing, but nothing else seen. Happens maybe once every 6 hours on average but can go days without occurring. Can alt-tab out and back to a blacked-out screen. Sometimes partially-blacked out, and/or "cutting planes" exaggerated, and move with character. Exiting the game usually returns to desktop, upon which time navigating an explorer window (or doing just about anything really) may cause a "video display driver stopped responding" error, which Win7 can often recover from, but not always. Infrequently, "snow" also appears on the desktop, but usually clears itself up. Once any of these things manifest, system stability is significantly compromised, and a BSOD may occur doing almost anything, but never without provocation (User must click on something.)
2. Video "scrambling" and artifacts. More frequently, various parts of the video frame become scrambled, both textures and color. Vertexes may be distorted in 3D. It may do it for a second, clear up, then stop for hours, or stay scrambled for awhile, or do it a few times rapidly then crash. Once it does any of this, the chances for a "video driver stopped responding" or "video driver in infinite loop" BSOD dramatically increase, and may occur at any time, without provocation.
3. Video "stuttering" and much increased time changing video modes. Alt-tabbing from a (working) fullscreen game, or experiencing any of the previous issues, might cause further alt-tabs to take an exorbitant amount of time, up to 30 or 45 seconds or more, to complete. During this time, the display flickers on and off about six times as it struggles to change modes. A BSOD can occur in this process.
Now this all sounds definable as a power issue, old drivers, or RAM... until I talk of what has been replaced in this system. EVERYTHING but the CPU, RAID, and RAM have been replaced with different components, yet exhibit the same results. I've tried WHQL's to Guru3D drivers, and update frequently. Even have a new monitor (only one, nothing fancy there.) Temps are good, voltages are good. Even under-clocked the CPU and RAM to half their rated speeds, toyed with their voltages across the safe range, tried running on each RAM stick separately, and nothing has EVER helped one iota. I don't have any other DDR2 RAM to test with, but ran memory tests for DAYS without a fault. Went through two mainboards, tried both onboard videos and the 8600GTS, all did the same thing.
The 8600GTS recently died, because the old ECS board had bad caps (tried replacing but lead-free solder proved to be a bitch to work with.) New board is a Biostar TA780G mini-ATX with ATI onboard vid... and get this, the ATI video driver crashes in place of the nVidia driver! Baffling.
At this point, I'm thinking of buying 2 Corsair 2GB DDR2-800 sticks, a better CPU (Phenom II x4 920 AM2+), and a GeForce GTS 450. I want to know what the culprit is that has been plaguing me all these years, and squash it like a little bug!
What do you think this problem could be, defective CPU? I can't find any links between these components and the stated video errors. Then again, defining the "error" is hard in itself. But over the years, I've logged many hundreds of BSOD's... sometimes a handful a day. Very annoying. The only reason this has gone on, is because I'm not an avid gamer. When I do play, I like to heal, so imagine how frustrating it is when the party healer goes linkdead multiple times a night... same with tanking.
Thanks for looking, have a great day.
Regards,
Mark