(Solved) Windows random reboot - HJT / Work in progress

Hello. I've been getting strange start ups from time to time. It's not a consistent problem, but today it happened a few times in a row. Here is the problem: Windows xp will start up and look fine for a moment or two. Then suddenly the skin will change from the default setting to "classic mode" ( the taskbar and everything on it turn gray, like from windows 2000 and earlier ). After a few more moments, the computer automatically restarts. I've noticed that when looking for attached hard drives ( sata system, but all hdds are connected pata ) upon this restart, it takes a bit longer than normal. I've included my Hijackthis log below for review. If there is also anything that can be removed as well, and started at a later time when I need it, please advise me on those as well. I like having a very minimalist start up ^^; - I also use Firefox rather than IE. ( just noting this cause I see things for IE in here. ) This is also a Windows xp 64-bit OS, which if I remember correctly has a Windows Server 2003 kernal, might be why it thinks I have that system below.

I've tried a different forum to solve this problem, and they refereed me here. Here is a link to that thread and what has been done so far: spyware beware post - I have removed the two files he asked me to in his last post.

the computer automatically restarts

Windows auto-restarts when there is a fault or conflict in hardware, or a faulty driver of a hardware component.
Windows can often report what, when, where the fault is.

turned-off "automatically restart" ?

start—right-click "my computer". When the "system Properties" window opens, click the -advanced- tab, then in the "Startup and Recovery" section, click the -settings- button. When the "startup and Recovery" window opens,
UN-check the "automatically restart" box, then click [OK], [OK].

Reboot and “write down with paper and pencil the exact “full” error message you may be receiving if you experience a Blue Screen Error or Stop Message

Post the Error Message information into your next reply so that we can identify what next steps may be necessary

the above may help us identify what hardware or driver is causing the problem.
If not we'll have an additional look into Event Viewer, but for now, please report back with "all" of the information contained in any BlueScreen shutdown. (You'll have to use pencil and paper and then type it back in to enter in your next post.) Sometimes you can take a ScreenShot, but that is not always clear enough to read in a Forum setting.
_________________

You do have a variety of items starting from Start Menu that are optional.
You inquired about this in your other thread with Catbyte.

Let's have a look.

Please consider running this simple utility that will help you get control of programs and processes that you wish to have running active, or not.

CodeStuff-Starters
http://www.snapfiles.com/get/Starter.html

Download and install, agreeing to the licensing terms and allow to install with all of the default settings as preselected in the installation wizard.

When you finally allow CodeStuff-Starters to run
It will preselect StartUps Tab)
• Click on File
• Select - save as .html (name the report file - Startups May23.html)


In your next reply, post the file as an attached file (use browse and upload buttons – at the bottom-right corner of your topic posting window where you are typing your next reply)

Please do not make any changes with Code-Stuff Starters, until after you post the requested information above and receive recommendations from a helper here.

Best Regards

As for the windows restarting issue, like I said it's not something that I can reproduce. I have taken the steps you advised and can remember to write down any error message that does appear. Until the fault appears though, I can't do anything. Attached is a copy of the starter document, as requested ^^;

Hi Cinaeth. Instead of waiting for the restart to occur, you can also grab the minidumps that were created the last times the problem occured. If you open My Computer and navigate to C:\Windows\minidump, you will find a series of minidump files. Please look for the 4 most recent minidump files (sorted by date) and select them all by holding the CTRL key and clicking each file. Once all 4 are selected, right-click one of them and click send to -> compressed zip folder. Now, a new .zip file will have been created. Upload and attach that file to the forum. This will provide the information Doug is requesting so that he can get an idea of what is causing the restart.

Just went to look there and found nothing. Yes my "show hidden files and folders" is checked so anything hidden would have been seen. Is there a different area for this on Windows Xp 64-bit..?

Ugh… Guess I should've noticed the 64-bit part previously. There isn't a different spot where these files are in the 64-bit version of XP I don't think. To be blunt, you are having problems because you have 64-bit XP. If you aren't yet, specifically because this is the 64-bit version of XP, you will. I've never seen a copy of 64-bit XP run stable, it just doesn't happen. Thats why its use is almost non-existent. The same holds true for 64-bit versions of Vista. It too is still notoriously unstable. I've literally seen these operating systems start blue screening almost fresh out of the box on brand new computers. It isn't all the fault of the operating system, much of it lies with the hardware manufacturers and their drivers and software. And also with the software creators. Sorry.

This is a home built computer, so I put in all the parts myself. I tried to make sure everything would be 64-bit compatible. I got 64-bit because I wanted to be able to have more then 3gb of ram at some point and because I have dual core. ( I heard dual core is better with 64-bit ). I do suspect this is originating from a HDD fault. I can hear something vibrating on startup, I can't figure out what that is, but the only moving part besides the fans should be the HDD. This low hum usually goes away by the time the Os is up. I also suspect this because of the slower HDD detection when the error does occur. I've already checked my wires to make sure their tight, so I'm just not sure if it's internal or something entirely different. I guess I won't find out till it has another error again. If it matters, I'm running two IDE HDDs, one is 160gb ( OS installed ) and 250gb

Hi Cinaeth.. The information found here: http://forums.whatthetech.com/Welcome_new_users_t104737.html

May help you to provide us better information. There is also a section on what to do if your problem might be hardware related that links to articles about using chkdsk and testing the drive for bad sectors. At least your system drive (usually C:) needs to be tested for bad sectors if you suspect hard drive failure.

CD-Roms also have moving parts. If there is a disc in the drive, it will spin up when the computer is first turned on and then slow down and stop probably right around the time your operating system gets booted.

And the fault happens! Don't think I've been glad to actually see a BSOD. Stop: c000021a {fatal system error} The windows logon process terminated unexpectedly with a status of 0xc0000005 { 0x00000000 ) ( 0x00000000 ). The system has shutdown. Looking this up quickly, it makes sense now as far as my symptoms go. Now I just need to figure out how to fix this.

Alright, So I have a minidump now, and I also know now it's dealing with winlogon.exe - I had a normal error come up before BSOD that said Winlogon.exe had failed, creating a log file. If either of you could tell me where this log file ends up, I'll get it for you. Until then, here is the zip containing the dump file.

It says it is your Razer Lachesis USB optical mouse driver. Again, you are running a 64-bit version of Windows XP (Although your memory dump says Server 2003, strange.) You will never have a stable 64-bit version of Windows XP. If anybody could ever prove to me differently I might say different. But, it isn't going to happen. Manufacturers did not support 64-bit XP properly. Software vendors did not support 64-bit XP properly. Microsoft did not support 64-bit XP properly. It is a dead operating system. You will endlessly be chasing driver and software updates that are compatible with your O/S, many of which will NEVER support your operating system. I wish I could tell you something differently. But that is just it. The answer to your problem is that you have 64-bit XP. My suggestion is that you begin deciding on an upgrade to a newer and more stable operating system. Windows 7 is coming out in October. The 64-bit versions of the newer operating systems, and the newer hardware created recently is now supporting things better although it has still been ridiculously un-reliable. My suggestion is that if you don't have more than 4 gigs of RAM there is absolutely no need, nor benefit, of running 64-bit windows. So, stick with 32-bit even if you upgrade.

Well, I'm stuck with what I got. I went to Raser's site and downloaded the most up to date driver supported by windows xp 64 bit and upgraded. So hopefully that'll fix the problem. If not, then yea, I guess I have to wait till Windows 7 comes out.