Win XP Boot up issues

  1. #1
    Falling is offline Junior Member

    Win XP Boot up issues

    My main machine has decided to start having boot issues. This afternoon we left it running when we went out, and when we returned, the machine had logged off the user and went to sleep. We tried to log on again but the screen froze at the log in screen. After having to push the reset button to reboot it the system seemed to boot ok until the blue starting windows screen, where it froze again. Anyway after several attempts to boot, all freezing at the starting windows or user log on screen, I tried booting into safe mode, that worked and I ran checkdisk that showed a few errors that were repaired. I tried again and it allowed me to log on before freezing up again. I noticed that each time the computer froze up I would here several times what sounded like the hard drives spinning down and then spinning back up again. there was also a clicking sound like a relay tripping that accompanied the spin down and spin up. Same sort of sound you get when you shut down and as the system powers off. That click and hard drive spin down sound. Any ideas where to look? Any other info you would like to know?? My machine is P3 1Ghz, 512 meg ram, 80 gig HD and 60 gig slave, Windows XP SP2. Thanks for your help again

  2. #2
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    Go back to Safe Mode & try Last Good Configuration.

    If that doesnt help try safe again to a system restore by booting safe mode & choosing to restore.

    If that doesnt help go back into safe mode & check your
    event viewer: rt. click My Computer then click Manage then Event Viewer.
    open the system as well as the application tabs & look for X errors. click error line for details. post back the source & event id especially of errors that seem to coincide with a boot.

  3. #3
    Falling is offline Junior Member
    Interesting file, never knew that was there. Ok lets see now.

    Event Type: Warning
    Event Source: Disk
    Event Category: None
    Event ID: 51
    Date: 2/20/2005
    Time: 7:18:47 PM
    User: N/A
    Computer: FALLING
    Description:
    An error was detected on device \Device\Harddisk1\D during a paging operation.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 03 04 68 00 01 00 b6 00 ..h...¶.
    0008: 00 00 00 00 33 00 04 80 ....3..€
    0010: 2d 01 00 00 85 01 00 c0 -...…..À
    0018: 00 00 00 00 00 00 00 00 ........
    0020: 00 2e 01 00 00 00 00 00 ........
    0028: 67 1d 00 00 00 00 00 00 g.......
    0030: ff ff ff ff 01 00 00 00 ÿÿÿÿ....
    0038: 40 00 00 82 02 00 01 00 @..‚....
    0040: ff 20 0a 12 4c 03 20 40 ÿ ..L. @
    0048: 00 00 00 00 0a 00 00 00 ........
    0050: 00 00 00 00 a8 ff f7 82 ....¨ÿ÷‚
    0058: 00 00 00 00 a8 c1 fa 82 ....¨Áú‚
    0060: 00 00 00 00 97 00 00 00 ....—...
    0068: 28 00 00 00 00 97 00 00 (....—..
    0070: 08 00 00 00 00 00 00 00 ........
    0078: f0 00 0b 00 00 00 00 0b ð.......
    0080: 00 00 00 00 00 00 00 00 ........
    0088: 00 00 00 00 00 00 00 00 ........


    Lots of disk source event id 7, and DCOM source Id #10005, but those were all cleared up after the chkdsk. I had done the last good and system restore before the chkdsk was done.
    In the application list i still get a couple errors

    Event Type: Warning
    Event Source: EvntAgnt
    Event Category: None
    Event ID: 1015
    Date: 2/20/2005
    Time: 9:16:51 PM
    User: N/A
    Computer: FALLING
    Description:
    TraceLevel parameter not located in registry; Default trace level used is 32.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    Event Type: Warning
    Event Source: EvntAgnt
    Event Category: None
    Event ID: 1003
    Date: 2/20/2005
    Time: 9:16:51 PM
    User: N/A
    Computer: FALLING
    Description:
    TraceFileName parameter not located in registry; Default trace file used is .

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    these show up twice after the diskcheck, but it seems to finally be stable again

  4. #4
    jephree is offline ¨*·.¸ «.·°·..·°·.» ¸.·*¨
    I will just list these finds. Let us know if you recognise anything.

    To fix this problem I disabled the “Write cache” feature on my disk. To do this go to Device Manager -> Disk Drives, right click on your disk and choose Properties. Here you can disable this feature.

    http://www.eventid.net/display.asp?e...e=Disk&phase=1

    I removed the service, WMI SNMP Provider, from the managment and monitoring tools. Then added the service back and all is well.

    http://www.eventid.net/display.asp?e...ntAgnt&phase=1

    Event mostly appears in combination with event ID 1015 of EvntAgnt and only on systems with installed SNMP service. I solved the problem by adding under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNMP_EVENTS \EventLog\Parameters" a value "TraceFileName", REG_SZ, containing a file name, for example "test.log". After restart, this file will be created under "%systemroot%\system32" and further SNMP information is logged into it.

    http://www.eventid.net/display.asp?e...ntAgnt&phase=1

    This is the source site for these notes:

    http://www.eventid.net/

  5. #5
    Falling is offline Junior Member
    Basically nothing serious then for the last 2 warnings anyway. I will see what i can do to eliminate them. Thanks for your help, I think this one is finished

  6. #6
    Falling is offline Junior Member
    Well it started to act up again this morning, same problems as last night. only other problem came after I did another chkdsk. When the computer shut down to reboot after the scan, the hard drives spun down and would not spin up again. A couple tries to reboot with no sucess, the hard drives were not located. Anyway to make a long story short, I went to my convenient Computer store and purchased a new 300 watt power supply to seeif that fixed the problem. Hooked up the jungle of wires and tied the leftover extra leads together to get them out of the way and it booted up fine. Looks like a flakey power supply was my issue. Hopefully this will be the last of it.

+ Reply to Thread