You don't get an error page that says "blah, blah". You get an error page that gives a specific error message or messages. (Which may or may not be clear to you.)

I'd suggest posting the error message, in full, without paraphrasing.

I'd also suggest typing it into a search engine to see if you can find discussions where others have had or solved the same problem.

The most likely cause is that the monitor you are removing has been designated as the 'primary' monitor. Use the same tool(s) you used to set up the multiple-display mode to undo that operation, and to designate the remaining attached display as the primary.

Alternately, and assuming that you machine is in otherwise excellent health, you could remove all displays using the device manager, and then allow Windows to rediscover the primary display. I'd save this option for a last-ditch procedure, though...

Jim

ha, indeed good point.

i have typed it into google along with many other word combos that seem sensible and appropriate, i'm only aslking here as a last resort.

the message is the GENERIC message that appears on the console/black screen at boot up when the system can't boot, i've seen it before with completely unrelated problems, it basically says:

windows is unable to start up properly, this could be because of a recent change of hardware configuration or software installation. (no hints from windows as to which!)
please choose from the following options:
recovery console
boot into safe mode
try again to boot into windows

(if windows shut down unexpectedly or due to a power failure, it is suggested you select: try again)

etc, etc

thanks for input jd,

i'd actually just done the last thing you suggested, which was delete all (relevant) from the device manager and hope for the best on reboot! figuring it will find the built in monitor.

have just done it, so we'll see in a minute i guess ... slight delay due to windows updates installing themselves when i shut down (still going on)

for future reference ...

i had to unistall the grafics controller on the mb, this forced a reboot and a reinstall of the driver but it did resolve the problem.

(no hints from windows as to which!)

might I be so bold as to suggest a visit to www.annoyances.org

it won't necessarily give you the answers to the vaguaries of 'doze in all it's flavours ( but it will make you smile :))..and realise that you are not a lone voice ;-) ..once upon a time there was even a link to a translation list ( app ) of all those messages that begin "windows has just done ...."

good site, thanks for that l-g ... it did