1.

Solve : xp pro continually restarts during boot?

Answer»

I have a computer running Windows XP Pro. When the boot process gets to the Windows SPLASH screen it can barely be seen and then the computer restarts. I have changed power supplies and RAM and no change. I put in the Windows XP Pro cd and did a repair install, as long as the cd is in the drive, Windows will boot fine. but when I TAKE the cd out, it starts resetting itself during boot. It is also the same way if I run chkdsk /r. I have also ran fixmbr and bootfix with no changes. Then when it let me into Windows using the above method, I turned off the RESTART on error. I reset the computer and got the following BSOD

file xtmqseqs.sys

Page_Fault_In_Nonpaged_area

0x00000050 (0xf6fdcfff, 0x00000001, 0xff285775, 0x00000000)

xtmqseqs.sys - address f7285775 base at f7212000, Datestamp 00000000

Can someone please help me get the computer back up and going? I'd suggest downloading and running a ram diagnostic utility (ie, memtest) as a first step in diagnosing the problelmHi,
    To resolve this problem, start your computer in Safe mode, remove the display adapter, rename the .inf files that are associated with the display adapter drivers, restart your computer in Normal mode, and then update your display adapter drivers. The following steps describe this procedure in more detail:
Start Windows in Safe mode. To do so:
Restart the computer, and then press F8 while the computer starts.
On the Windows Advanced Options Menu that appears, use the ARROW keys to select Safe Mode, and then press ENTER.
Use the ARROW keys to select the operating system to start, and then press ENTER to start Windows XP in Safe mode.
In the message that states that Windows is running in Safe mode, click Yes.
Click Start, click Run, type msinfo32 in the Open box, and then click OK.
Under System Summary, expand Components, and then click Display.
In the right pane, note the information that corresponds to the INF File item, for example, Nv4.inf, Oem0.inf, or Atim128.inf.
Quit the System Information utility.
Click Start, right-click My Computer, and then click Properties.
Click the Hardware tab, and then click Device Manager.
Expand Display adapters, right-click the display adapter, and then click Uninstall.
Click OK.
Click Start, click Run, type cmd, and then click OK.
In the COMMAND Prompt window, type the following commands, and then press ENTER after each line:
ren %systemroot%\inf\INF file name from Step 5.inf *inf.old
ren %systemroot%\inf\INF file name from Step 5.pnf *pnf.old
Close all open windows, and then restart the computer in the typical manner.
Log on to Windows by using an account that has administrative privileges, and then wait for Windows to detect new hardware.
When the Found New Hardware Wizard starts, click Cancel.

If you receive a stop error after you remove the updated display drivers, restart the computer and use the Last Known Good Configuration option. To do this, restart the computer, and then press the F8 key while the computer starts. On the Windows Advanced Options Menu that appears, use the ARROW keys to select Last Known Good Configuration, and then press ENTER.

If you receive a "System Has Recovered from a Serious Error" message when Windows starts, restart the computer again. This error message does not recur.
Ignore the above post for now.Not sure where these are copied/pasted from but some are innaccurate at best...

I agree with Allan.

Review ongoing.

For example the above instructions upon successive re-boots only eliminates the error message from recurring...it does not in fact correct the driver issues...which this most likely is... Quote from: Allan on April 12, 2010, 05:43:39 AM

I'd suggest downloading and running a ram diagnostic utility (ie, memtest) as a first step in diagnosing the problelm
OP SAID RAM and PSU have been changed.
It seems that "xtmqseqs.sys" is unknown.
Could this be malware of some sort? Quote from: Computer_Commando on May 12, 2010, 05:03:16 PM
OP said RAM and PSU have been changed.
It seems that "xtmqseqs.sys" is unknown.
Could this be malware of some sort?
I guess it's possible but if the system reboots before the gui loads I wouldn't think it's very likely. Quote from: Allan on May 13, 2010, 05:38:43 AM
I guess it's possible but if the system reboots before the gui loads I wouldn't think it's very likely.

Why? Badly written kernel-mode code causes blue-screens; viruses are notorious  for being constructed from bad code. Evidently whoever wrote this "xtmqseqs.sys" driver (which is almost certainly malware) was probably designed to compromise the system from kernel mode. Of course since a kernel-mode driver is usually set to startup with the other drivers (that is, before the GUI loads) it's not surprising it would crash then.

Okay


Discussion

No Comment Found