- Jun 30, 2004
- 16,122
- 1,738
- 126
The "Topic Summary" doesn't adequately describe my "incident" -- so let me explain.
I have a ten-month-old Viewsonic VX2235wm widescreen LCD monitor.
Perhaps -- I've grown a little careless -- unplugging the DVI plug with the monitor in "sleep" (amber) mode after shutting down the computer. Let me explain why I'd want to unplug it.
I have three computers here, operating through an old Belkin KVM 4-port switch. I am using two monitors -- one for my old Pentium 4 file server, the other for my Conroe and Penryn systems. The monitor for the server is Viewsonic E70f CRT-flat-screen (analog connection). So I'm sharing keyboard and mouse between all three systems, and I'm sharing the LCD monitor between two of them.
The latter two are using the same motherboard, BIOS revisions differing to optimize each for the respective Q6600 and E8400 processors. The E8400-based system has only recently been built, with two BFG nVidia Geforce 9600 GT cards in SLI. The Q6600 system has never had problems; it is OC'd to 3.15 GHz.
I have been carefully OC'ing the Penryn system. It uses 4GB 2x2GB of G.SKILL memory. It is running VISTA 64. The Q6600 system runs XP MCE 2005.
I had been switching the VX2235 monitor between the systems. The Penryn system is sort of a "pet project" for VISTA 64 -- so far, a success.
After running up the Penryn VISTA 64 to 3.82 Ghz and testing for some 5 hours with PRIME95 small-FFT test, I set it back to the less stressful 3.6 Ghz OC setting. There had never been any lockups, need for CLR CMOS, BSOD (except for initial troubles installing VISTA 64 -- thoroughly resolved), or any other abnormal difficulties as I proceeded to Over-clock. Remember -- I had extensive experience with this motherboard on the Q6600 system.
I decided that I need to test the RAM more thoroughly at the 3.6 Ghz settings -- not to confuse you -- this is the VISTA-Penryn system. These are DDR2-1000, running at DDR2-800 and the stock latencies (spec'd for DDR2-1000). The voltage was fixed near the bottom of G.SKILL's recommended acceptable range.
To test the RAM, I ran the PRIME95 Blend Test.
Twice, after running Blend Test for approximately 20 minutes, a BSOD would pop up and state "Hardware failure: consult hardware vendor." At this point, I am beginning to suspect the G.SKILL RAM modules, even for twisting up their voltage a bit more. I shut down the system, deciding to go back to my proven XP Q6600 system (same mobo model). I chose to reboot the Penryn and select "NORMAL" startup, shutting it down through VISTA normally. With the Penryn VISTA system shut-down (Viewsonic monitor in "amber" sleep mode), I removed the DVI plug and placed it back on the XP system.
Booting the XP system, I see the monitor blue light on, but no screen. Dead -- and black. I hit the ol' reset button. Nothing -- same result. I shut down the XP system, tried to turn off the monitor. The screen turns into a "checkerboard." I was finally able to turn it off. I unplugged it. I turned off the PSU of the XP system, unplugged the power cable, waited, plugged it back in, plugged the Viewsonic cable back on the graphics card, started up the XP system after powering up the Viewsonic, and . . . . all is well.
What may have happened here? I am thinking that my problem with the VISTA system is not the RAM, but more likely some glitch with regard to the monitor which may have occurred after dropping back to my earlier BIOS settings and less stressful over-clock.
YOUR INSIGHTS ARE EAGERLY -- EVEN DESPERATELY SOUGHT. I hate the thought of having to RMA this Viewsonic monitor, and for the moment, it looks as though it's working fine again. If there is a RAM problem on the VISTA-Penryn-SLI system instead, I can RMA or just pick up another DDR2 RAM kit for less than $100.
I have a ten-month-old Viewsonic VX2235wm widescreen LCD monitor.
Perhaps -- I've grown a little careless -- unplugging the DVI plug with the monitor in "sleep" (amber) mode after shutting down the computer. Let me explain why I'd want to unplug it.
I have three computers here, operating through an old Belkin KVM 4-port switch. I am using two monitors -- one for my old Pentium 4 file server, the other for my Conroe and Penryn systems. The monitor for the server is Viewsonic E70f CRT-flat-screen (analog connection). So I'm sharing keyboard and mouse between all three systems, and I'm sharing the LCD monitor between two of them.
The latter two are using the same motherboard, BIOS revisions differing to optimize each for the respective Q6600 and E8400 processors. The E8400-based system has only recently been built, with two BFG nVidia Geforce 9600 GT cards in SLI. The Q6600 system has never had problems; it is OC'd to 3.15 GHz.
I have been carefully OC'ing the Penryn system. It uses 4GB 2x2GB of G.SKILL memory. It is running VISTA 64. The Q6600 system runs XP MCE 2005.
I had been switching the VX2235 monitor between the systems. The Penryn system is sort of a "pet project" for VISTA 64 -- so far, a success.
After running up the Penryn VISTA 64 to 3.82 Ghz and testing for some 5 hours with PRIME95 small-FFT test, I set it back to the less stressful 3.6 Ghz OC setting. There had never been any lockups, need for CLR CMOS, BSOD (except for initial troubles installing VISTA 64 -- thoroughly resolved), or any other abnormal difficulties as I proceeded to Over-clock. Remember -- I had extensive experience with this motherboard on the Q6600 system.
I decided that I need to test the RAM more thoroughly at the 3.6 Ghz settings -- not to confuse you -- this is the VISTA-Penryn system. These are DDR2-1000, running at DDR2-800 and the stock latencies (spec'd for DDR2-1000). The voltage was fixed near the bottom of G.SKILL's recommended acceptable range.
To test the RAM, I ran the PRIME95 Blend Test.
Twice, after running Blend Test for approximately 20 minutes, a BSOD would pop up and state "Hardware failure: consult hardware vendor." At this point, I am beginning to suspect the G.SKILL RAM modules, even for twisting up their voltage a bit more. I shut down the system, deciding to go back to my proven XP Q6600 system (same mobo model). I chose to reboot the Penryn and select "NORMAL" startup, shutting it down through VISTA normally. With the Penryn VISTA system shut-down (Viewsonic monitor in "amber" sleep mode), I removed the DVI plug and placed it back on the XP system.
Booting the XP system, I see the monitor blue light on, but no screen. Dead -- and black. I hit the ol' reset button. Nothing -- same result. I shut down the XP system, tried to turn off the monitor. The screen turns into a "checkerboard." I was finally able to turn it off. I unplugged it. I turned off the PSU of the XP system, unplugged the power cable, waited, plugged it back in, plugged the Viewsonic cable back on the graphics card, started up the XP system after powering up the Viewsonic, and . . . . all is well.
What may have happened here? I am thinking that my problem with the VISTA system is not the RAM, but more likely some glitch with regard to the monitor which may have occurred after dropping back to my earlier BIOS settings and less stressful over-clock.
YOUR INSIGHTS ARE EAGERLY -- EVEN DESPERATELY SOUGHT. I hate the thought of having to RMA this Viewsonic monitor, and for the moment, it looks as though it's working fine again. If there is a RAM problem on the VISTA-Penryn-SLI system instead, I can RMA or just pick up another DDR2 RAM kit for less than $100.
Facebook
Twitter