Ok, solve this one, I'm stumped and stressed

amdskip

Lifer
Jan 6, 2001
22,530
13
81
Basic computer with fresh win 2k installation, ecs motherboard, 1.33 thunderbird, geforce 2 video card, virus and spyware free. Before the win 2k install, this problem was not an issue.

Computer is using a mv940 compaq monitor. The problem is that the windows 2k splash screen shows up and then before the login screen appears, blue screen of death and reboot before I can see what it says.

I have hooked up an old dell monitor and it's worked ever time. I've tried numerous resolutions and refresh rates and nothing has worked. Any ideas are highly appreciated.

Jeff
 

mechBgon

Super Moderator<br>Elite Member
Oct 31, 1999
30,699
1
0
If you have a digicam, you can try having it take a movie of the boot screen and see if it can capture the error message. Also, try starting it up in Safe Mode and tell me if it does that ok.

I had a similar experience with a particular monitor that my parents just happened to own, a 17" KDS flat-tube CRT. It simply will NOT run on an nForce2 chipset with an nVidia-based video solution, either add-in or onboard. nForce classic, yes. nF2 motherboard with ATI video, yes. nF2 motherboard with PCI Voodoo3, sure.

:confused:.

Anyway, the solution for my folks ended up being a monitor swap, so I'm stuck with their KDS, which has proven that it hates nF2 with nVidia-based video at MY place too. :frown: On the bright side, this is a great excuse to finally splurge for a new 19" Mitsubishi and if my next paycheck can stand it, that's what I'm gonna do :D
 

Brule

Golden Member
Apr 23, 2004
1,358
0
76
Shouldn't safe mode boot into a basic VGA mode? If the monitor can't handle that, there's a major issue.
 

nboy22

Diamond Member
Jul 18, 2002
3,304
1
81
maybe try to boot up on the monitor that works, then pull a fast one and change the cable to the other monitor that hasn't been working. Of course, do this while the computer is on, and see if you still get a blue screen.
 

amdskip

Lifer
Jan 6, 2001
22,530
13
81
Originally posted by: nboy22
maybe try to boot up on the monitor that works, then pull a fast one and change the cable to the other monitor that hasn't been working. Of course, do this while the computer is on, and see if you still get a blue screen.
Tried this and the monitor works fine.

I have tried safe mode and it did work.

It worked fine before I wiped the computer and loaded windows again.
 

AKA

Golden Member
Oct 10, 1999
1,304
0
76
Seen this one a few times.



Try this if you haven't already.


Boot into safe mode, go into device manager, remove all instances of monitor then display adapters. Then Restart.


If that doesn't work or you already tried it.

Get a copy of msconfig from XP and put it anywhere on your win2k, launch it, click on boot.ini tab and click on /basevideo, click okay and then restart with Compaq monitor.

It should load into normal mode this time.

After it loads into normal mode go into display settings, advance then set display colors to 16 color and resolution to 640x480. Go back into msconfig and undo the selection on /basevideo and restart.

Again it should load into normal mode safely. Then try setting your video colors &amp; resolution higher.


If that doesn't work, update service pack and delete the Compaq's monitor's inf if it is detecting the correct monitor. If its not detecting correct monitor (shows up as plug &amp; play) then install the monitor driver.

This has always worked for me. Hopefully will for you.
 

LiLithTecH

Diamond Member
Jul 28, 2002
3,105
0
0
Are you using the BNC cable?
If so, did it load the correct monitor Profile or just the Default monitor?
 

daveshel

Diamond Member
Oct 10, 1999
5,453
2
81
This is a driver issue. Sounds like you upgraded to Win2k from some 9x flavor. You should be able to use the recovery console to unload the driver (so says Microsoft) but the challenge is knowing which one is the offender.
 

amdskip

Lifer
Jan 6, 2001
22,530
13
81
The box had win 2k on it before. This is not using a BNC cable, just normal vga. I'm taking off right now to try what A.K.A. suggested.
 

VirtualLarry

No Lifer
Aug 25, 2001
56,587
10,225
126
A monitor causing a BSOD? Bizarre. I guess possibly the EDID data reported by the monitor got corrupted somehow, which is causing the video driver to fault? If no other solution works, either perhaps you could get software from the mfg to re-flash the EDID info in the monitor, or possibly get a VGA HD15 passthrough connector, and disconnect the lines used by the monitor to report the DDC/EDID data back to the video card. Then just manually set up the monitor in Windows instead of letting PnP do it. (Actually, you might be able to work-around this too, by booting using a different monitor, and then setting Windows to use a different, non-PnP monitor. I don't know if there is a way to get the video driver and/or Windows to disable PnP monitor support and/or not query the EDID data.)