Eagle wrote:
> FromTheRafters laid this down on his screen :
>> ~BD~ presented the following explanation :
>>> FromTheRafters wrote:
>>>> ~BD~ presented the following explanation :
>>>>> Eagle wrote:
>>>>>> ~BD~ presented the following explanation :
>>>>>>> Eagle wrote:
>>>>>>>> ~BD~ explained on 2/25/2013 :
>>>>>>>>> My replacement Dell monitor arrived this morning! That was a real
>>>>>>>>> surprise. I not really expected it until the end of the week. I
>>>>>>>>> unpacked it and set it up on my desk. I plugged it in and
>>>>>>>>> connected it
>>>>>>>>> to my Dell computer to check that it will work as expected.
>>>>>>>>>
>>>>>>>>> *Switch on*!
>>>>>>>>>
>>>>>>>>> WOW! ..... the *monitor* worked! *I was greeted by a BSOD*!!!!
>>>>>>>>>
>>>>>>>>> Right - take a photograph to show you! Find camera and ..... Argh!
>>>>>>>>> Battery flat (searches for charger and plugs it in!). Right -
>>>>>>>>> where's
>>>>>>>>> that iPod Touch?!! Oh dear, how *does* this camera App work?
>>>>>>>>> <grin>
>>>>>>>>> Got it - takes photo, and uploads it to iMac! Phew!
>>>>>>>>>
>>>>>>>>> At last, a piccie!
http://i49.tinypic.com/ao7qqr.jpg
>>>>>>>>>
>>>>>>>>> For those who don't click on links: "STOP 0x000000ED
>>>>>>>>> UNMOUNTABLE_BOOT_VOLUME" error message
>>>>>>>>>
>>>>>>>>> Seek quick procedure reminder to deal with this! <rolls eyes>
>>>>>>>>>
>>>>>>>>> Ah, yes! Recovery Console from the XP set-up disk. Yep, quick
>>>>>>>>> 'check
>>>>>>>>> disk' - found error. Best replace the MBR too! 'fixboot' should do
>>>>>>>>> the
>>>>>>>>> trick!
>>>>>>>>>
>>>>>>>>> Restart computer and ..... Hooray, up and running again! :-)
>>>>>>>>>
>>>>>>>>> I hope *your* day is going well too!
>>>>>>>>
>>>>>>>> Glad your day is going well, Dave. I wish I could say the same. :-(
>>>>>>>
>>>>>>>
>>>>>>> That doesn't sound too promising - what's up, Eagle?
>>>>>>>
>>>>>>> -
>>>>>>>
>>>>>>> I'm surprised that you made no comment about my computer. Do you
>>>>>>> think
>>>>>>> that whatever caused my computer failure could also have
>>>>>>> sabotaged my
>>>>>>> previous monitor?
>>>>>>
>>>>>> I didn't know you wanted a comment, Dave... :D
>>>>>
>>>>> What surprises me is that not one person, not one, has made a comment
>>>>> about the BSOD and how I brought the machine back to life!
>>>>
>>>> The BSOD pretty much assures you that it *is* alive.
>>>
>>> Semantics! As I said, I was actually checking the *monitor*! ;-)
>>>
>>> THAT seems just fine!
>>
>> The fact that you could *see* the BSOD also proves that.
>>>
>>>>>> It looks suspicious. A blue screen of death, right after your monitor
>>>>>> fizzles out?
>>>>>
>>>>> I'd not be at all surprised if some folk on these Usenet groups had
>>>>> something to do with it!
>>>>
>>>> It would be interesting to learn how it was done, if indeed it was done
>>>> by someone and not just an accidental hardware failure.
>>>
>>> I'd be interested too! Hardly likely anyone will own up though!
>>
>> Agreed.
>>>
>>> When hardware fails, in my experience anyway, it never actually
>>> repairs itself. What type of hardware failure do you imagine it might
>>> have been, FTR?
>>
>> The monitor fizzled, Windows noticed new hardware when you attached
>> the new monitor. Did your new monitor come with any software? Windows
>> may have found a generic driver and the driver in the software package
>> may offer more features.
>>
>>> The machine has been running for over twenty hours now with no sign
>>> of any further failure.
>>
>> That's good.
>>>
>>>>>> The good part is your puter fixed the issue, and you're
>>>>>> good to go.
>>>>>
>>>>> Not so! The 'puter' didn't fix anything - BD fixed the 'puter', Dopey!
>>>>
>>>> The computer wasn't broken, if it had been broken it would not have
>>>> given you that message.
>>>>
>>>> [...]
>>>
>>> Please see my response to Frozen North.
>>
>> Okay, I haven't gotten there yet.
>
> Getting a BSOD for a replacement monitor confuses Me. I've never seen
> anything like that. Every monitor I replaced never produced a BSOD.
> Windoze always uses a generic driver, or a driver listed in the windoze
> driver files.
Eagle,
The BSOD may well have just been waiting to "jump out' of the computer
to show me what some nasty hacker had done! <shock> It might well have
been there since the 'original' monitor failed - a number of days ago!
No new driver would have been necessary - the monitor I now have is
identical to the one which failed, so all should have been honky dory!
Here:-
http://www.urbandictionary.com/define.php?term=honky%20dory
--