Re: Blue screen's on start up by Tony
Tony
Wed Jun 04 16:44:29 PDT 2008
I was driving a taxi for more than 25 years (combined over a much longer
period) and I can safely say that I've heard innumerable nice remarks
regarding my driving, from people that I knew had little background in
making an honest asessment - one I could believe - the best one, I can never
forget was once in the early seventies when I had the 'then' Director of the
Gothenburg Symphony Orchestra in the back seat. When we arrived he asked me
what instrument I played, and I said Gramophone. He found that hard to
believe, saying: he'd never experienced anyone driving so rythmically. .
.not to brag, but WOW! If that isn't a home run?
This one I'm sure rates up there in those upper regions - thank you,
Darrell!
Tony. . .
""Darrell Gorter[MSFT]"" <Darrellg@online.microsoft.com> wrote in message
news:rvW7x6oxIHA.5796@TK2MSFTNGHUB02.phx.gbl...
> Hello,
> Following the thread I don't have anything to add, you guys did a great
job
> in answering as always
> other than thanks
> later,
> Darrell Gorter[MSFT]
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> --------------------
> | >From: "Tony Sperling" <tony.sperling@dbREMOVEmail.dk>
> | >References: <47E2336B-F378-41CC-B642-078B67D2592D@microsoft.com>
> <ujH$UFRxIHA.5652@TK2MSFTNGP06.phx.gbl>
> <715D7AE0-83BD-4A6E-ADF9-EAFA564B2489@microsoft.com>
> <5CECF167-F102-4169-8FDC-A30E1EA8932D@microsoft.com>
> <#9HetuZxIHA.524@TK2MSFTNGP05.phx.gbl>
> <ex6t9ebxIHA.2208@TK2MSFTNGP04.phx.gbl>
> | >Subject: Re: Blue screen's on start up
> | >Date: Tue, 3 Jun 2008 23:05:56 +0200
> | >Lines: 175
> | >X-Priority: 3
> | >X-MSMail-Priority: Normal
> | >X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
> | >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914
> | >X-Antivirus: avast! (VPS 080603-0, 03-06-2008), Outbound message
> | >X-Antivirus-Status: Clean
> | >Message-ID: <#7#RL2bxIHA.1768@TK2MSFTNGP03.phx.gbl>
> | >Newsgroups: microsoft.public.windows.64bit.general
> | >NNTP-Posting-Host: 1385155113.dhcp.dbnet.dk 82.143.202.41
> | >Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
> | >Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.64bit.general:17923
> | >X-Tomcat-NG: microsoft.public.windows.64bit.general
> | >
> | >Yeah - we're a hard bunch to beat ain't we?
> | >
> | > :0o
> | >
> | >Well, then I just think I'll re-send that post, you never really know
> where
> | >in the global community it was cought up. Someone, somewhere may have
to
> | >digest a duplicate, though.
> | >
> | >
> | >Tony. . .
> | >
> | >
> | >"R. C. White" <rc@grandecom.net> wrote in message
> | >news:ex6t9ebxIHA.2208@TK2MSFTNGP04.phx.gbl...
> | >> Hi, Tony.
> | >>
> | >> I saw your first post (Date: Tue, 3 Jun 2008 02:33:12 +0200); it's
> quoted
> | >in
> | >> my reply. But I don't see one between that and your latest.
> | >>
> | >> But it's good to know that we agree on diagnostic steps - and so does
> | >Colin.
> | >> ;<)
> | >>
> | >> RC
> | >> --
> | >> R. C. White, CPA
> | >> San Marcos, TX
> | >> rc@grandecom.net
> | >> Microsoft Windows MVP
> | >> (Running Windows Live Mail 2008 in Vista Ultimate x64 SP1)
> | >>
> | >> "Tony Sperling" <tony.sperling@dbREMOVEmail.dk> wrote in message
> | >> news:#9HetuZxIHA.524@TK2MSFTNGP05.phx.gbl...
> | >> > I don't know what happened to my reply seven hours ago. You've
> managed
> | >to
> | >> > duplicate some several of the better points I wanted to make, plus
a
> few
> | >> > extra ones of the more Vista specific type, so I'll stop worrying.
I
> | >> > totally
> | >> > agree that this error probably sits somewhere in the house, or the
> | >> > immediate
> | >> > vicinity.
> | >> >
> | >> >
> | >> > Tony. . .
> | >> >
> | >> >
> | >> >
> | >> > "R. C. White" <rc@grandecom.net> wrote in message
> | >> > news:5CECF167-F102-4169-8FDC-A30E1EA8932D@microsoft.com...
> | >> >> Hi, BW~Merlin.
> | >> >>
> | >> >> > That is correct they were unable to get a blue screen on startup
> | >> >>
> | >> >> If you consistently get blue screens, but they don't happen at the
> | >shop,
> | >> >> then perhaps there is something in your home environment that is
> | >> > triggering
> | >> >> the problem.
> | >> >>
> | >> >> The blue screen message seems to point elsewhere, but it sounds
like
> | >some
> | >> >> hardware problem in your office. Do you use a UPS or power strip?
> Is
> | >> > your
> | >> >> electricity source dependable? Are there RF interference sources
> | >nearby?
> | >> >> Have you checked connections with all the peripherals that you
don't
> | >take
> | >> > to
> | >> >> the shop, such as printers, modems, etc.?
> | >> >>
> | >> >> Your first message said, "About every second or so start up I
> recive a
> | >> > blue
> | >> >> screen, windows then reboots," Have you changed the default
setting
> | >for
> | >> >> what Vista should do in case of system failure? That is one of
the
> | >FIRST
> | >> >> changes that I make when I install any version of Windows. The
> default
> | >> >> is
> | >> >> fine for newbies because simply restarting solves MANY computer
> | >problems.
> | >> >> But when a restart does not fix it, we are left will few clues as
to
> | >what
> | >> >> might be wrong.
> | >> >>
> | >> >> It's buried deeply, so you'll need to navigate to Control Panel |
> | >System
> | >> >> |
> | >> >> Advanced System Settings (you'll need the Administrator password
to
> get
> | >> > past
> | >> >> here) | Advanced tab | Startup and Recovery / Settings. Once you
> get
> | >> > here,
> | >> >> the rest is easy: clear the check from the Automatically restart
> box
> | >> > under
> | >> >> System failure, then OK your way out to the desktop.
> | >> >>
> | >> >> Next time, instead of rebooting, the BSOD will stay onscreen until
> you
> | >> > push
> | >> >> the hardware Reset button. This will give you plenty of time to
> read
> | >and
> | >> >> copy down the STOP code and other details. (Don't bother with the
> "If
> | >> > this
> | >> >> is the first time..." stuff; that's just boilerplate which we've
> read
> | >too
> | >> >> many times already.) Be sure you copy any driver names that may
be
> | >shown
> | >> >> and those strings of hex codes that provide details for the actual
> STOP
> | >> >> code. Post those codes in your next message here and some of
these
> | >gurus
> | >> >> (not me!) can get you pointed in the right direction.
> | >> >>
> | >> >> If your shop can't fix it with those details, then you need a new
> | >> >> computer
> | >> >> or a new shop. Or both!
> | >> >>
> | >> >> RC
> | >> >>
> | >> >> "BW~Merlin" <BWMerlin@discussions.microsoft.com> wrote in message
> | >> >> news:715D7AE0-83BD-4A6E-ADF9-EAFA564B2489@microsoft.com...
> | >> >> >
> | >> >> >
> | >> >> > "Tony Sperling" wrote:
> | >> >> >
> | >> >> >> Are you saying that the shop cannot replicate the error that
you
> see
> | >> >> >> maybe
> | >> >> >> every second time you boot?
> | >> >> >
> | >> >> > That is correct they were unable to get a blue screen on startup
> | >> >> >
> | >> >> >> Can you tell us - how often do you turn off the machine and
what
> are
> | >> > the
> | >> >> >> sequence of steps you employ to turn it off?
> | >> >> >
> | >> >> > Generally I turn it on once a day and leave it on until I turn
it
> off
> | >> > for
> | >> >> > the night. Shutdown is done via the start menu, shutdown
> computer.
> | >> >> >
> | >> >> >> If you are heavily dependent on your computer at the moment I
> | >suggest
> | >> > to
> | >> >> >> not
> | >> >> >> turn it off at all once it boots and runs regularly. Just keep
it
> | >> > running
> | >> >> >> until a time when you can investigate further, you can save a
> lot of
> | >> >> >> watts
> | >> >> >> by turning off the monitor when you leave, though!
> | >> >> >
> | >> >> > Will investigate using hibernate feature. I already turn the
LCD
> | >> > monitor
> | >> >> > off at night so no problem with wasting power.
> | >> >> >
> | >> >> >> Such an error could be almost impossible (or un-payable) to
track
> | >> >> >> down,
> | >> >> >> and
> | >> >> >> is usually fixed by swapping components until it works, you
might
> | >> >> >> start
> | >> >> >> by
> | >> >> >> flashing the BIOS, that at least will cost you nothing.
> | >> >> >
> | >> >> > Incorrect BIOS update isn't covered by manufacturers warranty,
> also
> | >> > latest
> | >> >> > BIOS revisions are still beta.
> | >> >> >
> | >> >> > Also sorry for the double useless posts, I was at TAFE and the
> reply
> | >> > kept
> | >> >> > timing out and as it takes sometime for comments to appear I
> didn't
> | >> >> > know
> | >> >> > if
> | >> >> > the reply had posted, as for the copy and paste job it looks
like
> I
> | >> > forgot
> | >> >> > to
> | >> >> > copy my answers and instead pasted you reply back again :S
> | >>
> | >
> | >
> | >
>