Repair install of XP PRO

[JAS]

I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
does one go about to do an repair install? I have a Win XP Pro CD with
serial # and slipstreamed with SP3 on it. I purchased the laptop new and
it came with XP Pro installed on it. I clone my HD with Apricorn EZ Gig
and have three HDs that are bootable. My problem is that several years
ago at times when I would shut down and go to restart I would receive a
blue screen stating that certain files in System32 were corrupt or
missing also my system restore quite working and if I tried to do a
system restore I would get the blue screen. I would put my other drive
in and clone it on the one with the blue screen after coping my SM
profile and other files that were important and that changed since the
last clone and then put that drive back in and all is well as long as I
put the laptop in standby instead of shutting down although at times
when I do shut down all works OK but then I will get the blue screen and
have to switch drives again.
Any help would be appropriated.

JAS

[Paul[_32_]]

JAS wrote:
> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
> does one go about to do an repair install? I have a Win XP Pro CD with
> serial # and slipstreamed with SP3 on it. I purchased the laptop new and
> it came with XP Pro installed on it. I clone my HD with Apricorn EZ Gig
> and have three HDs that are bootable. My problem is that several years
> ago at times when I would shut down and go to restart I would receive a
> blue screen stating that certain files in System32 were corrupt or
> missing also my system restore quite working and if I tried to do a
> system restore I would get the blue screen. I would put my other drive
> in and clone it on the one with the blue screen after coping my SM
> profile and other files that were important and that changed since the
> last clone and then put that drive back in and all is well as long as I
> put the laptop in standby instead of shutting down although at times
> when I do shut down all works OK but then I will get the blue screen and
> have to switch drives again.
> Any help would be appropriated.
>
> JAS

VGN-BX540B

http://www.michaelstevenstech.com/XPrepairinstall.htm

"A Repair Install is not foolproof and should not
be considered the cure-all fix for non-boot situations."

You get to keep your programs and settings. The settings
are in the Registry, and only portions of the Registry
would change when a Repair Install is done. (Maybe the
hardware ENUM hive is wiped ?)

You have to do Windows Update over again.

To do a Repair Install, you need to go to Add/Remove
and remove any advanced version of Internet Explorer.
As the OS installer doesn't do the right thing. Once the
OS installation process is finished, you can reinstall
any advanced versions of Internet Explorer. Once
Internet Explorer is patched with the last Cumulative
Update for Internet Explorer for Windows XP, then
you can visit Windows Update and try to get the
security updates on the screen. There is a problem with
wuauserv on WinXP/Vista/Win7/Win8 which prevents the
list of updates from appearing in a timely fashion.

Whether you do a Repair Install or a Clean Install,
it's still a lot of work.

In your case, I like the idea of buying another
hard drive for this install. It covers two things.
It prevents a defective hard drive from blue screening
the machine again. It also gives you a clean place to
work.

The blue screen could have been caused by a driver
problem at shutdown. Maybe a driver is actually
crashing or something.

You disable "automatic reboot" in Windows, to make
the BSOD stay still. Then you can copy the STOP
code and look it up.

http://aumha.org/a/stop.htm

It really helps to have a root cause in hand for
a problem like this, so you don't waste time
on a solution that's not going to improve matters.
If it was an actual hardware issue for example,
you could BSOD the very same day after the
Repair Install.

And your OS partition should at least be "CHKDSK clean"
before you start the Repair Install. By the sounds
of your description, there may be damage after each
one of these BSODs.

I think conceptually, a Repair Install is great
for a "missing" file problem. Say I no longer have
an ntldr. I could Repair Install, and that puts one
back.

But for other classes of problems, like Malware,
a Repair Install is useless. And a broken System Restore
is not really all that good of a sign (permissions ?
something CKKDSK needs to fix ? State Info ?).

*******

I recently (three months ago) did a Clean Install,
and I'm still not all bolted back together yet. I used
a spare disk for the new OS, and I can refer back to
the "carcass" of the previous OS which is still
connected and running.

HTH,
Paul

[Bill Cunningham[_2_]]

"Paul" > wrote in message
...

> VGN-BX540B
>
> http://www.michaelstevenstech.com/XPrepairinstall.htm

Nice website Paul.

> "A Repair Install is not foolproof and should not
> be considered the cure-all fix for non-boot situations."
>
> You get to keep your programs and settings. The settings
> are in the Registry, and only portions of the Registry
> would change when a Repair Install is done. (Maybe the
> hardware ENUM hive is wiped ?)
>
> You have to do Windows Update over again.
>
> To do a Repair Install, you need to go to Add/Remove
> and remove any advanced version of Internet Explorer.
> As the OS installer doesn't do the right thing. Once the
> OS installation process is finished, you can reinstall
> any advanced versions of Internet Explorer. Once
> Internet Explorer is patched with the last Cumulative
> Update for Internet Explorer for Windows XP, then
> you can visit Windows Update and try to get the
> security updates on the screen. There is a problem with
> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
> list of updates from appearing in a timely fashion.
>
> Whether you do a Repair Install or a Clean Install,
> it's still a lot of work.
>
> In your case, I like the idea of buying another
> hard drive for this install. It covers two things.
> It prevents a defective hard drive from blue screening
> the machine again. It also gives you a clean place to
> work.
>
> The blue screen could have been caused by a driver
> problem at shutdown. Maybe a driver is actually
> crashing or something.
>
> You disable "automatic reboot" in Windows, to make
> the BSOD stay still. Then you can copy the STOP
> code and look it up.
>
> http://aumha.org/a/stop.htm
>
> It really helps to have a root cause in hand for
> a problem like this, so you don't waste time
> on a solution that's not going to improve matters.
> If it was an actual hardware issue for example,
> you could BSOD the very same day after the
> Repair Install.
>
> And your OS partition should at least be "CHKDSK clean"
> before you start the Repair Install. By the sounds
> of your description, there may be damage after each
> one of these BSODs.
>
> I think conceptually, a Repair Install is great
> for a "missing" file problem. Say I no longer have
> an ntldr. I could Repair Install, and that puts one
> back.
>
> But for other classes of problems, like Malware,
> a Repair Install is useless. And a broken System Restore
> is not really all that good of a sign (permissions ?
> something CKKDSK needs to fix ? State Info ?).
>
> *******
>
> I recently (three months ago) did a Clean Install,
> and I'm still not all bolted back together yet. I used
> a spare disk for the new OS, and I can refer back to
> the "carcass" of the previous OS which is still
> connected and running.
>
> HTH,
> Paul

I'll see if XP x64 Pro can do this. but I tell you what do. I back up all
my data. zero out the bootsectors and the mbr. Then set the boot code and
partition table and boot from scratch. Start with a newly formatted drve.
But you must be very careful. I've had disaster before.

Bill

[JAS]

Paul wrote:
> JAS wrote:
>> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
>> does one go about to do an repair install? I have a Win XP Pro CD with
>> serial # and slipstreamed with SP3 on it. I purchased the laptop new
>> and it came with XP Pro installed on it. I clone my HD with Apricorn
>> EZ Gig and have three HDs that are bootable. My problem is that
>> several years ago at times when I would shut down and go to restart I
>> would receive a blue screen stating that certain files in System32
>> were corrupt or missing also my system restore quite working and if I
>> tried to do a system restore I would get the blue screen. I would put
>> my other drive in and clone it on the one with the blue screen after
>> coping my SM profile and other files that were important and that
>> changed since the last clone and then put that drive back in and all
>> is well as long as I put the laptop in standby instead of shutting
>> down although at times when I do shut down all works OK but then I
>> will get the blue screen and have to switch drives again.
>> Any help would be appropriated.
>>
>> JAS
>
> VGN-BX540B
>
> http://www.michaelstevenstech.com/XPrepairinstall.htm
>
> "A Repair Install is not foolproof and should not
> be considered the cure-all fix for non-boot situations."
>
> You get to keep your programs and settings. The settings
> are in the Registry, and only portions of the Registry
> would change when a Repair Install is done. (Maybe the
> hardware ENUM hive is wiped ?)
>
> You have to do Windows Update over again.
>
> To do a Repair Install, you need to go to Add/Remove
> and remove any advanced version of Internet Explorer.
> As the OS installer doesn't do the right thing. Once the
> OS installation process is finished, you can reinstall
> any advanced versions of Internet Explorer. Once
> Internet Explorer is patched with the last Cumulative
> Update for Internet Explorer for Windows XP, then
> you can visit Windows Update and try to get the
> security updates on the screen. There is a problem with
> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
> list of updates from appearing in a timely fashion.
>
> Whether you do a Repair Install or a Clean Install,
> it's still a lot of work.
>
> In your case, I like the idea of buying another
> hard drive for this install. It covers two things.
> It prevents a defective hard drive from blue screening
> the machine again. It also gives you a clean place to
> work.
>
> The blue screen could have been caused by a driver
> problem at shutdown. Maybe a driver is actually
> crashing or something.
>
> You disable "automatic reboot" in Windows, to make
> the BSOD stay still. Then you can copy the STOP
> code and look it up.
>
> http://aumha.org/a/stop.htm
>
> It really helps to have a root cause in hand for
> a problem like this, so you don't waste time
> on a solution that's not going to improve matters.
> If it was an actual hardware issue for example,
> you could BSOD the very same day after the
> Repair Install.
>
> And your OS partition should at least be "CHKDSK clean"
> before you start the Repair Install. By the sounds
> of your description, there may be damage after each
> one of these BSODs.
>
> I think conceptually, a Repair Install is great
> for a "missing" file problem. Say I no longer have
> an ntldr. I could Repair Install, and that puts one
> back.
>
> But for other classes of problems, like Malware,
> a Repair Install is useless. And a broken System Restore
> is not really all that good of a sign (permissions ?
> something CKKDSK needs to fix ? State Info ?).
>
> *******
>
> I recently (three months ago) did a Clean Install,
> and I'm still not all bolted back together yet. I used
> a spare disk for the new OS, and I can refer back to
> the "carcass" of the previous OS which is still
> connected and running.
>
> HTH,
> Paul
Thanks for the reply, the next time it happens (I just rebooted and it
was fine) I will copy the message or take a photo of it and post back. A
lot of the times it does happen it is a config file.

Thanks again

[JAS]

Paul wrote:
> JAS wrote:
>> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
>> does one go about to do an repair install? I have a Win XP Pro CD with
>> serial # and slipstreamed with SP3 on it. I purchased the laptop new
>> and it came with XP Pro installed on it. I clone my HD with Apricorn
>> EZ Gig and have three HDs that are bootable. My problem is that
>> several years ago at times when I would shut down and go to restart I
>> would receive a blue screen stating that certain files in System32
>> were corrupt or missing also my system restore quite working and if I
>> tried to do a system restore I would get the blue screen. I would put
>> my other drive in and clone it on the one with the blue screen after
>> coping my SM profile and other files that were important and that
>> changed since the last clone and then put that drive back in and all
>> is well as long as I put the laptop in standby instead of shutting
>> down although at times when I do shut down all works OK but then I
>> will get the blue screen and have to switch drives again.
>> Any help would be appropriated.
>>
>> JAS
>
> VGN-BX540B
>
> http://www.michaelstevenstech.com/XPrepairinstall.htm
>
> "A Repair Install is not foolproof and should not
> be considered the cure-all fix for non-boot situations."
>
> You get to keep your programs and settings. The settings
> are in the Registry, and only portions of the Registry
> would change when a Repair Install is done. (Maybe the
> hardware ENUM hive is wiped ?)
>
> You have to do Windows Update over again.
>
> To do a Repair Install, you need to go to Add/Remove
> and remove any advanced version of Internet Explorer.
> As the OS installer doesn't do the right thing. Once the
> OS installation process is finished, you can reinstall
> any advanced versions of Internet Explorer. Once
> Internet Explorer is patched with the last Cumulative
> Update for Internet Explorer for Windows XP, then
> you can visit Windows Update and try to get the
> security updates on the screen. There is a problem with
> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
> list of updates from appearing in a timely fashion.
>
> Whether you do a Repair Install or a Clean Install,
> it's still a lot of work.
>
> In your case, I like the idea of buying another
> hard drive for this install. It covers two things.
> It prevents a defective hard drive from blue screening
> the machine again. It also gives you a clean place to
> work.
>
> The blue screen could have been caused by a driver
> problem at shutdown. Maybe a driver is actually
> crashing or something.
>
> You disable "automatic reboot" in Windows, to make
> the BSOD stay still. Then you can copy the STOP
> code and look it up.
>
> http://aumha.org/a/stop.htm
>
> It really helps to have a root cause in hand for
> a problem like this, so you don't waste time
> on a solution that's not going to improve matters.
> If it was an actual hardware issue for example,
> you could BSOD the very same day after the
> Repair Install.
>
> And your OS partition should at least be "CHKDSK clean"
> before you start the Repair Install. By the sounds
> of your description, there may be damage after each
> one of these BSODs.
>
> I think conceptually, a Repair Install is great
> for a "missing" file problem. Say I no longer have
> an ntldr. I could Repair Install, and that puts one
> back.
>
> But for other classes of problems, like Malware,
> a Repair Install is useless. And a broken System Restore
> is not really all that good of a sign (permissions ?
> something CKKDSK needs to fix ? State Info ?).
>
> *******
>
> I recently (three months ago) did a Clean Install,
> and I'm still not all bolted back together yet. I used
> a spare disk for the new OS, and I can refer back to
> the "carcass" of the previous OS which is still
> connected and running.
>
> HTH,
> Paul
Before I start on anything where does one get the WSUS Offline Update
for Windows XP PRO and instructions on downloading and burning to CD so
I can have it on hand when I do a repair of full reinstall.

Thanks,
JAS

[Paul[_32_]]

JAS wrote:
> Paul wrote:
>> JAS wrote:
>>> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
>>> does one go about to do an repair install? I have a Win XP Pro CD with
>>> serial # and slipstreamed with SP3 on it. I purchased the laptop new
>>> and it came with XP Pro installed on it. I clone my HD with Apricorn
>>> EZ Gig and have three HDs that are bootable. My problem is that
>>> several years ago at times when I would shut down and go to restart I
>>> would receive a blue screen stating that certain files in System32
>>> were corrupt or missing also my system restore quite working and if I
>>> tried to do a system restore I would get the blue screen. I would put
>>> my other drive in and clone it on the one with the blue screen after
>>> coping my SM profile and other files that were important and that
>>> changed since the last clone and then put that drive back in and all
>>> is well as long as I put the laptop in standby instead of shutting
>>> down although at times when I do shut down all works OK but then I
>>> will get the blue screen and have to switch drives again.
>>> Any help would be appropriated.
>>>
>>> JAS
>>
>> VGN-BX540B
>>
>> http://www.michaelstevenstech.com/XPrepairinstall.htm
>>
>> "A Repair Install is not foolproof and should not
>> be considered the cure-all fix for non-boot situations."
>>
>> You get to keep your programs and settings. The settings
>> are in the Registry, and only portions of the Registry
>> would change when a Repair Install is done. (Maybe the
>> hardware ENUM hive is wiped ?)
>>
>> You have to do Windows Update over again.
>>
>> To do a Repair Install, you need to go to Add/Remove
>> and remove any advanced version of Internet Explorer.
>> As the OS installer doesn't do the right thing. Once the
>> OS installation process is finished, you can reinstall
>> any advanced versions of Internet Explorer. Once
>> Internet Explorer is patched with the last Cumulative
>> Update for Internet Explorer for Windows XP, then
>> you can visit Windows Update and try to get the
>> security updates on the screen. There is a problem with
>> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
>> list of updates from appearing in a timely fashion.
>>
>> Whether you do a Repair Install or a Clean Install,
>> it's still a lot of work.
>>
>> In your case, I like the idea of buying another
>> hard drive for this install. It covers two things.
>> It prevents a defective hard drive from blue screening
>> the machine again. It also gives you a clean place to
>> work.
>>
>> The blue screen could have been caused by a driver
>> problem at shutdown. Maybe a driver is actually
>> crashing or something.
>>
>> You disable "automatic reboot" in Windows, to make
>> the BSOD stay still. Then you can copy the STOP
>> code and look it up.
>>
>> http://aumha.org/a/stop.htm
>>
>> It really helps to have a root cause in hand for
>> a problem like this, so you don't waste time
>> on a solution that's not going to improve matters.
>> If it was an actual hardware issue for example,
>> you could BSOD the very same day after the
>> Repair Install.
>>
>> And your OS partition should at least be "CHKDSK clean"
>> before you start the Repair Install. By the sounds
>> of your description, there may be damage after each
>> one of these BSODs.
>>
>> I think conceptually, a Repair Install is great
>> for a "missing" file problem. Say I no longer have
>> an ntldr. I could Repair Install, and that puts one
>> back.
>>
>> But for other classes of problems, like Malware,
>> a Repair Install is useless. And a broken System Restore
>> is not really all that good of a sign (permissions ?
>> something CKKDSK needs to fix ? State Info ?).
>>
>> *******
>>
>> I recently (three months ago) did a Clean Install,
>> and I'm still not all bolted back together yet. I used
>> a spare disk for the new OS, and I can refer back to
>> the "carcass" of the previous OS which is still
>> connected and running.
>>
>> HTH,
>> Paul
> Before I start on anything where does one get the WSUS Offline Update
> for Windows XP PRO and instructions on downloading and burning to CD so
> I can have it on hand when I do a repair of full reinstall.
>
> Thanks,
> JAS

Apparently 9.3 removed WinXP, so my guess is
that 9.2.1 might have it.

Look for 9.2.1 on the right-hand sidebar.

http://web.archive.org/web/20140605101941/http://download.wsusoffline.net/

http://web.archive.org/web/20140602113508/http://download.wsusoffline.net/wsusoffline921.zip

Run the generator, click the Legacy products tab.

Paul

[JAS]

Paul wrote:
> JAS wrote:
>> Paul wrote:
>>> JAS wrote:
>>>> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
>>>> does one go about to do an repair install? I have a Win XP Pro CD with
>>>> serial # and slipstreamed with SP3 on it. I purchased the laptop new
>>>> and it came with XP Pro installed on it. I clone my HD with Apricorn
>>>> EZ Gig and have three HDs that are bootable. My problem is that
>>>> several years ago at times when I would shut down and go to restart I
>>>> would receive a blue screen stating that certain files in System32
>>>> were corrupt or missing also my system restore quite working and if I
>>>> tried to do a system restore I would get the blue screen. I would put
>>>> my other drive in and clone it on the one with the blue screen after
>>>> coping my SM profile and other files that were important and that
>>>> changed since the last clone and then put that drive back in and all
>>>> is well as long as I put the laptop in standby instead of shutting
>>>> down although at times when I do shut down all works OK but then I
>>>> will get the blue screen and have to switch drives again.
>>>> Any help would be appropriated.
>>>>
>>>> JAS
>>>
>>> VGN-BX540B
>>>
>>> http://www.michaelstevenstech.com/XPrepairinstall.htm
>>>
>>> "A Repair Install is not foolproof and should not
>>> be considered the cure-all fix for non-boot situations."
>>>
>>> You get to keep your programs and settings. The settings
>>> are in the Registry, and only portions of the Registry
>>> would change when a Repair Install is done. (Maybe the
>>> hardware ENUM hive is wiped ?)
>>>
>>> You have to do Windows Update over again.
>>>
>>> To do a Repair Install, you need to go to Add/Remove
>>> and remove any advanced version of Internet Explorer.
>>> As the OS installer doesn't do the right thing. Once the
>>> OS installation process is finished, you can reinstall
>>> any advanced versions of Internet Explorer. Once
>>> Internet Explorer is patched with the last Cumulative
>>> Update for Internet Explorer for Windows XP, then
>>> you can visit Windows Update and try to get the
>>> security updates on the screen. There is a problem with
>>> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
>>> list of updates from appearing in a timely fashion.
>>>
>>> Whether you do a Repair Install or a Clean Install,
>>> it's still a lot of work.
>>>
>>> In your case, I like the idea of buying another
>>> hard drive for this install. It covers two things.
>>> It prevents a defective hard drive from blue screening
>>> the machine again. It also gives you a clean place to
>>> work.
>>>
>>> The blue screen could have been caused by a driver
>>> problem at shutdown. Maybe a driver is actually
>>> crashing or something.
>>>
>>> You disable "automatic reboot" in Windows, to make
>>> the BSOD stay still. Then you can copy the STOP
>>> code and look it up.
>>>
>>> http://aumha.org/a/stop.htm
>>>
>>> It really helps to have a root cause in hand for
>>> a problem like this, so you don't waste time
>>> on a solution that's not going to improve matters.
>>> If it was an actual hardware issue for example,
>>> you could BSOD the very same day after the
>>> Repair Install.
>>>
>>> And your OS partition should at least be "CHKDSK clean"
>>> before you start the Repair Install. By the sounds
>>> of your description, there may be damage after each
>>> one of these BSODs.
>>>
>>> I think conceptually, a Repair Install is great
>>> for a "missing" file problem. Say I no longer have
>>> an ntldr. I could Repair Install, and that puts one
>>> back.
>>>
>>> But for other classes of problems, like Malware,
>>> a Repair Install is useless. And a broken System Restore
>>> is not really all that good of a sign (permissions ?
>>> something CKKDSK needs to fix ? State Info ?).
>>>
>>> *******
>>>
>>> I recently (three months ago) did a Clean Install,
>>> and I'm still not all bolted back together yet. I used
>>> a spare disk for the new OS, and I can refer back to
>>> the "carcass" of the previous OS which is still
>>> connected and running.
>>>
>>> HTH,
>>> Paul
>> Before I start on anything where does one get the WSUS Offline Update
>> for Windows XP PRO and instructions on downloading and burning to CD
>> so I can have it on hand when I do a repair of full reinstall.
>>
>> Thanks,
>> JAS
>
> Apparently 9.3 removed WinXP, so my guess is
> that 9.2.1 might have it.
>
> Look for 9.2.1 on the right-hand sidebar.
>
> http://web.archive.org/web/20140605101941/http://download.wsusoffline.net/
>
>
> http://web.archive.org/web/20140602113508/http://download.wsusoffline.net/wsusoffline921.zip
>
>
> Run the generator, click the Legacy products tab.
>
> Paul
Paul,
downloaded and saved the wsusoffline file to use later. Here is a link
to a photo of the latest crash I have had, any idea as to cause? I was
able to reboot. https://s22.postimg.org/up9gonfrl/blue_screen.jpg
Sorry about the flash flare.

JAS

[Paul[_32_]]

JAS wrote:
> Paul wrote:
>> JAS wrote:
>>> Paul wrote:
>>>> JAS wrote:
>>>>> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed. How
>>>>> does one go about to do an repair install? I have a Win XP Pro CD with
>>>>> serial # and slipstreamed with SP3 on it. I purchased the laptop new
>>>>> and it came with XP Pro installed on it. I clone my HD with Apricorn
>>>>> EZ Gig and have three HDs that are bootable. My problem is that
>>>>> several years ago at times when I would shut down and go to restart I
>>>>> would receive a blue screen stating that certain files in System32
>>>>> were corrupt or missing also my system restore quite working and if I
>>>>> tried to do a system restore I would get the blue screen. I would put
>>>>> my other drive in and clone it on the one with the blue screen after
>>>>> coping my SM profile and other files that were important and that
>>>>> changed since the last clone and then put that drive back in and all
>>>>> is well as long as I put the laptop in standby instead of shutting
>>>>> down although at times when I do shut down all works OK but then I
>>>>> will get the blue screen and have to switch drives again.
>>>>> Any help would be appropriated.
>>>>>
>>>>> JAS
>>>>
>>>> VGN-BX540B
>>>>
>>>> http://www.michaelstevenstech.com/XPrepairinstall.htm
>>>>
>>>> "A Repair Install is not foolproof and should not
>>>> be considered the cure-all fix for non-boot situations."
>>>>
>>>> You get to keep your programs and settings. The settings
>>>> are in the Registry, and only portions of the Registry
>>>> would change when a Repair Install is done. (Maybe the
>>>> hardware ENUM hive is wiped ?)
>>>>
>>>> You have to do Windows Update over again.
>>>>
>>>> To do a Repair Install, you need to go to Add/Remove
>>>> and remove any advanced version of Internet Explorer.
>>>> As the OS installer doesn't do the right thing. Once the
>>>> OS installation process is finished, you can reinstall
>>>> any advanced versions of Internet Explorer. Once
>>>> Internet Explorer is patched with the last Cumulative
>>>> Update for Internet Explorer for Windows XP, then
>>>> you can visit Windows Update and try to get the
>>>> security updates on the screen. There is a problem with
>>>> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
>>>> list of updates from appearing in a timely fashion.
>>>>
>>>> Whether you do a Repair Install or a Clean Install,
>>>> it's still a lot of work.
>>>>
>>>> In your case, I like the idea of buying another
>>>> hard drive for this install. It covers two things.
>>>> It prevents a defective hard drive from blue screening
>>>> the machine again. It also gives you a clean place to
>>>> work.
>>>>
>>>> The blue screen could have been caused by a driver
>>>> problem at shutdown. Maybe a driver is actually
>>>> crashing or something.
>>>>
>>>> You disable "automatic reboot" in Windows, to make
>>>> the BSOD stay still. Then you can copy the STOP
>>>> code and look it up.
>>>>
>>>> http://aumha.org/a/stop.htm
>>>>
>>>> It really helps to have a root cause in hand for
>>>> a problem like this, so you don't waste time
>>>> on a solution that's not going to improve matters.
>>>> If it was an actual hardware issue for example,
>>>> you could BSOD the very same day after the
>>>> Repair Install.
>>>>
>>>> And your OS partition should at least be "CHKDSK clean"
>>>> before you start the Repair Install. By the sounds
>>>> of your description, there may be damage after each
>>>> one of these BSODs.
>>>>
>>>> I think conceptually, a Repair Install is great
>>>> for a "missing" file problem. Say I no longer have
>>>> an ntldr. I could Repair Install, and that puts one
>>>> back.
>>>>
>>>> But for other classes of problems, like Malware,
>>>> a Repair Install is useless. And a broken System Restore
>>>> is not really all that good of a sign (permissions ?
>>>> something CKKDSK needs to fix ? State Info ?).
>>>>
>>>> *******
>>>>
>>>> I recently (three months ago) did a Clean Install,
>>>> and I'm still not all bolted back together yet. I used
>>>> a spare disk for the new OS, and I can refer back to
>>>> the "carcass" of the previous OS which is still
>>>> connected and running.
>>>>
>>>> HTH,
>>>> Paul
>>> Before I start on anything where does one get the WSUS Offline Update
>>> for Windows XP PRO and instructions on downloading and burning to CD
>>> so I can have it on hand when I do a repair of full reinstall.
>>>
>>> Thanks,
>>> JAS
>>
>> Apparently 9.3 removed WinXP, so my guess is
>> that 9.2.1 might have it.
>>
>> Look for 9.2.1 on the right-hand sidebar.
>>
>> http://web.archive.org/web/20140605101941/http://download.wsusoffline.net/
>>
>>
>>
>> http://web.archive.org/web/20140602113508/http://download.wsusoffline.net/wsusoffline921.zip
>>
>>
>>
>> Run the generator, click the Legacy products tab.
>>
>> Paul
> Paul,
> downloaded and saved the wsusoffline file to use later. Here is a link
> to a photo of the latest crash I have had, any idea as to cause? I was
> able to reboot. https://s22.postimg.org/up9gonfrl/blue_screen.jpg
> Sorry about the flash flare.
>
> JAS

http://aumha.org/a/stop.htm

[tcpip.sys]

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a
kernel process IRQL that was too high. The most typical
cause is a bad device driver (one that uses improper addresses).

It can also be caused by caused by faulty or mismatched RAM,
or a damaged pagefile.

*******

This doesn't help much.

https://en.wikipedia.org/wiki/IRQL_(Windows)

*******

I would guess you have something like a filter
driver in the network stack. Something "unique",
perhaps an older add-on software product that
doesn't really belong on WinXP. Maybe a TAP or TUN.
I've had some tiny ones of those that caused
havoc, because they were written for some older
OS and didn't really belong on my machine. I
don't think the authors even had source, and
they were just carting around the binary and
handing it out.

With regard to the "faulty RAM" idea, don't take
that as gospel. One way to tell if hardware is
contributing, is the "randomness" of the error.
If one minute the error is 0x22, next time 0x33,
next time 0x45 and so on, then bad RAM *could*
contribute to that. But if the error is consistently
always 0xD1 and TCPIP.SYS, then you know it has
nothing to do with RAM, and everything to do with
software. The consistency over time of the error,
helps narrow down that side of the issue.

Just a guess,
Paul

[JAS]

Paul wrote:
> JAS wrote:
>> Paul wrote:
>>> JAS wrote:
>>>> Paul wrote:
>>>>> JAS wrote:
>>>>>> I have a Sony laptop VGN-BS540B with Windows XP Pro SP3 installed.
>>>>>> How
>>>>>> does one go about to do an repair install? I have a Win XP Pro CD
>>>>>> with
>>>>>> serial # and slipstreamed with SP3 on it. I purchased the laptop new
>>>>>> and it came with XP Pro installed on it. I clone my HD with Apricorn
>>>>>> EZ Gig and have three HDs that are bootable. My problem is that
>>>>>> several years ago at times when I would shut down and go to restart I
>>>>>> would receive a blue screen stating that certain files in System32
>>>>>> were corrupt or missing also my system restore quite working and if I
>>>>>> tried to do a system restore I would get the blue screen. I would put
>>>>>> my other drive in and clone it on the one with the blue screen after
>>>>>> coping my SM profile and other files that were important and that
>>>>>> changed since the last clone and then put that drive back in and all
>>>>>> is well as long as I put the laptop in standby instead of shutting
>>>>>> down although at times when I do shut down all works OK but then I
>>>>>> will get the blue screen and have to switch drives again.
>>>>>> Any help would be appropriated.
>>>>>>
>>>>>> JAS
>>>>>
>>>>> VGN-BX540B
>>>>>
>>>>> http://www.michaelstevenstech.com/XPrepairinstall.htm
>>>>>
>>>>> "A Repair Install is not foolproof and should not
>>>>> be considered the cure-all fix for non-boot situations."
>>>>>
>>>>> You get to keep your programs and settings. The settings
>>>>> are in the Registry, and only portions of the Registry
>>>>> would change when a Repair Install is done. (Maybe the
>>>>> hardware ENUM hive is wiped ?)
>>>>>
>>>>> You have to do Windows Update over again.
>>>>>
>>>>> To do a Repair Install, you need to go to Add/Remove
>>>>> and remove any advanced version of Internet Explorer.
>>>>> As the OS installer doesn't do the right thing. Once the
>>>>> OS installation process is finished, you can reinstall
>>>>> any advanced versions of Internet Explorer. Once
>>>>> Internet Explorer is patched with the last Cumulative
>>>>> Update for Internet Explorer for Windows XP, then
>>>>> you can visit Windows Update and try to get the
>>>>> security updates on the screen. There is a problem with
>>>>> wuauserv on WinXP/Vista/Win7/Win8 which prevents the
>>>>> list of updates from appearing in a timely fashion.
>>>>>
>>>>> Whether you do a Repair Install or a Clean Install,
>>>>> it's still a lot of work.
>>>>>
>>>>> In your case, I like the idea of buying another
>>>>> hard drive for this install. It covers two things.
>>>>> It prevents a defective hard drive from blue screening
>>>>> the machine again. It also gives you a clean place to
>>>>> work.
>>>>>
>>>>> The blue screen could have been caused by a driver
>>>>> problem at shutdown. Maybe a driver is actually
>>>>> crashing or something.
>>>>>
>>>>> You disable "automatic reboot" in Windows, to make
>>>>> the BSOD stay still. Then you can copy the STOP
>>>>> code and look it up.
>>>>>
>>>>> http://aumha.org/a/stop.htm
>>>>>
>>>>> It really helps to have a root cause in hand for
>>>>> a problem like this, so you don't waste time
>>>>> on a solution that's not going to improve matters.
>>>>> If it was an actual hardware issue for example,
>>>>> you could BSOD the very same day after the
>>>>> Repair Install.
>>>>>
>>>>> And your OS partition should at least be "CHKDSK clean"
>>>>> before you start the Repair Install. By the sounds
>>>>> of your description, there may be damage after each
>>>>> one of these BSODs.
>>>>>
>>>>> I think conceptually, a Repair Install is great
>>>>> for a "missing" file problem. Say I no longer have
>>>>> an ntldr. I could Repair Install, and that puts one
>>>>> back.
>>>>>
>>>>> But for other classes of problems, like Malware,
>>>>> a Repair Install is useless. And a broken System Restore
>>>>> is not really all that good of a sign (permissions ?
>>>>> something CKKDSK needs to fix ? State Info ?).
>>>>>
>>>>> *******
>>>>>
>>>>> I recently (three months ago) did a Clean Install,
>>>>> and I'm still not all bolted back together yet. I used
>>>>> a spare disk for the new OS, and I can refer back to
>>>>> the "carcass" of the previous OS which is still
>>>>> connected and running.
>>>>>
>>>>> HTH,
>>>>> Paul
>>>> Before I start on anything where does one get the WSUS Offline Update
>>>> for Windows XP PRO and instructions on downloading and burning to CD
>>>> so I can have it on hand when I do a repair of full reinstall.
>>>>
>>>> Thanks,
>>>> JAS
>>>
>>> Apparently 9.3 removed WinXP, so my guess is
>>> that 9.2.1 might have it.
>>>
>>> Look for 9.2.1 on the right-hand sidebar.
>>>
>>> http://web.archive.org/web/20140605101941/http://download.wsusoffline.net/
>>>
>>>
>>>
>>> http://web.archive.org/web/20140602113508/http://download.wsusoffline.net/wsusoffline921.zip
>>>
>>>
>>>
>>> Run the generator, click the Legacy products tab.
>>>
>>> Paul
>> Paul,
>> downloaded and saved the wsusoffline file to use later. Here is a link
>> to a photo of the latest crash I have had, any idea as to cause? I was
>> able to reboot. https://s22.postimg.org/up9gonfrl/blue_screen.jpg
>> Sorry about the flash flare.
>>
>> JAS
>
> http://aumha.org/a/stop.htm
>
> [tcpip.sys]
>
> 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
> (Click to consult the online Win XP Resource Kit article.)
> The system attempted to access pageable memory using a
> kernel process IRQL that was too high. The most typical
> cause is a bad device driver (one that uses improper addresses).
>
> It can also be caused by caused by faulty or mismatched RAM,
> or a damaged pagefile.
>
> *******
>
> This doesn't help much.
>
> https://en.wikipedia.org/wiki/IRQL_(Windows)
>
> *******
>
> I would guess you have something like a filter
> driver in the network stack. Something "unique",
> perhaps an older add-on software product that
> doesn't really belong on WinXP. Maybe a TAP or TUN.
> I've had some tiny ones of those that caused
> havoc, because they were written for some older
> OS and didn't really belong on my machine. I
> don't think the authors even had source, and
> they were just carting around the binary and
> handing it out.
>
> With regard to the "faulty RAM" idea, don't take
> that as gospel. One way to tell if hardware is
> contributing, is the "randomness" of the error.
> If one minute the error is 0x22, next time 0x33,
> next time 0x45 and so on, then bad RAM *could*
> contribute to that. But if the error is consistently
> always 0xD1 and TCPIP.SYS, then you know it has
> nothing to do with RAM, and everything to do with
> software. The consistency over time of the error,
> helps narrow down that side of the issue.
>
> Just a guess,
> Paul
Paul,
Thanks for the reply. Maybe the best bet overall would be to start anew
with a new drive also. Thanks again.

JAS

[Paul[_32_]]

JAS wrote:

> Paul,
> Thanks for the reply. Maybe the best bet overall would be to start anew
> with a new drive also. Thanks again.
>
> JAS

I had a problem here, which defeated my best attempts
to fix, so yes, reinstalling may mean less
aggravation.

My problem was starting a program, I could see a tremendous
amount of file system scanning go on. Then, the scan activity
would hit my RAMDisk, and eventually a call was made to
Explorer, for which it had no subroutine code (shell32.dll
ordinal 65). Leading to a crash of Explorer. I couldn't figure
out the root cause. I could sorta see the symptoms, but not
what kicked it off. And the OS had many other flaky symptoms
as well (missing Windows sound, task bar notification funny
business, and so on). Scans with AV products revealed absolutely
nothing. I played with it for a long time, before giving up. It
liked to crash just after midnight (so you typically only
got to "trace" it, once a day).

Paul

[JAS]

Paul wrote:
> JAS wrote:
>
>> Paul,
>> Thanks for the reply. Maybe the best bet overall would be to start
>> anew with a new drive also. Thanks again.
>>
>> JAS
>
> I had a problem here, which defeated my best attempts
> to fix, so yes, reinstalling may mean less
> aggravation.
>
> My problem was starting a program, I could see a tremendous
> amount of file system scanning go on. Then, the scan activity
> would hit my RAMDisk, and eventually a call was made to
> Explorer, for which it had no subroutine code (shell32.dll
> ordinal 65). Leading to a crash of Explorer. I couldn't figure
> out the root cause. I could sorta see the symptoms, but not
> what kicked it off. And the OS had many other flaky symptoms
> as well (missing Windows sound, task bar notification funny
> business, and so on). Scans with AV products revealed absolutely
> nothing. I played with it for a long time, before giving up. It
> liked to crash just after midnight (so you typically only
> got to "trace" it, once a day).
>
> Paul
Just a note on progress. Was getting ready to do the install and my
laptop screen went blank after flickering and turning pale and red. I
had an old IBM monitor and hooked it up dn it displayed OK but I am in
the search for a display: This is what I copied on my graphics before it
went black. Sony VGN-BX540B, I believe it is 14.1"
display Type: Digital
Gamma Value: 3.54
DDC2 Protocol: Supported
Maximum Image Size: Horizontal: Not Available
Vertical: Not Available
Monitor Supported Modes:
640 by 480 (60 Hz)
800 by 600 (60 Hz)
1024 by 768 (60 Hz)
Accelerator in Use: Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family
Video BIOS: 1220
Current Graphics Mode: 1024 by 768 True Color (60 Hz)
Where is a good place to purchase one?
Thanks and have a great weekend.
JAS


--
You either teach people to treat you with dignity and respect, or
you don't. This means you are partly responsible for the mistreatment
that you get at the hands of someone else.

[J. P. Gilliver (John)]

In message >, JAS >
writes:
[]
>Just a note on progress. Was getting ready to do the install and my
>laptop screen went blank after flickering and turning pale and red. I
>had an old IBM monitor and hooked it up dn it displayed OK but I am in
>the search for a display: This is what I copied on my graphics before
>it went black. Sony VGN-BX540B, I believe it is 14.1"
[]
Look on YouTube: there's probably a video on how to dismantle your
laptop to replace the display - there was for the Asus I had to do it
on. In my case, it wasn't necessary to dismantle the part of the laptop
below the hinges (or the hinges), it could all be done by prising off
the covers to the screws holding the bezel (screen surround), and
removing that; YMMV with the Sony (I'm assuming the laptop is the Sony
whose details you quoted).

Also, the person giving that tutorial said get the part number from the
back of the display, and search for that, rather than using the model
number of the laptop, as it'll probably turn out cheaper. In my case it
was about 30 pounds IIRR (which would probably be $30 in the USA - most
things are, electronics anyway).

Of course, it might not be the display but the display "card", but the
fact that it still drives an external monitor suggests that's still OK.
(Oh, thinking about it, the fact that you quoted several "Monitor
Supported Modes" suggests that the Sony might be the graphics chipset;
it certainly wouldn't be the display itself, as that has a fixed
resolution.)

From your description, it _could_ just be the backlight that's gone: can
you still see _anything_ on the laptop screen, if you hold it at funny
angles, shine lights on it, etcetera? In my case that wouldn't have made
any difference, because the display module and backlight were more or
less a sealed unit, but it might be different in your case.

Or, it could just be the _supply_ to the backlight (again, if that's the
case, you should still be able to see shadowy things on the display).
Unless they use LEDs now, the backlight is probably a fluorescent tube,
or an electroluminescent panel; both of those I think need about 180
volts, which is (was in my Asus, anyway) created on a small separate
circuit board (about 3 by ½ inch, IIRR) behind the display.

Or, if you're _very_ lucky, the connections may have just come loose.
The display is a ribbon cable not unlike that for the keyboard, and the
backlight supply a plug and socket. (Watch out for the voltages of
course; I don't _think_ there's enough oomph behind them to harm you,
but it could give a belt that causes you to knock the laptop off the
table, or move your hand suddenly into some of the sharp metalwork
that's exposed when you start taking bezels off.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"If god doesn't like the way I live, Let him tell me, not you." - unknown

[Paul[_32_]]

JAS wrote:
> Paul wrote:
>> JAS wrote:
>>
>>> Paul,
>>> Thanks for the reply. Maybe the best bet overall would be to start
>>> anew with a new drive also. Thanks again.
>>>
>>> JAS
>>
>> I had a problem here, which defeated my best attempts
>> to fix, so yes, reinstalling may mean less
>> aggravation.
>>
>> My problem was starting a program, I could see a tremendous
>> amount of file system scanning go on. Then, the scan activity
>> would hit my RAMDisk, and eventually a call was made to
>> Explorer, for which it had no subroutine code (shell32.dll
>> ordinal 65). Leading to a crash of Explorer. I couldn't figure
>> out the root cause. I could sorta see the symptoms, but not
>> what kicked it off. And the OS had many other flaky symptoms
>> as well (missing Windows sound, task bar notification funny
>> business, and so on). Scans with AV products revealed absolutely
>> nothing. I played with it for a long time, before giving up. It
>> liked to crash just after midnight (so you typically only
>> got to "trace" it, once a day).
>>
>> Paul
> Just a note on progress. Was getting ready to do the install and my
> laptop screen went blank after flickering and turning pale and red. I
> had an old IBM monitor and hooked it up dn it displayed OK but I am in
> the search for a display: This is what I copied on my graphics before it
> went black. Sony VGN-BX540B, I believe it is 14.1"
> display Type: Digital
> Gamma Value: 3.54
> DDC2 Protocol: Supported
> Maximum Image Size: Horizontal: Not Available
> Vertical: Not Available
> Monitor Supported Modes:
> 640 by 480 (60 Hz)
> 800 by 600 (60 Hz)
> 1024 by 768 (60 Hz)
> Accelerator in Use: Mobile Intel(R) 915GM/GMS,910GML Express
> Chipset Family
> Video BIOS: 1220
> Current Graphics Mode: 1024 by 768 True Color (60 Hz)
> Where is a good place to purchase one?
> Thanks and have a great weekend.
> JAS
>
>

Some possibilities:

1) Intel 915GM problem (not likely). If the GPU was
one of the affected NVidia ones, those had solder
ball problems which caused video failure. I don't
recollect any Intel Northbridges like that (the
GPU might be in the Northbridge).

2) Cable which connects mainboard to LCD panel
has come loose. This is what I'd check first.
The connector needs to be re-seated.

3) Power connections may be on that cable. Or
perhaps handled separate, or maybe power is
run through the hinges ? Normally the wires in
a data cable are quite thin, a bit thin for
power usage.

4) Backlight problem. Inverter and CCFL tubes.
There can be multiple of those. Those would
be separate from the LCD panel. A CCFL tube last
for 25000 hours. The light output "turns brown"
as they age.

5) LCD panel problem. Usually damaged single pixel
rows or columns.

6) Some sorta regulator on the mainboard which
feeds power to (3).

I'm not getting a strong feeling right now,
this is the panel itself. But it does happen.
This feels more like a cabling problem perhaps,
or something not quite right on the mainboard.

When buying LCD panels, you have to be careful.
As some models of laptops, happen to have two
different panel resolutions. And a firmware change
is required to handle a different panel. If you
get the wrong panel, there will be a "blank area"
on the right and bottom of the new screen.

Sometimes the cheapest source, is a non-parted-out
laptop. This one is intact for example.

http://www.ebay.com/itm/SONY-VAIO-14-CENTRINO-1-5GB-WORKING-AS-IS-/272449805928

So what you're looking for in a case like that,
is one where the panel isn't cracked or smashed.

Some people take the machines apart, sell all the
components separately, and then charge a lot more
for the panel. When you can find complete working
used laptops (different model) for less money than
a seller wants for the panel for your machine.

You can find TN monitors at the store today for
$100, so really, a replacement panel for a laptop
should be less than that. Anyone charging $200+
for an LCD panel is out of their mind. If the
panel was "fancy", a higher res panel of IPS type,
maybe they could make a case for charging a few
bucks more. But for cheap TN panels, they shouldn't
cost more than a complete LCD monitor.

Paul

[JAS]

J. P. Gilliver (John) wrote:
> In message >, JAS >
> writes:
> []
>> Just a note on progress. Was getting ready to do the install and my
>> laptop screen went blank after flickering and turning pale and red. I
>> had an old IBM monitor and hooked it up dn it displayed OK but I am in
>> the search for a display: This is what I copied on my graphics before
>> it went black. Sony VGN-BX540B, I believe it is 14.1"
> []
> Look on YouTube: there's probably a video on how to dismantle your
> laptop to replace the display - there was for the Asus I had to do it
> on. In my case, it wasn't necessary to dismantle the part of the laptop
> below the hinges (or the hinges), it could all be done by prising off
> the covers to the screws holding the bezel (screen surround), and
> removing that; YMMV with the Sony (I'm assuming the laptop is the Sony
> whose details you quoted).
>
> Also, the person giving that tutorial said get the part number from the
> back of the display, and search for that, rather than using the model
> number of the laptop, as it'll probably turn out cheaper. In my case it
> was about 30 pounds IIRR (which would probably be $30 in the USA - most
> things are, electronics anyway).
>
> Of course, it might not be the display but the display "card", but the
> fact that it still drives an external monitor suggests that's still OK.
> (Oh, thinking about it, the fact that you quoted several "Monitor
> Supported Modes" suggests that the Sony might be the graphics chipset;
> it certainly wouldn't be the display itself, as that has a fixed
> resolution.)
>
> From your description, it _could_ just be the backlight that's gone: can
> you still see _anything_ on the laptop screen, if you hold it at funny
> angles, shine lights on it, etcetera? In my case that wouldn't have made
> any difference, because the display module and backlight were more or
> less a sealed unit, but it might be different in your case.
>
> Or, it could just be the _supply_ to the backlight (again, if that's the
> case, you should still be able to see shadowy things on the display).
> Unless they use LEDs now, the backlight is probably a fluorescent tube,
> or an electroluminescent panel; both of those I think need about 180
> volts, which is (was in my Asus, anyway) created on a small separate
> circuit board (about 3 by ½ inch, IIRR) behind the display.
>
> Or, if you're _very_ lucky, the connections may have just come loose.
> The display is a ribbon cable not unlike that for the keyboard, and the
> backlight supply a plug and socket. (Watch out for the voltages of
> course; I don't _think_ there's enough oomph behind them to harm you,
> but it could give a belt that causes you to knock the laptop off the
> table, or move your hand suddenly into some of the sharp metalwork
> that's exposed when you start taking bezels off.)
John,
The screen is pitch black, on sec. it was there and next it was gone.
Laptop has never been carried much, just sits on desk or my lap. It has
a 14.1" XGA display. Thanks for reply and will study info more as I am
on a small netbook now.

[JAS]

Paul wrote:
> JAS wrote:
>> Paul wrote:
>>> JAS wrote:
>>>
>>>> Paul,
>>>> Thanks for the reply. Maybe the best bet overall would be to start
>>>> anew with a new drive also. Thanks again.
>>>>
>>>> JAS
>>>
>>> I had a problem here, which defeated my best attempts
>>> to fix, so yes, reinstalling may mean less
>>> aggravation.
>>>
>>> My problem was starting a program, I could see a tremendous
>>> amount of file system scanning go on. Then, the scan activity
>>> would hit my RAMDisk, and eventually a call was made to
>>> Explorer, for which it had no subroutine code (shell32.dll
>>> ordinal 65). Leading to a crash of Explorer. I couldn't figure
>>> out the root cause. I could sorta see the symptoms, but not
>>> what kicked it off. And the OS had many other flaky symptoms
>>> as well (missing Windows sound, task bar notification funny
>>> business, and so on). Scans with AV products revealed absolutely
>>> nothing. I played with it for a long time, before giving up. It
>>> liked to crash just after midnight (so you typically only
>>> got to "trace" it, once a day).
>>>
>>> Paul
>> Just a note on progress. Was getting ready to do the install and my
>> laptop screen went blank after flickering and turning pale and red. I
>> had an old IBM monitor and hooked it up dn it displayed OK but I am in
>> the search for a display: This is what I copied on my graphics before
>> it went black. Sony VGN-BX540B, I believe it is 14.1"
>> display Type: Digital
>> Gamma Value: 3.54
>> DDC2 Protocol: Supported
>> Maximum Image Size: Horizontal: Not Available
>> Vertical: Not Available
>> Monitor Supported Modes:
>> 640 by 480 (60 Hz)
>> 800 by 600 (60 Hz)
>> 1024 by 768 (60 Hz)
>> Accelerator in Use: Mobile Intel(R) 915GM/GMS,910GML Express
>> Chipset Family
>> Video BIOS: 1220
>> Current Graphics Mode: 1024 by 768 True Color (60 Hz)
>> Where is a good place to purchase one?
>> Thanks and have a great weekend.
>> JAS
>>
>>
>
> Some possibilities:
>
> 1) Intel 915GM problem (not likely). If the GPU was
> one of the affected NVidia ones, those had solder
> ball problems which caused video failure. I don't
> recollect any Intel Northbridges like that (the
> GPU might be in the Northbridge).
>
> 2) Cable which connects mainboard to LCD panel
> has come loose. This is what I'd check first.
> The connector needs to be re-seated.
>
> 3) Power connections may be on that cable. Or
> perhaps handled separate, or maybe power is
> run through the hinges ? Normally the wires in
> a data cable are quite thin, a bit thin for
> power usage.
>
> 4) Backlight problem. Inverter and CCFL tubes.
> There can be multiple of those. Those would
> be separate from the LCD panel. A CCFL tube last
> for 25000 hours. The light output "turns brown"
> as they age.
>
> 5) LCD panel problem. Usually damaged single pixel
> rows or columns.
>
> 6) Some sorta regulator on the mainboard which
> feeds power to (3).
>
> I'm not getting a strong feeling right now,
> this is the panel itself. But it does happen.
> This feels more like a cabling problem perhaps,
> or something not quite right on the mainboard.
>
> When buying LCD panels, you have to be careful.
> As some models of laptops, happen to have two
> different panel resolutions. And a firmware change
> is required to handle a different panel. If you
> get the wrong panel, there will be a "blank area"
> on the right and bottom of the new screen.
>
> Sometimes the cheapest source, is a non-parted-out
> laptop. This one is intact for example.
>
> http://www.ebay.com/itm/SONY-VAIO-14-CENTRINO-1-5GB-WORKING-AS-IS-/272449805928
>
>
> So what you're looking for in a case like that,
> is one where the panel isn't cracked or smashed.
>
> Some people take the machines apart, sell all the
> components separately, and then charge a lot more
> for the panel. When you can find complete working
> used laptops (different model) for less money than
> a seller wants for the panel for your machine.
>
> You can find TN monitors at the store today for
> $100, so really, a replacement panel for a laptop
> should be less than that. Anyone charging $200+
> for an LCD panel is out of their mind. If the
> panel was "fancy", a higher res panel of IPS type,
> maybe they could make a case for charging a few
> bucks more. But for cheap TN panels, they shouldn't
> cost more than a complete LCD monitor.
>
> Paul
Paul,
I am going to check out ebay and see what I can find, it lo9oks liker a
used unit with a good screen whould be the way to go. When I get some
time, right now grandkids here for a week or so for Thanksgiving. I will
be spending my time with them but all ideas will be appreciated.

JAS

[Paul[_32_]]

JAS wrote:
> Paul wrote:
>> JAS wrote:
>>> Paul wrote:
>>>> JAS wrote:
>>>>
>>>>> Paul,
>>>>> Thanks for the reply. Maybe the best bet overall would be to start
>>>>> anew with a new drive also. Thanks again.
>>>>>
>>>>> JAS
>>>>
>>>> I had a problem here, which defeated my best attempts
>>>> to fix, so yes, reinstalling may mean less
>>>> aggravation.
>>>>
>>>> My problem was starting a program, I could see a tremendous
>>>> amount of file system scanning go on. Then, the scan activity
>>>> would hit my RAMDisk, and eventually a call was made to
>>>> Explorer, for which it had no subroutine code (shell32.dll
>>>> ordinal 65). Leading to a crash of Explorer. I couldn't figure
>>>> out the root cause. I could sorta see the symptoms, but not
>>>> what kicked it off. And the OS had many other flaky symptoms
>>>> as well (missing Windows sound, task bar notification funny
>>>> business, and so on). Scans with AV products revealed absolutely
>>>> nothing. I played with it for a long time, before giving up. It
>>>> liked to crash just after midnight (so you typically only
>>>> got to "trace" it, once a day).
>>>>
>>>> Paul
>>> Just a note on progress. Was getting ready to do the install and my
>>> laptop screen went blank after flickering and turning pale and red. I
>>> had an old IBM monitor and hooked it up dn it displayed OK but I am in
>>> the search for a display: This is what I copied on my graphics before
>>> it went black. Sony VGN-BX540B, I believe it is 14.1"
>>> display Type: Digital
>>> Gamma Value: 3.54
>>> DDC2 Protocol: Supported
>>> Maximum Image Size: Horizontal: Not Available
>>> Vertical: Not Available
>>> Monitor Supported Modes:
>>> 640 by 480 (60 Hz)
>>> 800 by 600 (60 Hz)
>>> 1024 by 768 (60 Hz)
>>> Accelerator in Use: Mobile Intel(R) 915GM/GMS,910GML Express
>>> Chipset Family
>>> Video BIOS: 1220
>>> Current Graphics Mode: 1024 by 768 True Color (60 Hz)
>>> Where is a good place to purchase one?
>>> Thanks and have a great weekend.
>>> JAS
>>>
>>>
>>
>> Some possibilities:
>>
>> 1) Intel 915GM problem (not likely). If the GPU was
>> one of the affected NVidia ones, those had solder
>> ball problems which caused video failure. I don't
>> recollect any Intel Northbridges like that (the
>> GPU might be in the Northbridge).
>>
>> 2) Cable which connects mainboard to LCD panel
>> has come loose. This is what I'd check first.
>> The connector needs to be re-seated.
>>
>> 3) Power connections may be on that cable. Or
>> perhaps handled separate, or maybe power is
>> run through the hinges ? Normally the wires in
>> a data cable are quite thin, a bit thin for
>> power usage.
>>
>> 4) Backlight problem. Inverter and CCFL tubes.
>> There can be multiple of those. Those would
>> be separate from the LCD panel. A CCFL tube last
>> for 25000 hours. The light output "turns brown"
>> as they age.
>>
>> 5) LCD panel problem. Usually damaged single pixel
>> rows or columns.
>>
>> 6) Some sorta regulator on the mainboard which
>> feeds power to (3).
>>
>> I'm not getting a strong feeling right now,
>> this is the panel itself. But it does happen.
>> This feels more like a cabling problem perhaps,
>> or something not quite right on the mainboard.
>>
>> When buying LCD panels, you have to be careful.
>> As some models of laptops, happen to have two
>> different panel resolutions. And a firmware change
>> is required to handle a different panel. If you
>> get the wrong panel, there will be a "blank area"
>> on the right and bottom of the new screen.
>>
>> Sometimes the cheapest source, is a non-parted-out
>> laptop. This one is intact for example.
>>
>> http://www.ebay.com/itm/SONY-VAIO-14-CENTRINO-1-5GB-WORKING-AS-IS-/272449805928
>>
>>
>>
>> So what you're looking for in a case like that,
>> is one where the panel isn't cracked or smashed.
>>
>> Some people take the machines apart, sell all the
>> components separately, and then charge a lot more
>> for the panel. When you can find complete working
>> used laptops (different model) for less money than
>> a seller wants for the panel for your machine.
>>
>> You can find TN monitors at the store today for
>> $100, so really, a replacement panel for a laptop
>> should be less than that. Anyone charging $200+
>> for an LCD panel is out of their mind. If the
>> panel was "fancy", a higher res panel of IPS type,
>> maybe they could make a case for charging a few
>> bucks more. But for cheap TN panels, they shouldn't
>> cost more than a complete LCD monitor.
>>
>> Paul
> Paul,
> I am going to check out ebay and see what I can find, it lo9oks liker a
> used unit with a good screen whould be the way to go. When I get some
> time, right now grandkids here for a week or so for Thanksgiving. I will
> be spending my time with them but all ideas will be appreciated.
>
> JAS

In another post, you mention that the screen works
for a couple seconds, then goes black. That's the
inverter in the LCD panel shutting down. Either the
inverter is weak, or the CCFL tube is presenting
more load than normal.

On the old analog intensity setting knobs, you
could increase the intensity setting, and the
problem will go away for around two or three weeks.
Modern intensity controls use PWM (pulse width
modulation) and might not achieve the same result.

Both inverters and CCFL tubes can be replaced,
but you can never get "exact" replacements. There
are shops on the Internet selling generic solutions
covering more than one model. And that's about as
close as you get.

Having a computer to pick the parts off, is about
as effective a method as any. In fact, depending
on the condition of the unit, it might be possible
to just swap hard drives and repair it that way.

Paul

[JAS]

Paul wrote:


JAS wrote:
Paul wrote:
JAS wrote:
Paul wrote:
JAS wrote:

Paul,
Thanks for the reply. Maybe the best bet overall would be to start
anew with a new drive also. Thanks again.

JAS

I had a problem here, which defeated my best attempts
to fix, so yes, reinstalling may mean less
aggravation.

My problem was starting a program, I could see a tremendous
amount of file system scanning go on. Then, the scan activity
would hit my RAMDisk, and eventually a call was made to
Explorer, for which it had no subroutine code (shell32.dll
ordinal 65). Leading to a crash of Explorer. I couldn't figure
out the root cause. I could sorta see the symptoms, but not
what kicked it off. And the OS had many other flaky symptoms
as well (missing Windows sound, task bar notification funny
business, and so on). Scans with AV products revealed absolutely
nothing. I played with it for a long time, before giving up. It
liked to crash just after midnight (so you typically only
got to "trace" it, once a day).

Â*Â*Â* Paul
Just a note on progress. Was getting ready to do the install and my
laptop screen went blank after flickering and turning pale and red. I
had an old IBM monitor and hooked it up dn it displayed OK but I am in
the search for a display: This is what I copied on my graphics before
it went black. Sony VGN-BX540B, I believe it is 14.1"
display Type:Â*Â*Â*Â*Â*Â*Â* Digital
Gamma Value:Â*Â*Â*Â*Â*Â*Â* 3.54
DDC2 Protocol:Â*Â*Â*Â*Â*Â*Â* Supported
Maximum Image Size:Â*Â*Â* Horizontal: Not Available
Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Vertical:Â*Â* Not Available
Monitor Supported Modes:
640 by 480 (60 Hz)
800 by 600 (60 Hz)
1024 by 768 (60 Hz)
Accelerator in Use:Â*Â*Â*Â*Â*Â*Â* Mobile Intel(R) 915GM/GMS,910GML Express
Chipset Family
Video BIOS:Â*Â*Â*Â*Â*Â*Â* 1220
Current Graphics Mode:Â*Â*Â* 1024 by 768 True Color (60 Hz)
Where is a good place to purchase one?
Thanks and have a great weekend.
JAS



Some possibilities:

1) Intel 915GM problem (not likely). If the GPU was
Â*Â* one of the affected NVidia ones, those had solder
Â*Â* ball problems which caused video failure. I don't
Â*Â* recollect any Intel Northbridges like that (the
Â*Â* GPU might be in the Northbridge).

2) Cable which connects mainboard to LCD panel
Â*Â* has come loose. This is what I'd check first.
Â*Â* The connector needs to be re-seated.

3) Power connections may be on that cable. Or
Â*Â* perhaps handled separate, or maybe power is
Â*Â* run through the hinges ? Normally the wires in
Â*Â* a data cable are quite thin, a bit thin for
Â*Â* power usage.

4) Backlight problem. Inverter and CCFL tubes.
Â*Â* There can be multiple of those. Those would
Â*Â* be separate from the LCD panel. A CCFL tube last
Â*Â* for 25000 hours. The light output "turns brown"
Â*Â* as they age.

5) LCD panel problem. Usually damaged single pixel
Â*Â* rows or columns.

6) Some sorta regulator on the mainboard which
Â*Â* feeds power to (3).

I'm not getting a strong feeling right now,
this is the panel itself. But it does happen.
This feels more like a cabling problem perhaps,
or something not quite right on the mainboard.

When buying LCD panels, you have to be careful.
As some models of laptops, happen to have two
different panel resolutions. And a firmware change
is required to handle a different panel. If you
get the wrong panel, there will be a "blank area"
on the right and bottom of the new screen.

Sometimes the cheapest source, is a non-parted-out
laptop. This one is intact for example.

http://www.ebay.com/itm/SONY-VAIO-14-CENTRINO-1-5GB-WORKING-AS-IS-/272449805928


So what you're looking for in a case like that,
is one where the panel isn't cracked or smashed.

Some people take the machines apart, sell all the
components separately, and then charge a lot more
for the panel. When you can find complete working
used laptops (different model) for less money than
a seller wants for the panel for your machine.

You can find TN monitors at the store today for
$100, so really, a replacement panel for a laptop
should be less than that. Anyone charging $200+
for an LCD panel is out of their mind. If the
panel was "fancy", a higher res panel of IPS type,
maybe they could make a case for charging a few
bucks more. But for cheap TN panels, they shouldn't
cost more than a complete LCD monitor.

Â*Â* Paul
Paul,
I am going to check out ebay and see what I can find, it lo9oks liker a used unit with a good screen whould be the way to go. When I get some time, right now grandkids here for a week or so for Thanksgiving. I will be spending my time with them but all ideas will be appreciated.

JAS

In another post, you mention that the screen works
for a couple seconds, then goes black. That's the
inverter in the LCD panel shutting down. Either the
inverter is weak, or the CCFL tube is presenting
more load than normal.
It did flicker and go sort of brown and then would be OK for a bit but the last time it flickered and was black.
On the old analog intensity setting knobs, you
could increase the intensity setting, and the
problem will go away for around two or three weeks.
Modern intensity controls use PWM (pulse width
modulation) and might not achieve the same result.

Both inverters and CCFL tubes can be replaced,
but you can never get "exact" replacements. There
are shops on the Internet selling generic solutions
covering more than one model. And that's about as
close as you get.

Having a computer to pick the parts off, is about
as effective a method as any. In fact, depending
on the condition of the unit, it might be possible
to just swap hard drives and repair it that way.
Yes it a option to consider - I want to stay with my XP but may have to buy a win. 7 and move on in life,ha It would be nice to find a good used one like I have. For me change is always hard.
Â*Â*

[J. P. Gilliver (John)]

In message >, JAS >
writes:
[]
>John,
> The screen is pitch black, on sec. it was there and next it was
>gone. Laptop has never been carried much, just sits on desk or my lap.

Well, as Paul says, they do sometimes fail - but as he also says, it
sounds more like
o a loose connection
o a backlight failure
o an inverter failure (which provides the power to the backlight).

I'd open it up (as I said, there may well be a YouTube video showing you
how - worth looking for, as there can be gotchas, such as a right order
to remove screws to stop things suddenly falling away inside), and then
initially waggle connections, then look to see if the backlight is
separable from the panel or a sealed unit.

I take it there's no sign of light where there previously was (through
cracks in the casing, etc.) - though for a Sony, it might have been well
enough designed and assembled that there never was any such light
leakage.

>It has a 14.1" XGA display. Thanks for reply and will study info more
>as I am on a small netbook now.

XGA - that's 1024 × 768, isn't it? Anyway, you'll need the part number
from the display module itself (assuming you need the whole module not
just the backlight). It _might_ be a Sony special, but I hope it isn't,
as a generic is likely to be cheaper. (Or, as Paul says, you could get
hold of a broken-but-display-still-working computer of the same model,
and Frankenstein. Or, once you have the panel part number, google for it
and hope that it's advertised as "suitable for Sony xxx, cheap-make yyy,
....", then look for a broken-but-display-OK cheap-model yyy. Though
beware of finding ones where the same model came with two different
displays during its production lifetime.)
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

As the man said when confronted by a large dinner salad, "This isn't food.
This is what food eats."