Tom's Hardware > Forum > Windows XP > Windows XP General Discussion > Installed XP, now frequent reboots

Installed XP, now frequent reboots

Forum Windows XP : Windows XP General Discussion - Installed XP, now frequent reboots

Tom's Hardware: Over 1.4 million members in 6 different countries available to answer all your high-tech questions. Sign up now! Its free!
Word :    Username :           
 

I have a Asus P4S333/PA/WOL board with a Intle 1.5 GHz BX80531NK150G processor. I had been running Win98 with little problems. Got some kind of worm/virus so I decided to just start over with XP. I loaded XP, but now I get frequent reboots (system just shuts down and restarts with no warning).

I thought maybe it was my XP, so I loaded 2000 and got the same results. I put 98 back on and it was stable. Any idea what would cause the system to reboot with XP or 2000 but not 98?

Thanks, Jay

Sponsored Links
Register or log in to remove.

Did you do a clean format then install?

<b>1.4 Ghz AMD T-Bird underclocked to 1 Ghz...just to be safe!</b>

Reply to BunnyStroker

Yes. I used the XP disk to format the entire disk, partitioned it and then loaded XP.

Thanks for helping!

Reply to husker92
- 0 +

Have you tried safe mode? if you can get into safe mode look in the event logs and look for errors. Repost with more info. when you get a chance.

:cool: <font color=blue> I know nothing that is why i am here at THG!</font color=blue>

Reply to juice

it could possibly be a power issue, no?

Reply to Scarred_Angel

Frankly, it sounds like the usual m.o. for the Sasser worm. I know someone who timed it- it took less than 30 seconds after hooking up to the Internet before they got hit by the worm. So, if you didn't have an up to date firewall and anti-virus program running before that point, then you're screwed and you'll have to start all over.

Yo can try one of the removal tools, but why chance it on a new install?



Quote :

<font color=green>****</font color=green> Never Assume <font color=red>ANYTHING</font color=red> <font color=green>****</font color=green>


Reply to peartree

I ran a check and no sasser. I did notice that it usually re-boots when:
1) I just intalled something and it required a reboot. When it gets ready to load XP, it will re-boot again.
2) I am trying to install something (like office).

Also, when it does one of these phantom re-boots, the clock gets reset to around 7:30. Very weird.

Reply to husker92

Ah! Well, I don't think you mentioned THAT first time around! Now I'm thinking that the trouble is hardware. I start to suspect the motherboard! That's definitely not normal. Have you checked the event logs?


<font color=green>****</font color=green> Never Assume <font color=red>ANYTHING</font color=red> <font color=green>****</font color=green>

Reply to peartree

Sorry about that. I didn't realize the clock was resetting until last night.

Stupid question, but how do I check the event log?

Reply to husker92

Either use a util- http://www.windowsnetworking.com/j_helmig/wxpevent.htm

Or, see these instructions- http://uwadmnweb.uwyo.edu/ASKIT/ho [...] ventvw.htm


<font color=green>****</font color=green> Never Assume <font color=red>ANYTHING</font color=red> <font color=green>****</font color=green>

Reply to peartree

This is what the event log states:

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000008e (0xc0000005, 0xf82af78e, 0xf87940f0, 0x00000000). A dump was saved in: C:\WINDOWS\Minidump\Mini082604-01.dmp.

I installed 512 MB of new memory and it seemed to help a little, but then it rebooted again.

Any ideas? I am ready to just reload 98 and call it a day.

Reply to husker92

I just noticed that I get a W32Time warning a few hours before each re-boot:

The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized.

The clock is 2 hours off after the re-boot.

Reply to husker92

See the entry in the Microsoft Knowledgebase - http://support.microsoft.com/?kbid=310740 .

It seems to center on a driver error. Make sure all your drivers are up to date.




<font color=green>****</font color=green> Never Assume <font color=red>ANYTHING</font color=red> <font color=green>****</font color=green>

Reply to peartree
- 0 +

Stupid question, perhaps... but did you set your time zone correctly? That's the only way Windows will reset your clock.

<font color=red> If you design software that is fool-proof, only a fool will want to use it. </font color=red>

Reply to Zoron
- 0 +

Also, if you want to see the actual blue screen error come up and it not just reboot.. try this.

Open System Properties
- Advanced tab
- Startup and Recovery
- Uncheck "Automatically Restart"

This will at least halt the pc when you get the reboot and show ya onscreen... Just for SHITS and GIGGLES...


<font color=green>P4 2.4c @ 2.8
Asus P4P800
MSI R9800 Pro 128
1Gb DDR 2700 [Dual Channel]
80Gb WD </font color=green>

<font color=red>"Fo'Shizel Dats a Niceizel Rigizel = Nice Computer! " </font color=red>

Reply to Tyvy

I originally did not reset the time zone after installing XP. I changed it and it still reboots about every 23 hours.

I will get to the blue screen and let you know what is says.

Usually get the W32time error after 17 hours or so and then it reboots about 8 hours after that and starts over. Very strange.

Reply to husker92

Oh, yeah. FYI:

Did not have the problem with WIN 98.
Had the problem with WIN 2000.
Had the problem with XP, XPSP1 and now XPSP2.

I saw that SP2 had a fix for W32time and was hoping it would solve the problem, but no.

Thanks all for looking.

Reply to husker92

OK, now we are getting somewhere. The blue screen showed that it is not W32time that is causing the reboot, it is my audio driver.

I have an ASUS P4S3333 motherboard with on-board audio (C-Media CMI8738). I had already updated it to use the XP driver from the ASUS site, so now what?

I went ahead and downloaded the XP driver and installed it agian just to make sure, but if that doesn't work, what do I do?

Jay

Reply to husker92
- 0 +

Goto this site for more detail info.

<A HREF="http://aumha.org/win5/kbestop.htm" target="_new">http://aumha.org/win5/kbestop.htm</A>

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compability issues (which sometimes means a driver issue or a need for a BIOS upgrade).
“STOP 0x0000008e” Error Message During Windows XP Setup {KB 315335} Win XP
Games: “Stop” Error Message That References Nv4_disp.dll {KB 325730} Flight Simulator, other games (wth Nvidia-based video adapter)
Your Computer Stops Responding When You Use the Highlighter Feature & the Font Color Feature {KB 829578} Win XP
0x0000008F: PP0_INITIALIZATION_FAILED
0x00000090: PP1_INITIALIZATION_FAILED
0x00000092: UP_DRIVER_ON_MP_SYSTEM
0x00000093: INVALID_KERNEL_HANDLE
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
0x00000096: INVALID_WORK_QUEUE_ITEM
0x00000097: BOUND_IMAGE_UNSUPPORTED
0x00000098: END_OF_NT_EVALUATION_PERIOD
0x00000099: INVALID_REGION_OR_SEGMENT
0x0000009A: SYSTEM_LICENSE_VIOLATION
0x0000009B: UDFS_FILE_SYSTEM

:cool: <font color=blue> I know nothing that is why i am here at THG!</font color=blue>

Reply to juice
Tom's Hardware > Forum > Windows XP > Windows XP General Discussion > Installed XP, now frequent reboots
Go to:

There are 1304 identified and unidentified users. To see the list of identified users, Click here.

Please mind

You are about to answer a thread that has been inactive for more than 6 months.
If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.

Add a reply Cancel
Sponsored links
  • Ask the community now
  • Publish
Ad
They won a badge
Join us in greeting them