J
Jose
Flightless Bird
On Jan 12, 10:28 am, "Terry R." <F1...@NOSPAMpobox.com> wrote:
> On 1/9/2010 1:44 PM On a whim, Daave pounded out on the keyboard
>
>
>
>
>
> > Terry R. wrote:
> >> On 1/9/2010 8:19 AM On a whim, Daave pounded out on the keyboard
>
> >>> Terry R. wrote:
> >>>> On 1/8/2010 7:27 AM On a whim, Daave pounded out on the keyboard
>
> >>>>> Terry R. wrote:
> >>>>>> XP on this workstation will randomly freeze. While I'm working on
> >>>>>> it, sitting idle. It will go for a week or more, then lock every
> >>>>>> day. I've slowly reduced Hardware acceleration. Updated drivers,
> >>>>>> changed
> >>>>>> out RAM, repair install. Even swapped out the power supply. Just
> >>>>>> when I think I've resolved it, it freezes...
>
> >>>>>> It doesn't happen with any other OS's on this machine.
>
> >>>>>> Does anyone have a thought as to something I may have missed?
>
> >>>>> Are these other OSes on another physical hard drive?
>
> >>>> No, two of them on the same drive (W2k& Win7).
>
> >>> It seems like you looked at every conceivable thing. And since it
> >>> seems that your issue is not related to hardware, you might want to
> >>> perform a Clean Install at this point (since a Repair Install didn't
> >>> fix your random freezes).
>
> >> Hi Dave,
>
> >> Yeah, that is what I was trying not to do...
But in the time I've
> >> spent t-shooting I could have rebuilt it.
>
> > That was what I was driving at.
>
> >> Then again, I have the
> >> other OS's I can use, but XP is my main one.
>
> >> I'll create a dump file like Jose suggested and then research getting
> >> it analyzed. Have you done that before?
>
> > I have never done that, but I am curious to see what information it
> > reveals.
>
> Strange thing, yesterday the only things I did was:
> 1. MS Update
> 2. CmdHere Powertoy, ImageResizer Powertoy, TweakUi Powertoy
> 3. Disktrix UltimateDefrag
>
> and it was frozen this morning when I came in. Since the old install
> could go for a week at a time without freezing, I may have added
> programs too soon.
>
> Now this is to the point where I would have to install XP, wait a week
> to see if it freezes, then progress with a program each week until I
> find the problem. I'm wondering whether I should just retire XP on this
> workstation...
>
> Terry R.
> --
> Anti-spam measures are included in my email address.
> Delete NOSPAM from the email address after clicking Reply.
Nah.
If your system stops responding, hangs or freezes and you can't figure
out why, you can force a
BSOD which will create a crash dump file that you can analyze and see
what is running at the point
of the freeze and get some ideas that do not involve guesswork.
While it may seem odd to think about purposefully causing a Blue
Screen Of Death (BSOD), Microsoft
includes such a provision in Windows XP. The feature is built in to XP
specifically to diagnose
the problem when a system stops responding and there is no trail in
any of the Event Logs, etc.
about what might have happened.
Here's how to force your system to create a BSOD:
Before making registry changes, backup your registry with this popular
free and easy to use tool:
http://www.larshederer.homepage.t-online.de/erunt/
Launch the Registry Editor (Regedit.exe) and navigate to:
HKLM\System\CurrentControlSet\Services\i8042prt\Parameters
Click Edit, select New DWORD Value and name the new value
CrashOnCtrlScroll.
Double-click the CrashOnCtrlScroll DWORD Value, type 1 in the Value
Data text box, and click OK.
Close the Registry Editor and restart Windows XP.
When you want to cause a BSOD (when your system has stopped
responding), press and hold down the
[Ctrl] key on the RIGHT side of your keyboard, and then tap the
[ScrollLock] key twice. Now you
should see the BSOD and you will have a crash dump file to analyze.
If your system reboots instead of displaying the BSOD, you'll have to
disable the Automatically
Restart setting in the System Properties dialog box. To do so, follow
these steps:
Press [Windows]-Break.
Select the Advanced tab.
Click the Settings button in the Startup And Recovery panel.
Clear the Automatically Restart check box in the System Failure
panel.
Click OK twice.
You can read about the feature here:
http://msdn.microsoft.com/en-us/library/cc266483.aspx
There is no harm in leaving the feature enabled, but if you are
compelled to remove it:
Launch the Registry Editor (Regedit.exe) and navigate to:
HKLM\System\CurrentControlSet\Services\i8042prt\Parameters
Select the CrashOnCtrlScroll value, click the Edit menu, and select
the Delete command.
Close the Registry Editor and restart Windows XP.
> On 1/9/2010 1:44 PM On a whim, Daave pounded out on the keyboard
>
>
>
>
>
> > Terry R. wrote:
> >> On 1/9/2010 8:19 AM On a whim, Daave pounded out on the keyboard
>
> >>> Terry R. wrote:
> >>>> On 1/8/2010 7:27 AM On a whim, Daave pounded out on the keyboard
>
> >>>>> Terry R. wrote:
> >>>>>> XP on this workstation will randomly freeze. While I'm working on
> >>>>>> it, sitting idle. It will go for a week or more, then lock every
> >>>>>> day. I've slowly reduced Hardware acceleration. Updated drivers,
> >>>>>> changed
> >>>>>> out RAM, repair install. Even swapped out the power supply. Just
> >>>>>> when I think I've resolved it, it freezes...
>
> >>>>>> It doesn't happen with any other OS's on this machine.
>
> >>>>>> Does anyone have a thought as to something I may have missed?
>
> >>>>> Are these other OSes on another physical hard drive?
>
> >>>> No, two of them on the same drive (W2k& Win7).
>
> >>> It seems like you looked at every conceivable thing. And since it
> >>> seems that your issue is not related to hardware, you might want to
> >>> perform a Clean Install at this point (since a Repair Install didn't
> >>> fix your random freezes).
>
> >> Hi Dave,
>
> >> Yeah, that is what I was trying not to do...
But in the time I've> >> spent t-shooting I could have rebuilt it.
>
> > That was what I was driving at.
>
> >> Then again, I have the
> >> other OS's I can use, but XP is my main one.
>
> >> I'll create a dump file like Jose suggested and then research getting
> >> it analyzed. Have you done that before?
>
> > I have never done that, but I am curious to see what information it
> > reveals.
>
> Strange thing, yesterday the only things I did was:
> 1. MS Update
> 2. CmdHere Powertoy, ImageResizer Powertoy, TweakUi Powertoy
> 3. Disktrix UltimateDefrag
>
> and it was frozen this morning when I came in. Since the old install
> could go for a week at a time without freezing, I may have added
> programs too soon.
>
> Now this is to the point where I would have to install XP, wait a week
> to see if it freezes, then progress with a program each week until I
> find the problem. I'm wondering whether I should just retire XP on this
> workstation...
>
> Terry R.
> --
> Anti-spam measures are included in my email address.
> Delete NOSPAM from the email address after clicking Reply.
Nah.
If your system stops responding, hangs or freezes and you can't figure
out why, you can force a
BSOD which will create a crash dump file that you can analyze and see
what is running at the point
of the freeze and get some ideas that do not involve guesswork.
While it may seem odd to think about purposefully causing a Blue
Screen Of Death (BSOD), Microsoft
includes such a provision in Windows XP. The feature is built in to XP
specifically to diagnose
the problem when a system stops responding and there is no trail in
any of the Event Logs, etc.
about what might have happened.
Here's how to force your system to create a BSOD:
Before making registry changes, backup your registry with this popular
free and easy to use tool:
http://www.larshederer.homepage.t-online.de/erunt/
Launch the Registry Editor (Regedit.exe) and navigate to:
HKLM\System\CurrentControlSet\Services\i8042prt\Parameters
Click Edit, select New DWORD Value and name the new value
CrashOnCtrlScroll.
Double-click the CrashOnCtrlScroll DWORD Value, type 1 in the Value
Data text box, and click OK.
Close the Registry Editor and restart Windows XP.
When you want to cause a BSOD (when your system has stopped
responding), press and hold down the
[Ctrl] key on the RIGHT side of your keyboard, and then tap the
[ScrollLock] key twice. Now you
should see the BSOD and you will have a crash dump file to analyze.
If your system reboots instead of displaying the BSOD, you'll have to
disable the Automatically
Restart setting in the System Properties dialog box. To do so, follow
these steps:
Press [Windows]-Break.
Select the Advanced tab.
Click the Settings button in the Startup And Recovery panel.
Clear the Automatically Restart check box in the System Failure
panel.
Click OK twice.
You can read about the feature here:
http://msdn.microsoft.com/en-us/library/cc266483.aspx
There is no harm in leaving the feature enabled, but if you are
compelled to remove it:
Launch the Registry Editor (Regedit.exe) and navigate to:
HKLM\System\CurrentControlSet\Services\i8042prt\Parameters
Select the CrashOnCtrlScroll value, click the Edit menu, and select
the Delete command.
Close the Registry Editor and restart Windows XP.