movement of mouse turns on pc

  • Thread starter Thread starter Jack B
  • Start date Start date
Nah, normal 2 button mouse with wheel that came with the pc.

Jack
Click to expand...

If it is still locking up sometimes, why don't you try to figure that
out with the method I told you about before?

It will take less time than figuring out which heat sensor is right
for you, realizing that TEMPIN2 of 81 is not your CPU, taking pictures
of your motherboard, reading about learning how to recap a mohterboard
(although that is all very interesting) - you would have been done by
now and we would perhaps know something for sure instead of wondering/
guessing day after day about what it might be.

Make the registry adjustment (1 minute)
Reboot (2 minutes)
Wait for it to lock up
Press Ctrl+Scroll Lock-Scroll Lock to force a memory dump - or two
dumps, or three dumps (30 seconds)
Email me the latest memory dumps from c:\windows\minidump for
analysis. (3 minutes)

I am always set up to analyze memory dumps.
 
Jose said:
snip
Make the registry adjustment (1 minute)
Reboot (2 minutes)
Wait for it to lock up
Press Ctrl+Scroll Lock-Scroll Lock to force a memory dump - or two
dumps, or three dumps (30 seconds)
Email me the latest memory dumps from c:\windows\minidump for
analysis. (3 minutes)

I am always set up to analyze memory dumps.
Click to expand...

Note that this procedure you described supposedly only works with a PS/2
keyboard in WinXP (USB keyboard only in Win7 and some Windows Server
versions).

Additionally, it may be of little or no use as, while the dump will show
all the drivers and modules loaded at the specific time, it will
generally give no indication of which is involved in the freeze, so you
gain no more insight into the freeze than if it were done when the
computer was *not* freezing. An analysis of the dump after being user
initiated like this will give a Bug Check 0x2E: MANUALLY_INITIATED_CRASH
and show what was loaded/running at the time. <shrug>

It might be helpful only if a new process starts that causes the freeze,
and you recognize the process in the dump as one that was not running
just prior to the freeze....but you have to know what processes where
running before the freeze to be useful.
 
Note that this procedure you described supposedly only works with a PS/2
keyboard in WinXP (USB keyboard only in Win7 and some Windows Server
versions).

Additionally, it may be of little or no use as, while the dump will show
all the drivers and modules loaded at the specific time, it will
generally give no indication of which is involved in the freeze, so you
gain no more insight into the freeze than if it were done when the
computer was *not* freezing.  An analysis of the dump after being user
initiated like this will give a Bug Check 0x2E: MANUALLY_INITIATED_CRASH
and show what was loaded/running at the time. <shrug>

It might be helpful only if a new process starts that causes the freeze,
and you recognize the process in the dump as one that was not running
just prior to the freeze....but you have to know what processes where
running before the freeze to be useful.
Click to expand...

Note that I have a XP Pro SP3 with USB mouse plugged in right now and
it works just fine.

Note that I can switch to a PS/2 mouse and it still works just fine.

Note that you should try it yourself and see how it works instead of
supposing.

Note that I know it will show a MANUALLY_INITIATED_CRASH as the cause
because that is indeed the cause:

MANUALLY_INITIATED_CRASH (e2) <- not 2E
The user manually initiated this crash dump.

Note that the cause of the crash will always be MANUALLY_INITIATED (in
this case) because that is indeed the cause.

Note that we are not looking for the cause of the crash and the system
is not crashing, it is hanging.

Note that we are not trying to determine the cause of the crash, we
are trying to get a memory dump when the system is hung.

Note that in this situation the other information from the dump is the
most useful information, not the cause of the crash.

Note that there is more useful information in a dump besides the
cause.
 
replied inline....
Jose said:
Note that I have a XP Pro SP3 with USB mouse plugged in right now and
it works just fine.

Note that I can switch to a PS/2 mouse and it still works just fine.

Note that you should try it yourself and see how it works instead of
supposing.
Click to expand...


Good to know....the MS info is (again) not quite accurate.
No time right now to try it, hence the "supposedly" based on what the MS
articles state.

Note that I know it will show a MANUALLY_INITIATED_CRASH as the cause
because that is indeed the cause:

<snip of repetitious re-stating>

Note that in this situation the other information from the dump is the
most useful information, not the cause of the crash.

Note that there is more useful information in a dump besides the
cause.
Click to expand...

I'm well aware of that, but as I stated in my post, all it will tel you
is what was loaded at the time, which in this case will most likely be
exactly the same things that were loaded when it was NOT freezing, so
exactly what other info do you expect to see? I'm asking seriously, not
to get a condescending or defensive reply.

Certainly, it is worth trying if the results are also compared with a
dump from when the system is NOT freezing, but you did not indicate that
the OP send a pre-freeze dump, so again, what do you expect it to tell
you?
 
Sorry I didn't get to look at your pictures sooner. You and Paul are
correct....you've got bad caps. Your symptoms fit the bill too. The
system may keep working a for a little while, but the freezes will get
more frequent, and you may eventually see crashes and possible data
loss.

Getting an identical replacement motherboard may still be possible, but
as Paul mentioned, it will likely have the same defective caps and will
eventually do the same thing.

I wonder what Dell's policy is (you did say it is a Dell, didn't you?)
on out of warranty systems that have these bad caps. Some OEM's were
replacing the motherboards or at least the caps even if the unit was out
of warranty, but I dunno if they still are. It might be worth a support
call or email to find out.
 
Yes, the indication is pretty certain that the MOBO has had it.

The pc is Systemax and support has been great. But the Socket A Gigabyte
MOBO (GA-7VTXE) may be impossible to find.


Jack



Sorry I didn't get to look at your pictures sooner. You and Paul are
correct....you've got bad caps. Your symptoms fit the bill too. The
system may keep working a for a little while, but the freezes will get
more frequent, and you may eventually see crashes and possible data
loss.

Getting an identical replacement motherboard may still be possible, but
as Paul mentioned, it will likely have the same defective caps and will
eventually do the same thing.

I wonder what Dell's policy is (you did say it is a Dell, didn't you?)
on out of warranty systems that have these bad caps. Some OEM's were
replacing the motherboards or at least the caps even if the unit was out
of warranty, but I dunno if they still are. It might be worth a support
call or email to find out.
 
Dunno where I got Dell from....probably from another thread altogether.
No, you're not likely to find that motherboard anywhere except on eBay.

It might still be worthwhile to contact Systemax, or Gigabyte, and see
if either one has a policy to replace the caps at little or no charge,
since it may be the result of a widespread materials defect.
 
Jose,

Thanks for all your insight/help. I'm a little worried about screwing
something up while in the middle of this project, especially since the issue
appears to be the capacitors on the MOBO which is basically no short term
fix if at all. The Registry makes me uneasy right now. Nonetheless, after
I get some breathing room, I would like to try your recommendations and take
you up on your offer if I could get hold you at that time.

Thanks again,
Jack

-----------------------------------------------



If it is still locking up sometimes, why don't you try to figure that
out with the method I told you about before?

It will take less time than figuring out which heat sensor is right
for you, realizing that TEMPIN2 of 81 is not your CPU, taking pictures
of your motherboard, reading about learning how to recap a mohterboard
(although that is all very interesting) - you would have been done by
now and we would perhaps know something for sure instead of wondering/
guessing day after day about what it might be.

Make the registry adjustment (1 minute)
Reboot (2 minutes)
Wait for it to lock up
Press Ctrl+Scroll Lock-Scroll Lock to force a memory dump - or two
dumps, or three dumps (30 seconds)
Email me the latest memory dumps from c:\windows\minidump for
analysis. (3 minutes)

I am always set up to analyze memory dumps.
 
Back
Top