jsinaiko
Premium
join:2001-04-25
Chicago, IL
 ·AT&T Midwest
| [XP Pro] Spontanious Reboot Issue
So everything is going fine. Then the thing gets hit with Aurora. YIKES!
So I obliterate it with MS Anti-Spyware, Spybot S & D, and AdAware. Plus the manual registry fix.
Since then the box has been re-booting all over the place. Never when it is just sitting there - always when I click on something. Often Outlook is open. Or when an anti-spyware utility is running. Or when I click on some icon to open something. Several times per day. It was steady as a rock before Aurora, now it's ready for the loony bin and so am I.
No proof, but I would think this is a registry issue.
I'd love to NOT have to do a reformat/reinstall, but it is starting to look that way.
Any ideas or good registry checkers/fixers? I'd love to make the thing stable again without taking a day out of my life to re-do everything.
I suppose there is a slight chance this is a hardware problem, but it's a pretty new machine (Athlon XP 3200) and has always been very steady. Plus the Aurora plague.
Any ideas out there? Thanks in advance!
--
Illigitimati non carborundum |
|
MSeng
Premium,Ex-Mod 2001-08
join:2000-07-13
Ork
clubs:
 ·AT&T U-Verse
| Anything showing up in the Event Viewer?
»Microsoft Application Tips and Tweaks »How do I access event viewer and find what the system error codes mean?
--
Life is like an Adventure... BUT COOL GRAPHICS |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
| NO! Well, that not is 100% the case. Once I had a error around it trying to find the time server. Once it was around the CD burning software. Once it was something to do with my Symantec AV Corporate. But most of the time it just has info about when the various services start up AFTER the shutdown.
So no obvious errors in any of the three Event viewer categories with the exceptions above. Very annoying and quite confusing.
I suppose it might be a hardware thing but I don't see why it would happen all of a sudden. It seems to me the main thing is the installation and uninstalling of Aurora. |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL | reply to MSeng
I was very much hoping that event viewer would give a hint, but alas, nada.
I'd be happy to post a screenshot or the error numbers. |
|
auggy
Premium,Mod
join:2001-12-24
Brockville, ON | Do you have a C:\Windows\minidump folder, and if so, are there any minidump files in that folder? |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
1 edit | I'm sorry (or pleased - I'm not sure which) to say I don't have a c:\Windows\minidump folder.
Thanks anyhow.
It seems to be crashing less today - only two or three times. |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
| reply to auggy
If I'm not mistaken, XP re-boots after major errors that would have resulted in the BSD back in the 98 days. Isn't there a setting that would give me the BSD instead of just re-booting? Think that would help diagnose?
I've blocked out eight hours tomorrow to back everything up and reformat/reinstall. I'd be SOOO grateful if I could avoid doing that.
--
Illigitimati non carborundum |
|
jimmie
join:2001-12-01
Sault Ste Marie, ON | system properties | advanced | startup and recovery/settings
uncheck automatically restart for system failure
That will give you the bsod though event viewer should give what you need also. |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL | Thanks -
Yeah, I'm baffled by the lack of anything obvious in Event Viewer. Makes me worry that it's a bad mobo or something.
I'll turn the setting off and see what that does. |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
1 edit | reply to MSeng
MSeng and Auggy and everyone else -
Many thanks for your help.
I am now in the process of the dreaded reinstall. So far so good. Pretty seamless although it takes a day out of my life.
It has not rebooted yet, so that's an indication that this was a Windows/Registry problem, probably related to the removal of Aurora (don't ask how it got on the box in the first place - too stupid to relate  ).
I guess we can just chalk it up to one of those mysterious problems that pop up from time to time.
I appreciate the time you spent on this,
Jesse
--
Illigitimati non carborundum |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
| reply to MSeng
Ok guys -
Did the reinstall. Everything was peachy. Then I installed Office XP and the @$%&?! started again.
I'm still not 100% sure that it isn't a hardware - mobo or something - issue, but I did go to Dr. Watson and pull some of the errors. Most of the involve deadly OLE files.
I'll be happy to paste as many as you may want if you thin it'll help diagnose.
Here's one:
application exception occurred:
App: C:\WINDOWS\system32\mmc.exe (pid=240)
When: 6/10/2005 @ 13:48:19.265
Exception number: c0000005 (access violation)
*----> System Information Task List Module List State Dump for Thread Id 0x1ac 74c835fd 0000 add [eax],al ds:0023:74c85d9c=4c
74c835ff 50 push eax
74c83600 ff155412c874 call dword ptr [OLEACC+0x1254 (74c81254)]
74c83606 668906 mov [esi],ax
74c83609 83c704 add edi,0x4
74c8360c 46 inc esi
74c8360d 46 inc esi
74c8360e 81ff80000000 cmp edi,0x80
74c83614 72db jb OLEACC!AccessibleObjectFromWindow+0x15fe (74c835f1)
74c83616 6a18 push 0x18
74c83618 59 pop ecx
*----> Stack Back Trace Raw Stack Dump ----*
000000000007d630 9c 5d c8 74 98 47 0a 00 - 01 00 00 00 20 3a 09 00 .].t.G...... :..
000000000007d640 18 00 16 02 50 d6 07 00 - 00 00 00 00 d0 24 19 00 ....P........$..
000000000007d650 4f 00 4c 00 45 00 41 00 - 55 00 54 00 33 00 32 00 O.L.E.A.U.T.3.2.
000000000007d660 2e 00 44 00 4c 00 4c 00 - 00 00 97 7c 4f 5b 91 7c ..D.L.L....|O[.|
000000000007d670 40 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 @...............
000000000007d680 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
000000000007d690 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
000000000007d6a0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
000000000007d6b0 00 00 00 00 28 d7 07 00 - 00 00 00 00 00 00 00 00 ....(...........
000000000007d6c0 a8 59 c8 74 02 00 00 00 - d4 69 60 77 3c d7 07 00 .Y.t.....i`w...
000000000007d6d0 00 00 00 00 18 00 1a 00 - 8c 59 c8 74 50 ee 00 00 .........Y.tP...
000000000007d6e0 00 00 00 00 07 57 91 7c - 00 00 02 00 08 d7 07 00 .....W.|........
000000000007d6f0 08 d7 07 00 08 d7 07 00 - 02 00 00 00 02 00 00 00 ................
000000000007d700 98 47 0a 00 3c e6 80 7c - 00 00 00 00 50 ee 00 00 .G....|....P...
000000000007d710 78 d8 07 00 b0 d7 07 00 - 78 d8 07 00 00 5a 91 7c x.......x....Z.|
000000000007d720 64 d7 07 00 04 d9 07 00 - 01 00 00 00 65 5a 91 7c d...........eZ.|
000000000007d730 00 00 08 02 74 c1 97 7c - 00 00 08 02 00 00 00 00 ....t..|........
000000000007d740 58 db 07 00 fc d8 07 00 - 00 00 00 00 04 d9 07 00 X...............
000000000007d750 00 00 00 00 f4 d8 07 00 - 00 00 80 00 d4 d7 07 00 ................
000000000007d760 00 00 00 00 00 00 00 00 - 00 00 00 00 18 00 1a 00 ................ |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL
·AT&T Midwest
| reply to jsinaiko
Heres another:
Application exception occurred:
App: C:\WINDOWS\system32\mmc.exe (pid=2676)
When: 6/10/2005 @ 12:44:52.843
Exception number: c0000005 (access violation)
*----> System Information Task List Module List State Dump for Thread Id 0xa78 74c835fd 0000 add [eax],al ds:0023:74c85d9c=4c
74c835ff 50 push eax
74c83600 ff155412c874 call dword ptr [OLEACC+0x1254 (74c81254)]
74c83606 668906 mov [esi],ax
74c83609 83c704 add edi,0x4
74c8360c 46 inc esi
74c8360d 46 inc esi
74c8360e 81ff80000000 cmp edi,0x80
74c83614 72db jb OLEACC!AccessibleObjectFromWindow+0x15fe (74c835f1)
74c83616 6a18 push 0x18
74c83618 59 pop ecx
*----> Stack Back Trace Raw Stack Dump ----*
000000000007d630 9c 5d c8 74 50 44 0a 00 - 01 00 00 00 20 3a 09 00 .].tPD...... :..
000000000007d640 18 00 16 02 50 d6 07 00 - 00 00 00 00 d0 24 19 00 ....P........$..
000000000007d650 4f 00 4c 00 45 00 41 00 - 55 00 54 00 33 00 32 00 O.L.E.A.U.T.3.2.
000000000007d660 2e 00 44 00 4c 00 4c 00 - 00 00 97 7c 4f 5b 91 7c ..D.L.L....|O[.|
000000000007d670 40 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 @...............
000000000007d680 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
000000000007d690 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
000000000007d6a0 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 ................
000000000007d6b0 00 00 00 00 28 d7 07 00 - 00 00 00 00 00 00 00 00 ....(...........
000000000007d6c0 a8 59 c8 74 02 00 00 00 - d4 69 60 77 3c d7 07 00 .Y.t.....i`w...
000000000007d6d0 00 00 00 00 18 00 1a 00 - 8c 59 c8 74 18 30 00 00 .........Y.t.0..
000000000007d6e0 00 00 00 00 07 57 91 7c - 00 00 02 00 08 d7 07 00 .....W.|........
000000000007d6f0 08 d7 07 00 08 d7 07 00 - 02 00 00 00 02 00 00 00 ................
000000000007d700 50 44 0a 00 3c e6 80 7c - 00 00 00 00 18 30 00 00 PD....|.....0..
000000000007d710 78 d8 07 00 b0 d7 07 00 - 78 d8 07 00 00 5a 91 7c x.......x....Z.|
000000000007d720 64 d7 07 00 04 d9 07 00 - 01 00 00 00 65 5a 91 7c d...........eZ.|
000000000007d730 00 00 08 02 74 c1 97 7c - 00 00 08 02 00 00 00 00 ....t..|........
000000000007d740 58 db 07 00 fc d8 07 00 - 00 00 00 00 04 d9 07 00 X...............
000000000007d750 00 00 00 00 f4 d8 07 00 - 00 00 80 00 d4 d7 07 00 ................
000000000007d760 00 00 00 00 00 00 00 00 - 00 00 00 00 18 00 1a 00 ................ |
|
mooch
No Booing Allowed
join:2001-11-11
Johnstown, OH
| I'm sure there's a bazillion reasons for the reboots...my issue related to the video driver. I installed a new one and that fixed it. A buddy's reboot problem related to a weak power supply. Good luck with it.
--
DRS grey dish,freq 1210, G3C, XP pro, Athlon XP2400, |
|
jsinaiko
Premium
join:2001-04-25
Chicago, IL | Thanks -
Yeah, I've seen thepower supply issue, and the CPU fan reason as well.
You are correct. Hopefully itisn't the mobo. |
|
