«

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" <> wrote in message
news:...
> 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
>
> Microsoft Windows MVP
> (Running Windows Live Mail 2008 in Vista Ultimate x64 SP1)
>
> "Tony Sperling" <> wrote in message
> news:#...
> > 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" <> wrote in message
> > news:5CECF167-F102-4169-8FDC-...
> >> 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" <> wrote in message
> >> news:715D7AE0-83BD-4A6E-ADF9-...
> >> >
> >> >
> >> > "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
>

"R. C. White" wrote:

> 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?

UPS no, power board yes.

Is your
> electricity source dependable?

We don't have brown/black outs and blown appliances if that is what you
mean, other wise I don't know if the power is "clean" or not.

Are there RF interference sources nearby?

Wireless network and TV other wise I can't think of any RF problems

> Have you checked connections with all the peripherals that you don't take to
> the shop, such as printers, modems, etc.?

Microsoft Keyboard and mouse, monitor and sound system/headphones are the
only things plugged into the computer. No printers are installed.

> Your first message said, "About every second or so start up I receive 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.

Thanks, I used the similar option by pressing F8 and turning the auto
restart on error's off but that only seemed to last that one time (enough for
me to copy the original error down).

> If your shop can't fix it with those details, then you need a new computer
> or a new shop. Or both!

That is a bridge ill cross when I come to it

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" <>
| >References: <47E2336B-F378-41CC-B642->
<ujH$>
<715D7AE0-83BD-4A6E-ADF9->
<5CECF167-F102-4169-8FDC->
<#>
<>
| >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-200, Outbound message
| >X-Antivirus-Status: Clean
| >Message-ID: <#7#>
| >Newsgroups: microsoft.public.windows.64bit.general
| >NNTP-Posting-Host: 1385155113.dhcp.dbnet.dk 82.143.202.41
| >Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.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" <> wrote in message
| >news:...
| >> 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
| >>
| >> Microsoft Windows MVP
| >> (Running Windows Live Mail 2008 in Vista Ultimate x64 SP1)
| >>
| >> "Tony Sperling" <> wrote in message
| >> news:#...
| >> > 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" <> wrote in message
| >> > news:5CECF167-F102-4169-8FDC-...
| >> >> 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" <> wrote in message
| >> >> news:715D7AE0-83BD-4A6E-ADF9-...
| >> >> >
| >> >> >
| >> >> > "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
| >>
| >
| >
| >

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]"" <> wrote in message
news:...
> 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" <>
> | >References: <47E2336B-F378-41CC-B642->
> <ujH$>
> <715D7AE0-83BD-4A6E-ADF9->
> <5CECF167-F102-4169-8FDC->
> <#>
> <>
> | >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-200, Outbound message
> | >X-Antivirus-Status: Clean
> | >Message-ID: <#7#>
> | >Newsgroups: microsoft.public.windows.64bit.general
> | >NNTP-Posting-Host: 1385155113.dhcp.dbnet.dk 82.143.202.41
> | >Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TNGP03.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" <> wrote in message
> | >news:...
> | >> 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
> | >>
> | >> Microsoft Windows MVP
> | >> (Running Windows Live Mail 2008 in Vista Ultimate x64 SP1)
> | >>
> | >> "Tony Sperling" <> wrote in message
> | >> news:#...
> | >> > 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" <> wrote in message
> | >> > news:5CECF167-F102-4169-8FDC-...
> | >> >> 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" <> wrote in message
> | >> >> news:715D7AE0-83BD-4A6E-ADF9-...
> | >> >> >
> | >> >> >
> | >> >> > "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
> | >>
> | >
> | >
> | >
>

Hi, Darrell.

Aw, shucks! ;<)

And, like Tony said, Thanks for the compliment.

RC
--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP
(Running Windows Live Mail 2008 in Vista Ultimate x64 SP1)

""Darrell Gorter[MSFT]"" <> wrote in message
news:...
> 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]
<SNIP>

Brown-outs, I think R.C. was specifically thinking about - you may not know
you have them, standard PC-PSU's can be pretty horrible and they can create
havoc for no particular apparent reason. If you live very near or very far
from your power station you could be in the danger zone. It sounds as though
this is something you had not suspected, but if nothing else turns up I
would ask (and pay!) a qualified electrician to make measurements that you
can use to analyze your situation.

I almost never have any problems with my power supply, I have two standard
machines running with one having a well known good quality PSU. I also have
one machine that was built to my specifications having a very high-quality
PSU (Seasonic M12) and one evening we had the shortest imaginable flicker of
the lights and the two standard machines turned off with no hesitation, the
one with the Seasonic just kept on running as if nothing happened.

Our good NG colleague, Carlos, consistently suggests dual 12V lines for the
PSU, and I entirely agree. Furthermore, I suggest that any PSU you
contemplate can deliver it's full rating on all it's lines all of the time,
and not just on any one line, as is common.

But before making costly experiments, you would want to know how your local
situation really looks, in view of your somewhat peculiar circumstances.
There is no way I can think of that would implicate the OS as the culprit,
so you will be well advised to stop worrying about that and concentrate on
something else. Find yourself an electrician!


Tony. . .




"BW~Merlin" <> wrote in message
news:A08C9702-A689-44BE-B611-...
> "R. C. White" wrote:
>
> > 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?
>
> UPS no, power board yes.
>
> Is your
> > electricity source dependable?
>
> We don't have brown/black outs and blown appliances if that is what you
> mean, other wise I don't know if the power is "clean" or not.
>
> Are there RF interference sources nearby?
>
> Wireless network and TV other wise I can't think of any RF problems
>
> > Have you checked connections with all the peripherals that you don't
take to
> > the shop, such as printers, modems, etc.?
>
> Microsoft Keyboard and mouse, monitor and sound system/headphones are the
> only things plugged into the computer. No printers are installed.
>
> > Your first message said, "About every second or so start up I receive 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.
>
> Thanks, I used the similar option by pressing F8 and turning the auto
> restart on error's off but that only seemed to last that one time (enough
for
> me to copy the original error down).
>
> > If your shop can't fix it with those details, then you need a new
computer
> > or a new shop. Or both!
>
> That is a bridge ill cross when I come to it

I agree completely, Colin. These issues are important and easily overlooked.
Except, I am probably missing the pooint about the 'hub' thing.


Tony. . .



"Colin Barnhorst" <> wrote in message
news:75784FB4-FFB0-477D-9898-...
> Make sure that the computer is set up exactly as it was in the shop.
Don't
> reattach unneeded devices. Change some cables that you didn't take along
to
> the shop. Give it some time before reattaching things like the printer.
> When you do, use a different port. Don't use any hubs.
>
> "BW~Merlin" <> wrote in message
> news:715D7AE0-83BD-4A6E-ADF9-...
> >
> >
> > "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
>

I had a hub that I had been using on a computer just fine but when I moved
it to a new computer I started getting blue screens. I finally figured out
what was causing the problem and replaced it.

"Tony Sperling" <> wrote in message
news:...
>I agree completely, Colin. These issues are important and easily
>overlooked.
> Except, I am probably missing the pooint about the 'hub' thing.
>
>
> Tony. . .
>
>
>
> "Colin Barnhorst" <> wrote in message
> news:75784FB4-FFB0-477D-9898-...
>> Make sure that the computer is set up exactly as it was in the shop.
> Don't
>> reattach unneeded devices. Change some cables that you didn't take along
> to
>> the shop. Give it some time before reattaching things like the printer.
>> When you do, use a different port. Don't use any hubs.
>>
>> "BW~Merlin" <> wrote in message
>> news:715D7AE0-83BD-4A6E-ADF9-...
>> >
>> >
>> > "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
>>
>
>

O.K. - good point, I was curious if it would be something generic that I had
missed.


Tony. . .


"Colin Barnhorst" <> wrote in message
news:81FA9B7E-ECC2-47B7-AC1D-...
> I had a hub that I had been using on a computer just fine but when I moved
> it to a new computer I started getting blue screens. I finally figured
out
> what was causing the problem and replaced it.
>
> "Tony Sperling" <> wrote in message
> news:...
> >I agree completely, Colin. These issues are important and easily
> >overlooked.
> > Except, I am probably missing the pooint about the 'hub' thing.
> >
> >
> > Tony. . .
> >
> >
> >
> > "Colin Barnhorst" <> wrote in message
> > news:75784FB4-FFB0-477D-9898-...
> >> Make sure that the computer is set up exactly as it was in the shop.
> > Don't
> >> reattach unneeded devices. Change some cables that you didn't take
along
> > to
> >> the shop. Give it some time before reattaching things like the
printer.
> >> When you do, use a different port. Don't use any hubs.
> >>
> >> "BW~Merlin" <> wrote in message
> >> news:715D7AE0-83BD-4A6E-ADF9-...
> >> >
> >> >
> >> > "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
> >>
> >
> >
>

Hi, Tony.

> Brown-outs, I think R.C. was specifically thinking about - you may not
> know
> you have them, standard PC-PSU's can be pretty horrible and they can
> create
> havoc for no particular apparent reason.

Uh, no. Not a PSU (Power Supply Unit - which all PC's have built in). A
UPS (Uninterruptible Power Supply), which is external to the PC. It is
basically just a big battery that continually recharges itself from the wall
plug and supplies power to the PC's PSU. The UPS plugs into the wall and
has one or more (usually several) receptacles into which we can plug the PC
and peripherals, like a printer, modem, or the PC's monitor. Just unplug
the PC from the wall and plug it into the UPS. When there is a power
failure, the PC doesn't even blink or notice until the battery runs down.
As soon as the power comes on again, the battery recharges for next time.

The better UPSes also have power line conditioning (by whatever fancy name
the UPS marketer chooses to call it). This smoothes out brownouts and
spikes, so that the PC always gets clean, conditioned power.

Perhaps the OP's shop uses a good UPS, but the OP has confirmed "UPS no" at
home. He did say "power board yes", but I don't know what that means.

RC
--
R. C. White, CPA
San Marcos, TX

Microsoft Windows MVP
(Running Windows Live Mail 2008 in Vista Ultimate x64 SP1)

"Tony Sperling" <> wrote in message
news:...
> Brown-outs, I think R.C. was specifically thinking about - you may not
> know
> you have them, standard PC-PSU's can be pretty horrible and they can
> create
> havoc for no particular apparent reason. If you live very near or very far
> from your power station you could be in the danger zone. It sounds as
> though
> this is something you had not suspected, but if nothing else turns up I
> would ask (and pay!) a qualified electrician to make measurements that you
> can use to analyze your situation.
>
> I almost never have any problems with my power supply, I have two standard
> machines running with one having a well known good quality PSU. I also
> have
> one machine that was built to my specifications having a very high-quality
> PSU (Seasonic M12) and one evening we had the shortest imaginable flicker
> of
> the lights and the two standard machines turned off with no hesitation,
> the
> one with the Seasonic just kept on running as if nothing happened.
>
> Our good NG colleague, Carlos, consistently suggests dual 12V lines for
> the
> PSU, and I entirely agree. Furthermore, I suggest that any PSU you
> contemplate can deliver it's full rating on all it's lines all of the
> time,
> and not just on any one line, as is common.
>
> But before making costly experiments, you would want to know how your
> local
> situation really looks, in view of your somewhat peculiar circumstances.
> There is no way I can think of that would implicate the OS as the culprit,
> so you will be well advised to stop worrying about that and concentrate on
> something else. Find yourself an electrician!
>
>
> Tony. . .
>
>
> "BW~Merlin" <> wrote in message
> news:A08C9702-A689-44BE-B611-...
>> "R. C. White" wrote:
>>
>> > 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?
>>
>> UPS no, power board yes.
>>
>> Is your
>> > electricity source dependable?
>>
>> We don't have brown/black outs and blown appliances if that is what you
>> mean, other wise I don't know if the power is "clean" or not.
>>
>> Are there RF interference sources nearby?
>>
>> Wireless network and TV other wise I can't think of any RF problems
>>
>> > Have you checked connections with all the peripherals that you don't
> take to
>> > the shop, such as printers, modems, etc.?
>>
>> Microsoft Keyboard and mouse, monitor and sound system/headphones are the
>> only things plugged into the computer. No printers are installed.
>>
>> > Your first message said, "About every second or so start up I receive 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.
>>
>> Thanks, I used the similar option by pressing F8 and turning the auto
>> restart on error's off but that only seemed to last that one time (enough
> for
>> me to copy the original error down).
>>
>> > If your shop can't fix it with those details, then you need a new
> computer
>> > or a new shop. Or both!
>>
>> That is a bridge ill cross when I come to it