Windows XP Pro continually resets itself

[Andy K]

I have Windows XP Pro and for the past few week for no reason at all my PC
started to reset itself every few minutes, followed by a 'windows has
recovered from a serious error' message when Windows loaded up again,
stating that it was a problem with a driver but was unable to determine
which driver specifically.

I initially thought that i may have been the Blaster Worm virus and so went
about scanning my pc for the virus, (which took ages due to my pc
continually resetting itself every few minutes). However, when i finally
managed to fully scan my drives the virus didnt show and i installed the
offical patch from Microsoft so that my pc wasnt vulnerable in the future.

I then thought that it may be due to a fault with my MSI K7T266 Pro
mainbaord. So i replaced the mainboard and processor with a Asus A7N8X
mainboard and Athlon XP 2600+ processor. However, to my horror after
installing Windows the problem of the pc resetting itself spontaniously
reocurred.

The problem only seems to occur when i am using the internet. Furthermore,
i had only installed the latest usb adsl modem drivers so that i could get
on the net and update windows and so, unless it was a problem with windows
drivers themselves, it could not have been any additional driver that i had
installed, like windows was making out.

I had 1GB of Crucial PC2100 DDR RAM installed in my pc (consisting of
1x512MB module and 2x256MB modules). I removed one of the 256MB modules but
the problem still occurred. I then removed the second 256MB module and the
problem has not come back so far (touch wood!).

Does this mean that there is a problem with both of the 256MB memory
modules, or could it be some sort of problem with Windows when handling it?
As it seems unlikely that both of the modules have become faulty at the same
time. Finally, if it turns out that the problem reoccurs again, what other
possible causes are there?

Any assistance/comments would be much appreciated.

My previous PC spec is as follows:

AMD Athlon Thunderbird 1.333GHz CPU
MSI K7T266 Pro mainboard (with the latest BIOS)
Western Digial 20Gb 5400rpm HDD
1GB Crucial PC2100 DDR RAM (1x512MB and 2x256MB)
Gainward GeForce3 GS
Sound Blaster Audigy sound card
Pioneer DVR-105 DVD-RW
Windows XP Pro (SP1 and all available updates)

Current specification

AMD Athlon XP 2600+ CPU
Asus A7N8X mainboard
Western Digial 120 Caviar SE 120Gb 7200rpm 8mb cache HDD
512MB Crucial PC2100 DDR RAM (1x512MB with 2x256MB removed)
Gainward GeForce3 GS
Sound Blaster Audigy sound card
Pioneer DVR-105 DVD-RW
Windows XP Pro (SP1 and all available updates)

 

[Gordon]

-----Original Message-----
I have Windows XP Pro and for the past few week for no reason at all my PC
started to reset itself every few minutes, followed by a 'windows has
recovered from a serious error' message when Windows loaded up again,
stating that it was a problem with a driver but was unable to determine
which driver specifically.

I initially thought that i may have been the Blaster Worm virus and so went
about scanning my pc for the virus, (which took ages due to my pc
continually resetting itself every few minutes). However, when i finally
managed to fully scan my drives the virus didnt show and i installed the
offical patch from Microsoft so that my pc wasnt vulnerable in the future.

I then thought that it may be due to a fault with my MSI K7T266 Pro
mainbaord. So i replaced the mainboard and processor with a Asus A7N8X
mainboard and Athlon XP 2600+ processor. However, to my horror after
installing Windows the problem of the pc resetting itself spontaniously
reocurred.

The problem only seems to occur when i am using the internet. Furthermore,
i had only installed the latest usb adsl modem drivers so that i could get
on the net and update windows and so, unless it was a problem with windows
drivers themselves, it could not have been any additional driver that i had
installed, like windows was making out.

I had 1GB of Crucial PC2100 DDR RAM installed in my pc (consisting of
1x512MB module and 2x256MB modules). I removed one of the 256MB modules but
the problem still occurred. I then removed the second 256MB module and the
problem has not come back so far (touch wood!).

Does this mean that there is a problem with both of the 256MB memory
modules, or could it be some sort of problem with Windows when handling it?
As it seems unlikely that both of the modules have become faulty at the same
time. Finally, if it turns out that the problem reoccurs again, what other
possible causes are there?

Any assistance/comments would be much appreciated.

My previous PC spec is as follows:

AMD Athlon Thunderbird 1.333GHz CPU
MSI K7T266 Pro mainboard (with the latest BIOS)
Western Digial 20Gb 5400rpm HDD
1GB Crucial PC2100 DDR RAM (1x512MB and 2x256MB)
Gainward GeForce3 GS
Sound Blaster Audigy sound card
Pioneer DVR-105 DVD-RW
Windows XP Pro (SP1 and all available updates)

Current specification

AMD Athlon XP 2600+ CPU
Asus A7N8X mainboard
Western Digial 120 Caviar SE 120Gb 7200rpm 8mb cache HDD
512MB Crucial PC2100 DDR RAM (1x512MB with 2x256MB removed)
Gainward GeForce3 GS
Sound Blaster Audigy sound card
Pioneer DVR-105 DVD-RW
Windows XP Pro (SP1 and all available updates)



.
Sorry me aain. Jusr re-read andys message, and I have XP

home installed NOT Pro. does this make a difference.
Again Thanks and my apologies again!

 

[Ron]

Andy,

Is the Asus A7N8X board the dual channel memory board? I don't remember the
number off the top of my head but if it is you have to have a matched set of
memory sticks for it to operate correctly. One stick is OK, if the second
isn't matched, look out. I fought with this board earlier this year and
finally gave up and got the A7V8X (conventional memory) board. If the MSI
board is a dual channel, maybe it's the same problem.

Ron

 

[T.C.]

For the original problem I would have suggested: If it's only been for the
past week, that narrows it down. Have you installed any new drivers,
software, or updates? If so uninstall them, reboot, and see if that fixes
the problem. If it doesn't, then boot into Safe Mode (press the F8 key)
just before the Safe Mode desktop fully loads, a dialog box asks if you want
to continue booting into Safe Mode or go directly to System Restore. Opt to
go directly to System Restore. Once in System Restore, opt to Restore My
Computer to an Earlier Time. In the left pane you'll see a calendar. The
bold numbers are the days that have System Restore Points. Select a date
that's in bold print, just prior to when the problem started. Then in the
right pane, select the Restore Point for that date to highlight it. Then
click the NEXT button at the bottom of the window, and follow the rest of
the System Restore wizard. Any data files which you created, or email etc.,
will not be effected, only Windows System files and settings will be
restored to what they were on the date of the Restore Point that you
selected. Hopefully that will fix the problem.

BUT, since you changed the motherboard after the ORIGINAL problem, the above
won't help. Do a "Repair Install," which will retain your data files and
software, and should pick up and configure for the new motherboard, and
repair the original problem too. To do a repair install go to:

http://www.webtree.ca/windowsxp/repair_xp.htm

When the page opens, scroll down and click on: How To Run A Repair
Install. There is a step by step walk through including images. Your
software, settings, data files, desktop, etc. are retained.

Windows XP Repair Installs have save me a few times...

If the above doesn't fix the problem, check to see if some of your RAM is
defective, or if your system is overheating.

 

[GSV Three Minds in a Can]

Bitstring <[email protected]>, from the wonderful

I had 1GB of Crucial PC2100 DDR RAM installed in my pc (consisting of
1x512MB module and 2x256MB modules). I removed one of the 256MB modules but
the problem still occurred. I then removed the second 256MB module and the
problem has not come back so far (touch wood!).

Does this mean that there is a problem with both of the 256MB memory
modules, or could it be some sort of problem with Windows when handling it?
As it seems unlikely that both of the modules have become faulty at the same
time. Finally, if it turns out that the problem reoccurs again, what other
possible causes are there?

Sounds like a problem with the nForce2 dual channel memory handling. Or
maybe (one of?) the 256MB modules had a problem (I assume you really
were running them at 133Mhz*2, and not trying to over-clock them).

Try putting it all back in and running www.memtest86.com - I bet you'll
see errors. Or put in the 2*256 and remove the 512, and try again. If
you do see memory problems only when all modules are in, but all of them
pass on their own, then it's time to get some assistance from the
hardware newsgroups (eg .. it
definitely isn't an XP problem.